From: V@nguard.LH   
      
   VanguardLH  wrote:   
      
   > winston  wrote:   
   >   
   >> VanguardLH wrote:   
   >>   
   >>> I can go into Control Panel -> All Control Panel Items -> Network   
   >>> Connections, and rename a connectoid.  However, that only changes the   
   >>> InterfaceAlias attribute of the connectoid, not the Name attrib.  When I   
   >>> run the following command in PowerShell (admin):   
   >>>   
   >>> get-netconnectionprofile   
   >>   
   >> Change the name attribute in the registry.   
   >>   
   >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersi   
   n\NetworkList\Profiles   
   >>   
   >> Inspect each GUID folder for your respective network name   
   >> Modify the ProfileName string value   
   >> Close the registry editor   
   >> Restart the device   
   >>   
   >> Note: You may find a variety of no longer applicable/orphan network   
   >> profiles(including some with same description and profile name   
   >>   - Caution: Unless you know what you are doing, best not the delete any   
   >> suspected orphans until absolutely certain doing so is safe and without   
   >> impact.   
   >   
   > Thanks for that info.  Went there, and found the profile names,   
   > including one with the 2.4 GHz wifi name (and another with the 5 GHz   
   > wifi name).  Yeah, some have oddball names, but I'll leave them for now.   
   > Later I'll hunt around to find any matching names to determine if there   
   > are any dependent entries in the registry, or elsewhere.  MS should have   
   > provided a user config option to rename, but maybe they figure not   
   > somewhere typical users should tread.   
      
   Got time to address this issue.  What you mentioned worked.  There were   
   2 network profiles that had the names of the SSIDs in the wifi cable   
   modem, but they were actually RJ45 Ethernet wired connections as ports   
   on the backpanel of the computer.  I renamed both of them: HomeEther1   
   (connected) and HomeEther2 (not connected).   
      
   I'm not yet using the 2nd one (unconnected), and probably won't as I   
   don't need to bridge through this desktop to another segment in my   
   intranet nor have my desktop PC act as a router or firewall to other   
   intranet hosts.  The mobo had other features that I wanted, and happened   
   to have 2 Ethernet ports (for bridging, I guess).   
      
   I didn't delete any of the other network profiles.  A couple were for   
   Proton VPN.  Didn't know what the other few were for, and was not   
   interested in hunting them down.   
      
   Thanks again.  Renaming the network profiles makes it far more clear to   
   which I'm connected.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)