Lenovo ThinkServer TS200v how doth thou suck *ss?
Ceaselessly and with great fervor. Let me count the ways:
1) Server 2003 installation crashes.
2) No 2003 Server drivers are available for download.
3) ThinkServer "EasyStartup" program hangs.
4) Driver installations need .Net framework 3.5 installed to run cleanly, meaning you have to add the Application Server role BEFORE installing drivers.
5) Hypervisor setting turned off in BIOS
6) When the Hypervisor setting is turned on, graphics go squirrely and machine freezes
7) If you boot into Safe Mode with Hypervisor setting turned on graphics are OK but machine blue screens upon password entry
8) BIOS flasher fails mid-flash.
I finally got the Hypervisor to successfully start up the virtual machine by turning off the Hypervisor in BIOS, booting, removing the display drivers (built-in, on-board adapter), booting, turning on the Hypervisor in BIOS, full power off, and then rebooting.
WHAT A PIECE OF CRAP.
1) Server 2003 installation crashes.
2) No 2003 Server drivers are available for download.
3) ThinkServer "EasyStartup" program hangs.
4) Driver installations need .Net framework 3.5 installed to run cleanly, meaning you have to add the Application Server role BEFORE installing drivers.
5) Hypervisor setting turned off in BIOS
6) When the Hypervisor setting is turned on, graphics go squirrely and machine freezes
7) If you boot into Safe Mode with Hypervisor setting turned on graphics are OK but machine blue screens upon password entry
8) BIOS flasher fails mid-flash.
I finally got the Hypervisor to successfully start up the virtual machine by turning off the Hypervisor in BIOS, booting, removing the display drivers (built-in, on-board adapter), booting, turning on the Hypervisor in BIOS, full power off, and then rebooting.
WHAT A PIECE OF CRAP.
posted by Corgi, Dr. of Ursinity, Prattling Pasha of Positivity at 7/22/2010 08:19:00 AM
3 Comments:
Lenovo clearly states that Windows Server 2003 is not supported. Did you try with Windows Server 2008?
Yup, everything from point 3 on applies to a 2008 server install. I was presented with one of these to use in a job so I hadn't read the spec. It may be clearly stated, but I still think it sucks. Sure, I know that it's 2010, but sometimes you need to run a vertical market app where the vendor still isn't officially supporting 2008. Would it have killed them to provide a few drivers and make sure that the 2003 installer didn't blue screen? I got around it in the end by virtualizing the 2003 server but because of the hypervisor display driver conflict that took me about a half a dozen reboots to work out.
Go into the BIOS and change the SATA MODE to IDE instead of ACHI and 2003 will load. Also, the drivers for 2008 have 32 bit drivers with it that work in 2003. I know the network and chipset packages do anyway.
Post a Comment
<< Home