asked on

windows 2019 Hyper V running windows 2003 R2 Guest OS drivers

We currently have a Windows 2003 std r2 install that is running some legacy software its hosted on a VMware workstation.

i would like to move this virtual image over to newer hardware on one of our windows 2019 servers that i have installed hyper v on. iv coped and converted the image and got it booting okay BUT it seems windows 2019 hyper v client services does not support windows 2003 as a guest so there is no drivers for mouse and some other functions.

is there anyway around this? (iso download leagcy drivers pack or something) or am i best to stick with VMWare as they seem to support 2003 with no issues

Steve

Officially it's not supported and you should avoid using 2003 on here as it wont be supported and could be unstable. Hacking it to get it working may be viable but is not recommended, especially for anything important.

You can install an old version of the integration services that will support 2003, but the services will be out of step with the host OS so it's still possible it could be unstable.

https://www.deltik.net/news/view/45/download-hyper-v-integration-services-for-legacy-operating-systems

ASKER CERTIFIED SOLUTION

Ian Pattison

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Andy Wilkie

ASKER

yes if i could avoid using 2003 i heavily would but as we all know some software with connected hardware just does not work with newer stuff so you end up running it on a VM on a separate network.

i think the best option is to just keep using VMWare as iv had no issues in the past i did hope Microsoft might have better support for there own os but seems this is not the case.

thanks for the advise guys

Steve

i did hope Microsoft might have better support for there own os but seems this is not the case.

In defence of Microsoft, that OS is almost 20 years old. If i ran Microsoft I would also consider not supporting such an old OS too.

Philip Elder

We have a few environments where this is needed.

Make sure the VM is on its own VLAN and _only_ the needed inbound TCP and/or UDP ports are enabled from production with a jump server/management server allowed inbound for needed protocols. Block all access to the Internet for that VM. None. Nada. Zippo. Zilch.

At least then one does not have to worry about having an open security weakness on the network.