Jump to content


ZeZe

reference image - Windows 7 x64

By ZeZe, in System Center Configuration Manager (Current Branch)

Recommended Posts

ZeZe Newbie

ZeZe

Posted
Posted

Hi all

 

I just create successfully a reference image. The image was captured using the task sequence "build and capture". During the running of this TS I have added a couple of applications (nothing special).

 

Later I try to use this image but for some reason, at some point, the task sequence just hangs in the client manager. The agent was already installed and now is trying to start... SMSTS.log doesn't show much but after troubleshooting some online, I saw a couple of people with the same issue. I got some logs that might contain more details.

 

ClientAuth.log:

 

Signing Certificate is not available in the store ClientAuth 8-2-2016 18:36:42 1264 (0x04F0)
Error signing client message (0x80004005). ClientAuth 8-2-2016 18:36:44 1264 (0x04F0)
Signing Certificate is not available in the store ClientAuth 8-2-2016 18:51:44 1784 (0x06F8)
Error signing client message (0x80004005). ClientAuth 8-2-2016 18:51:44 1784 (0x06F8)
ClientIDManagerStatup.log:
[----- STARTUP -----] ClientIDManagerStartup 8-2-2016 18:40:11 1888 (0x0760)
Notified startup event to 'RDV' Identity store. ClientIDManagerStartup 8-2-2016 18:40:11 1888 (0x0760)
RefreshCCMIdentity: Nothing to do in provisioning mode. ClientIDManagerStartup 8-2-2016 18:40:11 1888 (0x0760)
PopulateRegistrationHint: Nothing to do in provisioning mode. ClientIDManagerStartup 8-2-2016 18:40:11 1888 (0x0760)
Read SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000360035002000390061002000300032002000640034002000640035002000320065002D0031003200200061006300200034003100200033003600200066006300200038006400200034003500200030006600 ClientIDManagerStartup 8-2-2016 18:40:19 2284 (0x08EC)
Evaluated SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000360035002000390061002000300032002000640034002000640035002000320065002D0031003200200061006300200034003100200033003600200066006300200038006400200034003500200030006600 ClientIDManagerStartup 8-2-2016 18:40:19 2284 (0x08EC)
No SMBIOS Changed ClientIDManagerStartup 8-2-2016 18:40:19 2284 (0x08EC)
SMBIOS unchanged ClientIDManagerStartup 8-2-2016 18:40:19 2284 (0x08EC)
SID unchanged ClientIDManagerStartup 8-2-2016 18:40:19 2284 (0x08EC)
HWID unchanged ClientIDManagerStartup 8-2-2016 18:40:20 2284 (0x08EC)
GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE ClientIDManagerStartup 8-2-2016 18:40:20 2284 (0x08EC)
Windows To Go requires a minimum operating system of Windows 8 ClientIDManagerStartup 8-2-2016 18:40:20 2284 (0x08EC)
Computed HardwareID=2:D98F62168A6BA77F2A35DCB7723787A68A6FD64B
Win32_SystemEnclosure.SerialNumber=<empty>
Win32_SystemEnclosure.SMBIOSAssetTag=<empty>
Win32_BaseBoard.SerialNumber=None
Win32_BIOS.SerialNumber=VMware-56 4d 65 9a 02 d4 d5 2e-12 ac 41 36 fc 8d 45 0f
Win32_NetworkAdapterConfiguration.MACAddress=00:50:56:2B:83:5F ClientIDManagerStartup 8-2-2016 18:40:20 2284 (0x08EC)
Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
HardwareID1=2:D98F62168A6BA77F2A35DCB7723787A68A6FD64B
HardwareID2=74BA0600010000FA ClientIDManagerStartup 8-2-2016 18:40:20 2284 (0x08EC)
RegEndPoint: Event notification: CCM_RemoteClient_Reassigned ClientIDManagerStartup 8-2-2016 18:40:20 1612 (0x064C)
RegEndPoint: Deleting pending re-registration on site re-assignment. ClientIDManagerStartup 8-2-2016 18:40:20 1612 (0x064C)
RegEndPoint: Received notification for site assignment change from '<none>' to 'PR1'. ClientIDManagerStartup 8-2-2016 18:40:20 1612 (0x064C)
RegEndpoint: Skipping re-registration due to no previous site assignment or provisioning mode. ClientIDManagerStartup 8-2-2016 18:40:20 1612 (0x064C)
Failed to open to WMI namespace '\\.\root\ccmvdi' (8007045b) ClientIDManagerStartup 8-2-2016 18:41:18 1888 (0x0760)
[----- SHUTDOWN -----] ClientIDManagerStartup 8-2-2016 18:41:18 1888 (0x0760)
[----- STARTUP -----] ClientIDManagerStartup 8-2-2016 18:43:43 1964 (0x07AC)
Notified startup event to 'RDV' Identity store. ClientIDManagerStartup 8-2-2016 18:43:43 1964 (0x07AC)
RefreshCCMIdentity: Nothing to do in provisioning mode. ClientIDManagerStartup 8-2-2016 18:43:43 1964 (0x07AC)
PopulateRegistrationHint: Nothing to do in provisioning mode. ClientIDManagerStartup 8-2-2016 18:43:43 1964 (0x07AC)
Read SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000360035002000390061002000300032002000640034002000640035002000320065002D0031003200200061006300200034003100200033003600200066006300200038006400200034003500200030006600 ClientIDManagerStartup 8-2-2016 18:45:55 2948 (0x0B84)
Evaluated SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000360035002000390061002000300032002000640034002000640035002000320065002D0031003200200061006300200034003100200033003600200066006300200038006400200034003500200030006600 ClientIDManagerStartup 8-2-2016 18:45:55 2948 (0x0B84)
No SMBIOS Changed ClientIDManagerStartup 8-2-2016 18:45:55 2948 (0x0B84)
SMBIOS unchanged ClientIDManagerStartup 8-2-2016 18:45:55 2948 (0x0B84)
SID unchanged ClientIDManagerStartup 8-2-2016 18:45:55 2948 (0x0B84)
HWID unchanged ClientIDManagerStartup 8-2-2016 18:45:56 2948 (0x0B84)
GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE ClientIDManagerStartup 8-2-2016 18:45:56 2948 (0x0B84)
Windows To Go requires a minimum operating system of Windows 8 ClientIDManagerStartup 8-2-2016 18:45:56 2948 (0x0B84)
Computed HardwareID=2:D98F62168A6BA77F2A35DCB7723787A68A6FD64B
Win32_SystemEnclosure.SerialNumber=<empty>
Win32_SystemEnclosure.SMBIOSAssetTag=<empty>
Win32_BaseBoard.SerialNumber=None
Win32_BIOS.SerialNumber=VMware-56 4d 65 9a 02 d4 d5 2e-12 ac 41 36 fc 8d 45 0f
Win32_NetworkAdapterConfiguration.MACAddress=00:50:56:2B:83:5F ClientIDManagerStartup 8-2-2016 18:45:56 2948 (0x0B84)
Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
HardwareID1=2:D98F62168A6BA77F2A35DCB7723787A68A6FD64B
HardwareID2=74BA0600010000FA ClientIDManagerStartup 8-2-2016 18:45:56 2948 (0x0B84)
Failed to open to WMI namespace '\\.\root\ccmvdi' (8007045b) ClientIDManagerStartup 8-2-2016 18:46:32 1964 (0x07AC)
[----- SHUTDOWN -----] ClientIDManagerStartup 8-2-2016 18:46:32 1964 (0x07AC)
[----- STARTUP -----] ClientIDManagerStartup 8-2-2016 18:49:28 1796 (0x0704)
Notified startup event to 'RDV' Identity store. ClientIDManagerStartup 8-2-2016 18:49:28 1796 (0x0704)
RefreshCCMIdentity: Nothing to do in provisioning mode. ClientIDManagerStartup 8-2-2016 18:49:28 1796 (0x0704)
PopulateRegistrationHint: Nothing to do in provisioning mode. ClientIDManagerStartup 8-2-2016 18:49:28 1796 (0x0704)
Read SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000360035002000390061002000300032002000640034002000640035002000320065002D0031003200200061006300200034003100200033003600200066006300200038006400200034003500200030006600 ClientIDManagerStartup 8-2-2016 18:51:36 2460 (0x099C)
Evaluated SMBIOS (encoded): 56004D0077006100720065002D00350036002000340064002000360035002000390061002000300032002000640034002000640035002000320065002D0031003200200061006300200034003100200033003600200066006300200038006400200034003500200030006600 ClientIDManagerStartup 8-2-2016 18:51:36 2460 (0x099C)
No SMBIOS Changed ClientIDManagerStartup 8-2-2016 18:51:36 2460 (0x099C)
SMBIOS unchanged ClientIDManagerStartup 8-2-2016 18:51:36 2460 (0x099C)
SID unchanged ClientIDManagerStartup 8-2-2016 18:51:36 2460 (0x099C)
HWID unchanged ClientIDManagerStartup 8-2-2016 18:51:37 2460 (0x099C)
GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE ClientIDManagerStartup 8-2-2016 18:51:37 2460 (0x099C)
Windows To Go requires a minimum operating system of Windows 8 ClientIDManagerStartup 8-2-2016 18:51:37 2460 (0x099C)
Computed HardwareID=2:D98F62168A6BA77F2A35DCB7723787A68A6FD64B
Win32_SystemEnclosure.SerialNumber=<empty>
Win32_SystemEnclosure.SMBIOSAssetTag=<empty>
Win32_BaseBoard.SerialNumber=None
Win32_BIOS.SerialNumber=VMware-56 4d 65 9a 02 d4 d5 2e-12 ac 41 36 fc 8d 45 0f
Win32_NetworkAdapterConfiguration.MACAddress=00:50:56:2B:83:5F ClientIDManagerStartup 8-2-2016 18:51:37 2460 (0x099C)
Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
HardwareID1=2:D98F62168A6BA77F2A35DCB7723787A68A6FD64B
HardwareID2=74BA0600010000FA ClientIDManagerStartup 8-2-2016 18:51:37 2460 (0x099C)
Notified shutdown event to 'RDV' Identity store. ClientIDManagerStartup 8-2-2016 18:51:45 1796 (0x0704)
[----- SHUTDOWN -----] ClientIDManagerStartup 8-2-2016 18:51:45 1796 (0x0704)
LocationServices.log:
The client version is compatible with the MP for Application Catalog. LocationServices 8-2-2016 18:51:38 1340 (0x053C)
Registered for changes to reg key Software\Microsoft\SMS\Mobile Client. LocationServices 8-2-2016 18:51:38 1340 (0x053C)
Registered for event SiteRoleCycleEvent. LocationServices 8-2-2016 18:51:38 1340 (0x053C)
Registered for event RefreshSecuritySettingsEvent. LocationServices 8-2-2016 18:51:38 1340 (0x053C)
Processing Location reply message LocationServices 8-2-2016 18:51:42 1856 (0x0740)
Updating portal information. LocationServices 8-2-2016 18:51:42 1856 (0x0740)
Processing Location reply message LocationServices 8-2-2016 18:51:42 1296 (0x0510)
Received reply of type PortalCertificateReply LocationServices 8-2-2016 18:51:42 1296 (0x0510)
The reply from location manager contains 1 certificates LocationServices 8-2-2016 18:51:42 1296 (0x0510)
Updating portal certificates LocationServices 8-2-2016 18:51:42 1296 (0x0510)
Successfully created certificate context. LocationServices 8-2-2016 18:51:42 1296 (0x0510)
Successfully created context from the raw certificate. LocationServices 8-2-2016 18:51:42 1296 (0x0510)
Client is set to use HTTPS when available. The current state is 224. LocationServices 8-2-2016 18:51:45 2488 (0x09B8)
Client is not assigned to a site. Cannot get portal info. LocationServices 8-2-2016 18:51:45 2488 (0x09B8)
SMSTS.log:
Query = 'CCM_NetworkAccessAccount.SiteSettingsKey="1"' TSManager 8-2-2016 19:50:55 532 (0x0214)
Verified policy for instance path 'CCM_NetworkAccessAccount.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 8-2-2016 19:50:55 532 (0x0214)
Query = 'CCM_NetworkAccessAccount.SiteSettingsKey="1"' TSManager 8-2-2016 19:50:55 532 (0x0214)
Verified policy for instance path 'CCM_NetworkAccessAccount.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 8-2-2016 19:50:55 532 (0x0214)
Query = 'CCM_RebootSettings.SiteSettingsKey="1"' TSManager 8-2-2016 19:50:55 532 (0x0214)
Verified policy for instance path 'CCM_RebootSettings.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 8-2-2016 19:50:55 532 (0x0214)
Query = 'CCM_ApplicationManagementClientConfig.SiteSettingsKey="1"' TSManager 8-2-2016 19:50:55 532 (0x0214)
Verified policy for instance path 'CCM_ApplicationManagementClientConfig.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 8-2-2016 19:50:55 532 (0x0214)
Query = 'CCM_ClientAgentConfig.SiteSettingsKey="1"' TSManager 8-2-2016 19:50:55 532 (0x0214)
Verified policy for instance path 'CCM_ClientAgentConfig.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 8-2-2016 19:50:55 532 (0x0214)
Policy verification done TSManager 8-2-2016 19:50:55 532 (0x0214)
Config policies compiled successfully TSManager 8-2-2016 19:50:55 532 (0x0214)
_SMSTSReturnToGINA variable set to true TSManager 8-2-2016 19:50:55 532 (0x0214)
Waiting for CcmExec service to be fully operational TSManager 8-2-2016 19:50:55 532 (0x0214)
Succeeded loading resource DLL 'C:\Windows\CCM\1033\TSRES.DLL' TSManager 8-2-2016 19:50:56 532 (0x0214)
* just last messages....

----------

 

 

So basically that's it.. Windows 7 x64 trying to be installed and hangs in the client configuration manager... I've already create two images, since it's the second time that happens. Not sure where is the issue, but now I'm running a TS to build Windows 10. Any feedback is much appreciated !!

 

Thank you all!

Share this post

Link to post
Share on other sites
ZeZe Newbie

ZeZe

Posted
Posted

Yes I did. The only way to finish the TS was running ccmrepair... The TS would then resume the normal state...

 

Now I have done a captured manually the OS and it works, for both cases (windows 10 and windows 7). I can't image why is that... but looks like the agent fails to connect with the site...

Share this post

Link to post
Share on other sites
ZeZe Newbie

ZeZe

Posted
Posted

ah I forgot you are using CM1511 ? that's a bug.... as explained here

Oh jesus!!! One day I'll be bald... this is a huge time consuming just for small bugs in the CM1511... At least I learn for myself that ccmrepair during the TS resolves the issue or if you capture the image manually (using your guide step by step) the bug is not there and the image works perfectly! Thanks again Niall!

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
Go to topic listing
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.