Installing .NET v3.5 on a Virtuozzo Virtual Private Server (VPS)
Several months ago, I gave up on trying to get .NET v3.5 installed on the 1&1 Virtual Private Server I acquired to replace my old leased Linux server. The install kept failing, and I presumed it was because Virtuozzo was blocking the install due to it acting too much like an OS component. It turns out there is a simple, but obscure workaround. Special thanks to Andre Loker for spelling it out:
Coincidentally I had to setup two Virtuozzo machines this week as well, both running Windows Server 2003 Std SP2 64bit. One had 3.5 installed but needed SP1, the other had only 2.0 installerd. I ran into the problems again on both machines. Here's what I did to install SP1:
Andre Loker
1. Restart the VPS (via the Virtuozzo control panel)
2. When the VPS is running again, rename "C:\Windows\System32\CatRoot2" (e.g. to C:\Windows\System32\oldCatRoot2 or so). DO NOT RENAME C:\Windows\System32\CatRoot, only CatRoot2
3. Start the Printer Spooler service (no need to set the start mode to auto, leave it at manual)
4. Run the .NET 3.5 SP1 installer (full version)
5. You'll probably need to reboot after installation
It worked on both machines for me, but of course I can't make any guarantees. Make sure you have a backup.
Good luck!
Posted at 12:06PM Mar 22, 2009 by raydoo in Software | Comments[1]
Hi,
this blog post is quite old, so I'm assuming you've been running .NET3.5 on virtuozzo for a while using this workaround. I'm about to embark on performing this workaround myself.
How has it been for you since you'v eimplemented it? Is Virtuozzo happy? Has this workaround affected the stability of Virtuozzo at all?
Would you still recommend doing it?
Posted by Fred on August 03, 2010 at 09:56 AM PDT #