pfSense on Hyper-V running slow?

Obviously I switched back to Hyper-V but my environment is built for 2gig internet. Speedtests were south of 1meg… So on each Hyper-V host I ran this powershell command for each external vmswitch to clear it up..

Set-VMSwitch -Name "The switch name" -EnableSoftwareRsc $false


Set-VMSwitch -Name External -EnableSoftwareRsc $false
Set-VMSwitch -Name Bridge -EnableSoftwareRsc $false

Exchange Online easy forward rule

A really basic single line way to create new mail flow email redirection with Exchange Online, probably onprem too. The to address can be internal or external and there will be an alert that the rule has been created.

From your favorite Exchange CLI. I personally like from the Azure portal open the CLI and run Connect-EXOPSSession then I can run all my Exchange commands from whatever computer I currently have access to.


New-TransportRule -Name AmericasNextTopForwardRule -Priority 69 -Enabled $true -SentTo -RedirectMessageTo

Exchange Online mailbox too big?

Patience is important, messages might not start vanishing for a few hours but quota is freed up.

Hoping you have Exchange Online Plan 2 license so you really have the over 50 GB available.

Set-Mailbox -ProhibitSendQuota 98GB -ProhibitSendReceiveQuota 99GB -IssueWarningQuota 97GB

Clean up things? Again, it may take a few hours to see the numbers start shrinking.

Change that hold to just 0 days then?

Set-Mailbox -RetainDeletedItemsFor 0

Make sure there’s no litigation hold on anything?

Set-Mailbox -RemoveDelayReleaseHoldApplied

The run a clean up?

Start-ManagedFolderAssistant -Identity

Extra Cleanups

Search-mailbox -Identity -SearchDumpsterOnly -DeleteContent -Force
Start-ManagedFolderAssistant -Identity “ ” -HoldCleanup

Work From Home Companies

VMWare –

HomeDepot –

Amazon –

Wells Fargo –





A Place For Mom –

Functional level too low for catalog

Right now with Citrix Cloud it has an agent that runs on the system, called the VDA, there are VDA versions 1811, 2003 and 2106.

In the past when publishing the a new image I could safely update that from 1811 to 2003 then there was no affect on the running systems until the reboot would occur then you’d have a happy system running on the new VDA version.

Well not today, today when I updated both the base images and the catalog 2106 with a scheduled reboot for much later in the night instantly all systems running 2003 unregistered themselves.

The fix was to for now…. republish the base image with the minimum functional level of 2003 to keep the active systems operating then tonight republish for a 3rd time using the correct version.

Move an Appliance Disk to Azure

This process for making a Hyper-V based appliance disk images work in Azure. This has been used several times for Linux based appliance.

ESXi network configurations work different and don’t transfer correctly to Azure, always go for Hyper-V images.

Boot up VM, enable remote settings and remove Hyper-V agents.

Using Hyper-V disk manager convert whatever the disk images is to a Fixed VHD(NOT VHDX).

Upload to blob storage, slowly…. Disk images over 100 GiB will take over 24 hours apparently.

Create a template from the disk image stored in blob storage.

Create a VM from the template.

Boot diagnostics are useless, you’re flying blind. Thanks for no console Microsoft.

Squeeze a little break between Exchange calendar meetings

Set-OrganizationConfig -ShortenEventScopeDefault 2 -DefaultMinutesToReduceLongEventsBy 5 

These are set using the Set-OrganizationConfig setting. The three new properties are ShortenEventScopeDefault, DefaultMinutesToReduceShortEventsBy and DefaultMinutesToReduceLongEventsBy. You turn on the reduced length meetings by setting ShortenEventScopeDefault to 0, 1 or 2 where 0 is the default and meetings are not shortened and 1 means to end meetings early and 2 means to start meetings late.

Once ShortenEventScopeDefault is set to 1 or 2 you can set the DefaultMinutesToReduce…EventsBy properties. These are set to the minutes that you want taken off the meeting. Short meetings are those of an hour or less and long meetings exceed one hour. So for example if you set DefaultMinutesToReduceLongEventsBy to 10 then all meetings over 1 hour would be 10 minutes shorter, either at the start or the end (not both) based on the value of ShortenEventScopeDefault.