A blog about technology and things…

Post navigation

While reviewing users in Office 365 I noticed that some of the users had incorrect email addresses. Rather than using our companies email domain name they were using the Microsoft email domain (domain.onmicrosoft.com), In order to change the email domain (primary SMTP) address for these users I had to Connect to Exchange Online and run a few commands through PowerShell.

Due to the environment setup I could not change the primary SMTP address through the web portal. This is the error I received when trying (which is expected based on our setup):

The operation on mailbox “Jon Smith” failed because it’s out of the current user’s write scope. The action ‘Set-Mailbox’, ‘EmailAddresses’, can’t be performed on the object ‘Jon Smith’ because the object is being synchronized from your on-premises organization. This action should be performed on the object in your on-premises organization.

For many people using VMware Workstation they should be aware of an issue which occurs after updating Windows 10 to the new Windows 10 Anniversary. In fact I have run across this issue with other major Windows 10 updates.

After performing a major update to Windows 10 VMware Workstation’s VMnet0 is removed. The removal of VMnet0 breaks the network connection for guest Virtual Machines. To repair connectivity for the guest Virtual Machines you can add a new virtual network or set the Virtual Network back to their default settings. If you set the VMware Workstation network back to default settings you will lose any and all custom networks.

The other day I was prompted to install an update for my HP Printer however the update failed every time I attempted to apply it. After searching the web I found out that you can Show and/or Hide Windows 10 updates. Microsoft’s official KB page can be found here: Windows 10 Show or Hide updates trouble shooter.

A couple of days ago I updated my Windows 10 workstation with the new “Windows 10 Threshold 2” update. Once the upgrade was complete I launched VMware Workstation 12 Pro and noticed that my Virtual Machine did not have network connectivity.

Based on my past experience when upgrading from Windows 8.1 to Windows 10 I discovered that VMware Workstation’s VMnet0 was removed. Due to this previous experience it made sense to check VMware Workstations “Virtual Network Editor” to confirm if VMnet0 had been removed again. Sure enough the same problem existed after applying “Windows 10 Threshold 2.”

To restore “Bridged Networking” in VMware Workstation you have to re-add VMnet0. In order to add VMnet0 you’ll need to restore your default network settings. Be warned though as any custom network configurations will be lost when restoring your default network settings. See my past post here: VMware Workstation Bridged Network Failure after upgrade to Windows 10.

If you have any issues restoring Bridged Networking please reply to this post or send me a note via the Contact Page.