in my environment that is from a GPO tattoo leaving an old site code behind. http://myitforum.com/myitforumwp/2012/10/05/configmgr-client-gpo-assignment-removal/
On Mon, Dec 1, 2014 at 4:59 PM, Murray, Mike <[email protected]> wrote: > The ccmsetup.log file says it completed successfully. There is no > execmgr.log (in fact, there are only 13 log files in the CCM\Logs folder). > ClientIDManagerStartup.log has this error repeatedly: > > > > RegTask: Failed to refresh site code. Error: 0x8000ffff > > > > I’ll try running this script. Thanks! > > > > Mike > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Krueger, Jeff > *Sent:* Monday, December 1, 2014 1:24 PM > *To:* [email protected] > *Subject:* RE: [mssms] Client won't install properly > > > > Does the ccmsetup.log show that it completed successfully? What does the > ClientIDManagerStartup.log say? Do you have an execmgr.log on that PC? > > > > If it looks like ccmsetup finished successfully but the components/actions > aren’t showing up in the control panel applet you may have an issue with > WMI, you can try running mofcomp on the PC. We’ve seen instances where it > looks like the client installed but it cannot register with the site > (errors in ClientIDManagerStartup.log) and we noticed that there would not > be an execmgr.log file and many others that were missing. > > > > Here’s a script you can try which will recompile the .mof files on the PC > > > > $PC = 'Computer name goes here' > > Invoke-Command -ScriptBlock ${function:Fixwmi} -ComputerName $PC > > Invoke-Command -ComputerName $pc -ScriptBlock {Start-Service -Name CcmExec > } > > > > > > > > Function FixWMI (){ > > Set-Service -Name Winmgmt -StartupType Disabled > > Stop-Service -Name Winmgmt -Force > > $wbem = 'C:\Windows\System32\wbem' > > Set-Service -Name Winmgmt -StartupType Automatic > > Start-Service -Name Winmgmt > > Start-Sleep -Seconds 10 > > $mofget = Get-ChildItem -Path $wbem -Name '*.mof' > > Foreach ($mof in $mofget) > > { > > & c:\windows\system32\wbem\mofcomp.exe "$wbem\$mof"} > > } > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Sean Pomeroy > *Sent:* Monday, December 1, 2014 3:34 PM > *To:* [email protected] > *Subject:* Re: [mssms] Client won't install properly > > > > Have you tried manually designating the site code in control panel? > > On Mon, Dec 1, 2014, 14:45 Paul Winstanley <[email protected]> wrote: > > Is the DNS address correct? Always worth checking first. > > > On 1 Dec 2014, at 19:24, Murray, Mike <[email protected] > <https://urldefense.proofpoint.com/v2/url?u=http-3A__mailto-3AMMurray-40csuchico.edu&d=AAMFaQ&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=UIAc1TNoGO2HuYHjp9C4h6d6nNTeM48LUr_BwpjL8I8&s=YtgIYvFS534ZZ3ro0kdPVbQoJpcNc84OFWq-Ld2_tbU&e=>> > wrote: > > Hey folks, > > > > We have a computer that when we try to install the client, it appears to > install OK, but it’s not communicating with the server. The CM control > panel applet is missing the site code, server info, etc. Early > troubleshooting led me to think it may be BITS related, but there are no > jobs in BITS. I checked the LocationServices.log file (attached) and there > are multiple errors. I Googled these errors, but the matches I find relate > these errors to workgroup systems. However, this computer is domain-joined, > and is getting policy as expected. It is within our defined boundaries as > well. > > > > Any other ideas? > > > > > > Best Regards, > > > > Mike Murray > > Desktop Management Coordinator - IT Support Services > > California State University, Chico > > 530.898.4357 > [email protected] > <https://urldefense.proofpoint.com/v2/url?u=http-3A__mailto-3Ammurray-40csuchico.edu&d=AAMFaQ&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=UIAc1TNoGO2HuYHjp9C4h6d6nNTeM48LUr_BwpjL8I8&s=Tm5xikMvnHV_OqQemHaXW2lsdrf9_9GkAsBoE_GXdtY&e=> > > > > > > <LocationServices.log> > > > > > > > ------------------------------ > > > CONFIDENTIALITY NOTICE: This email contains information from the sender > that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise > protected from disclosure. This email is intended for use only by the > person or entity to whom it is addressed. If you are not the intended > recipient, any use, disclosure, copying, distribution, printing, or any > action taken in reliance on the contents of this email, is strictly > prohibited. If you received this email in error, please contact the sending > party by reply email, delete the email from your computer system and shred > any paper copies. > > Note to Patients: There are a number of risks you should consider before > using e-mail to communicate with us. See our Privacy & Security page on > www.henryford.com for more detailed information as well as information > concerning MyChart, our new patient portal. If you do not believe that our > policy gives you the privacy and security protection you need, do not send > e-mail or Internet communications to us. > > > >
