Winmail.dat when sending from Exchange/Office 365 to Gmail (and perhaps others)

Author: Andrew Tryon  //  Category: Uncategorized
Set-RemoteDomain Default -TNEFEnabled $false

Configuring NTP on Windows Server 2012

Author: Andrew Tryon  //  Category: Windows Server 2012
w32tm /config / /syncfromflags:MANUAL
Stop-Service w32time
Start-Service w32time

Azure AD Connect Sync

Author: Andrew Tryon  //  Category: Uncategorized
Start-ADSyncSyncCycle -PolicyType Initial
Start-ADSyncSyncCycle -PolicyType Delta

Connect to Office 365 via PowerShell

Author: Andrew Tryon  //  Category: Exchange
$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $UserCredential -Authentication Basic -AllowRedirection
Import-PSSession $Session

Get External IP Address From Command Line

Author: Andrew Tryon  //  Category: Uncategorized

Exchange – Get Distribution Group Members

Author: Andrew Tryon  //  Category: Exchange
foreach ($group in Get-DistributionGroup) { get-distributiongroupmember $group | ft @{expression={$_.displayname};Label=$group} | Out-File c:\temp\DistributionListMembers.txt -append}

Install Dell OpenManage on PowerEdge T20

Author: Andrew Tryon  //  Category: Stupid Server

Dell OpenManage is not technically supported on the PowerEdge T20 and perhaps others, but you can still install it with the right commands.

If you try to run the installer per Dell’s instruction you will get the following error:

This is not a supported server. Server Administrator software can only be installed on supported servers.

To install the software you will need to open a command prompt and browse to the msi file typically located at C:\OpenManage\windows\SystemsManagementx64\. From here run the following command:

msiexec /i SysMgmtx64.msi SYSTEMCHECK=NO

This will install OpenManage without doing the prerequisite check.

Silently install Vipre agent with MSI install

Author: Andrew Tryon  //  Category: Antivirus

Create a MSI installer for the policy you want to use
Copy the file to a location accessible by the computer you want to run the agent installer on
Run the following command

AgentInstaller-SITE-NAME-Workstations-General-EN.MSI /q /qn /promptrestart

Reset ESXi to 60-day eval license

Author: Andrew Tryon  //  Category: VMWare ESXi

Access the console of the ESXi
Press Alt-F1
Log in as root
Run the following commands to delete two files and restart the VMWare services

cd  /etc/vmware
rm -r vmware.lic
rm -r license.cfg restart

When you log back into ESXi using the vSphere Client you will be back in Evaluation Mode for 60 days

Note: If you get a message that says ‘Tech Support Mode has been disabled by the administrator’ message you may do the following:

Log into vSphere Client
Select the host and then the configuration tab
Select Security Profile under Software and then click Properties
Select Local Tech Support and then click Options
Click Start under Service Commands
You may now log into the ESXi console using Tech Support Mode

Slow Network Performanceon Hyper-V Guest

Author: Andrew Tryon  //  Category: Hyper-V, Windows Server 2008, Windows Server 2012

A few weeks ago during a server migration I encountered a very interesting issue. This was a brand new Dell PowerEdge R420 server running Hyper-V with two freshly installed VMs on it all using Windows Server 2008 R2. The installation of everything went perfectly fine, but when I started the migrating data from an old Server 2003 box I started to notice an issue – network transfers were taking insanely long. On average I was copying 200KB/sec. I then did a ping test from the new VM to the old sever and was getting response times from 20ms to 2000ms. I got the same ping results to every device on the network from desktop PCs to routers. My troubleshooting made me questing network switches and wiring, but in the end it turned out to be neither. After some extensive troubleshooting I then noticed that the old server was able to ping everything on the network within 1ms (excluding the Hyper-V sever and guests). Next I swapped out the network cable with a known good cable – the issue continued. At this point I knew the issue was with the server; either the software or hardware. After some more extensive troubleshooting I stumbled across an article (I wish I could find it again and link it here) that discussed Virtual Machine Queues for certain NICs that support it. In the Device Manager I selected my NIC and opened the advanced properties to discover that this Virtual Machine Queues was enabled. I changed the setting to disabled and instantly my ping tests went from being no less than 20ms to being 1ms. This fix seamed too easy for all the work I put into this. I quickly started another test by copying files from the old server and was copying at full gigabit speeds. I could not believe my eyes; this simple setting that is meant to help improve networking speeds between the host and the guest was actually doing the total opposite.

Below is a screenshot of the Virtual Machine Queue setting that you want to disable – Do not confuse it with the VMQ LAN Filtering:


Now just this week while setting up a very similar Dell PowerEdge R520 server with Hyper-V I ran into the same issue. This time within minutes I was able to get it resolved. Based on the two servers I uncounted this issue I believe the root cause is the Broadcom NIC drivers as both servers were using the same NIC. I checked on another sever I deployed with Hyper-V in the past that has an Intel NIC and discovered that the Virtual Machine Queue is enabled and that none of the VMs are experiencing the issue.