Hi There,I am a bit new to both SMS and SCCMThis is our current situation:We have a SMS installation which is a total mess, we don't want to migrate any settings, packages or collections. The only thing currently being used are the remote tools. We have used it to deploy software but not worried about the packages. No boundries setup, Schema extensions was done with previous implementation.I have a second server and ran a clean installation of SCCM 2007 R2, SP 1. I have setup discovery to one OU with a few test machines in the OU. I have done schema extensions for SCCM2007, but I removed the option to publish to AD and also haven't provided access to the computer account to publish. Now my questions are: What will the effect be if I enable the schema for SCCM to be published and I remove the SMS setting to publish. Will the current clients change to the new sccm server, or do I need to roll this settings out with a custom client installation. And which option would be the best? I am not sure what to do here. I just don't want the remote tools to stop working until I am sure sccm 2007 are working properly before I roll out the new client and change the server location

Hi,You need to reassign the old SMS clients to the new site. That wont happen automatically. You can use this procedure1) Remove the Boundaries in the SMS 2003 site2) Add the boundaries to the new ConfigMgr site3) Run a script to reassign the package (I have used this package http://myitforum.com/cs2/blogs/cstauffer/archive/2009/03/06/sccm-migration-change-site-code-exe-style.aspx)4) Clients will now be assigned to the new site and be visible in the ConfigMgr. console. From here you can create a package to upgrade the SMS client to ConfigMgr.You should extend the Schema it's fully supported and will work with SMS 2003. Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

What will happen though with SCCM and SMS both published to AD. Also is it not possible with a client push and upgrade installation to re-assign the clients to the new site and then decommision the old SMS site?

Yes you could just get rid of the old site and remove it from AD, discover the clients and push out the new client. Just be aware that automatic client push will fail because it will see the old client is installed and it won't try to install. You have to use manual client push. I personally would send out a package of ccmclean from the old sms site before I got rid of it to get the client off as many computers as possible.John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

As long as you don't have any overlapping boundaries you can have multiple sites published to AD without any problems. As John is saying a client push (reinstallation) will upgrade the clients. I like using the swd process because it gives me more control and better reporting options.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

"Yes you could just get rid of the old site and remove it from AD, discover the clients and push out the new client. Just be aware that automatic client push will fail because it will see the old client is installed and it won't try to install. You have to use manual client push. I personally would send out a package of ccmclean from the old sms site before I got rid of it to get the client off as many computers as possible." John, or whomever might be able to answer this. As far as the manual client push goes, if you push it manually to groups of computer will it remove the old 2003 client software in the process? In other words it won't do it with a automatic client push, but since we only have around 350 client machines, doing 3 or 4 groups and pushing it manually would do the trick and leave no remnants of the old client software? Also, will the CCMCLEAN.EXE remove it from all clients it see's or do you get an option of only removing from some if you would like to test some machines? Thank you very much. -Scott