Disable Intel Teaming

Good day,
I am using sysprep to create windows 7 image. I am trying to create a script to work  with the Unattend.xml   to do following: using  "PROSETCL" to join the intel adapters only to create a teaming. I have other NICs as well. But only interested in the two intel adapters. After teaming is done between two intel nics, next I need to have it "DISABLE" till the end user make it enable manually to get IP address. So, when Windows 7 starts on the very first boot, Only two intel NIC are teamed and disabled to avoid any DHCP request and adding entry in DNS.  This is a remote site and not ready for DHCP/DNS request yet, in case you are wondering! But need the workstations yesterday!! So, I really appreciate your quick prompt.

Who is Participating?
NetRock6Connect With a Mentor Author Commented:
I found the solution, thanks
Dale HarrisProfessional Services EngineerCommented:
I see it's been 6 days since you asked the question, so I'm going to take a stab at it.

I found some great information on using Powershell to do the Teaming commands:

Team_Create <AdapterList TeamName TeamMode> [/help]

  AdapterList - Comma delimited list of adapter indices (i.e., 1,2,3). To obtain
                adapter indices, use the Adapter_Enumerate command.
  TeamName    - Name to apply to the team.
  TeamMode    - Type of team to create. Valid team modes are: ALB, AFT, SLA,
                802.3AD, SFT, and VMLB.
                Note:  SFT teams can only be created with 2 or fewer adapters.

For example, to create a new team, type:

  prosetcl.exe Team_Create 1,2 TeamNew ALB

If a team has been successfully created, the following will appear:
  Attempting to create team 'TeamNew' ...

      Successfully create team 'TeamNew'

  - If Intel(R) Active Management Technology has been enabled on a device, then
    you cannot add the device to a team.

  - Microsoft* Windows Powershell* users must put the AdapterList in quotes.
    For example: prosetcl.exe Team_Create "1,2" TeamNew ALB

This would be the starting test point for you.  Try to see if you can't get it to work on a workstation newly imaged.

Disabling DHCP is pretty easy but you'll need to find the exact code needed for your images

I would suggest simply googling Powershell Disable DHCP or Setting static IP

This way, you could put some innocuous IPs that won't work for your environment to ensure they don't connect to DNS.  You could also put in your DNS at that point as well if you'd like.

To me, the hardest thing about this is integrating it into your Unattend.xml.  As most of my scripts are created to run after first boot, I don't know how you're going to do this, but I do know we can easily have it do it when the person first boots up the computer for the first time only.

Do some checking out of these two websites, that give a lot of information:


Good luck, and I know it's not a perfect solution, but I can't test it out for you since I can't reproduce what you have going on.


Dale HarrisProfessional Services EngineerCommented:
Spent a little time creating the solution and didn't refresh before posting.  Can you post what you had to do that worked?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.