Just getting to the upgrade from SMS 2003 SP3 to SCCM 2007 R2 at my site. SCCM 2007 single site. All roles installed on single server with exception of SQL on a 2nd server. SCCM server is Windows Server 2008 R2 Standard, IIS 7. AD Schema extended with no errors in the log file. Separate site names. I have removed the boundary of our servers from SMS 2003 and put it into SCCM boundaries. I manually installed the client on the servers, no problem. I've pushed security updates to them this month using the new Software Updates no problem. Deployed some software to them as well, no problem. Client Push problem: I'm running an AD discovery. Adsysdis.log looks clean. I can see the WinXP Sp3 client that I'm working with and that a DDR was written for the system. I can actually watch the ddm.box inbox and see the records being processed. I see the client in my collection, but I am not seeing the client being assigned. The client is in the same boundary as the servers. I'm sure the problem is that the push isn't working because the client is not being assigned. I've exhausted Google looking for site assignment problems and have checked everything others have posted and tried, but cannot seem to get it working. I have spent several days looking at this and have not had any luck. I want to migrate the clients over in another week, but this is kinda holding me up as I'd like to use the Client Push menthod of client deployment. I have everything configured and all logs (SCCM, IIS) appear to be clean with the exception of the SMS_AD_SYSTEM_DISCOVERY_AGENT Component Status where I'm getting the following 'warning' message which I'm not sure if it is contributing to the problem: "SMS Active Directory System Discovery Agent reported errors for 339 objects. DDR's were generated for 0 objects that had errors while reading non-critical properties. DDR's were not generated for 339 objects that had errors while reading critical properties. Possible cause: The SMS Service might not have access to some properties of this object. The container specified might not have the properties available. Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information." Perhaps I've dug so deep into this, I'm missing the obvious. Any ideas/suggestions would be much appreciated!wde

Hi, If your SMS 2003 Environment is still up and running then I suggest you: 1) Create a package that will reassign the SMS 2003 client to the new site. You can use this script - http://www.myitforum.com/articles/1/view.asp?id=12548 2) In the new site create a package that will upgrade the SMS 2003 to SCCM client. Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

Hi Kent, Thanks for your reply! My SMS 2003 environment is still up and running. Do you think once I remove SMS 2003 from my environment the Client Push will begin working? -Waynewde

Client push only deals with an account that has permission and the right client settings. Depending on what you're doing, you can use the same user account and settings that you use for SMS 2003. You are using a different site code for the ConfigMgr enviroment right? Give us more information about the discovery errors. Do you see errors for machines that are already in the Domain/ConfigMgr console? Are you using the the same discovery parameters you used in SMS 2003? http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Hi, If your SMS 2003 Environment is still up and running then I suggest you: 1) Create a package that will reassign the SMS 2003 client to the new site. You can use this script - http://www.myitforum.com/articles/1/view.asp?id=12548 2) In the new site create a package that will upgrade the SMS 2003 to SCCM client. Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products My test environment is in this position right now. I have both environments setup as part of the side by side upgrade process, all packages and collections migrated to my new SCCM site and now ready for the client migration. I have a query around boundaries, If I re-assign the clients to the new SCCM 2007 site, for this scenario I have 1 AD site which I use for SMS, and will need to use for SCCM also. So do I setup the boundary as active on both setups? will this work? At this point the clients are still SMS 2003 advanced. Ready for the new package upgrade.

Avoid overlapping boundaries, they are not supported and will cause issues. Remove it from SMS and add it to ConfigMgr; the only things that are not working without boundaries are automatic site assignment and limited roaming capabilities.Torsten Meringer | http://www.mssccmfaq.de

Avoid overlapping boundaries, they are not supported and will cause issues. Remove it from SMS and add it to ConfigMgr; the only things that are not working without boundaries are automatic site assignment and limited roaming capabilities. Torsten Meringer | http://www.mssccmfaq.de ok so we migrate workstations to the configmr server, dont create a boundary - is that right?