I have a domain network that has 3 VMs running on Hyper-V 2012. 2 Servers are 2003--one of which is a AD, DHCP, File server and the other 2003 server runs SQL. The 2012 will eventually replace the first 2003, and it too has AD, DHCP, DNS, and the admin interface for our network anti-virus. All 3 servers have been running OK without any issues for about 3 months now. This past long weekend all systems were turned off and then turned back on this morning. Now the 2012 server is having network identification issues. Initially it started up and connected itself as a PUBLIC network--that caused all kinds of problems since the windows firewall settings for public would not allow most client connections to it. So I went into gpedit on that server and changed the network ID from public to private (see attached word document). That solved some but not all of the problems since the Windows firewall still sees it as a PRIVATE network and not a DOMAIN network which still is causing issues with some programs and client connections which still are not been allowed. So how and where do I change what to get the server to see itself on domain network like it was before this weekend?