I run this powershell script as a scheduled task on my vcenter servers
weekly. Helps me keep an eye on VM deployments and hopefully catch the
rollout of VMs with incorrect adapters. I include the OS information in my
e-mailed report so I can quickly disregard VMs with other than VMXNet3
adapters, based on OS limitations.
Add-PSSnapin VMware.VimAutomation.Core
$vcenter = [System.Net.Dns]::GetHostByName((hostname)).HostName
$recipients = <e-mail address>
$from = <e-mail address>
$subject = "Virtual Machine Network Adapter Inventory - $vcenter"
$smtpserver = <SMTP server>
Connect-VIServer "$vcenter"
$report = Get-vm | Get-NetworkAdapter | where {$_.Type -ne
"vmxnet3"} | Select @{N="VM";E={$_.parent.name}}, @{N="Operating
System";E={(get-vmguest $_.parent.name).OSFullName}}, Name, Type
if(!$report){$report = @("No VMs found")}
$head = "<style>
TABLE{border-width:1px; border-color: black;font-size:12px;
font-family:courier; border-style: solid; border-collapse: collapse;}
TH{border-width:1px; border-style: solid; padding: 0px; border-color:
black; background-color: #006699; color: white;}
TD{border-width:1px; border-style: solid; padding: 7px; border-color:
black; background-color: #424242; color: white;}
</style>"
$html = $report | sort "VM" | ConvertTo-Html -Head $head | Out-String
Send-MailMessage -To $recipients -From $from -Body $html -BodyAsHtml
-Subject $subject -SmtpServer $smtpserver
Disconnect-VIServer -server * -confirm:$false
- Sean
On Mon, Dec 2, 2013 at 7:16 AM, Kent, Mark <[email protected]> wrote:
> This seems to have done the trick and the performance is much better too!
> What took a bout 5-6 minutes before to download the Windows 7 installer
> files now takes maybe a minute. Rather impressed.
>
>
>
> Mark Kent (MCP)
>
> Sr. Desktop Systems Engineer
>
> Computing & Technology Services - SUNY Buffalo State
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Stephen Owen
>
> *Sent:* Friday, November 29, 2013 7:28 PM
> *To:* [email protected]
> *Subject:* Re: [mssms] RE: Hash errors
>
>
>
> Seconding the change to VMxNext from emulated E1000 nic. I'm guessing
> somehow the emulation of the NIC fails when offloading certain aspects of
> the packet transfer, but we saw this time and time again on one customer.
>
>
>
> On Wed, Nov 27, 2013 at 2:37 PM, Russ Rimmerman <
> [email protected]> wrote:
>
> Ahh the ole E1000 vs VMXNET3 driver. I’ve seen a LOT of network
> performance issues with using this default nic driver rather than the one
> that comes with VMWare Tools. VMXNET3 should definitely help your overall
> network performance, even if it doesn’t solve the hash issues.
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Kent, Mark
>
> *Sent:* Wednesday, November 27, 2013 10:31 AM
>
>
> *To:* [email protected]
> *Subject:* [mssms] RE: Hash errors
>
>
>
> Well this is interesting: http://www.toolzz.com/?p=1085
>
>
>
> We have the exact same environment and our VM’s are using the E1000
> adapter. I am having our VMWare admin change them to the VMXNET 3 adapter
> to see if that resolves our issues.
>
>
>
> Mark Kent (MCP)
>
> Sr. Desktop Systems Engineer
>
> Computing & Technology Services - SUNY Buffalo State
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Kent, Mark
> *Sent:* Wednesday, November 27, 2013 8:46 AM
> *To:* [email protected]
> *Subject:* [mssms] RE: Hash errors
>
>
>
> I excluded the drives the packages are on, as that is all that is on those
> drives: DP’s. I have turned off BDR for one of the images and will see
> what happens.
>
>
>
> Thanks for the blog I will check it out now.
>
>
>
> I’ll also look at the logs Trevor mentions.
>
>
>
> Mark Kent (MCP)
>
> Sr. Desktop Systems Engineer
>
> Computing & Technology Services - SUNY Buffalo State
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Russ Rimmerman
> *Sent:* Tuesday, November 26, 2013 10:56 PM
> *To:* [email protected]
> *Subject:* [mssms] RE: Hash errors
>
>
>
> When you say you’ve excluded SCEP from scanning the DPs, what exclusions
> did you do, or are you saying you’ve excluded the DP completely? The most
> common reason for hash errors from my experience is due to missing AV
> exclusions. Also have seen LUN errors/issues cause it. I would also test
> a few packages with BDR disabled as well just for troubleshooting purposes.
>
>
>
> This may have some helpful info in it too
> http://blogs.technet.com/b/configmgrteam/archive/2012/05/07/troubleshooting-content-mismatch-warnings-on-a-distribution-point-in-system-center-2012-configuration-manager.aspx.
> Ignore the part about the known issue with a warning not returning to a
> success state since you’re on R2.
>
>
>
> *Russ Rimmerman*
> MICROSOFT | SR. PREMIER FIELD ENGINEER | System Center Configuration
> Manager
>
> http://blogs.technet.com/b/configmgr_geek_speak/
> *------------------------------*
>
> Office: (832) 252-4558 | *[email protected]
> <[email protected]>*
>
>
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Kent, Mark
> *Sent:* Tuesday, November 26, 2013 3:12 PM
> *To:* [email protected]
> *Subject:* [mssms] Hash errors
>
>
>
> Is there some way to determine why these occur? I seem to get an
> inordinate number of them happening. I have excluded SCEP from scanning
> the DP’s but they still occur. This is frustrating. I was hoping this
> crap would have ended when we moved away from SCCM2007.
>
>
>
> We are on SCCM2012 R2 running on Server 2012. The servers are running on
> VMWare 5.1 with an Equilogic iSCSI backend.
>
>
>
> Mark Kent (MCP)
>
> Sr. Desktop Systems Engineer
>
> Computing & Technology Services - SUNY Buffalo State
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
