Reading your posts again, it seems like this would be a good starting point for you - here's the mods I'd consider:
It might be better to move the files interactively, rather than on the back end.
Modify the Move line so the destination path is your common share instead of the original folder. My method is a simple rename, but you can actually move the file by specifying a new target path. The PST files will all have the format "USERID_originalname.PST", which should work well if they are all in a common folder.
Don't run the Disassociate command - instead, update the path in the registry to reflect the new path and file name. Actually, you might want to update the registry with the new path, export the registry key, then delete the key. This will prevent outlook from opening the file while it is moved. Once the move completes, you can import the reg key and Outlook will find the PST in its new location the next time it starts.
You can eliminate the log, or place the log on the local system to aid in troubleshooting, rather than using a central logging folder.
You can update the script so if the PST file is already in the new location, simply exit.
Keep in mind that users may have very large PST files, and it could take several minutes to several hours to copy, depending on size and network speed. (copying a 3Gig PST over a 256K Frame Relay link can take a LONG time!) The user will not be able to access the PST during this time.
Hope that gets you a start in the right direction.
Glenn
_________________________
Actually I
am a Rocket Scientist!
