Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Managing hardware on a Server Core environment (here: creating VLANs with Intel NIC)

Answered Managing hardware on a Server Core environment (here: creating VLANs with Intel NIC)

  • Friday, March 28, 2008 2:25 PM
     
     
    Sign In to Vote
    0

    Hello,

     

    currently I have a Windows Server 2003 Server. I've got one extra NIC for the internet connection. Because of technical requirement of VDSL I need a NIC with VLAN ID 7 and 1.

    On Windows Server 2003 there is no problem handling with this because Intel have got their own software for this; integrated in the device manager (in the properties of the NIC).

    But on Windows Server 2008 I can not access the device manager remotely for this (because it is read only then) and the core installation haven't got the device manager.

    I absolutly need this two NICs for a Hyper-V machine which has got the RRAS installed.

     

    The goal is to create this two VLANs and asign this two NICs to a Hyper-V machine with RRAS installed. Please help me to do this. Thanks in advanced.

     

All Replies

  • Sunday, March 30, 2008 8:32 AM
     
     Answered
    Sign In to Vote
    0
     Markus Schuhmacher wrote:
    On Windows Server 2003 there is no problem handling with this because Intel have got their own software for this; integrated in the device manager (in the properties of the NIC).

      

    As stated before:

    The Windows Management Instrumentation Console (wmic.exe) might be the right tool to change these vendor-specific settings, but it depends on the quality of the driver basically. The vendor might help you with the information you need to find the aliases, classes and paths to make your preferred the changes. Some NIC vendors also have command line tools that allow you to configure these settings. You might check the web site for your NIC vendor and see if they have such a tool.

      

      

     Markus Schuhmacher wrote:
    But on Windows Server 2008 I can not access the device manager remotely for this (because it is read only then) and the core installation haven't got the device manager.

      

    Device Manager being Read only when accessed remotely is by design. You can circumvent this default behavior by enabling remote management of the PnP interface through policies. This policy setting is located underneath Computer Configuration, Administrative Templates, Device Installation. It is called Allow remote access to the PnP interface.

      

    You can change this policy by redirecting your Group Policy Editor (gpedit.msc) to your Server Core box (as described here) or using Group Policies within Active Directory. Don't forget to issue the gpupdate command on the console of your Server Core box when you want the policy to take effect promptly.

      

      

     Markus Schuhmacher wrote:
    I absolutly need this two NICs for a Hyper-V machine which has got the RRAS installed.

      

    And here I was thinking Network Policy Server (NPS), Routing and Remote Access Services (RRAS), Health Registration Authority (HRA) and the Host Credential Authorization Protocol (HCAP) weren't supported roles on Server Core installations of Windows Server 2008...

     
  • Monday, March 31, 2008 4:13 PM
    Owner
     
     
    Sign In to Vote
    0

    Hi,

     

    As Sander pointed out RRAS is not available in Server Core, so if that is required for your scenario you'll need a full Server installation.

     

    Andrew

     

     
  • Saturday, April 05, 2008 6:30 PM
     
     
    Sign In to Vote
    0

    I will use the RRAS in a hyper-v machine.

     

    I still need to know how to add this VLAN. The remote access with changing th rule pnp access is unfortunatelly not usefull because I need RW access. But anyway the intel driver does not install the ProSet thing because no device manager is available. I also dont know wheather it install the wmi part.

     

    But if the WMI support is installed I don't know how to write a script to add the VLAN. Its to complicated for me.

     
  • Sunday, April 06, 2008 6:47 PM
     
     
    Sign In to Vote
    0

     Markus Schuhmacher wrote:
    I will use the RRAS in a hyper-v machine.

     

    Hyper-V offers virtual network switches. In the Hyper-V console you can assign network adapters to virtual machines and assign VLAN identifiers. More info and assistance can be found in the Microsoft TechNet - Server Virtualization forum.

     

    If you need help installing a driver from Intel, I suggest you contact Intel support.

     
  • Wednesday, April 09, 2008 4:19 PM
     
     
    Sign In to Vote
    0

    I'm in the same boat - trying to create VLANs with an Intel Pro 1000 MT (but not to use in Hyper-V).  If you could install Advanced Networking Services, you could write a WMI script to create VLANs.  Unfortunately it looks like you can't install ANS on Server Core.  When you run the installer (prosetdx.msi) on a Server Core machine, the feature is not shown.

    I couldn't find any information from Intel about if ANS can be installed on Server Core or not.  Anyone know?

     
  • Friday, April 11, 2008 9:14 AM
     
     
    Sign In to Vote
    0

     

    No unfortunatelly not. I've contacted Intel for that issue. But as expected no relly usefull help for now. I am waiting for a reply.

    But here the first answer. Quit funny Smile:

     

    Code Snippet

    Hello Markus,

    Thank you for contacting Intel(R) Technical Support.

    Before attempting to create a VLAN, you need to make sure you are using the latest Intel(R) drivers from the Intel(R) website: http://support.intel.com/support/network/sb/cs-012904.htm.
    Please note that for creating a VLAN in Windows* 2008 Core Server, you need to open the Start Menu, Right Click on the “Computer” line, click on “Manage”, click on the plus sign next to “Diagnostics”, click on “Device Manager”, on the right hand side pane, click on the plus sign next to “Network Adapters” to expand the branch, Double click the adapter you want to use with the VLAN, click on the “VLAN” tab and click on the “NEW VLAN” button and follow the onscreen instructions.

    Please be aware that if you are connecting remotely, using Remote Desktop Connection  you might not be able to see the Intel(R) Advanced Network Services tabs (VLANs, Teaming) . If this is the case, try the solution described here: http://www.intel.com/support/network/sb/cs-020166.htm. Please be aware that this solution was designed for Windows* 2003 Server and might not work in Windows* 2008 Server. If you are unable to apply this fix, you will need to connect locally to the server in order to create the VLANs.

     

     

     
  • Tuesday, April 15, 2008 2:05 PM
     
     
    Sign In to Vote
    0
    Has anyone figured this out?  I am afraid REGEDIT will be the only way to do it.

     

     
  • Tuesday, April 15, 2008 5:28 PM
     
     
    Sign In to Vote
    0

    If you can't get Intel ANS installed, not even regedit would help.

    I ended up implementing my solution on full server instead of Server Core.

    I've never worked with Intel support, but it'd be interesting to know if they have a stance on whether they officially support VLAN/teaming on Server Core or not.
     
  • Tuesday, May 29, 2012 11:40 AM
     
     
    Sign In to Vote
    0

    Hello,

    Advanced Networking Services (ANS) version 17.1 has command line utility PROSetCL.exe (my path is C:\Program Files\Intel\DMIX\CL\PROSetCL.exe) that alows to configure NIC Teaming and VLANs. This version of ANS runs on Hyper-V Server 2008 R2 SP1.