Author Archives: Brendan Skoreyko

Change Users Office 365 Email (SMTP Address)

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.

To connect to Office 365 (Exchange Online) following the instructions (or click here for the official Microsoft article – Connect to Exchange Online):

Step 1) Open PowerShell (as administrator) and run the following command:

$UserCredential = Get-Credential

Step 2) Sets the PowerShell environment for your Office 365 tenant:

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

Step 3) Sets your PowerShell session to use Microsoft Exchange Online:

Import-PSSession $Session

Step 4) Change your users email address (Primary SMTP) from [email protected] to [email protected]:

Set-Mailbox username -WindowsEmailAddress [email protected]

Step 5) Check the mailbox by running the following command:

Get-Mailbox -Identity [email protected]

Step 6) Disconnect your PowerShell session from Exchange Online:

Remove-PSSession $Session

If you have any questions or see an error please let me know. If you are looking for more  around PowerShell and Office 365 check here: http://powershell.office.com/

VMware Workstation bridged networking stopped working

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.

How to fix bridged networking in VMware Workstation after applying Windows 10 update (Threshold 2)

How to fix bridged networking in VMware Workstation after upgrading to Windows 10

Remove a print driver from Windows

Looking to remove a print driver well here is an easy way that many won’t think of.

From the Start Menu in the search box type the following: printmanagement.msc. Navigate to “Printer Servers” and selected “Drivers.” The main column will list the installed drivers:

You can right click the driver you wish to remove and select “Delete.” This will remove the desired Printer Driver.

How to Show or Hide Windows updates in Windows 10

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.

I found a similar post on HP Forums: Error 0x80070490, Error 0X8024200b – Windows 10 / Windows Update.

Below are the steps within the Windows 10 Show and/or Hide updates:

As you can tell from the screenshots I chose to hide the HP “NULL” device driver as the update would not install.

Windows 10 Threshold 2 & VMware Workstation Bridged Networking

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.