As an administrator of M365 you may be required that Only Specific Users Can Reserve a Resource in Exchange. Normally a room or resource would be for the entire organization to reserve and the only things stopping them from booking it would be its availability. Other things like room capacity, equipment resources in the room, working hours, etc., can also be a factor.

However, sometimes the room might be an office used by one person but they need the ability for a group of users (maybe members in the department) to be able to book it like a resource. I will show you how to enable this through PowerShell.

You thought you only had to worry about a calendars working hours…

How Only Specific Users Can Reserve a Resource in Exchange

When you initially set up a resource mailbox, it processes meeting requests from all users. What if you need to restrict it to specific users?

We can use PowerShell for this:

Logon to Exchange Online (Connect-ExchangeOnline), then issue the command below.

Set-Mailbox -Identity “resourcemailbox@domain.com” -AcceptMessagesOnlyFrom “username1@domain.com ″,”username2@domain.com ″,”username3@domain.com”

AcceptMessagesOnlyFrom is used for specifying what users can send to email addresses and distribution groups. However, a resource has a mail box so why not use it to specify who can book meetings. You can’t hide the resource and only notify only the users who you want to use it so this is the next best thing!

The “Only specific users can book the resource” by sending meeting requests requirement is satisfied. The resource mailbox automatically process the meeting requests by accepting or rejecting depending upon availability.

A pretty neat hack if I do say so myself. Sometimes it takes a little digging but you can find out different ways to use what M365 already has available, you can pretty much accomplish anything you need to properly administer your M365 tenant.

Happy IT’ing

Dan

So you would like to try Windows 11? Well it is pretty easy. We are starting to see more of these installations and it is important that your currently running software works with it. It is better to test before upgrading so you know what works and what doesn’t before a full scale upgrade. I strongly suggest rolling it out in phases and per Microsoft’s Recommendations. All you have to is initiate the following five steps.

1. Have at least Windows 10 Professional
2. Install Microsoft Hypervisor Manager
3. Download the Windows 11 ISO
4. Create Your Virtual Machine
5. Configure Your Newly Installed Virtual Machine

I will show you how to do this in the next Sections:

Have at least Windows 10 Professional

Unfortunately you can’t just have “Widows 10” you also need to meet the following requirements:

• Windows 10 Enterprise, Pro, or Education
• 64-bit Processor with Second Level Address Translation (SLAT).
• CPU support for VM Monitor Mode Extension (VT-c on Intel CPUs).
• Minimum of 4 GB memory You will need at least 8 GB if you are going to use Microsoft Hypervisor Manager

The Hyper-V role cannot be installed on Windows 10 Home.

Install Microsoft Hypervisor Manager

To install the Hypervisor Manager, you need to go into settings or the control panel and add Windows Featires:

All that is left is a reboot and then you can proceed to the next step.

Download the Windows 11 ISO

Please go to Microsoft’s Windows 11 Site and Download the ISO file for your region. I would recommend the Multi-Edition ISO so you can decide what version is best for you. You can leave it in your download folder of your favorite browser or you can move it to a location you would like, Just remember where you saved it. You will need it for the next step.

Create Your Virtual Machine

First Verify that your computer can support Virtualization in the BIOS / UEFI. Start the Microsoft Hypervisor Manager and click New / Virtual Machine.

This will start the Virtual Machine Wizard.

Click Next.

Name Your Machine and Click Next.

You need to choose Generation 2 as Windows 11 uses these features in order to run. You will have to come back after configuration to set the number of processors you want your virtual machine to use.

Assign at least 4 GB of memory. This is a minimum requirement for Windows 11. Having said that you will need at least 8GB of RAM on your host machine to be able to run the virtual machine. I have 16 GB of RAM on my machine. It was really helpful.

For the Networking section. Choose “not connected” for now. We will set it up after the Virtual Machine is created. For now, just click Next.

For the Virtual Hard Disk, just accept the defaults and Click Next.

In this section, please choose “Install an operating system from a bootable image file” and browse to where you saved the Windows 11 installation ISO. Click Next.

Click Finish and your Virtual Machine has been created. Now lets configure it…..

Configure Your Newly Installed Virtual Machine

Go to the main window of the hypervisor manager and right click on the virtual machine you just created and choose “Settings”. We need to configure the processors so Windows 11 can run and the networking so it can access the internet / intranet through the host machine.

Adjust the processors by clicking the item on the left pane. On the right choose 2 processors to start. That should be enough for testing purposes.

Go back to the Main window and in the right pane you will see the Virtual Switch Manager. Double click that and you will be able to create a virtual switch so the VM can get networking:

Select External and Click Create Switch:

Name the Switch and click OK.

Go back to the settings of your VM and choose Network Adapter from the left pane. In the right pane choose the virtual switch you created from the drop down and click OK.

Conclusion

You are now ready to Try windows 11. Just double click the machine you created in the main window of the Hypervisor Manager and it will begin the installation process of Windows 11 like you you were running it on Bare Metal Hardware. It’s like Hardware Troubleshooting. You need to make sure your systems will work reliably and predictably with the new OS.

Happy IT’ing

Dan