Monthly Archives: April 2019

How to check your Office 365 tenant for auto-forward rules

Use the following steps to check for any Office 365 auto-forward rules to external email addresses.

In this blogpost I’m using Powershell to check for any existing auto-forward rules to external email addresses.

Step 1 Logon to Office 365 using Powershell

Step 2 Export the mailbox(es) that have either redirect or forwarding

This produces a list of all mailboxes that exist in the organization where the forwaring or redirect flags are enabled

Step 3 Investigate which rules are in use

Step 4 Remove the inbox rule from a specific mailbox

Step 5 Remove all the available inbox rules from all mailboxes (if you prefer)

Howto update ESXi without vCenter (Update Manager)

Use the following steps to upgrade your ESXi version to the latest version without download patches first! We are going to use Putty to talk against the command line 🙂

First step, put your ESXi server into maintenance mode :

Now we are going to check the profile version we are running

Or check the build version using the UI:

Now enable the host firewall rule to allow web traffic

Run the following command to list the online depot profiles available :

When you run into an error using the above command. Check your DNS and Gateway settings. ESXi needs to resolve some information using the internet!

Now let’s install the appropriate update, in my case I found out that I’m currently running 20170601001s. In your situation that can be different!

You can see what version you’re running using the previous command :

Ok, let’s reboot!

After installation I noticed the latest build :

Now set the firewall rule to the previous setting :

Final step exit maintenance mode :

Script to update all Azure Powershell Modules

Use this script to update all your Azure Powershell Modules to their latest versions.

Troubleshooting Visual Studio Code: language client undefined

Recently I ran into the following problem when editing Powershell scripts using Visual Studio Code ;


First I tried to remove the specific extension. Go to the extenstion tab and check for installed extensions using @installed :


Click the action/config wheel to uninstall the specific extension and reload and reinstall it. In my case that wasn’t the solution. I found out that the specific extension wasn’t completely removed. My solution was after removing the extension in Visual Studio Code, checking for any leftovers in %userprofile%\.vscode\extensions :


After deleting the specific folder and reinstalling the extension the error was gone!