I have a compliance requirement. All new server objects must be added to X policy filtering group in 3 of our AD's
I have workflow setup - to detect a computer created under domain\Xservers (for which there are sub OU's for IIS/SQL/FILE/SharePoint ... etc
I want to filter out further processing on any new computer creation executed in the SharePoint OU.
Everything fires off fine - except the filter. Unless I'm misunderstanding filters ... the workflow checks for new creation under the XServers OU and only begins the if/then policy blocks defined in the GUI - if it's under XServers AND not in a sub OU named SharePoint ...
Regardless of which path property of the target object I evaluate, SharePoint servers end up in the group like the other WinServers do.
Ideas on how to prevent the workflow from continuing past the initiate 'create' trigger - based on a word in the directory path to the object?