Setting Network Location to Private

re: Setting Network Location to Private

Abhishek Agrawal — Fri, 03 Apr 2009 12:28:13 GMT

Why is the script using reg.exe tool and not the registry provider???

It hurts my eyes to see a script with /param syntax on the powershell blog :-(

Thanks,

Abhishek Agrawal

re: Setting Network Location to Private

Jason Archer — Fri, 03 Apr 2009 19:52:25 GMT

Cool, but two questions.

1) Why the need to reset those registry keys?

2) Why not use PowerShell commands to set those registry keys?

NETWORKING-THE.INFO |

NETWORKING-THE.INFO | — Sat, 04 Apr 2009 02:13:52 GMT

PingBack from http://www.networking-the.info/2009/04/02/windows-powershell-blog-setting-network-location-to-private/

re: Setting Network Location to Private

Blake Coverett — Sat, 04 Apr 2009 13:54:49 GMT

Wow... when would it ever be appropriate for some random COM client code to decide to re-register some other COM server's progids??

Am I missing something here?

re: Setting Network Location to Private

required name — Sun, 05 Apr 2009 09:43:32 GMT

could you clarify a bit ... is that ACTIVE public connections or ANY at all (e.g. disconnected wifi from the hotel you stayed at) that will cause remoting to be disabled?

re: Setting Network Location to Private

remoting question — Mon, 06 Apr 2009 09:04:44 GMT

>> You cannot enable and use Windows PowerShell Remoting feature if you have Public connections on your machine

Does this mean I can't use it as a remoting client? Or this restriction is only for remoting server.

re: Setting Network Location to Private

PowerShellTeam — Thu, 09 Apr 2009 18:54:59 GMT

@ Abhishek an Jason,

Thanks for your feedback. I have fixed the code which creates the registry settings.

Vladimir Averkin

Windows PowerShell Team

re: Setting Network Location to Private

PowerShellTeam — Thu, 09 Apr 2009 19:04:08 GMT

@ Blake

NetworkListManager does not have ProgID and Windows PowerShell needs ProgID to be able to call on COM-objects. That's why we have to create it.

Currently, NetworkListManager COM API is the only way to programmatically change Network Location type. And I guess using Windows Powershell script is much better option than writing, compiling and distributing a C++ program.

Thanks,

Vladimir Averkin

Windows PowerShell Team

re: Setting Network Location to Private

PowerShellTeam — Thu, 09 Apr 2009 19:11:33 GMT

@ Remoting question

You are right, this requires some clarification. Enabling remoting means configuring Windows PowerShell and Windows Remote Management (aka WinRM) so that the local machine could be used as a remoting server. Client does not require any specific configuration, it only requires Windows PowerShell 2.0 and Windows Remote Management 2.0 to be present on the machine.

Thanks,

Vladimir Averkin

Windows PowerShell Team

re: Setting Network Location to Private

Blake Coverett — Fri, 10 Apr 2009 03:06:19 GMT

new-object needs a progid, but that doesn't mean PowerShell can't create COM objects by CLSID. In this case you can simply use:

[Activator]::CreateInstance([Type]::GetTypeFromCLSID([Guid]"{DCB00C01-570F-4A9B-8D69-199FDBA5723B}"))

Well, perhaps it isn't simple, but it is certainly better than leaving random new progids in the registry.

re: Setting Network Location to Private

PowerShellTeam — Fri, 10 Apr 2009 20:04:40 GMT

@ Blake

Brilliant! You are absolutely right! Somehow I was focused on how to do it through new-object and totally missed that there is a .NET way to create instances of COM objects, which can also be used in Windows Powershell. I have updated the script with your code.

Thanks,

Vladimir Averkin

Windows PowerShell team