- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have a problem with teaming adapters. I have a WinXP image that I want to deploy to a series of machines. The image is
sysprep'ed. I've created a script teaming the 'Intel Pro/1000 PF dual adapters' via the following commands (after having
run the Adapter_Enumerate command):
prosetcl.exe Team_Create 6,4 LAN1 SFT
prosetcl.exe Team_Create 1,5 LAN2 SFT
After teaming, the network interfaces are renamed and addresses assigned via the netsh command. The script works fine
but the adapter index differs from each time I run the 'prosetcl.exe Adapter_Enumerate' command after having sysprep'ed
the machine, pls see the 3 test runs below:
First sysprep attempt
C:\Program Files\Intel\DMIX\CL>prosetcl.exe Adapter_Enumerate
Number of adapters currently present: 7
1) Intel(R) PRO/1000 PF Dual Port Server Adapter # 3
2) Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller # 2
3) Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
4) Intel(R) PRO/1000 PF Dual Port Server Adapter # 2
5) Intel(R) PRO/1000 PF Dual Port Server Adapter # 4
6) Intel(R) PRO/1000 PF Dual Port Server Adapter
7) VIA Rhine III Management Adapter
Second sysprep attempt
C:\Program Files\Intel\DMIX\CL>prosetcl.exe Adapter_Enumerate
Number of adapters currently present: 7
1) Intel(R) PRO/1000 PF Dual Port Server Adapter # 4
2) Intel(R) PRO/1000 PF Dual Port Server Adapter # 3
3) Intel(R) PRO/1000 PF Dual Port Server Adapter # 2
4) Intel(R) PRO/1000 PF Dual Port Server Adapter
5) Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
6) VIA Rhine III Management Adapter
7) Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller # 2
Third sysprep attempt
C:\Program Files\Intel\DMIX\CL>prosetcl.exe Adapter_Enumerate
Number of adapters currently present: 7
1) Intel(R) PRO/1000 PF Dual Port Server Adapter # 3
2) Intel(R) PRO/1000 PF Dual Port Server Adapter # 4
3) Intel(R) PRO/1000 PF Dual Port Server Adapter # 2
4) Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
5) Intel(R) PRO/1000 PF Dual Port Server Adapter
6) Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller # 2
7) VIA Rhine III Management Adapter
Allright so the NIC index differs after each sysprep run - so I'll script my way out of this problem - but the I ran
into another problem. When I try to redirect the output from the 'prosetcl.exe Adapter_Enumerate' command to a file, the
resulting file is empty! I then tried redirecting stderr (prosetcl.exe Adapter_Enumerate 2>&1 c:\NICenum.txt) but same
result.
I consulted the 'PROSETCL.EXE Help File' to check if there was a command to print the NIC index, but without luck.
Please help me with hints on how to write the output of the 'Adapter_Enumerate' command to a file or env. variable.
Thanks
Jacob
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I do not have Windows XP handy, so I tried a quick test with Windows 7.
From the command prompt I ran prosetcl Adapter_Enumerate > test.txt.
My result was that access was denied.
I opened a command prompt as an administrator and ran the same command as before, prosetcl Adapter_Enumerate > test.txt.
This time, I successfully created and wrote the output to the file.
Those results lead me to believe that you might be running into a Windows permissions issue when you try to write the ouput to a file. On the other hand, the security might be different enough between these different Windows versions that your issue is something else.
I hope the permissions idea helps you.
Mark H
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unable to capture the console output from prosetcl in Windows XP. Running the command as administrator:
prosetcl adapter_enumerate > output.txt
Output file is empty. Has anyone been able to run the command on XP successfully?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I did some more checking. There was a bug that prevented redirection in the original release of prosetcl that has been fixed. I just posted a zip file of a brand new Intel(R) Network Connections software CD. We will have smaller OS specific downloads posted later this week or early next week.
Try installing the new software and see if the latest prosetcl resolves the redirection issue:http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18664 Intel® Ethernet Connections CD, version 15.2.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've downloaded the suggested version (15.2) and ran a test at my system (Windows XP 32-bit SP3) and the output redirection works like a charm . Thnx a lot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
PROSETCL seems to have a problem redirecting output with either Windows 2012 or the .net Framework 4.5.
When I attempt this either from PowerShell or from an independent C# program, the output file generated is null. I have been doing this successfully on Windows7 until now.
Here's a sample PowerShell script that fails, output.txt is 0 bytes:
./prosetcl.exe adapter_enumerate | Out-File ./output.txt
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page