Problem with Case Sensitive String type in AD
I have three custom attributes in my Active Directory schema that are of type "Case Sensitive String." With MIIS 2003 and ILM 2007 (incl FP1) these didn't cause a problem. But FIM is seeing these as type "Binary," which means I can't do a Direct export or import on them like I did in the previous versions.
Case Sensitive String is a valid type in AD -- why would FIM want to treat these as binary?Ed Bell - Specialist, Network Services, Convergys
March 27th, 2010 12:06am
Ed,please file a bug in conjunction with this via connect.Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation
Free Windows Admin Tool Kit Click here and download it now
April 15th, 2010 7:52pm
I entered an Incident through our Select Agreement. A QFE has been entered for this issue.
Thanks!Ed Bell - Specialist, Network Services, Convergys
April 21st, 2010 6:37pm