Ran into a couple snags trying to install VMWare Server 2.0 onto Windows Server 2003 R2 today, and figured I’d share in the workarounds:
First issue was an error when trying to launch the setup program: “The System Administrator has set policies to prevent this installation.” Hm. I’m the system administrator, and I don’t recall setting any such policies.
Happily, Jason Boche — a VMWare Virtualtization Evangelist — wrote a blog entry which explained a simple fix. Apparently this is part of Windows 2003’s new “high security” mode, and I suppose I can’t fault Microsoft for it… much.
Jason’s solution is thus:
- Click Start
- Click Run
- gpedit.msc <enter>
- Drill down to Computer configuration
- Windows Settings
- Security Settings
- Software Restriction Policies
- Security Settings
- Windows Settings
- Right click Software Restriction Policies
- Choose Create New Policies
- On the right hand side, right click Enforcement
- Choose Properties
- Down below, choose All users except local administrators
- Click OK
- Close Group Policy
- Open a Command Prompt
- Run the command gpupdate /force <enter>
- When local group policy is finished updating, re-run the VMware Server 2.0 setup
Worked like a charm. Thanks, Jason!
Second up was once the install started running, I got stymied with “Error 1718: File c:\windows\installer\randomstring.msi was rejected by digitial signature policy.”
According to Shawn Bass’ blog, there’s an issue with the WIndows Installer engine and big MSIs. Microsoft has made a hotfix availablewhich, after a reboot, took care of things.
My pleasure! Glad to hear it!
Great, thanks you saved me hours of fumbling.
We use windows 2003 server for training machines and I am ocassionally asked to re-install vmware. Thanks for posting this as it is a godsend