WesJones

We have been moving child primary sites from our old central site to our new central site. In both central site infrastructures, we create and manage our software deployments from the central site, to include the update lists. In the process of moving one site, I missed checking and making sure the old central site update lists were removed before disconnecting the child site from the old central site. The move has now been completed, all looks good, except now the old central site update lists are locked and can't be removed. I realize that the update lists are now "orphaned" and I am probably going to have to use a SQL query to clean up the SQL database, just wanted to find out if anyone else has dealt with this and has a query to clean up the SQL database. Thanks, Wes Jones

Yep, but not by choice. I was thinking about just adding a run command line step in my hardlink TS, using xcopy to copy the the statestore share off the local drive to a network share. Any thoughts on this?

Hey guys, anyone ever backed-up users data using both the network SMP share and hardlinking in the same task sequence(TS)? Reason I ask is that I am getting ready to finish up my pilot deployment for migrating machines from Windows XP to Windows 7. We are using SCCM 2007 R2, USMT 4.0. Everything works great using SMP or hardlinking, and I wanted to use hardlinking for our production deployment. However, management...won't go into this, but they have decided they want to use both for extra data security. Any ideas? I currently have two separate task sequences I have been using in our lab environment; i.e., hardlink and SMP. Any thoughts on how to do this would be appreciated. Thanks!