Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About geckostech

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
  1. 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-6
  2. 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 (0x0
  3. 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 comple
  4. 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
  5. 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
  6. 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 vari
  7. 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.
  8. 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.
  9. 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.
  10. I'm also getting this. Where do I find the client.msi.log? smsts.log smsts-20130308-194245.log
  • Create New...