Please forgive me if this has already been answered. I searched and did not find my exact issue. I have an attribute called employeeStatus that was flowing from AD as follows: However, now new accounts are created with a new MA. When the AD account is flowed out, then an import is run, this flow has a value of [Unchanged] This is my attribute precedence for employeeStatus: 1: ADMA 2: NewHireMA Use Equal Presedence is UNCHECKED. The ADMA CS object has userAccountControl of 512 The MV employeeStatus is set to "new". What am I missing? This was working when I was creating accounts in AD. Alex Trusler Systems Engineer

Have you verified that the synchronization rule is being applied to the object with the Expected Rule Entry? Thanks, Sami

Only my outbound rules are Expected. This is an inbound rule. Do I have to explicitly add them to an inbound rule? It used to work.Alex Trusler Systems Engineer

Mine looks a little different but it's working fine.

Sometimes I've had to do a full sync to get changes in SRs to apply, but not sure if that applies in your situation... This post also has some helpful information that may aid you: http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/e1cc0e39-2735-4bce-b2bf-5f607073cb3e

Full sync is what I've been trying. I also created an account in AD and it also doesn't import. And here is the object created in the MV: It's missing everything from the rule. I tryed diconnecting and doing another full import. Everything is in the AD CS but nothing gets synced.Alex Trusler Software Developer

Is it possible for an inbound sync rule to just stop working altogether? It finds no changes, but the data isn't synced. I'm rebooting then calling support. This is weird.Alex Trusler Software Developer

That warning triangle on the provisioning summary node indicates something is wrong. What's the error?My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

Reboot fixed it. I'm embarrassed. Alex Trusler Software Developer