
It was 164 years ago when the Atlantic Telegraph Company started the expedition that wou. We made it, Friday is here! Before we talk about what's going on today, let's think for a moment about how we got here.
Applocker windows 10 windows#
Our domain is running server 2008, with a secondary DC on Windows server 2016. The policy is set to start the ApplicationIdentity service, and every time I check, I it is running with an "Automatic" start-type. EXE file in the %ProgramFiles% folder(s), even though my test rules are set to block that behavior. No matter what I try, the rules are ignored, and when I'm logged in as a regular user, I can open up any. So I created a test AppLocker policy in our production domain, and applied it to a single OU for testing.

There, I had similar problems initially, but AppLocker immediately started working once I enabled the Application Identity service on the target machines. Originally set up an isolated environment with its own AD domain. I'm tearing my hair out trying to get AppLocker to work on our new Win10 workstations.
