VMware Player: Run Windows Server 2003 as guest?

Discussion in 'Operating Systems' started by PingSpike, Nov 9, 2012.

  1. PingSpike

    PingSpike Lifer

    Feb 25, 2004
    Likes Received:
    I'm a bit of a noob when it comes to virtualization and the WMware website seems kind of vague about the capabilities of their free player product. I gather that WMware Server (which is free) is no longer supported and required a Server host OS to begin with. I'm just wondering if what I'm planning to do is possible and/or a good idea. I have a small home server running a celeron G540 with H61 chipset, 8GB ram.

    What I'd like to do is:
    Install XP x64 as host OS
    Then install VMWare Player with
    Windows 2003 Server as a guest OS running WSUS
    And possibly one other Windows or Linux OS as a guest in the future but no immediate plans for that.

    Later I might want to run Windows 2008 Server but no immediate plans for that.

    Are there any networking considerations I'm not aware of? I'll probably store the WSUS data on the host OS and setup a network share since I feel that would be easier to backup.
  2. Loading...

    Similar Threads - VMware Player Windows Forum Date
    Another HyperV vs VMWare thread Operating Systems Jun 13, 2017
    Ubuntu 17.04 crashes on Kaby Lake if VMware running Operating Systems May 11, 2017
    Networking with VMware Player, two different NIC's Operating Systems Apr 30, 2015
    VMware Player 5. No USB 3.0 HDDs. Operating Systems Jul 24, 2013
    VMware player - keyboard not working (not keystrokes). Operating Systems May 15, 2010

  3. Snoop

    Snoop Golden Member

    Oct 11, 1999
    Likes Received:
    Your plan should work fine. Networking should be no problem, I would use bridged settings for the VM and it should function like any other pc within your lan.

    I have a box (Athlon X4, 12gb ram)with a base windows 7 install. I run VMware workstation with one Server 2008 guest running SQL and IIS and a Win 7 guest to test applications and give others remote access to both test clients and the SQL server. Everything is scripted so when the host OS starts, it has a timeout then launches the VM's.

    The only reason I went with this setup over running ESXI (which is likely a better solutions) is that with the Windows host, backups of my VM's are easy. I have a backup client which ships out the VM's nightly, and I also have a backup set (two weeks worth) in case somethings gets corrupted within a nightly backup.