I have a MOSS 2007 environment, where the SSP does not import profiles from AD. The schedule is set up and looks correct, but the only way I can run the import is by starting it manually. I've read through several posts and there is one fix I would like to try, but I still need to understand it better (since this is a production environment and I can't replicate it in a dev- or test environment). I ran stsadm -o sync -listolddatabases 10 got a list of four entries. Something like this: Service Provider xxx SSP <GUID> Synhronized: 3/3/2012 ... ... Now I read that this could be fixed by running -deleteolddatabases <days> and that is has something to do with deleting entries (and not databases). However - 1. Is this really a safe command to issue? I.e. executing a command with text like "delete" and "databases" in a production environment makes me want to triplecheck... 2. How could this solve the issue with the profile import? I mean - is there more steps after this or does the delete command simply restore synchronization and everything is fine? If anyone has alternatives for solving the issue I would love to hear about it!

From the sync stsadm operation page: Parameter Value Required? Description listolddatabases A valid number of days, such as "2" Yes Lists content databases that have not been synchronized since n days. The presumption is that they have been deleted or moved. deleteolddatabases A valid number of days Yes Performs the same operation as the listolddatabases parameter, except it deletes old records corresponding to these databases. It does not delete the databases themselves. The -deleteolddatabases parameter does not delete the databases, it only removes the old records from the database (the specific table and records I do not know for this information is not published). Provided you run the sync operation with the -listolddatabases and -deleteolddatabases using the same number of days, deleteolddatabases will only remove the records that listolddatabases outputs. Jason Warren Infrastructure Specialist Habanero Consulting Group habaneroconsulting.com/blog

Yes, but I'm not entirely sure if this is the correct thing to do or not. I mean, if you get databases out of sync listed with the listolddatabases command is it always the fix to run deleteolddatabases, and are there cases where you should'nt do it?