I am brand new to FIM and I am having trouble getting my first AD's to sync. I built up the machines following the Installation Guides on technet. I may have missed something of course. I reviewed the virtual lab and compared a lot of settings as well as did the lab. I watched this video http://technet.microsoft.com/en-us/forefront/ff182885.aspx and set up the rules as I saw best matched my domain. I tell you this so you know I am not totally guessing at this :). Here is what my server is doing. The data in my portal syncs to the metaverse and shows up there when I search the metaverse. The data from my AD ou syncs to the metaverse and shows up there when I search the metaverse. A new account created in the AD syncs into the portal but has no information and shows (No Display Name) each time I create a new AD user I get another one. If I create a new account in the portal server it does not sync back to the AD but it does sync into the metaverse. If I delete an account in the AD it doesnt remove the (No Display Name) that corresponded to it. If I delete an account in the portal nothing happens because it never synced it into the ad anyways, it does remove it from the metaverse. So I am not sure where to look and make a change to fix this problem . I have rebuilt my agents, workflows, management policies, and my syncronization rules 4 times now, the last time I brought in our AD administrator to make sure I was making good selections, however he too has never run a product like FIM so he is unsure on where the failure is occuring. I could use some help this would really be a big deal for me to get working. We want to test this product to see if we can sync our two forests and get free busy time... before i can even look at doing something liek that I should be able to create and remove AD units. Thanks in Advance

Welcome to the FIM forum, Loren. Here are the doc versions of these scenarios. You are actually better off starting with the Getting Started Guides that are mentioned in the How Do I Guides to get a better understaning of how the synchronization process works. If attributes are expected to be populated but don't show up, you should look into the attribute flow precedence configuration. You can get a good understaning of how deletions are processed from Understaning Deletions. You should also take a look at FIM deprovisioning approach and sync rules and Synch rule deprovisioning. Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Alright I will read all of this tomorrow then give it a shot again. thanks for pulling together a list of documentation for me. phew im gonna be busy tomorrow :)

I have spent some time reading the above documents. I have tried setting attribute flow precedences. I have tried adjusting deletion processes. I was not able to gain anymore functionality that I listed above. I decided to build a new all in one FIM server instead everything installed clean and I ran the updates. While reading the above posts I found a link to a basic File MA import. I dont think things could be any simpler than this example. http://technet.microsoft.com/en-us/library/ee534911(WS.10).aspx I am pretty sure I followed everything in the document. When I got to the following part the result did not match what was expected. The following step: Synchronizing the scenario user inside the FIM Synchronization Service In this section, you project the scenario user into the metaverse and you provision the scenario user into the connector space of your FIM Service management agent. After a successful full synchronization on the Fabrikam FileMA, the synchronization statistics report the following: One projection One connector with flow updates One provisioning adds One export attribute flow What I got: I did not get those results however instead all I got was One disconnectors I was hoping I could get a very specific response on what I might have missed to have the results so different. If there is something even more introductory than that "Introduction to Inbound Syncronization" that helps preconfigure the FIM to be ready to do that Introduction to Inbound Syncronization let me know and ill go follow that guide. I cave learned a lot reading your documents, I have learned at least 10 ways not to do it. However with out having a single successful sync I am having a hard time thinking thru this issue. Thanks Loren

Ok so I got somewhere now. I did not know that if you delete an agent after you create a sync that you need to delete the sync and recreate it. Initially I created my fileMA but didnt select the right file. I had then created the sync and when I did the initial sync it found nothing (wrong file). I noticed the file issue and recreated the Filema and did another scan and this time it found 1 add so I thought I was back on the road of success. However the sync I had created was now broken so when I told it to sync it just disconnected the stuff I imported because it didnt know what to do with the data. I then recreated the sync, and did all the runs again and this time it worked as intended. I think im ok again and will post back here if I get stuck. moving on to other parts of the guides you originally posted.

I rebuilt the server once again to straighten out some other issues I think inherited by inexperience on my first build. At this point I am able to import from the AD and Export to the AD. However I get errors when exporting on the FIMMA. When I built the server automatically the admin account I am logged into and the built in administrator accounts are automatically created as users. They imediately show up before you even create an agent. When I do a export I get failed-modification-via-web-services for the account I am logged into the computer with. If I create a new user in the fim portal it will import, sync, export, delta sync with no errors except the one for domain.admin originally created by the fim server when I installed it. If I create a new user in the AD it will import, sync, export, into the fm portal but again the domain.admin account always shows up when I am doing exports. Here is the error: Fault Reason: The endpoint could not dispatch the request. Fault Details: <DispatchRequestFailures xmlns="http://schemas.microsoft.com/2006/11/ResourceManagement" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><DispatchRequestAdministratorDetails><FailureMessage>Request could not be dispatched. Exception: Other Stack Trace: Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---&gt; System.Data.SqlClient.SqlException: Procedure or function 'GetDomainConfigurationIdentifiersFromDomain' expects parameter '@domainName', which was not supplied. at Microsoft.ResourceManagement.Utilities.ExceptionManager.ThrowException(Exception exception) at Microsoft.ResourceManagement.Data.Exception.DataAccessExceptionManager.ThrowException(SqlException innerException) at Microsoft.ResourceManagement.Data.DataAccess.GetDomainConfigurationIdentifiersFromDomain(String domainName) at Microsoft.ResourceManagement.ActionProcessor.DomainConfigurationSynchronizer.SetDomainConfigurationFromDomain(RequestType request, CreateRequestParameter domainNameParameter) at Microsoft.ResourceManagement.ActionProcessor.DomainConfigurationSynchronizer.Synchronize(RequestType request) at Microsoft.ResourceManagement.ActionProcessor.UserActionProcessor.PreProcessRequestFromObjectType(RequestType request) at Microsoft.ResourceManagement.ActionProcessor.ActionDispatcher.PreProcessRequestFromObjectType(RequestType request) at Microsoft.ResourceManagement.WebServices.RequestDispatcher.CreateRequest(CreateRequestDispatchParameter dispatchParameter) at Microsoft.ResourceManagement.WebServices.RequestDispatcher.CreateRequest(UniqueIdentifier requestor, UniqueIdentifier targetIdentifier, OperationType operation, String businessJustification, List`1 requestParameters, CultureInfo locale, Boolean isChildRequest, Guid cause, Boolean doEvaluation, Nullable`1 serviceId, Nullable`1 servicePartitionId) at Microsoft.ResourceManagement.WebServices.RequestDispatcher.CreateRequest(UniqueIdentifier requestor, UniqueIdentifier targetIdentifier, OperationType operation, String businessJustification, List`1 requestParameters, CultureInfo locale, Boolean isChildRequest, Guid cause, Boolean doEvaluation) at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Put(Message request) --- End of inner exception stack trace ---</FailureMessage><DispatchRequestFailureSource>Other</DispatchRequestFailureSource></DispatchRequestAdministratorDetails></DispatchRequestFailures> at the same time I get this error: .Net SqlClient Data Provider: System.Data.SqlClient.SqlException: Procedure or function 'GetDomainConfigurationIdentifiersFromDomain' expects parameter '@domainName', which was not supplied. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.ResourceManagement.Data.DataAccess.GetDomainConfigurationIdentifiersFromDomain(String domainName)

I worked on the above error some more and I was able to stop the issue by moving the admin account into the fim objects folder, as well as filling in the missing fields such as first name and last name. It then synced and stop giving me the above error with that account.