Hi, We're looking to merge our networks in summer and part of this will be to build a new SCCM server. However before we merge we need to re-image ~200 PCs using our old servers due to the project timescale. If I image them as normal with SCCM installing the client at the end of the Task Sequence what would be better? a) set site code to AUTO, will it then pick up the new site code when I install the new SCCM instance and join the machines to the new domain? b) set the site code manually to the code I've chosen for the new SCCM server, then they should pick up once they join the new domain? Thanks :)

It will not pickup the site code automatically when you build the new site no matter what you do. Plus see this: http://blogs.technet.com/b/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspx John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

you will need to reassign the clients in to the environment. It's not a problem and can be done by running a package/script. When you configure the new site, you can use the old as a child site until all clients has been migrated. Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

In which case might I be better off disabling the client installation step and just doing a push install from the new SCCM server once it's up and running?

In which case might I be better off disabling the client installation step and just doing a push install from the new SCCM server once it's up and running? In a couple small environemnts where I moved customers clients from one to another I advertised ccmclean from the old server then pushed the client from the new server. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|