locked
OSD Deployment--SCCM Client will not install RRS feed

  • Question

  • We have created an XP SP3 OSD it installs fine but the SCCM client does not install and there are no errors that we can work off of.

    We have followed the instructions for creating a Client Package from a definition ..Can anyone give us some direction?
    • Moved by TorstenMMVP Monday, November 23, 2009 8:19 AM Moved to OSD subforum (From:Configuration Manager Setup/Deployment)
    Friday, November 20, 2009 3:38 PM

Answers

  • There is always an smsts.log, it just won't get moved to the client folder (because there isn't one) and will stay in c:\windows\temp.

    When you created the client/agent install package, did you specifiy source files? If so, what directory did you use? Have you confirmed that it is out on the DP?
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    • Proposed as answer by eaglebcr Friday, December 18, 2009 9:31 PM
    • Marked as answer by Garth JonesMVP Sunday, December 13, 2015 5:36 PM
    Friday, November 20, 2009 9:32 PM

All replies

  • A lot more details are needed for us to help you at all.

    What does your TS look like?

    Are you doing a deployment or a build & capture?

    Did you use the wizard to create the task sequence or did you use a custom ts?

    If deployment, how did you build your image and does it include the client in it already?

    Have you reviewed the smsts.log?


    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    Friday, November 20, 2009 5:16 PM
  • We used the wizard to create the TS ...our image does not include the Client ...we are doing a deployment ..there is no smsts.log because once the image is installed there is no client and no smsts.log ..The OS installs, the drivers install, the PC joins the domain ..but the client does not and there are no errors.
    Friday, November 20, 2009 6:01 PM
  • We can assume you have created a package and program for the SCCM Client and that has been added to the TS?


    BR
    Friday, November 20, 2009 7:42 PM
  • There is always an smsts.log, it just won't get moved to the client folder (because there isn't one) and will stay in c:\windows\temp.

    When you created the client/agent install package, did you specifiy source files? If so, what directory did you use? Have you confirmed that it is out on the DP?
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    • Proposed as answer by eaglebcr Friday, December 18, 2009 9:31 PM
    • Marked as answer by Garth JonesMVP Sunday, December 13, 2015 5:36 PM
    Friday, November 20, 2009 9:32 PM
  • I checked for the smsts.log it is not in the temp folder.  The client package that was created is from a definition and is the advanced client silent upgrade found the data source for this is \\server\sms_site\client.exe ..the program command line is ccmsetup.exe.  It is out on all dp's.

    Monday, November 23, 2009 2:21 PM
  • c:\windows\temp on the destination\client system, not the server.
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    Monday, November 23, 2009 2:52 PM
  • Yes ..we looked on 3 diffrent destinations systems and the log is not present.
    Monday, November 23, 2009 3:26 PM
  • CCMSETUP.EXE /noservice SMSSITECODE=AUTO command line in the program ..is this correct??
    Monday, November 23, 2009 6:22 PM
  • If it got created from the package defintion then yes that is correct. How about checking for the ccmsetup.log and client.msi.log on the destination system?
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    Monday, November 23, 2009 9:42 PM
  • There are no log files at all in the temp folder. There is no ccmsetup.log or client.msi.log on any of the destination PC's.  Has anyone had this issue before? 
    Wednesday, December 2, 2009 4:39 PM