ZeZe

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...

Update: I created a manual image, using the capture media and now it works. I used step-by-step by Niall! Still... what can make difference?

Which driver is it?! If it's not woking injecting, create a package to install using manufacture package (ex: msiexec /i install.msi /quiet) ... add this step your TS... I use this method when I have tricky drivers...

Are you using categories to select the drivers to be injected to that model?

I think i have this issue... what do you mean by refreshing?

The same problem happens with Windows 10... so... I'm doing something or I can't imagine why CCM fails to start... Does someone has any ideas?!

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!

Thanks GarthMJ. That's what I'm trying to do... to move the SQL to the same server because right now SQL and CM1511 are not running under the same server!

Hi all, I've my lab setup running under two servers (SCCM server and SQL server). I did this to keep the environment as equal as other environments where I work with. However, I need more space (hdd) and maybe this will also help me to gain some performance. I want to install the a new instance of SQL in the SCCM Server. Is this as simply as it should or it's a big challenge?! Steps that I think are necessary: - install same SQL version in SCCM server, same collation, reporting services; - remove reporting services roles - follow all these steps https://blogs.technet.microsoft.com/configurationmgr/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server/ - restart sccm server - install reporting services Is this to much or should I just refresh everything? (that's a lot of work as well)... This steps are for CM12 but since I'm using CM1511 not sure if they will work... I believe they will, but if someone has this kind of experience, I really appreciate. Thank you all!

Why not create a dynamic collection to target the models?

You might find the uninstaller execution on the VLC installation folder.

Check the agent settings... there is a small settings that it's kinda important to change in the "Computer Agent": - Set the default webcatalog point; - to add your web catalog to the trusted domains - YES - Allow Silverlight... - YES - Set your Portal name... (optional) When you deploy an application to users, if they aren't required, the user must go to the portal and request the application. You can also add the web catalog to the favorites in the internet explorer, via GPO (this is only a suggestion)... Enjoy!

You're deploying applications to users, then you are using Application Catalog... The applications will not be shown in the Software Center! Check this out: https://www.windows-noob.com/forums/topic/6629-using-system-center-2012-configuration-manager-part-8-deploying-applications/ You might need to install the roles and configure the CCM agent. If using Windows 10, make sure you don't try to open Application Catalog with Windows Edge.

Wow, thanks! Cool tip!

I guess Named Pipes are a requirement to run SCCM 2012. From all installation step-by-steps that I've read, SQL Named Pipes must be enabled. Just because named pipes are "old technology" it doesn't bring necessarily a security issue. Keep your environment updated (OS and service) patched with the appropriated firewall rules, access policy, accounts permissions, etc. That's my opinion, of course !

I had the same problem... Solution: downgrade to the ADK RTM. https://www.windows-noob.com/forums/topic/13626-sccm-lab-build-and-capture-on-vmware/ Check the last post that I published. All your problems will be gone with ADK RTM - check both links.

Question: during the migration how are the clients handle? Can do we migrate the agents to a new environment? What if the agent it's a old version?

and with ADK 10 RTM and not the latest version!

It's funny that we don't see this kinda of information on the MOC from the course!

Yep... agreed! The specified network password is not correct. (Error: 80070056; Source: Windows)]LOG]!><time="15:43:31.525+480" date="01-29-2016" component="CaptureSystemImage" context="" type="3" thread="740" file="capturesystemimage.cpp:809"> Also, I recommend that you use the FQDN!

true! I miss that! Indeed!

Did you try to manually install the update?!

hmm... strange! https://technet.microsoft.com/en-us/library/hh427336.aspx#BKMK_ManageSMSprovider If there was a problem during the installation you can always remove and re-install or you could also install the componente in another server (for what I have been reading so far, you can have multiple SMS providers). But I would consider to test this before you run this procedure on your production environment.

Ok, but did you check the messages? Select the componente, right click, show messages, show all messages, select date and time 1 day ago... What does it say?! opssy... wrong topic! but still works for you !

Check the monitoring for more troubleshooting. Is the firewall ON in the server that is running that componente?