geckostech

iirc this was a known issue. Need to get that patched to fix

I thought it has worked, the client is off, but now I am getting this in ccmrepair.log: Running query 'SELECT * FROM CCM_Service_HostedApplication WHERE Type="Server"' against namespace: '\\.\ROOT\ccm\Policy\Machine' CcmRepair 07/09/2015 14:51:42 2128 (0x0850) CCMExec is supporting application versions 5.0.7000.* through 5.0.9000.* CcmRepair 07/09/2015 14:51:42 2128 (0x0850) CCMExec is currently hosting a server application. CcmRepair 07/09/2015 14:51:42 2128 (0x0850) Checking product registrations. CcmRepair 07/09/2015 14:51:42 2128 (0x0850) Found product code = {948643F6-8526-4555-93DA-6EBF50CA7650} CcmRepair 07/09/2015 14:51:42 2128 (0x0850) Found product "ConfigMgr Distribution Point" version 5.00.7804.1000 upgrade code {31CEACF7-394A-4FF4-B591-2E7B0E0F90B8} CcmRepair 07/09/2015 14:54:14 2128 (0x0850) Found product code = {861C35CB-8117-469B-A847-D948AEE1F507} CcmRepair 07/09/2015 14:54:14 2128 (0x0850) Found product "ConfigMgr Management Point" version 5.00.8239.1000 upgrade code {ABD0F60F-1622-4311-8989-106B60D784FF} CcmRepair 07/09/2015 14:54:14 2128 (0x0850) Looking for product code '{948643F6-8526-4555-93DA-6EBF50CA7650}' in WMI CcmRepair 07/09/2015 14:54:14 2128 (0x0850) Could not get registration for product "ConfigMgr Distribution Point". Repair required. WMI returned (80041002) CcmRepair 07/09/2015 14:54:14 2128 (0x0850) Initiating repair. CcmRepair 07/09/2015 14:59:14 104 (0x0068) Repairing CCM products CcmRepair 07/09/2015 14:59:14 4044 (0x0FCC) Repairing product {948643F6-8526-4555-93DA-6EBF50CA7650} CcmRepair 07/09/2015 14:59:14 4044 (0x0FCC) Upgrade Code = {31CEACF7-394A-4FF4-B591-2E7B0E0F90B8} CcmRepair 07/09/2015 14:59:14 4044 (0x0FCC) MSI will log to E:\SMS_CCM\logs\repair-msi-948643F6-8526-4555-93DA-6EBF50CA7650.log CcmRepair 07/09/2015 14:59:14 4044 (0x0FCC) Couldn't get ccmsetup path. Repair the client msi directly. CcmRepair 07/09/2015 14:59:14 4044 (0x0FCC) Installation failed. Check log file for details CcmRepair 07/09/2015 14:59:16 4044 (0x0FCC) Repairing product {861C35CB-8117-469B-A847-D948AEE1F507} CcmRepair 07/09/2015 14:59:16 4044 (0x0FCC) Upgrade Code = {ABD0F60F-1622-4311-8989-106B60D784FF} CcmRepair 07/09/2015 14:59:16 4044 (0x0FCC) Installed product is Management Point CcmRepair 07/09/2015 14:59:16 4044 (0x0FCC) MSI will log to E:\SMS_CCM\logs\repair-msi-861C35CB-8117-469B-A847-D948AEE1F507.log CcmRepair 07/09/2015 14:59:16 4044 (0x0FCC) Repairing Management Point with command line: REINSTALL=ALL REINSTALLMODE=vmaus USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=63 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 CcmRepair 07/09/2015 14:59:16 4044 (0x0FCC) Running query 'SELECT * FROM CCM_Service_HostedApplication WHERE Type="Server"' against namespace: '\\.\ROOT\ccm\Policy\Machine' CcmRepair 07/09/2015 15:00:45 4496 (0x1190) CCMExec is supporting application versions 5.0.7000.* through 5.0.9000.* CcmRepair 07/09/2015 15:00:45 4496 (0x1190) CCMExec is currently hosting a server application. CcmRepair 07/09/2015 15:00:45 4496 (0x1190) Checking product registrations. CcmRepair 07/09/2015 15:00:45 4496 (0x1190) Found product code = {948643F6-8526-4555-93DA-6EBF50CA7650} CcmRepair 07/09/2015 15:00:45 4496 (0x1190) Found product "ConfigMgr Distribution Point" version 5.00.7804.1000 upgrade code {31CEACF7-394A-4FF4-B591-2E7B0E0F90B8} CcmRepair 07/09/2015 15:00:45 4496 (0x1190) Found product code = {861C35CB-8117-469B-A847-D948AEE1F507} CcmRepair 07/09/2015 15:00:45 4496 (0x1190) Found product "ConfigMgr Management Point" version 5.00.8239.1000 upgrade code {ABD0F60F-1622-4311-8989-106B60D784FF} CcmRepair 07/09/2015 15:00:45 4496 (0x1190) Looking for product code '{948643F6-8526-4555-93DA-6EBF50CA7650}' in WMI CcmRepair 07/09/2015 15:00:45 4496 (0x1190) Could not get registration for product "ConfigMgr Distribution Point". Repair required. WMI returned (80041002) CcmRepair 07/09/2015 15:00:45 4496 (0x1190) Initiating repair. CcmRepair 07/09/2015 15:05:45 1352 (0x0548) Success CcmRepair 07/09/2015 15:05:54 4044 (0x0FCC) Repair complete. CcmRepair 07/09/2015 15:05:54 4044 (0x0FCC) and this in mpcontrol.log: SSL is enabled. SMS_MP_CONTROL_MANAGER 07/09/2015 15:09:28 4036 (0x0FC4) Client authentication is also enabled. SMS_MP_CONTROL_MANAGER 07/09/2015 15:09:28 4036 (0x0FC4) CRL Checking is also enabled. SMS_MP_CONTROL_MANAGER 07/09/2015 15:09:28 4036 (0x0FC4) Machine name is 'blahblahblah.local'. SMS_MP_CONTROL_MANAGER 07/09/2015 15:09:28 4036 (0x0FC4) Begin validation of Certificate [Thumbprint ebf1c024fbffc3bbf6e46bb098bf291b6020a540] issued to 'blahblahblah.local.local' SMS_MP_CONTROL_MANAGER 07/09/2015 15:09:28 4036 (0x0FC4) Certificate has "SSL Client Authentication" capability. SMS_MP_CONTROL_MANAGER 07/09/2015 15:09:28 4036 (0x0FC4) Completed validation of Certificate [Thumbprint ebf1c024fbffc3bbf6e46bb098bf291b6020a540] issued to 'blahblahblah.local.local' SMS_MP_CONTROL_MANAGER 07/09/2015 15:09:28 4036 (0x0FC4) >>> Selected Certificate [Thumbprint ebf1c024fbffc3bbf6e46bb098bf291b6020a540] issued to 'blahblahblah.local.local' for HTTPS Client Authentication SMS_MP_CONTROL_MANAGER 07/09/2015 15:09:28 4036 (0x0FC4) Call to HttpSendRequestSync failed for port 443 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 07/09/2015 15:09:28 4036 (0x0FC4) Sent summary record of SMS Management Point on ["Display=\\blahblahblah.local.LOCAL\"]MSWNET:["SMS_SITE=site"]\\blahblahblah.local.LOCAL\ to E:\SMS\MP\OUTBOXES\sitestat.box\xqhc2f3q.SUM, Availability 1, 366998524 KB total disk space , 338284764 KB free disk space, installation state 0. SMS_MP_CONTROL_MANAGER 07/09/2015 15:09:28 4036 (0x0FC4) Successfully performed Management Point availability check against local computer. SMS_MP_CONTROL_MANAGER 07/09/2015 15:09:28 4036 (0x0FC4) Initialization still in progress. SMS_MP_CONTROL_MANAGER 07/09/2015 15:09:28 4036 (0x0FC4)

Hi, I've been having a problem with one of my management points since I upgraded to Configuration Manager 2012R2 SP1 CU1 on Server 2012R2. The management point doesn't seem to be communicating with clients. in mpcontrol log I get this repeating: SSL is enabled. SMS_MP_CONTROL_MANAGER 07/09/2015 09:49:29 3944 (0x0F68) Client authentication is also enabled. SMS_MP_CONTROL_MANAGER 07/09/2015 09:49:29 3944 (0x0F68) CRL Checking is also enabled. SMS_MP_CONTROL_MANAGER 07/09/2015 09:49:29 3944 (0x0F68) Machine name is 'blahblahblah.local'. SMS_MP_CONTROL_MANAGER 07/09/2015 09:49:29 3944 (0x0F68) Begin validation of Certificate [Thumbprint ebf1c024fbffc3bbf6e46bb098bf291b6020a540] issued to 'blahblahblah.local' SMS_MP_CONTROL_MANAGER 07/09/2015 09:49:29 3944 (0x0F68) Certificate has "SSL Client Authentication" capability. SMS_MP_CONTROL_MANAGER 07/09/2015 09:49:29 3944 (0x0F68) Completed validation of Certificate [Thumbprint ebf1c024fbffc3bbf6e46bb098bf291b6020a540] issued to 'blahblahblah.local' SMS_MP_CONTROL_MANAGER 07/09/2015 09:49:29 3944 (0x0F68) >>> Selected Certificate [Thumbprint ebf1c024fbffc3bbf6e46bb098bf291b6020a540] issued to 'blahblahblah.local' for HTTPS Client Authentication SMS_MP_CONTROL_MANAGER 07/09/2015 09:49:29 3944 (0x0F68) Call to HttpSendRequestSync failed for port 443 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 07/09/2015 09:49:29 3944 (0x0F68) Sent summary record of SMS Management Point on ["Display=\\blahblahblah.LOCAL\"]MSWNET:["SMS_SITE=site"]\\blahblahblah.LOCAL\ to E:\SMS\MP\OUTBOXES\sitestat.box\0wco2fhb.SUM, Availability 1, 366998524 KB total disk space , 365956168 KB free disk space, installation state 0. SMS_MP_CONTROL_MANAGER 07/09/2015 09:49:29 3944 (0x0F68) Successfully performed Management Point availability check against local computer. SMS_MP_CONTROL_MANAGER 07/09/2015 09:49:30 3944 (0x0F68) Initialization still in progress. SMS_MP_CONTROL_MANAGER 07/09/2015 09:49:30 3944 (0x0F68) I read somewhere about WMI causing the client to repair repeatedly and sure enough in ccmrepair.log I am getting this repeating: Initiating repair. CcmRepair 07/09/2015 10:30:24 6524 (0x197C) Ccmsetup returned exit code 0 CcmRepair 07/09/2015 10:47:58 408 (0x0198) Success CcmRepair 07/09/2015 10:47:58 408 (0x0198) Repair complete. CcmRepair 07/09/2015 10:47:58 408 (0x0198) Running query 'SELECT * FROM CCM_Service_HostedApplication WHERE Type="Server"' against namespace: '\\.\ROOT\CCM\Policy\Machine' CcmRepair 07/09/2015 10:48:09 1600 (0x0640) CCMExec is currently NOT hosting a server application. CcmRepair 07/09/2015 10:48:09 1600 (0x0640) Checking product registrations. CcmRepair 07/09/2015 10:48:09 1600 (0x0640) Found product code = {948643F6-8526-4555-93DA-6EBF50CA7650} CcmRepair 07/09/2015 10:48:09 1600 (0x0640) Found product "ConfigMgr Distribution Point" version 5.00.7804.1000 upgrade code {31CEACF7-394A-4FF4-B591-2E7B0E0F90B8} CcmRepair 07/09/2015 10:48:10 1600 (0x0640) Found product code = {343D4507-997F-4553-9F86-2BB81F19A05E} CcmRepair 07/09/2015 10:48:10 1600 (0x0640) Found product "Configuration Manager Client" version 5.00.8239.1000 upgrade code {252DA259-82CA-4177-B8D0-49C78937BA3E} CcmRepair 07/09/2015 10:48:10 1600 (0x0640) Looking for product code '{343D4507-997F-4553-9F86-2BB81F19A05E}' in WMI CcmRepair 07/09/2015 10:48:10 1600 (0x0640) Confirmed registration for product "Configuration Manager Client". CcmRepair 07/09/2015 10:48:10 1600 (0x0640) Looking for product code '{948643F6-8526-4555-93DA-6EBF50CA7650}' in WMI CcmRepair 07/09/2015 10:48:10 1600 (0x0640) Could not get registration for product "ConfigMgr Distribution Point". Repair required. WMI returned (80041002) CcmRepair 07/09/2015 10:48:10 1600 (0x0640) I have tried completely stripping the server down and removing all IIS, wsus, DP roles, the files for those roles, manually removing the client and all associated services and registry keys, and if I think reinstall the client, it is fine. As soon as I turn the server back into a site system server again however, the same issue starts. Help, I am stuck.

No worries

I really should remember to blog that

Are you 100% sure the client is installed correctly? I see this on my clients when the install has been corrupted. I usually fix it by: Stopping WMI service Stopping CCMExec SC Delete any sccm services (ccmexec, smstsmgr, cmecservice, ccmsetup) Delete C:\windows\ccm, C:\windows\ccmsetup, C:\windows\ccmcache, C:\Windows\SMSCFG.ini Go into regedit and remove: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCMSetup HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS Then restart WMI, and reinstall the client. You shouldn't need a reboot to complete this. Once this has been done the client should install ok and it should pick up the cert.

Try deleting any "unknown computer" from devices (obviously not unknown computer x86 and x64) as I've noticed this happening from a UEFI pxe if the system has already been through once

I was having a similar issue with regards to setting system language etc, these were being set in the unattend.xml and then being overwritten once the windows settings were applied. We don't set the password in the task sequence any more, for workgroup machines we set up a specific image with the users necessary (non-domain machines tend to be a rarity for us and generally for events and have specific requirements so this works well), and for domain machines the local admin password is set by group policy. I tried using with and without MDT but I was getting the same results, so now we fill in the User Name and Organization in the TS, as you've suggested.

Hi Jeroen, I had a similar problem with setting the variables during the task sequence, and I ended up not setting the variables this way, but setting them in collection variables instead. For instance (and I know this one isn't going to help your particular issue, but it might give you a direction to look in) I set OSDComputername as blank on the All Unknown Computers collection so that any new pc's we build we are asked for a computer name (due to the nature of our naming convention it just makes life easier as we are not a huge organisation). I was wondering if perhaps setting the variables for the organisation etc as collection variables, and then inputting the variable into the field in the TS might get around it?

Hi, I've recently upgraded to SCCM 2012 R2 and have an increasing number of clients moving from installed, to showing as no client installed at all. If I check the client on the machine, they look as thought they are reporting back, and if they are showing the old version, and I then manually instigate the upgrade, they upgrade ok, but still don't show as installed in the console. I'm pulling my hair out a bit and am at a loss as to where to look, is anyone able to give me some guidance? I'm running in native mode.

I'm getting this on one of mine too

Hi Niall, Check this post: http://www.windows-noob.com/forums/index.php?/topic/7217-client-version-50078041000-is-not-compatible-with-the-site-111-version-50077110000/ DerGali near the bottom made a post which has at least got the client installing for me. I will wait to see if the management points sort their pickle out by the morning.

This has got the clients installing for me after R2 upgrade. Thanks

Fixed it. You need to make sure the SMS_<site_code> share on your route has read permissions for the network access account and SCCM Server computer accounts.

I'm also getting this. Where do I find the client.msi.log? smsts.log smsts-20130308-194245.log

I got to the bottom of this in the end. It is because I had WAIK and ADK installed at the same time. Once I uninstalled ADK it runs fine. On to the next issue!

I've installed MDT on an SCCM site server running 2012 and server 2008. When I try to create a client task image, whatever combination of settings I use, I get this as the result: Started processing. Creating boot image. Copying WIM file. Mounting WIM file. WIM file mounted. Setting Windows PE system root. Set Windows PE system root. Set Windows PE scratch space. Adding standard components. Adding component: winpe-mdac Adding extra content from: C:\Users\blahblah\AppData\Local\Temp\2\zig2ez2h.ztm Unmounting WIM. Copying WIM to the package source directory. Creating boot image package. Error while importing Microsoft Deployment Toolkit Task Sequence. Failed to insert OSD binaries into the WIM file Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObject.Put(PutOptions options) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport) --- End of inner exception stack trace --- at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put() at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data) Can someone give me some pointers as to what is going wrong?

Hi, I'm running SCCM 2012. I have several windows 7 and 8 OS task sequences which run and install packages and come out great (well, apart from Flash, but hey, thats Flash!). My only problem is that all of the packages take literally hours to install, to the point where I end up leaving it running over night. The download is very short, even for bit things like office, but they all take hours. Is there a way I can speed this up, or something I may have overlooked?