[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 632
  • Last Modified:

VMaware OS Upgrade from 2003 SRV to 2008 SRV 32 bit

I have converted a stand alone server to a Virtual Server in VMWare ESXi 4.1.0.
The Server that I converted was brought in as a Windows 2003 operating system.
Today, I upgraded that virtual server to windows 2008 R2 32 bit.
When I go to "edit settings" in VSphere, and look under the options tab, it still says Windows 2003 Server as the OS type.  
Also, the Server 2008 OS cannot find drivers for the nic or base device.

How can I get it to show the proper OS under options if this is possible?
How do I now get the correct Vmware virtual hardware for my network adapter?
This is kind of two questions, but I'm assuming that both are tied together in a virtual server upgrade scenereo.  This is one of the reasons that I'm wanting to go virtual is for ease of OS migration.  
This is a lab environment and no production server has been affected at all so now is the time for education.  

Any help would be greatly appreciated.
0
mcrossland
Asked:
mcrossland
  • 2
  • 2
1 Solution
 
Paul SolovyovskySenior IT AdvisorCommented:
No such thing as windows 2008 R2 32 bit..all R2 are 64 bit and would need a wipe of OS and full re-install of Windows 2008 R2 OS
0
 
mcrosslandAuthor Commented:
Correction: Strike the R2.
Windows Server 2008 Standard SP2 32 bit.
Typo on my part.  Sorry.
0
 
Paul SolovyovskySenior IT AdvisorCommented:
uninstall and re-install vmware tools
0
 
mcrosslandAuthor Commented:
Worked perfectly!
I also changed the OS type with that virtual machine powered down.
Thanks!
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now