locked
Deploy Windows 10 via SCCM Task Sequence RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    For testing purposes, I am trying to deploy Windows 10 via my SCCM 2012 R2 OSD. The deployment Task Sequence goes well until it arrives to install the ConfigMgr Client and it does not move on to install my apps/programs since the ConfigMrg installation fails. I know that ConfigMgr is not installing on Windows 10 unless you specify this switch (/skipprereq:windowsupdateagent30-x64.exe). In order to tweak this, I created a package with the program command to run this (CCMSetup.exe /mp:mysccmserver.mydomain /logon SMSSITECODE=mysitecode FSP=myfspserver.mydomain /skipprereq:windowsupdateagent30-x64.exe), and I added in the package to install SCCM client. Then I included this package in my Task Sequence to run before the SCCM client installation starts, but still no luck. When my task sequence comes to the step to install SCCM client nothing happens as it seems that task sequence cannot run this step and completely ignores SCCM client installation and suddenly Windows login screen shows up.

    Any suggestion is highly appreciated.

    Cheers,
    Sameer

    Thursday, June 11, 2015 10:25 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    It works fine when I manually install the SCCM client from the same location and same package which is attached to my task sequence. For some reason, the task sequence completely ignore this step and any other steps after it.

    Sameer

    This sounds like an error is being encountered during TS execution.
    Most errors during the TS would cause the TS to abort/abandon at that TS step, which means the remaining steps in the TS will not be executed.

    You would need to examine the SMSTS logfile(s) on the affected client machine.
    That can be tricky, depending upon the stage/phase in the TS when abort occurs (the logs might be in several different places)

    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    • Proposed as answer by Joyce L Tuesday, June 23, 2015 11:23 AM
    • Marked as answer by Joyce L Friday, June 26, 2015 3:55 AM
    Thursday, June 18, 2015 9:31 AM

All replies

  • Question
    Sign in to vote
    2
    Sign in to vote

    Task Sequences don't use programs to install the client agent. The logic and functionality to install the client agent is directly built into the Setup Windows and ConfigMgr task. Anything before this task happens in WinPE and thus installing the agent at this time is invalid. You can add parameters like skipprreq to the installation properties input box of the Setup Windows and ConfigMgr task though.

    Are you running R2 SP1? Without that, installing the agent at all isn't even supported.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Friday, June 12, 2015 12:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Jason,

    I supplied the parameter on the task "Setup Windows and ConfigMgr" as follows:

     smsmp=mysccmserver.mydomain fsp=myfspserver.domain /skipprereq:windowsupdateagent30-x64.exe

    However, now the task sequence moves on Virtual machines fine, but not on the actual physical computers. Do you know why is that so? Physical computers completely escape installing SCCM client and it moves to the Windows login screen, and obviously escaping the other steps listed in the task sequence after installing the SCCM client. 

    Thanks,
    Sameer

    Friday, June 12, 2015 10:22 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Sameer

    Recommend you post smsts.log from a physical build to see if anything can be gathered from that. Also the client install logs - ccmsetup.log and client.msi.log

    Cheers Paul |

    Friday, June 12, 2015 10:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    In physical machine, are your drivers installed from driver package or not?

    My previous non-SP1 enviroment stopped working at some point with specific technical preview version, and just like that I saw some "manifest failed" error in ccmsetup.log, and stopped to troubleshot it further right there because that version was not supported.

    Saturday, June 13, 2015 10:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Paul,

    I would like to do that, but unfortunately my company policy does not allow me to upload this data to an online source. However, I couldn't find any useful data in the log file of the smsts.log. As for the ccmsetup.log and client.msi.log, I couldn't even locate these two log files. Do you know where under the physical machine are they located?

    Thanks,
    Sameer

    Monday, June 15, 2015 9:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am sure that the task sequence load the driver package for that specific model and install them fine. Right after the driver installation, my task sequence has the "Setup Windows and ConfigMgr" task with the parameter "smsmp=mysccmserver.mydomain fsp=myfspserver.mydomain /skipprereq:windowsupdateagent30-x64.exe". It seems that task sequence does not like this step and The task sequence start to ignore all the other tasks in the list as well and load the Windows login screen. Meaning that task sequence is not moving from this step forward to complete the other tasks in the list. I actually have a bunch of software that I want them to be installed as part of my OSD. I this working fine with Windows 7 and Windows 8 task sequences.<o:p></o:p>

    Sameer<o:p></o:p>




    Monday, June 15, 2015 9:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    As for the ccmsetup.log and client.msi.log, I couldn't even locate these two log files. Do you know where under the physical machine are they located?

    Typically located at c:\windows\ccmsetup\

    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Monday, June 15, 2015 9:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Don,

    This folder "c:\windows\ccmsetup\" wasn't even created under the machine being imaged by this SCCM task sequence. It seems that my task sequence does not reach that step and it stops before that.

    Regards,
    Sameer

    Monday, June 15, 2015 10:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you upgrade your Site system to SP2, to Support Windows 10?
    Tuesday, June 16, 2015 6:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes, my SCCM site system is SP2 and supports Windows 10. The Windows 10 deployment is not an issue, however, the SCCM client installation during the task sequence fails which cause the whole task sequence to ignore the other steps listed after the SCCM client installation, and that's because SCCM client needs to be installed first in order to allow you install other applications/programs listed in the task sequence.

    Tuesday, June 16, 2015 5:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Are you sure that the pre-req is causing an issue? I've not heard of this being a problem?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, June 16, 2015 6:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just thinking, how about if you try to install same Client manually with the same options from the same location, what will happen then?

    Wednesday, June 17, 2015 6:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It works fine when I manually install the SCCM client from the same location and same package which is attached to my task sequence. For some reason, the task sequence completely ignore this step and any other steps after it.

    Sameer

    Wednesday, June 17, 2015 4:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It works fine when I manually install the SCCM client from the same location and same package which is attached to my task sequence. For some reason, the task sequence completely ignore this step and any other steps after it.

    Sameer

    This sounds like an error is being encountered during TS execution.
    Most errors during the TS would cause the TS to abort/abandon at that TS step, which means the remaining steps in the TS will not be executed.

    You would need to examine the SMSTS logfile(s) on the affected client machine.
    That can be tricky, depending upon the stage/phase in the TS when abort occurs (the logs might be in several different places)

    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    • Proposed as answer by Joyce L Tuesday, June 23, 2015 11:23 AM
    • Marked as answer by Joyce L Friday, June 26, 2015 3:55 AM
    Thursday, June 18, 2015 9:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    That's fine guys! It seems that we are pretty new to the Windows 10 environment and is actually even not officially released yet. I will catch up with you guys when Microsoft release this Windows and will do my testing on that time.

    Thanks to all for their inputs!


    Tuesday, June 23, 2015 10:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Any news on this topic? We actually cannot deploy Windows 10 LTSB on some models. Mostly they manage to join the domain, but TS does not continue. Latest lines in c:\_smstasksequence\smsts.log show successful step "Setup Windows and ConfigMgr" (exitcode 0), but no stepping in again after Windows setup to start ccmsetup.exe. No ccmsetup folder created. Some models are ok after fourth or fifth retry.

    Thorsten Lau - IT-Lösungen http://blog.system-center.de

    Wednesday, January 20, 2016 10:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Any news on this topic? We actually cannot deploy Windows 10 LTSB on some models. Mostly they manage to join the domain, but TS does not continue. Latest lines in c:\_smstasksequence\smsts.log show successful step "Setup Windows and ConfigMgr" (exitcode 0), but no stepping in again after Windows setup to start ccmsetup.exe. No ccmsetup folder created. Some models are ok after fourth or fifth retry.

    Solved it. We were using CB/CBB image first, then switched to LTSB. LTSB uses another KMS client license key, but we forgot to change that in Apply Windows Settings step.

    Last lines in C:\Windows\Panther\UnattendGC\setupact.log showed that setupcomplete.cmd (which in turn calls OSDSetupHook.exe to continue TS after Windows setup) will not run because of an "OEM license key" (the wrong KMS client key).

    Somehow some clients did not believe having an "OEM license" and ran setupcomplete.cmd, later manage to contact AD and got the correct LTSB KMS key. But others didn't.

    With the correct KMS license key no more errors so far. :-)

    Thorsten Lau - IT-Lösungen http://blog.system-center.de

    Thursday, January 21, 2016 2:22 PM