G
Guest
Greetings, all!
I have a GPO linked to a test OU for Windows Firewall. The GPO enables the
remote administration exception on all networks (*) when the computer detects
its domain. When I place the computer inside this OU and perform a GPUPDATE
/FORCE /BOOT, the firewall does turn on but I can't use the Computer
Management snap-in to administrate the computer, using its name or its IP.
When I move the computer out of my test OU and perform another GPUPDATE
/FORCE /BOOT I can use the Computer Management snap-in to manage the computer.
Is there a setting that I am enabling which is negating my exception or some
other similar problem?
TIA,
- S
I have a GPO linked to a test OU for Windows Firewall. The GPO enables the
remote administration exception on all networks (*) when the computer detects
its domain. When I place the computer inside this OU and perform a GPUPDATE
/FORCE /BOOT, the firewall does turn on but I can't use the Computer
Management snap-in to administrate the computer, using its name or its IP.
When I move the computer out of my test OU and perform another GPUPDATE
/FORCE /BOOT I can use the Computer Management snap-in to manage the computer.
Is there a setting that I am enabling which is negating my exception or some
other similar problem?
TIA,
- S