gent, we are in the process to migrate all our machines system from xp to win 7. I'm responsible for SCCM 2007 deployment site.our sms site consist of one site server and 500 xp machines. we plan to migrate xp machines smoothly to win 7,to do so,it is possible to do the following plan: keep sms 2003 site running to continue managing xp machines. deploy new sccm 2007 site server (it will discover and manage only the new deployed win 7 machines). apply a gpo on xp OU that prevent sms 2003 server to manage win 7 clients. apply another gpo on win 7 OU to prevent sccm 2007 site to manage xp clients. NB: the use of gpo is to avoid overlaping sms/sccm site,since they will share same boundaries under AD IP subnets. so,my question:It is possible to do this,and what is pros/cons when applying that scenarion. your help will be appreciated. thanks.

1) SMS and ConfigMgr can coexist on the same network, no problems 2) Overlapping boundaries are not supported and can cause you all kinds of weird problems. I would recommend having a speciel IP range scope for the new Win7 clients and specify that as the boundary in the new installation or even better, let ConfigMgr. service all clients instead of maintaining two environments.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

kent, thank for your reply,but the business need is to keep sms site running and serve xp machines,till we migrate all of them to win 7. also,all our xp machines are in different ip subnets,if we create a new IP subnet specially for futur win 7 machines,at the end of the migration project,all machines (+300) will be in that new subnet,and zero in the other subnets. any clarification about that. thanks.

different subnets = no overlapping boundaries, that's cool and should workKent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

sorry kent,i should explain exact what is our situation: Our network is divided to many ip subnets:130.201.55.0,130.201.56.0,130.201.57.0 and so on. sms site is configured to use above adresses as boundaries. if we install and configure new sccm site server we should define the same boundaries,and this is the problem,we should avoid overlapping,and my question:it is possible to apply a gpo to prevent sccm to contact xp machines and vers sms to contacts win 7 machines. I hope that i clarify my scenarion well. thanks in advance.

Our network is divided to many ip subnets:130.201.55.0,130.201.56.0,130.201.57.0 and so on. sms site is configured to use above adresses as boundaries. if we install and configure new sccm site server we should define the same boundaries,and this is the problem,we should avoid overlapping,and my question:it is possible to apply a gpo to prevent sccm to contact xp machines and vers sms to contacts win 7 machines. I hope that i clarify my scenarion well. thanks in advance. As per i know, it is not possible to use GPO to prevent the clients to not contact SCCM and use SMS server if same boundaries are used in SMS and SCCM. As Kent said ,The only way is to not use same bounadries which are already defined in SMS server which makes the enviroment cool and work as expected. //Eswar Koneti @ www.eskonr.com

Is there a business reason why you can't upgrade you SMS site to SCCM before the rollout of XP? Regards, Blair Muller Check Out My Blog: http://blair-muller.blogspot.com/

Blair, this is the aim of the project,is to migrate to sccm without impacting current sms site. what i'm trying to understand is:it is possible to coexiste both sms/sccm sites,and migrate smoothly all xp machines to win 7. now xp machines are managed by sms,when we migrate it to win 7 it will be managed by the new sccm server. it's possible to apply above gpo's to do so. thanks.

what i'm trying to understand is:it is possible to coexiste both sms/sccm sites,and migrate smoothly all xp machines to win 7. now xp machines are managed by sms,when we migrate it to win 7 it will be managed by the new sccm server. it's possible to apply above gpo's to do so. thanks. after the migration of computers to Windows 7 and if you want to manage these Via SCCM ,you should migrate(remove and add) the Boundaries from SMS to SCCM and can not be possible to stop Via GPO.//Eswar Koneti @ www.eskonr.com

Hi Inzou, I agree with Eswar and recommend you to complete one task at a time. either you only procced with win 7 migration and do not add SCCM now or else Add SCCM first move XP client to SCCM and then migrate to win 7. There will be more complications if you are doing 2 projects at the same time. troubleshooting is bit tough in sms and i am sure it will become more tougher if you proceed with what you have mentioned as your plan. Cheers!!

I wrote a pretty long reply but accidently clicked Kents name and lost the lot, the back button doesn't bring you back to your post grr Ok what you want to do, you have to manage the transition you can't just setup two hierarchies, share boundaries and everything works fine. It won't work. You will experience new levels of frustration troubleshooting all kinds of issues, mostly around the (Content) Location Services area. You'll be a better troubleshooter for it, but have less time to do the "good things" :-) Google\bing "ConfigMgr overlapping boundaries" (http://lmgtfy.com/?q=ConfigMgr+overlapping+boundaries) and you'll see it makes the hierarchies become unreliable. You're best bet is to setup the ConfigMgr hierarchy without boundaries. Then, upgrade your XP machines to Win7, and when the ConfigMgr client is installed onto the Win7 clients, hard code the Site Code so they assign to the boundary-less ConfigMgr Site server. Repeat this until most of your XP clients have been migrated, and when you have enough Win7 machines on a subnet, compared to WinXP machines, you can move the boundary from the old hierarchy to the new hierarchy. Any business logic applies here, 50% then swap boundaries, 100%, or even now. You're call, but do read up on what happens when boundaries are not present, and how that affects location services, and how advertisements should be configured to accomodate a boundary-less site server (hierarchy). So essentially what you want to do, isn't that hard, its side by side with the new hierarchy running boundary-less until the old hierarchy can be collapsed. Also forget this filtering by OS type, its not done like that, its "all clients" on a boundary, not "all winXP machines" on a boundary ... sorry :-< HTH!

the problem is that the project of migration from xp to win 7 depend of sccm project (we will sccm osd to deploy win 7). we will be in this situation: take a small number (<10 per day) of xp machines and migrate them to win 7,but we keep all other win xp machines running under sms server till we finish all of them,and it will take time yo do so. also,on the new sccm server,we should re-create all our current sms packages to met win 7 (office 2010 and so on). what do you think???? thanks.

I wrote a pretty long reply but accidently clicked Kents name and lost the lot, the back button doesn't bring you back to your post grr Ok what you want to do, you have to manage the transition you can't just setup two hierarchies, share boundaries and everything works fine. It won't work. You will experience new levels of frustration troubleshooting all kinds of issues, mostly around the (Content) Location Services area. You'll be a better troubleshooter for it, but have less time to do the "good things" :-) Google\bing "ConfigMgr overlapping boundaries" (http://lmgtfy.com/?q=ConfigMgr+overlapping+boundaries) and you'll see it makes the hierarchies become unreliable. You're best bet is to setup the ConfigMgr hierarchy without boundaries. Then, upgrade your XP machines to Win7, and when the ConfigMgr client is installed onto the Win7 clients, hard code the Site Code so they assign to the boundary-less ConfigMgr Site server. Repeat this until most of your XP clients have been migrated, and when you have enough Win7 machines on a subnet, compared to WinXP machines, you can move the boundary from the old hierarchy to the new hierarchy. Any business logic applies here, 50% then swap boundaries, 100%, or even now. You're call, but do read up on what happens when boundaries are not present, and how that affects location services, and how advertisements should be configured to accomodate a boundary-less site server (hierarchy). So essentially what you want to do, isn't that hard, its side by side with the new hierarchy running boundary-less until the old hierarchy can be collapsed. Also forget this filtering by OS type, its not done like that, its "all clients" on a boundary, not "all winXP machines" on a boundary ... sorry :-< HTH! Mr Marshall, Could you please simplify your idea,what do you mean by boundary-less ConfigMgr Site server and how config mgr client be installed without define boundaries in sccm site. cheers.

Mr Marshall, Could you please simplify your idea,what do you mean by boundary-less ConfigMgr Site server and how config mgr client be installed without define boundaries in sccm site. cheers. 1. boundary-less environment. Just don't configure any boundaries for your configmgr environment. There are drawbacks, but its temporary, and as my plan stated, you'll be migrating subnets into configmgr once you've upgraded parts of the desktop estate in your company. Things to research are: Location Services, and the behaviour you can control using the advertisement "Distribution Points" tab. Starting point for you: http://technet.microsoft.com/en-us/library/bb632366.aspx 2. Client The client can be assigned to a Site server even if it doesn't reside in the sites boundaries, or in this case, if the site server does not have any boundaries Look at Client installation properties: http://technet.microsoft.com/en-us/library/bb680980.aspx Here's a superflow explaining Client Install and Assignment: http://go.microsoft.com/fwlink/?LinkId=200706 HTH

Mr Marshall, Could you please simplify your idea,what do you mean by boundary-less ConfigMgr Site server and how config mgr client be installed without define boundaries in sccm site. cheers. 1. boundary-less environment. Just don't configure any boundaries for your configmgr environment. There are drawbacks, but its temporary, and as my plan stated, you'll be migrating subnets into configmgr once you've upgraded parts of the desktop estate in your company. Things to research are: Location Services, and the behaviour you can control using the advertisement "Distribution Points" tab. Starting point for you: http://technet.microsoft.com/en-us/library/bb632366.aspx 2. Client The client can be assigned to a Site server even if it doesn't reside in the sites boundaries, or in this case, if the site server does not have any boundaries Look at Client installation properties: http://technet.microsoft.com/en-us/library/bb680980.aspx Here's a superflow explaining Client Install and Assignment: http://go.microsoft.com/fwlink/?LinkId=200706 HTH Marshal, Could I deploy win 7 from sccm osd method without define boundaries???? thanks.

Please refer to the documentation, I appreciate that it is easier to ask questions but these questions are pretty much covered off by all the linking and referencing I've done for you. You should understand clearly what a boundary is, how advertisements work and how content is located ...