Windows 2003 services on a stressed VMware workstation; aka fixing the ZCM Utopia services startup

Novell has a fantastic demo suite known as Utopia – listen to this Novell Open Audio Podcast for details.

One issue that was reported by the field was that running Windows 2003 server on VMware workstation with ZENworks Configuration Management would sometimes cause the ZENworks services not to start.

I’ve never really seen this issue; I saw one VM that was broken – but only saw that everything was slow.

For the sales kickoff I built a set of VMs and was testing them. Moving from ESX to VMware Workstation on SLED running on a Thinkpad T42p laptop I saw the issue.

In short the workstation service was being slow to start; the server was stressed – and the service timed out. The dominos started to fall; Net Logon failed etc etc etc.

My fix is simple. Make the workstation service dependant on something that is relatively benign but that will start with some reliability. I chose the DNS service (it’s a single server) – because that ultimately provides the DDNS underpinning to Active Directory and other services.

Here’s how:

sc config lanmanworkstation depend= dns

That simple. Reboot and you should now have a working ZCM Utopia demo.

For the internal Novell people – did this fix your problem?

One thought on “Windows 2003 services on a stressed VMware workstation; aka fixing the ZCM Utopia services startup

  1. I booted the utopia vm and got the service start up error.

    When the above command is issued at the DOS prompt and the server rebooted, the server simply does not boot. left it for 15 minutes.

    If i revert the snapshot the server comes up with obviously with the service start up errot

Leave a Reply