I understand the security implications but in a proper environment where a firewall should prevent ping from outside the network and administrator access is needed to use management tools like Remote Registry, the hidden admin share (C$), and Computer Management of another computer, the policy change should be relatively safe while allowing more predictable remote access. That is why it’s surprising to see the default setting has this turned off. Being able to see if a computer is powered on or on the network with a simple ping is a basic function. Fortunately, it’s pretty easy to turn them on for your environment. Unfortunately, some basics are turned off by default. Touching each machine by hand to make the changes is something that nobody here has time for.One of the benefits of having computers joined to a domain and within a local network is the ability to manage things over the network pretty easily. This will be an easy problem to fix going forward with new images, however I have some support personnel that would like to begin utilizing this feature now if possible. What I would like to know is if there is a way to check that final exception using Group Policy.įYI, I've tried the method by using 'netsh firewall' and 'netsh advfirewall' commands in the startup scripts section under Windows Settings as well as the login scripts section under user configuration, but neither worked. If you manually check that exception, everything works. This is from my own workstation where it is checked but there is a good amount of users where their's are unchecked). Even with those policies set, I still have a "Remote Assistance" exception in the windows firewall on the client machine unchecked. I have setup all of the remote access policies under Administrative Templates -> System -> Remote Assistance AND Administrative Templates -> Network -> Network Connections -> Windows Firewall -> Domain Profile. The main exception is "Remote Assistance" and here is what's happening. I am trying to enable some firewall exceptions on our Windows 7 clients using group policy.
0 kommentar(er)
