He made a routine addition to the firewall rules, but when he closed the policy editor On Tuesday, one of our admins (running Windows 8.1) was troubleshooting an application issue with a desktop support tech, and sharing his screen to the tech via Lync. Workstations running RSAT without any issues, and until recently, this held true for edits performed on Windows 8.1 / GPMC as well. ![]() This policy was routinely edited on Windows 7 圆4 Since we deployed Windows 7, we have used AppLocker executable rules and Windows Firewall incoming traffic rules (defined in a Group Policy object) to restrict applications on our production workstations. ![]() ![]() We ran into a weird and disturbing issue in production this week, wondering if anybody has seen this before and/or can help us find root cause.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |