PENDING Windows Server 2016 - Config Client Failing

[PKSCCM]

Hi,

I'm trying to run up a build Windows 2016 task sequence using the Server 2016 ISO from Microsoft.

Everything works ok, until it gets up to the 'Setup Windows and ConfigMgr" step. I've set this step up with the latest Client package SCCM has (which has the same distribution date as when I upgraded SCCM to 1806. so it appears to have done it's job and updated my client package also) I also have ticked the "use pre-production client package when available" option and configured the pilot package. I then have configured SMSMP and SMSCACHESIZE in the installation properties for the client package with in the TS, but still it fails with error 0x80004005 and nothing can be found in the logs on X: or C:.

I have tried running the task sequence with no installation properties for the client package, but still I get the same error.

This works fine for my 2012 R2 task sequence.

Has anyone else ran into this issue or know of why this is occurring for Server 2016? I'm using Option 2 from the ISO which is Server Standard.

Kind Regards
PKSCCM

 

[PKSCCM]

The client for 2016 also deploys fine when deploying to an already built machine through the SCCM console.

Anyone else had these issues during a TS?

 

[Prajwal Desai]

You can check for the below three locations for smsts.log file after OSD and when the OS is installed.

Before SCCM agent installed - c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

If Windows OS is 32-bit, after SCCM agent installed - c:\windows\system32\ccm\logs\Smstslog\smsts.log

If Windows OS is 64-bit, after SCCM agent installed - c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log

 

[PKSCCM]

Before SCCM agent installed - c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

I checked C:\_SMSTaskSequence\Logs\smsts.log and also smsts-20181003-015604.log which only exists while the error is up and disappear once the time out occurs.

The date file had a ShellExecute ('raserver.exe) failed. 0x80070002 error but I don't its related and it occurs very early on in the log.

The smsts.log has a lot of yellow lines about unsuccessful in finding a suitable device driver for device.

C:\Windows does not seem to exist at this stage, which is weird.

The OS is Server 2016 and is 64bit.

 

[PKSCCM]

I can see in the SMSTS.log the following entries

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful 0x8007002

then a few lines down it says

TS environment is not initialized

Hope this helps?

 

[Prajwal Desai]

No that doesn't help. Upload the log file so that we can investigate further.

 

[PKSCCM]

No that doesn't help. Upload the log file so that we can investigate further.

Unfortunately I can't due to it being a government client. I did the following error which I think would be the issue, not sure why its occurring though.

System partition not set
Unable to locate a bootable volume. Attempting to make C:\ bootable
Volume C:\ is on the boot disk.
Volume C:\ has an NTFS filesystem

So it looks like it resolves that error and continues on as my error pops up at the installing config mgr client not at the applying operating system step.
-----------
I also found the following error

Failed to load existing answer file "c:\_SMSTaskSequence\unattend.xml"

 

[PKSCCM]

No one else is having the same issue? It seems very odd that it fails during a TS but works when pushed from SCCM console.