[mssms] SCCM Client auto site assignment not working as expected with OSD [75affas]
From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Michael Roach
Sent: Thursday, January 08, 2009 4:25 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] SCCM Client auto site assignment not working as expected with OSD
Bummer. I did create the boot media on the central. Thanks for the tip... will give it a try later tonight.
From: admin@lists.myITforum.com [admin@lists.myITforum.com] On Behalf Of Feret, Greg [Greg.Feret@Tiffany.com]
Sent: Thursday, January 08, 2009 11:28 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] SCCM Client auto site assignment not working as expected with OSD
Where did you create your deployment media? At the central site?
I think you need to build it at each of the child sites in order to have it become a client of that site. Or you have to reassign the client to the correct site code after the fact.
In other words the deployment media is specific to the site it is created in. If you created it at the central then all clients will be assigned to that site regardless of boundaries.
The properties should be put in the Installation Properties field rather than the install program and you can not use the SMSSITECODE property in there it wont let you.
From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Michael Roach
Sent: Thursday, January 08, 2009 11:35 AM
To: mssms@lists.myitforum.com
Subject: [mssms] SCCM Client auto site assignment not working as expected with OSD
I just finished implementing a XP thin image that is deployed curtesy of SCCM R2 w/MDT integration (not using the MDT db/console) and noticed that when the client is installed its being assigned to our central site instead of its correct primary. I've never seen this behavior before at our site and am not sure how to correct it.
Our central site does not contain any clients and all of the site boundaries are assigned to its child primaries. The command line used on the client package used in the TS is:
CCMSETUP.EXE /noservice SMSSITECODE=AUTO FSP=LXWFSP01P
Except for the fact that machines are being assigned to the wrong site this is working as expected. Should those command line options been put in the Installation Properties field of the TS Setup Windows and ConfigMgr node rather than the install program?
What else do I need to look?
The information contained in this email message may be privileged,confidential, and protected from disclosure. Any unauthorized use, printing,copying, disclosure, dissemination of or reliance upon this communication bypersons other than the intended recipient may be subject to legal restrictionor sanction. If you think that you have received this E-mail message in error,please reply to the sender and delete this email promptly.
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/
Published with BlogMailr
Trackbacks
No Trackbacks
Comments
No Comments
