I'm in the middle of migrating all clients to a new site. I've migrated applications, packages, Task Sequences etc. along with their respective deployments. I obviously dont want the clients to re-run the deployments that have been migrated over and as far as I know, since they were migrated using a migration job, that shouldn't happen. The issue is that we use Anders Rodland's Client Health script, and if the cleint hasn't changed site codes using the vbs script we will be deploying, it will detect that the client is in the wrong site and re-install the client with the correct settings for the new site. If this happens will all deployments re-run? Almost all deployments are Applications, so if that happens they should just detect the app and stop, but it could be a real problem if the TS's or Software Update deployments re-ran. Any thoughts?