Here is the scenario.I have a environment where I installed FIM Eval (box1). Then Update 2 and then Update 3. I am confident that all the upgrades went smooth but I suppose I could have missed something, anyway.I have a new server with a freash install from Update 3 only (box2). Install went smooth with no issues.I perrformed a schema only Export on box1I am trying to import the schema only (havent got to the portal and policy yet) on box2. Most of my changes made it through. In fact I think all of my cusomization made it through. I think I have narrowed it by doing some queries on the FIMServce DB. The offending object in the Undone_schema file is 1b364ece-d609-461f-a365-9b3ebfb6ba16. there are two other objects but I think they are dependency.When I look this object up using the objects table to get the objectkey and then looking in the attributes view i see that it is MailNickname. in the xml it appears to trying to update the attribute validation. - <ImportChange> <Operation>Replace</Operation> <AttributeName>StringRegex</AttributeName> <AttributeValue>^[^@ ]{1,64}$</AttributeValue> <FullyResolved>true</FullyResolved> <Locale>Invariant</Locale> </ImportChange> on the new box (box2) in the BingingInternal table the validation appears to be this^(?=[^\.])+(?!.*(\.)\1+.*)+(?=.*[^\.]$)+[?=!#%&'=`~\$\*\+\-\/\?\^\{\|\}a-zA-Z0-9_\u00A1-\u00FF\.]{1,64}$So at this point it is assumption, because I never changed that attribute validation nor do I think I can very easily, that this is a FIM issue. I have not tried to re-produce this error because of the time involved but I am curious what the real value is supposed to be since both boxes are at update 3.any thoughts would be appreciated.Paul

If I recall correctly, we updated one of the binding descriptions for mail nickname in the update 2 or update 3 timeframe (I'm sorry I don't know off the top of my head). This looks like the config migration tool is picking up the difference and trying to migrate the change to box 2. The fact that it's picking up a difference seems to be a problem with the upgrade process. The fact that config migration cannot push the new value is due to fundamental system constraints on resources which are considered protected. I believe the regular expression of mail nicknames is considered protected.So, in short, I would ignore the undone import for now. Thank you for reporting.