tag:blogger.com,1999:blog-1117496458526737084.post5249534962834386333..comments2024-03-16T02:45:40.540+10:00Comments on AnonIT: Change the Network Location in Server 2012 R2AnonIThttp://www.blogger.com/profile/06870397873107318020noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-1117496458526737084.post-54907745832169986272016-12-30T07:36:12.958+10:002016-12-30T07:36:12.958+10:00Sorry, but this is not helpful since servers have ...Sorry, but this is not helpful since servers have ALWAYS to be joined to Domains. Waste of time in many blogs.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1117496458526737084.post-79119007330025144072016-12-17T09:50:40.532+10:002016-12-17T09:50:40.532+10:00Since the last batch of Windows Security Updates N...Since the last batch of Windows Security Updates Nov\Dec 16' I have the following issue:<br />The Network Profile via the GUI or PowerShell shows DomainAuthenticated\Domain Network.<br />The problem is that Windows Firewall Profiles show Public for the only connection I have...the domain one.<br />When I attempt the Network List Manager Policies for my domain in Local Group Policy, there is no Network Location tab.<br />So even though I'm clearly on a domain and being authenticated and can reach a domain controller and Forest PDC via 389, my Windows Firewall stays set at the more restrictive Public profile.<br />I've restarted NLA and also set it to Delayed Start with no effect.<br />Help?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1117496458526737084.post-72362859663531878992016-12-17T09:49:33.175+10:002016-12-17T09:49:33.175+10:00This comment has been removed by the author.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1117496458526737084.post-27302389845939289832016-12-17T09:44:25.241+10:002016-12-17T09:44:25.241+10:00This comment has been removed by the author.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1117496458526737084.post-2660285490195413542016-05-19T20:05:15.490+10:002016-05-19T20:05:15.490+10:00Does not work for me
Does not work for me<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1117496458526737084.post-31334536239486074742015-02-13T07:10:14.399+10:002015-02-13T07:10:14.399+10:00Thanks, I agree ... sometimes for a one off change...Thanks, I agree ... sometimes for a one off change on one machine, the GUI can be quicker and easier.AnonIThttps://www.blogger.com/profile/06870397873107318020noreply@blogger.comtag:blogger.com,1999:blog-1117496458526737084.post-82750715628327173132015-02-12T18:09:27.150+10:002015-02-12T18:09:27.150+10:00This is better then powershell for many mixed netw...This is better then powershell for many mixed networks on server :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1117496458526737084.post-29170429863126033352014-07-31T14:28:26.586+10:002014-07-31T14:28:26.586+10:00I found a link on how to do the same thing by Powe...I found a link on how to do the same thing by Powershell:<br />http://blogs.msmvps.com/russel/2013/12/29/set-network-location-to-private-in-windows-8-1server-2012-r2/<br />AnonIThttps://www.blogger.com/profile/06870397873107318020noreply@blogger.comtag:blogger.com,1999:blog-1117496458526737084.post-34688003967577041832014-07-11T06:51:23.188+10:002014-07-11T06:51:23.188+10:00Your welcome.Your welcome.AnonIThttps://www.blogger.com/profile/06870397873107318020noreply@blogger.comtag:blogger.com,1999:blog-1117496458526737084.post-42621015410836390952014-07-11T06:49:34.561+10:002014-07-11T06:49:34.561+10:00Thanks for posting this. I used the PowerShell app...Thanks for posting this. I used the PowerShell approach previously but this works as well and not all things GUI are bad.Anonymousnoreply@blogger.com