Technical tips and musings within the End User Computing area
Today I was involved in a particular incident where Windows Updates did its thing and broke something. This time it involved an update for Access, a database program provided by Microsoft, causing specific queries to output that they are corrupt.
Due to its unclear nature at first, I thought I would write a quick blog post and hopefully spare other system administrators from at least some amount of head scratching.
With the release of the Windows 7 and corresponding server operating system, the AppLocker technology has become a quintessential tool for system administrators to utilize. Thanks to it, administrators can restrict or allow end-users to run certain applications based on its publisher value, file path or even its unique file hash, all within an On-premise Domain-wide level. In other words, it is a given implementation within an enterprise environment to further defend itself from the many and various threats that can stem from executing suspicious programs.
In this post however, I would like to share an isolated issue in which an already known application was suddenly blocked by an AppLocker Group Policy and how it being a ClickOnce executable required some creative thinking right on the spot.