Hello All, I need to know wether there are any implications of installing SCCM 2007 SP2 OR R3 into existing SMS 2003 environment completely as a new system essentially mean that the new server would not join the existing site architecture?

Can they run independent of each other? the old one would eventually be decommissioned? thanks in advance.

Hi, SMS 2003 and ConfigMgr can coexist in the same infrastructure, but don't use the same boundaries to avoid the overlapping which can cause you problems. If you plan a side by side migration, you can refer to this link http://technet.microsoft.com/en-us/library/bb632845.aspx Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/

Thanks for the reply. I have gone ahead and installed SCCM 2007 R3. They have same boundaries? I do not know how that is affecting, but I would like anyone to explain? On the other hand, I have gone ahead and installed clients on the machines as well. So, the client machines have both sms as well as sccm clients and they both seem to be working fine, at least, I have tested remote desktop from both SMS 2003 and SCCM 2007 on the same machine and it is working? Can both clients exist on the same machine? They sure are by my experience, but is it a good idea? Also, what could be best way now to install clients on the remaining client machines as client push installation method is enabled and some of the client machines already have the client, but some are missing even after attempting install through wizard. So what could be the best way to install the remaining clients? thanks in advance.

If both SMS 2003 and SCCM 2007 have the same boundaries, then the clients won't know which server to be managed by. Another problem is with PXE booting, when you try to do a network boot, the system won't know which of the servers to contact and you may end up with erratic results. Separating the two servers with VLANs and site bounaries would be best so that they do not get in each other's way. It sounds like you would be better off trying things with a test environment or only a few computers first, and then just do an upgrade. When I implemented SCCM 2007 in my environment, I found that the 2007 client did not always install automatically for many different reasons. For example, we had an old version of symantec that was blocking the installation. We also had computers that were in pretty bad shape that were not installating anything from the network. We ended up getting the bulk of the installations through client push, then the rest were done when we reimaged the machines with Windows 7.

Thanks for the reply. Separating the two environments via VLAN is not possible and I do not have any requirement of PXE Point at the moment. This can be done once the SMS 2003 is decommissioned. Can I still continue to run them together? or should I just remove the boundaries from SMS 2003 so that there is no conflict. Currently, SMS 2003 is only being used to provide remote desktop support to end users? Kindly, suggegst. Is it possible that a client machine can hold both SMS 2003 and SCCM 2007 Clients? What is the best method of installing clients to the remaining machines?

Anyone?

Can I still continue to run them together? or should I just remove the boundaries from SMS 2003 so that there is no conflict. Currently, SMS 2003 is only being used to provide remote desktop support to end users? Kindly, suggegst. Is it possible that a client machine can hold both SMS 2003 and SCCM 2007 Clients? Have you seen my answer ??? Never configure SMS 2003 and ConfigMgr to use the same boundary and as Abraham said and he's correct "the clients won't know which server to be managed by". In plus the SMS 2003/ConfigMgr clients cannot coexist on the same workstation. Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/

Can I still continue to run them together? or should I just remove the boundaries from SMS 2003 so that there is no conflict. Currently, SMS 2003 is only being used to provide remote desktop support to end users? Kindly, suggegst. Is it possible that a client machine can hold both SMS 2003 and SCCM 2007 Clients? Have you seen my answer ??? Never configure SMS 2003 and ConfigMgr to use the same boundary and as Abraham said and he's correct "the clients won't know which server to be managed by". In plus the SMS 2003/ConfigMgr clients cannot coexist on the same workstation. Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/

Thanks for the replies, but there are quite a few confusions that I would want you to guide me through solving it. 1. Now that SMS 2003 and SCCM 2007 R3 are sharing same boundaries, should I go ahead and remove the boundaries from SMS 2003? Would the clients already reporting to SMS 2003 be affected by this? Can I still be able to take remote desktop of those machines? By removing the boundary, would all the clients be disconnected from the SMS 2003? Further Information: SMS 2003 is just being used for taking remote desktop of client machines and no other features are being utilized. 2. I have both SMS 2003 and SCCM 2007 R3 clients installed on quite a few machines? and I can take remote desktop of the machine from both SMS 2003 and SCCM 2007 R3? Is this a coincidence or something else? 3. In this situation what is best strategy to transition from SMS 2003 to SCCM 2007 R3? Like provide both consoles to all the helpdesk personnel so that if a client is not found in one, it can searched in the other until all the clients are move to SCCM 2007 R3? Thanks in advance.

1a) yes remove boundaries from SMS 2003 1b) yes it will have an effect on SMS 2003 but since you are only using RD, there will be no issues. 1c) yes 1d) no 2a) It is impossible to have ConfigMgr and SMS installed on the same PC. 2b) Remote Desktop has nothing to do with either ConfigMgr or SMS, it is a windows feature. ConfigMgr leverages it. 2c) it is a Windows feature not SMS or ConfigMgr 3a) --- 3b) Since you are only use RD there is no need for the console at all. Just use the Remote Desktop tool which is installed on all workstations (xp and above) http://www.enhansoft.com/

If you're only using SCCM for remote desktop support, you would be better off just using remote desktop directly rather than going through the SCCM interface. You don't need SCCM to use remote desktop.

Thanks for the replies, again some questions: 1. If I remove the boundaries from the SMS 2003 then for the clients already part of SMS 2003 environment, would I be able to take remote deskop to those machines without any problem? That is from the SMS 2003 console? There is some confusion that I would like to clarify that Helpdesk takes remote desktops through the consoles and do not use mstsc? 2. On the SMS 2003 and SCCM 2007 R3 clients on the same machines, I can see the same machine with client installed on both SMS 2003 and SCCM 2007 R3 Servers and I am able to explore the resource on both Servers as well as take remote desktop as well? How is that happening? 3. Helpdesk personnel use SMS 2003 consoles to take remote desktops of end users so what could be the strategy for the time till all clients are moved to SCCM 2007 R3? Provide users with both consoles? I hope I have clarified. Thanks in advance.

1) It will work 2) it is not happening... SMS 2003 is old data. 3) you DON'T need to the console to RD to a PC. Use mstsc instaed.http://www.enhansoft.com/

Thanks for the replies. I am just confirming on above point. 1. I should go ahead and remove boundaries from SMS 2003 and the clients would still be connected to the site and SMS 2003 console can still be used to take remote desktop of machines that are part of SMS 2003? 2. You are right. The site assignment does not show on those clients that are now part of SCCM 2007 Site and Remote Tools does not work giving error that component does not exist on the client machine. However, remote desktop can be peformed by providing user name and password. 3. Users are acustom to consoles and they might require the reporting as well. So, what do you suggest. Providing them Console is better in this scenario or asking them to use browser to access reports and use remote desktop through MSTSC. The only downside to it is that they would be required to provide the user name and password and the enduser would not be able to see what is happening to his/her machine. WHat do you suggest. tHANKS IN ADVANCE.

Why would you want to keep a mixed 2003/2007 environment in that scenario? Why not just upgrade all of the clients and have them report to 2007? If you don't want to jump right in, you could limit the deployment to a group of test users. Even better might be to wait until SCCM 2012 comes out this summer. No point in going through a big upgrade to 2007 only to have to do it again (assuming you want the latest version)