HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Renaming New Team NIC connection via script
ProLiant Servers (ML,DL,SL)
1830938
Members
2147
Online
110017
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
05-09-2006 05:41 PM
05-09-2006 05:41 PM
Renaming New Team NIC connection via script
Hi
I have just created a new Team via the CQNICCMD utility - works fine. It creates a Team Network connection called "Local Area Connection 3". I want to rename this connection to "Team NIC" via a script or utility. The registry location is GUID based which changes so a simple registry hack wont work. Is there a way to do this so it can be run from a script as a post sysprep task?
Thanks
Anthony
I have just created a new Team via the CQNICCMD utility - works fine. It creates a Team Network connection called "Local Area Connection 3". I want to rename this connection to "Team NIC" via a script or utility. The registry location is GUID based which changes so a simple registry hack wont work. Is there a way to do this so it can be run from a script as a post sysprep task?
Thanks
Anthony
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2006 01:50 AM
05-11-2006 01:50 AM
Re: Renaming New Team NIC connection via script
Anthony,
There isn't a teaming command or script that will rename the associated Local Area Connection. Any solution you find will be teaming independent. Meaning, I recommend looking for a way to script the renaming of any local area connection - teamed or untea med.
That being said, NETSH may work for you. I recommend searching for "rename" within this document. I haven't personally tried what it suggests, but it may work for you.
http://msdn.microsoft.com/library/en-us/dnxpesp1/html/tchWorkingWithNetshInWindowsXPEmbedded.asp?frame=true
Regards,
-sean
There isn't a teaming command or script that will rename the associated Local Area Connection. Any solution you find will be teaming independent. Meaning, I recommend looking for a way to script the renaming of any local area connection - teamed or untea med.
That being said, NETSH may work for you. I recommend searching for "rename" within this document. I haven't personally tried what it suggests, but it may work for you.
http://msdn.microsoft.com/library/en-us/dnxpesp1/html/tchWorkingWithNetshInWindowsXPEmbedded.asp?frame=true
Regards,
-sean
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP