Archive for February, 2010

VMware Mount Drive/ISO & SQL Server 2008 DVD

The SQL Server 2008 disk acts as though it were corrupted if mounted to a VM through VMware.

Back Story

So I’m doing some work from home and one of the tasks I had set for myself was to install SQL Server 2008 on a virtual machine; so when I was leaving the office the other day I jammed the SQL Server disk into one of our ESX boxes dvd drive and boom I’m out the door.

Unfortunately when I tried to run the Setup file to begin the prerequisites I got an error

“.net Framework 3.5 installation Failed”

which was bizarre as I had already installed it and doubley bizarre as SQL Setup normally installs .net framework if it isn’t available.

Google was once again my friend and I quickly discovered this was a common error when people were trying to mount ISO’s they had downloaded from Volume licensing websites.

Mounting with daemon tools, or isomount util works, and for me copying the files to the server over the network did the job. Damn dodgy esx :)

SVGA Driver Killing Server 2008 VM’s

Vmware’s legacy SVGA driver that comes as part of the VMware Tools typical installation with is causing Windows 7 and Server 2008 R2 virtual machines to lock up.

The frozen VM will still perform most of it’s functions but video output over vSphere console / Remote Desktop just doesn’t work.

According to VMware Update 1 for vSphere 4 has a new driver that fixes the issue.

Terminal Server: Exceeding the Connection Limit

How often have you run into the max-connection limit on your servers because you or other admins have left disconnected sessions logged in? Too often !

“The terminal server has exceeded the maximum number of allowed connections”

Terminal Server Warning

Terminal Server Woes

Terminal services allows up to 2 simultaneous connections for administrative purposes; but counts disconnected / inactive sessions towards this limit. Forgetting to log off; can essentially lock you and other admins out. Luckily session zero (console) doesn’t count towards this limit.

While connecting directly to the console often alleviates this problem, what happens when someone has commited the sin of leaving a session connected to the console (session 0).  Keyboard, Mouse and LCD?

Here’s a little work around I came across on the technobuff blog;

  • Open a command prompt and run the following;

query session /server:SERVERNAME
  • Record the ID of the session you want to terminate and run the following command

reset session [ID] /server:SERVERNAME
Return top