When trying to start Tsbootshell from a cmd box, to restart a task sequence which failed to start. The wizard does not appear. This only happens when the machine is booted via PXE. When using USB, or a virtual machine with an iso is does appear and works as a charm.

I already tried to recreate the boot wim, but this was not the problem.

Does somebody have seen this issue before?

Thanks in advance,

Michael

Hi Team,

I am getting alerts for "State Migration Point HTTP Response Monitor". When I check the alerting machine, I see event ID  6207 stating "Component SMS_STATE_MIGRATION_POINT on computer servername.domain.com reported:  SMP Control Manager detected SMP is not responding to HTTP requests.  The http status code and text is 500, Internal Server Error".

When I checked the smpisapi.log it only shows the below readings -

========== BEGIN: HttpExtensionProc ==========    
Query string to parse: 'op=healthcheck'.    
Creating state store - E:\USMTStore\SMPSTOREE_95D77C19$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.    
Creating Migration Status Parent Directory - E:\USMTStore\SMPSTOREE_95D77C19$\MigrationStatus.    
Statestore - E:\USMTStore\SMPSTOREE_95D77C19$\MigrationStatus exists.    
Creating Migration Status Child Directory - E:\USMTStore\SMPSTOREE_95D77C19$\MigrationStatus\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.    
Returning status "200 OK"    
========== END: HttpExtensionProc ==========   

I have also gone through the below resolution from one of the technet blogs -

Issue 2:   SMP is not working, and you see Status Messages like “SMP is not responding to HTTP requests.  The http status code and text is 500, Internal Server Error.”

Issue Cause: This is usually caused by either incorrect permissions on the folder(s) specified in the State Migration Point component, or that the folder specified does not exist anymore.

Issue Resolution:   First verify whether the folder(s) specified in the State Migration Point exist, secondly, ensure that the local account “Local Service” has full control on that folder.  The SCCM ISAPI application for the State Migration Point runs under the “Local Service” account (worth pointing out here it’s not “Local System”).

I have verified that my folder "E:\USMTStore\SMPSTOREE_95D77C19$\MigrationStatus" has full permissions for "Local Service".

What else could be the issue behind these alerts and how can I resolve this.

Thanks, S K Agrawal

Hi all,

I have a strange issue in one environment. I have created a few TS with different steps but I have seen that none of then are finished during the deployment. So after the first reboot is made computer is comeback with windows logon window. I didn't find any errors in SMSTS.log. SCCM client is copied but not installed, no cmd commands and apps executed, nothing.

Please find attached last part from my log:

Start executing the command line: osdnetsettings.exe configure TSManager 23/06/2016 15:58:18 1188 (0x04A4)
!--------------------------------------------------------------------------------------------! TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Expand a string: WinPEandFullOS TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Executing command line: osdnetsettings.exe configure TSManager 23/06/2016 15:58:18 1188 (0x04A4)
==============================[ OSDNetSettings.exe ]=========================== OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Command line: "osdnetsettings.exe" configure OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Setting %SystemRoot% to "C:\Windows" OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Loading existing answer file "C:\Windows\panther\unattend\unattend.xml" OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Configuring global network settings OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Join type: 1 OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Joining workgroup: workgroup-test OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Getting namespace "Microsoft-Windows-UnattendedJoin" for architecture "amd64" OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
DNS domain:  OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
DNS domain search order:  OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
IP filter sec enabled: false OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
No adapters found in environment.  Performing global configuration only. OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Writing configuration information to C:\Windows\panther\unattend\unattend.xml OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Successfully saved configuration information to C:\Windows\panther\unattend\unattend.xml OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Configuring "OSDNetSettings.exe finalize" to run on first boot OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
OSDNetSettings finished: 0x00000000 OSDNetSettings 23/06/2016 15:58:18 1960 (0x07A8)
Process completed with exit code 0 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
!--------------------------------------------------------------------------------------------! TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Successfully completed the action (Apply Network Settings) with the exit win32 code 0 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Do not send status message in full media case TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Clear local default environment TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Updated security on object C:\_SMSTaskSequence. TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=7 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a TS execution environment variable _SMSTSNextInstructionPointer=7 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSInstructionStackString=0 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a TS execution environment variable _SMSTSInstructionStackString=0 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Save the current environment block TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Successfully save execution state and environment to local hard disk TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Start executing an instruction. Instruction name: Install Operating System. Instruction pointer: 7 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSCurrentActionName=Install Operating System TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=7 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
The group (Install Operating System) has been successfully completed TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Do not send status message in full media case TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Updated security on object C:\_SMSTaskSequence. TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=8 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a TS execution environment variable _SMSTSNextInstructionPointer=8 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSInstructionStackString= TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a TS execution environment variable _SMSTSInstructionStackString= TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Save the current environment block TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Successfully save execution state and environment to local hard disk TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Start executing an instruction. Instruction name: Setup Operating System. Instruction pointer: 8 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSCurrentActionName=Setup Operating System TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=8 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
The group (Setup Operating System) has been successfully started TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Do not send status message in full media case TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Updated security on object C:\_SMSTaskSequence. TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=9 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a TS execution environment variable _SMSTSNextInstructionPointer=9 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSInstructionStackString=8 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a TS execution environment variable _SMSTSInstructionStackString=8 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Save the current environment block TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Successfully save execution state and environment to local hard disk TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Start executing an instruction. Instruction name: Setup Windows and Configuration Manager. Instruction pointer: 9 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSCurrentActionName=Setup Windows and Configuration Manager TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=9 TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a local default variable SMSClientInstallProperties TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a local default variable _SMSClientPackageID TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Expand a string: OSDSetupWindows.exe TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Expand a string:  TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Command line for extension .exe is "%1" %* TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Set command line: OSDSetupWindows.exe TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Start executing the command line: OSDSetupWindows.exe TSManager 23/06/2016 15:58:18 1188 (0x04A4)
!--------------------------------------------------------------------------------------------! TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Expand a string: WinPEandFullOS TSManager 23/06/2016 15:58:18 1188 (0x04A4)
Executing command line: OSDSetupWindows.exe TSManager 23/06/2016 15:58:18 1188 (0x04A4)
==============================[ OSDSetupWindows.exe ]=========================== OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Command line: "OSDSetupWindows.exe" OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
ResolveSource flags: 0x00000000 OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
SMSTSPersistContent: . The content for package NTM00075 will be persisted OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Package location: _SMSTSNTM00075, file:VOL001:\SMS\PKG\NTM00075 OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Searching C:\ for Fullmedia content OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Searching D:\ for Fullmedia content OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Found Fullmedia content in drive D:\. OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Entering ReleaseSource() for D:\SMS\PKG\NTM00075 OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
The user tries to release a source directory D:\SMS\PKG\NTM00075 that is either already released or we have not connected to it OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Command line for extension .EXE is "%1" %* OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Set command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/configure:C:\Windows\SYSTEM32" /version:6.1 OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Executing command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/configure:C:\Windows\SYSTEM32" /version:6.1 OSDSetupWindows 23/06/2016 15:58:18 1880 (0x0758)
Configuring OSD setup hook OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Configuring setup hook OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Resolving source for SMS client, package ID = NTM00003. OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
ResolveSource flags: 0x00000000 OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
SMSTSPersistContent: . The content for package NTM00003 will be persisted OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Package location: _SMSTSNTM00003, file:VOL001:\SMS\PKG\NTM00003 OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Searching C:\ for Fullmedia content OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Searching D:\ for Fullmedia content OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Found Fullmedia content in drive D:\. OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Copying SMS client package source from "D:\SMS\PKG\NTM00003" to "C:\_SMSTaskSequence\OSD\NTM00003". OSDSetupHook 23/06/2016 15:58:18 1696 (0x06A0)
Locating architecture-specific OSDGina.dll OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Successfully copied file OSDSETUPHOOK.EXE to C:\Windows\SYSTEM32 OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Successfully copied file TSProgressUI.exe to C:\Windows\SYSTEM32\_SMSOSDSetup OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Successfully copied file tsres.dll to C:\Windows\SYSTEM32\_SMSOSDSetup\1033 OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Saving desktop wallpaper information. OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Entering ReleaseSource() for D:\SMS\PKG\NTM00003 OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
The user tries to release a source directory D:\SMS\PKG\NTM00003 that is either already released or we have not connected to it OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Exiting ConfigureEx: 0x00000000 OSDSetupHook 23/06/2016 15:58:29 1696 (0x06A0)
Process completed with exit code 0 OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Installing hook to 'C:\Windows' OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Command line for extension .EXE is "%1" %* OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Set command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:C:\Windows" /version:6.1 OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Executing command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:C:\Windows" /version:6.1 OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Installing OSD setup hook OSDSetupHook 23/06/2016 15:58:29 1748 (0x06D4)
Setup hook install completed successfully OSDSetupHook 23/06/2016 15:58:29 1748 (0x06D4)
Process completed with exit code 0 OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
OfflineRegistry::Init("C:\Windows") OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Loading offline registry hive "C:\Windows\system32\config\software" into HKLM\OfflineRegistry1 OSDSetupWindows 23/06/2016 15:58:29 1880 (0x0758)
Loading offline registry hive "C:\Windows\system32\config\system" into HKLM\OfflineRegistry2 OSDSetupWindows 23/06/2016 15:58:31 1880 (0x0758)
CurrentControlSet is mapped to ControlSet001 OSDSetupWindows 23/06/2016 15:58:31 1880 (0x0758)
SMS Client is not installed OSDSetupWindows 23/06/2016 15:58:31 1880 (0x0758)
Unloading offline SOFTWARE registry hive OSDSetupWindows 23/06/2016 15:58:31 1880 (0x0758)
Unloading offline SYSTEM registry hive OSDSetupWindows 23/06/2016 15:58:31 1880 (0x0758)
Exiting with code 0x00000000 OSDSetupWindows 23/06/2016 15:58:32 1880 (0x0758)
Process completed with exit code 0 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
!--------------------------------------------------------------------------------------------! TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Successfully completed the action (Setup Windows and Configuration Manager) with the exit win32 code 0 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Do not send status message in full media case TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Clear local default environment TSManager 23/06/2016 15:58:32 1188 (0x04A4)
The action (Setup Windows and Configuration Manager) requested a retry TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Reboot to local harddisk TSManager 23/06/2016 15:58:32 1188 (0x04A4)
_OSDGinaIsConfigured variable set to TRUE TSManager 23/06/2016 15:58:32 1188 (0x04A4)
_SMSTSServiceStartType variable set to  TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Command line for extension .exe is "%1" %* TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set command line: "bcdedit.exe" TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Executing command line: "bcdedit.exe" TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Process completed with exit code 0 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Calling RebootSystem() TSManager 23/06/2016 15:58:32 1188 (0x04A4)
OSD type of task sequence. ignore the service window setting TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Updated security on object C:\_SMSTaskSequence. TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set a global environment variable _SMSTSNextInstructionPointer=9 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set a TS execution environment variable _SMSTSNextInstructionPointer=9 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set a global environment variable _SMSTSInstructionStackString=8 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Set a TS execution environment variable _SMSTSInstructionStackString=8 TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Save the current environment block TSManager 23/06/2016 15:58:32 1188 (0x04A4)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 23/06/2016 15:58:32 1188 (0x04A4)

Morning all,

Hopefully this is a straight forward one, I've got a TS running on a collection that has a maintenance schedule starting at 1800 and finishing at 0600.

Working hours finish at 2200 and start at 0500 on the Software Center client.

However, last night all clients are stuck on 'waiting to install' due to 'Waiting for a Service Window'. The servicewindow log looks fine, but I'm not great at finding stuff in the logs so hopefully someone else can.

Is there something I'm missing?

Thanks

Hi,

We have SCCM 2012 R2 SP1 in our environment and planning to do Windows 7 / 8.1 to Windows 10 upgrade using custom task sequence.

Wanted to check if Windows 10 ADK required for in place upgrade scenarios?

Does any TechNet reference available which suggest requirement or non requirement of Windows 10 ADK during Windows 10 in place upgrade scenario.

We are trying to deploy Windows 7 from WDS but we need to add certain nic drivers to the boot.wim image.

To do so i am using DISM to inject the drivers into the image.

However, having added the drivers to the image and then adding the boot.wim file back into WDS, if i close WDS, then open it again, the Boot image has disappeared.

If i add another boot.wim file to WDS, that i haven't added any drivers to, it doesn't disappear.

The process that i used to add the extra drivers to the image is as follows:

Create a folder named bootimage in the root of the C drive, in the boot directory we will create a folder named mount. When this is done, copy the boot.wim from the Windows 7 prodcut DVD into the c:\bootimage directory.

From the Deployment Tools command prompt we are going to mount the image.

DISM /Mount-Wim /WimFile:C:\bootimage\boot.wim /index:1 /MountDir:C\bootimage\mount

The image is mounted we have to add the drivers. Before we do this let's check which 3rd party drivers are available.

DISM /Image:c:\bootimage\mount /get-drivers

So the basic boot.wim does not contain any 3rd party drivers. Add some Windows 7 network drivers to the image now. The  /recurse switch in this command tells the DISM command to search all subdirectories and add the files nested into it in their own directory.

DISM /image:c:\bootimage\mount /Add-Driver /driver:E:\networkdrivers\PRO1000\Win32\NDIS62 /recurse

The drivers are installed now, Run the get-drivers command another time to see if something has really changed.

DISM /Image:c:\bootimage\mount /get-drivers

The drivers are installed , save the image and unmount it. The /commit switch makes the changes to the image, you can use the /discard switch to unmount without saving the changes to the image.

DISM /Unmount-Wim /MountDir:C:\bootimage\mount\ /Commit

Any idea why the boot.wim file with the added drivers is unusable and will not stay in WDS ?

Thanks,

Andrew

Hello the scenario I believe I'm running into is

we used to Deploy to "Unknown" for OSD but we switched it over to Deploying a to Collection Created for OSD. I was under the impression by going deploying to a "Known" collection would remove the need to delete from SCCM and re-import the data.

We are running into some of the machines that were once Imaged from the Unknown OSD and now when trying to reimage them they do no install any applications.

Is there any solution out there to re-mediate this? I believe its due to failing to download client policy which I'm thinking maybe a mismatch on the GUID?

I got something weird in my task sequence. I've got several steps and 1 one them is the 'Application install' with 8 applications. 6 of them are on the computer but 2 of them aren't. In the log everything is "The task sequence successfully installed application Belgium e-ID middleware (ScopeId_2C86EC9D-653B-42AE-915A-7C9838B0EA73/Application_cdbe5b95-3ed4-47a1-9869-e514c388228d) for action (Install Applications) in the group () with exit code 0."

There's 1 standard .exe (/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-) and the other is a .msi (/qn /norestart). When I launch them manually for installation (after OSD is finished) they are on the computer.

Any help is welcome :-)

Morning all,

This might be blindingly obvious, but I'm new to SCCM. I have 3 sites, I have a main SCCM site based in site 1, sites 2 and 3 have a DP at each. And that's it.

I've added in site 1 and 2 into WDS. However, when a client on site 2/3 network boots, it has an issue. 

The error is 0xc0000098, windows failed to start. A recent hardware or software change might be the cause...

It's fairly generic. Any ideas?

Am I supposed to assign site 1 and 2's DP's as management points as well? I'm a bit lost here.

Oh, the boot image is the same on all 3 locations (3 DP's), it's distributed fine.

Thanks

VISTA / XP Support Trainer

Hi,

We have SCCM 2012 1602 Env. We've recently noticed that during the OSD, the "Apply Software Updates" step is not working.

It stays on that page for a long duration and then the OSD finishes. All the deployed updates then come afterwards through software center.

The WUAHandler shows this snippet (and keeps on repeating it):



Unable to read existing WUA resultant policy. Error = 0x80070002.2016-07-28 15:58
Group policy settings were overwritten by a higher authority (Domain Controller) to: Server  and Policy NOT CONFIGURED2016-07-28 15:58
Failed to Add Update Source for WUAgent of type (2) and id ({6622B5DC-1C2D-4C47-A08C-5B6D8E18F38E}). Error = 0x87d00692.2016-07-28 15:58
Its a WSUS Update Source type ({6622B5DC-1C2D-4C47-A08C-5B6D8E18F38E}), adding it.2016-07-28 15:58
Unable to read existing resultant WUA policy. Error = 0x80070002.2016-07-28 15:58
Enabling WUA Managed server policy to use server: http://whatever.xxx.com:85302016-07-28 15:58
Waiting for 2 mins for Group Policy to notify of WUA policy change...2016-07-28 15:58
Timed out waiting for Group Policy notification. 2016-07-28 16:00




We have made NO change in the GPOs. We can safely say that the this was first noticed during our recent upgrade to 1511 and then subsequently to 1602.

Any suggestions.

Hi Folks,

I have been working on a task sequence to deploy Windows 10 to our company's laptops. We are running SCCM 2012 R2 SP1 w/CU3 and MDT 2013 Update 2 integrated. Without going into too much detail, let me just say that this was working perfectly up until just recently. The only thing that changed in our environment recently is the deletion of one of our secondary site systems. This site system isn't even involved in my OSD testing, so I'm not sure if it's even related.

I've read all the threads in this forum that describe similar issues. I've attempted all the applicable fixes I can think of. Nothing has worked so far. Log files are not very helpful.

AppIntentEval.log says the following for the various applications in the list I'm attempting to install:

Rejecting ScopeId_blablabla/RequiredApplication_blablabla/<version number> due to evaluation error

There's also another log that gets generated called InstallApplication.log (in the Windows\CCM\Logs folder) that has the following in it:

Execution status received: 16 (Application failed to evaluate)

App Install Failed

Install Dynamic application action failed to install application: '<first application in list>'. Error Code 0x80004005

The smsts.log isn't even worth posting. Everything looks perfect with respect to the dynamic app install until it tells you that it failed.

Failed to run the action: Install Applications. Unspecified error (Error: 8004005; Source: Windows)

I had this working perfectly for at least two weeks having performed numerous tests where I'm sure all the applications installed without issue. Based on everything I've read here, this issue should be resolved with the version and CU level we're at. We're planning to upgrade to the very latest SCCM (major upgrade to 1511 and then apply 1602 update) for a variety of reasons. This is yet another one. That being said, if anyone has any non-typical troubleshooting steps/possible solutions, I'd love to hear them. I have literally read everything on the general issue of application install failures during OSD and nothing seems to even apply to my case.

Thanks,

Andre

So I have a Windows 10 image that I've been testing deployment with, all has been good up until this week. When imaging a PC the task sequence goes as planned until the first reboot and when the PC goes into the windows setup portion, it stops at a grey screen that asks you to select a network connection so windows can finish setting up. (This is all windows setup and not configuration manager). The screen shows my wired connection and some wireless networks it's detected, if I click next it continues on with windows setup and the rest of the task sequence resumes.

I've reviewed all the unattendedgc and configmanager logs after the deployment was finished and didn't see anything that corresponded to an error which would cause this "Let's Get Connected" screen to show up? With this screen coming up it really doesn't make the entire process automated and our techs would have to click next halfway thru on the imaging process, which isn't acceptable from management's perspective.

Is there a better way to troubleshoot this? Or a specific log to look at?

Thanks

Hi,

I am testing OS image build on Lenovo x250 but it fails with "Windows failed to configure one or more components" after when image is applying drivers. I am looking through dism.log but could not find any issues with driver installed. Is there anywhere else or other log I should be looking to find the cause of image failure?

I am using CB1602 with MDT2013 Update 2. The driver package contains 50 drivers for this model and not sure what is this error about. I am troubleshooting by adding few drivers at a time and if it works then I add more but its very time consuming and wondering if anyone knew where to look to find the cause.

Thank you

Hello,

could somebody tell me if there is a way to install the computer with Standalone Media + UDI Wizard!? The installation for Drivers and Applications fails.

Br,

bad3m3ist3r

I have been running into an issue since I started deploying Windows 10. When I image using MDT, sometimes it will find driver updates as soon as it boots to the OS. The bad thing is when it wants to update the NIC. As soon as it does that, my deployment fails and leaves me with a blank white screen. Not your normal white summary screen, but completely white. I've tried setting HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching\SearchOrderConfig=00000003, but I'm seeing different sites saying to set it to 0 or 2 as well. I'm running 10586 so maybe something has changed with this build because the screen shots look different than what I am seeing. I'm attaching a screenshot of what I see, but others have screen shots that there should be more choices under the 'No' option. In MDT I have the WSUS server set and when I image, it is joining a local workgroup, not a domain.

Is anyone else running into this or know any other settings I could check or change? Thanks for your help!

Hello,

Scenario:

I deploy Windows 10 1511 CB/CBB using Configuration Manager 2012 R2 SP1. This is a supported config according to official MS sources. According to some blog posts, Windows 10 1511 will be the last Windows 10 branch supported by Config Mgr 2012, and any future updates will require new Configuration Manager (Current Branch).

Here is the question I can't find a clear answer to:

What does the lack of support mean exactly? If I have W10 1511 CB/CBB in my environment, will I be able to update them to any more recent builds (lets say 1607?) using SUP to deploy updates? Or maybe it will simply be impossible and these updates will not be avaialble? If I would like to delpoy a 1607 Windows 10 branch WIM file on a machine, would SCCM 2012 R2 let me do that? I understand that some configuration manager features like software inventory / software update / application depoyment etc. would not be guaranteed to work (would not be supported) if I would try to use the newer W10 builds with SCCM 2012 R2?

Thanks in advance for your feedback.

Thanks in advance for your answers

Hello, 

I have a really strange issue that is occurring with our new hardware that we just got in. The standalone and pxe boot both result in this picture: https://social.technet.microsoft.com/Forums/getfile/229329

The systems are Dell Latitude 3350s

The drivers are imported into SCCM; PXE and the boot.wim have the nic and HDD drivers needed.

There is no log files to pull because it force boots. The odd part about this is that is only happening on this model and not on any others. (previously had it with 7370s but it was due to 1 MAC for many computers (USB NIC)).

If you have any suggestions or things you would like me to check, let me know. 

Thank you 

Benny

Hi,

I have:

Subnet01:

- Server01 = DHCP

- 066 Option = Server02 IP Address 

- 067 Option = smsboot\x64\bootmgfw.efi

- Server02 = SCCM+PXE

- Client01 = Gen2 VM + UEFI Secure Boot

Subnet02:

- 066 Option = Server02 IP Address

- 067 Option = smsboot\x64\bootmgfw.efi

- Server03 = RRAS+DHCP Relay to Server01

- Client02 = Gen2 VM + UEFI Secure Boot

---------------

Client01 config = Client02 config

Client01: successfully boot from PXE + successfully install task sequence OS + work fine

Client02:

...after power on

...and then

...any idea?