AD Connect Filter not working
We're testing the AD Connect filtering before using it in production environment. The goal is simple, filtering by user's attribute setting, so we followed this article https://social.technet.microsoft.com/wiki/contents/articles/54333.azure-ad-connect-customize-sync-options.aspx Using CASE3 So we created a Catch all rule that blocks all users to be synced and a rule with higher priority that should sync only users with specific attribute set. However it simply doesn't work, the rule that gets applied is the catch all I double checked the rule that should enable the sync of some user and looks correct but cannot find why is not working thanks Nobody from MS eager to help ?
AD Connect installed in different forests
Hello friends, I have an AD Connect synchronized with my forest (companyA.local) with UPN (company.com) that is in the datacenter. I now want to install another AD Connect to synchronize another forest (companyB.local) with UPN (company.com) that is in my office. It is possible? If this is not possible, is it enough for me to remove AD Connect synchronized with my forest (companyA.local) to enable the other one in the forest (companyB.local)? Is there a procedure for removing this synchronization? Thanks.
Office 365 and AD Connect to On Premise AD
Our organization began with the Office 365 product and we have now installed an on-premise Domain Controller with AD DS. There are no users created in the on-premise AD yet. If I run AD Connect, will it create the users that currently on Office 365 on the on-premise AD? Thanks