Quantcast
Channel: Configuration Manager 2012 - Application Management forum
Viewing all articles
Browse latest Browse all 4762

Black screen to implement windows 10 1803 in sccm 1806

$
0
0
  1. is currently implementing Windows 10 1803 with sccm 1806, at the end of the task sequences appears on a black screen after the message of the moment.

smts.log 

Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002TSManager30/10/2018 12:33:56 p. m.5804 (0x16AC)
Start to cleanup TS policyTSManager30/10/2018 12:33:56 p. m.5804 (0x16AC)
End Task Sequence policy cleanupTSManager30/10/2018 12:33:56 p. m.5804 (0x16AC)
Start to evaluate TS policy with lockTSManager30/10/2018 12:33:56 p. m.5804 (0x16AC)
Updating settings in \\.\root\ccm\policy\machine\actualconfigTSManager30/10/2018 12:33:56 p. m.5804 (0x16AC)
Total RequestedConfig policy instance(s) : 526 TSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
New/Changed ActualConfig policy instance(s) : 2 TSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
{
ClientID = "GUID:8318f608-67cd-4451-8b0c-91c26e3d5145";
DateTime = "20181030173357.242000+000";
PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 5800;
ThreadID = 5804;
};
TSManager 30/10/2018 12:33:57 p. m.5804 (0x16AC)
Status Agent hasn't been initialized yet. Attempting to create pending event.TSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
Raising pending event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
{
ClientID = "GUID:8318f608-67cd-4451-8b0c-91c26e3d5145";
DateTime = "20181030173357.242000+000";
PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 5800;
ThreadID = 5804;
};
TSManager 30/10/2018 12:33:57 p. m.5804 (0x16AC)
Successfully submitted pending event to WMI. TSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
End TS policy evaluationTSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
Policy evaluation initiatedTSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
Sending success status messageTSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
Not in SSLTSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgramTSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
GetTsRegValue() is unsuccessful. 0x80070002. TSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
End program: TSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
Finalize logging request ignored from process 5800 TSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
Waiting for CcmExec service to be fully operationalTSManager30/10/2018 12:33:57 p. m.5804 (0x16AC)
CcmExec service is up and fully operational TSManager30/10/2018 12:38:25 p. m.5804 (0x16AC)
Current Assigned Management Point is xxxx.xxx-xxx.com with Version 8692 and Capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>ClientLocation30/10/2018 12:38:25 p. m.5804 (0x16AC)
Successfully connected to MP xxxxxxxxxxx.com:80 TSManager30/10/2018 12:38:25 p. m.5804 (0x16AC)
Attempting to release request using {864A7763-C6C6-4013-92BC-B43D73318AF1}TSManager30/10/2018 12:38:25 p. m.5804 (0x16AC)
ReleaseRequest failed with error code 0x80004005 TSManager30/10/2018 12:38:25 p. m.5804 (0x16AC)
Task Sequence Manager could not release active TS request. code 80004005TSManager30/10/2018 12:38:25 p. m.5804 (0x16AC)
Process completed with exit code 0TSMBootstrap30/10/2018 12:38:25 p. m.5652 (0x1614)
Exiting with return code 0x00000000TSMBootstrap30/10/2018 12:38:25 p. m.5652 (0x1614)
Process completed with exit code 0OSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
Task sequence completed 0x00000000OSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
Resume SCCM Client.OSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
CCMExec service startup type is set to enabled OSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
Modifying CCMExec Service to auto start.OSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
CCMExec Service startedOSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
Waiting for CcmExec service to be fully operationalOSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
CcmExec service is up and fully operational OSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
Successfully connected to MP xxxxxxxxxx.com:80 OSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
Cleaning up any active TS requests in WMI.OSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
No instances of CCM_TSExecutionRequest found. OSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
Cleaning up any maintenance task requests in WMI. OSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
No instances of SMS_MaintenanceTaskRequests found. OSDSetupHook30/10/2018 12:38:25 p. m.5400 (0x1518)
Uninstalling Setup HookOSDSetupHook30/10/2018 12:38:27 p. m.5400 (0x1518)
Removing setup hook from registry.OSDSetupHook30/10/2018 12:38:27 p. m.5400 (0x1518)
Successfully removed C:\WINDOWS\system32\OSDGINA.DLLOSDSetupHook30/10/2018 12:38:27 p. m.5400 (0x1518)
Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXEOSDSetupHook30/10/2018 12:38:27 p. m.5400 (0x1518)
Successfully removed C:\WINDOWS\system32\_SMSOSDSetupOSDSetupHook30/10/2018 12:38:27 p. m.5400 (0x1518)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgramOSDSetupHook30/10/2018 12:38:27 p. m.5400 (0x1518)
GetTsRegValue() is unsuccessful. 0x80070002. OSDSetupHook30/10/2018 12:38:27 p. m.5400 (0x1518)
End program: OSDSetupHook30/10/2018 12:38:27 p. m.5400 (0x1518)
Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\LogsOSDSetupHook30/10/2018 12:38:27 p. m.5400 (0x1518)

He is currently implementing Windows 10 1803 with sccm 1806, at the end of the task sequences appears on a black screen after the message of the moment.

Viewing all articles
Browse latest Browse all 4762

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>