Additionally on Windows XP Professional with at least SP2 and Windows Server 2003 with at least SP1 this policy setting also allows SVCHOST.EXE and LSASS.EXE to receive unsolicited incoming messages and allows hosted services to open additional dynamically-assigned ports typically in the range of 1024 to 1034. Services typically use these ports to communicate using remote procedure calls (RPC) and Distributed Component Object Model (DCOM).
To do this Windows Firewall opens TCP ports 135 and 445.
Touching each machine by hand to make the changes is something that nobody here has time for.Allows remote administration of this computer using administrative tools such as the Microsoft Management Console (MMC) and Windows Management Instrumentation (WMI). 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)
