Archive for the ‘VMware’ Category

Finding which LUN a datastore is on

January 25, 2018 Leave a comment

Recently we were doing some reconfiguration of our SAN and need to consolidate our VMFS datastores.  This required us to remove some LUNs and datastores.  While I was pretty confident our naming convention was correct between VMWare and one of our SAN arrays I wanted to be extra careful when removing the LUNs.  To my surprise I could not find a way to see which LUN a datastore was on in VMWare vCenter (6.0).  I checked everywhere I could think of but could not find any mapping.

Even though this information is not exposed in vCenter you can easily find it with PowerCLI with a simple one liner.

get-datastore “Datastore Name” | Get-SCSILun | ft CanonicalName

This finds the VMFS datastore and pipes the object over to Get-SCSILun which returns the LUN it’s store on.  You can do this for all datastores but the Get-SCSILun cmdlet is very slow so if you have dozens or hundreds of datastores this can take a while to run.

Categories: Powershell, VMware

vCenter 4.1 database transaction log growth restricted to 500MB by default

January 13, 2011 Leave a comment

I recently upgraded my vCenter 4.0 server to 4.1.  Since my old server was a Window 2003 R2 32 bit server I had to migrate everything over to a 64-bit Windows 2008 R2 server.  I didn’t want to lose my vCenter configuration so I used the data migration utility VMware includes to move all the data from the old server to the new server.  During the install of the new vCenter server I chose to use the SQL 2005 Express install since I have a very small environment.  Everything installed and I was able to connect to my new vCenter server.

Life was good…until I came in 3 days later and the vCenter Server service was stopped.  I was able to start it but 30 seconds later it would stop again.  It turns out when vCenter is installed with the SQL 2005 Express database it restricts the SQL log file to only 500MB!  This seems on the small side since it was just a few days before my log was full and I have a very small environment.  I set my log to unrestricted growth so I would not get hit with this again.  Make sure you have some other way to control the log growth (backup, shrinking, etc) so it doesn’t use up all your available space.

So if you do an upgrade of vCenter 4.0 to 4.1 make sure to check your log file size after the upgrade.

Categories: VMware Tags:

VMware Workstation network drivers for WinPE

November 4, 2010 4 comments

I’ve recently begun using VMware Workstation to test image deployments with MDT 2010 and immediately ran into an issue with the default NIC that VMware Workstation 7 uses. 

When you create a new VM and use the XP profile it defaults to using an emulated AMD PCNet NIC.  If you choose a Windows Vista or 7 profile it defaults to using an emulated Intel e1000 NIC.  None of my MDT LiteTouch images included the AMD driver so I had to go searching for it.  I didn’t find the drivers on VMware’s site but I did find it on AMD’s site here.

Once you download the extract the drivers open up your Deployment Workbench.  Import them into your Out-of-Box drivers into the correct folder (You are using folders in MDT 2010 right?).


Don’t forget to rebuild your Deployment Share to regenerate your WinPE images.


Now just import the WinPE images into your PXE server or update your boot CD.  You can now boot your LiteTouch image on a VMware Workstation 7 VM.

Categories: Deployment, MDT, VMware Tags: ,
%d bloggers like this: