- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Microsoft
- >
- A VirtualWin2003R2 was built under Win2008Core, Dr...
Operating System - Microsoft
1823131
Members
3400
Online
109646
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2009 12:13 PM
04-14-2009 12:13 PM
A VirtualWin2003R2 was built under Win2008Core, Drivers for Virtual Session?
OK, so I have a virtual Windows 2003 R2 built under Windows 2008. The virtual server can't get out to the network. There are no nics defined so I need the drivers. Where can I can I get them?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2009 04:27 PM
04-14-2009 04:27 PM
Re: A VirtualWin2003R2 was built under Win2008Core, Drivers for Virtual Session?
Pat,
My understanding is that you will need to install the Hyper-V drivers into your 2003 guest.
From the console of the virtual machine there is an option to install drivers or something - this will activate a self installer on the 2003 guest and install the necessary drivers and thus provide network and improved guest performance.
As for Win Core - I havent bothered with Hyper-V there (just std Win2008 srv). I am less than impressed with Core as it was sold as making administration easier like that of UNIX systems in a cut down manner - but simple aspects such as networking are painful compared to editing a couple of files in UNIX! This part hasnt grown on me at this time!
Also with adding Hyper-V role it required modification of the base server networking. The primary host NIC is detached and a virtual is installed at the host - effectively placing a virtual switch/bridge in place on the Hyper-V host and allowing guests to attach when building guests. The physical network interface is then attached to the switch/bridge - this process may not be handled so well in Core environments - expecting the user to do this aspect via command line as opposed to the gui.
Of course your guest will need to be created with a network interface, you get a selection of private (no external access), none (no nic at all) and effectively bridged using the hosts NIC. If setting up you didnt ask for a NIC then you wont have the necessary configuration to allow for networking.
Robert.
My understanding is that you will need to install the Hyper-V drivers into your 2003 guest.
From the console of the virtual machine there is an option to install drivers or something - this will activate a self installer on the 2003 guest and install the necessary drivers and thus provide network and improved guest performance.
As for Win Core - I havent bothered with Hyper-V there (just std Win2008 srv). I am less than impressed with Core as it was sold as making administration easier like that of UNIX systems in a cut down manner - but simple aspects such as networking are painful compared to editing a couple of files in UNIX! This part hasnt grown on me at this time!
Also with adding Hyper-V role it required modification of the base server networking. The primary host NIC is detached and a virtual is installed at the host - effectively placing a virtual switch/bridge in place on the Hyper-V host and allowing guests to attach when building guests. The physical network interface is then attached to the switch/bridge - this process may not be handled so well in Core environments - expecting the user to do this aspect via command line as opposed to the gui.
Of course your guest will need to be created with a network interface, you get a selection of private (no external access), none (no nic at all) and effectively bridged using the hosts NIC. If setting up you didnt ask for a NIC then you wont have the necessary configuration to allow for networking.
Robert.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP