I have used FileSystemWatcher for a few script to monitor the filesystem. It is working correct. Only haeavy loads can be a problem because of a buffer overrun. A few useful tutorials I used:
https://mcpmag.com/articles/2015/09/24/changes-to-a-folder-using-powershell.aspx
http://www.mobzystems.com/code/using-a-filesystemwatcher-from-powershell/
Some more information about de buffersize:
https://msdn.microsoft.com/en-us/library/system.io.filesystemwatcher.internalbuffersize(v=vs.110).aspx
Sunday, June 10, 2018
Saturday, June 9, 2018
Microsoft: Windows 10 version 1803 - Broken Policies
Windows 10 version 1803 has some problems with policies. Keys locations or values are changed. So if something is broken, check your policies and de keys they change. I found an example of one of them here:
Microsoft broke "disable web search" in Windows 10 version 1803
Windows 10 users and administrators who plan to upgrade devices running the operating system to Windows 10 version 1803, the Spring Creators Update, need to be aware that certain policies are broken currently in the new version of Windows 10.
In particular, the policy "Do not allow web search" has no effect when enabled on the device. The initial version of Windows 10 combined local search functionality with web search functionality when it came out.
Search results displayed local results, for example files or preferences that match the search term, and suggested web search results. These suggestions were pulled from Bing and loaded the results page on Bing in Microsoft Edge when selected.
Another problem I found was with the site list in Edge to open websites with IE 11:
I don't have a solution yet, but it is a problem with the changed policies.
Subscribe to:
Posts (Atom)