That was it...thanks for your help, Carol!

Thanks for the input, Carol. I manually ran scripts, and saw nothing logged in the Operations tab of the Sync Service GUI. I re-generated the script from the run profile, and simply ran it in a command prompt, and it behaved as expected, but did pop up the acknoledgement boxes (i.e., "Running ADMA-DeltaImport"). It seems that when these Echo's are listed, the scheduled task doesn't complete as it expects the acknoledgement. So, I tried "rem"-ing them out, but I see that it breaks the script--nothing happens when it's run. How do I get these scripts to run in a scheduled task without the Echo pop-ups? The action I've got listed in the task is as follows: Run Program: c:\windows\system32\cscript Arguments: "C:\FIMScripts\ADMA-DeltaImport.vbs" Am I setting up the scheduled task incorrectly?

You should set the scheduled task like this: Run Program: cmd.exe Arguments: /c cscript.exe "C:\FIMScripts\ADMA-DeltaImport.vbs"http://www.wapshere.com/missmiis

Greetings, all. I've got a question on automating MA's through scheduled tasks. In an attempt to keep FIM updated automatically, I've created four scheduled tasks, running in this order: 1) ADMA-DeltaImport 2) ADMA-DeltaSync 3) FIMMA-Export 4) FIMMA-Delta Import I've exported the .vbs script from each of the (properly functioning) run profiles, and then created Windows scheduled tasks for each, using cscript to run them. They do run without error, but they aren't actually doing their jobs. Specifically, a test user created in AD does not show up in a MV search after the scripts run. So what am I missing? Thanks for your help!

For reference, here's the text of my ADMA-DeltaImport.vbs: Const PktPrivacy = 6 rem Const wbemAuthenticationLevelPkt = 6 Set Locator = CreateObject("WbemScripting.SWbemLocator") rem rem Credentials must only be specified when Microsoft Identity Integration Server is on remote system. rem rem Locator.Security_.AuthenticationLevel = wbemAuthenticationLevelPkt rem Set Service = Locator.ConnectServer("MyServer", "root/MicrosoftIdentityIntegrationServer") rem Set Service = Locator.ConnectServer("MyServer", "root/MicrosoftIdentityIntegrationServer", "Domain\Me", "MyPassword") rem Set Service = GetObject("winmgmts:{authenticationLevel=PktPrivacy}!root/MicrosoftIdentityIntegrationServer") Set MASet = Service.ExecQuery("select * from MIIS_ManagementAgent where Guid = '{79991072-1D36-471A-9779-3A6AA7EC7E12}'") rem for each MA in MASet rem WScript.Echo "Running " + MA.name + ".Execute(""Delta Import"")..." rem WScript.Echo "Run completed with result: " + MA.Execute("Delta Import") rem next

Thanks, Carol. Still no luck...I am also using a service account to run the script, which I've made a local admin on the FIM server. It appears as though I'm unable to run the script though a command line as that service account. Does FIM have some way to manage the users that can run run profiles or anything like that?

The job of these scripts is to run run profiles - whether or not an object turns up somewhere as a result depends on how you've configured your rules. So to see if the scripts are actually working, run one of them and then check the Operations tab in the Sync Service GUI.http://www.wapshere.com/missmiis

The service acount must be a member of the FIM Sync Admins grouphttp://www.wapshere.com/missmiis