SCE Agents reacting curiously with SCE Server
Hello,I have a pretty interesting issue going on with my SCE deployment. The installation of the server went fine, as well as installation of the agent on several machines (appx. 20 PCs). The computers show up on the adminstration page, under the "Agents Managed" node, and shows "healthy" as its health states. However, on the computers page, under the "All computers" node; the computer names are visible, however it show that the computers have not been contacted yet. So, I go to the client pc that has the agent, and run wuauclt /detectnow command. After a few seconds, I check the "all computers" node and notice that the computer I ran the command on now shows that it has been contacted. Now here is where it gets weird. When I proceed to do the same procedure (wuauclt /detectnow) on another computer name, and check the "all computers" node; i notice that the computer I just ran the command on shows that it has been contacted, BUT, the computer I had previously ran the command on is now GONE! The "all computers" node still shows that there are a total of 20 PCs in it, but I don't see the ones I ran the command on. Please advise. If you need any logs to be posted, please let me know and I will give you addtional info.I also wanted to include that the computers that have the agent installed do show up on the "agents managed" node on the admin page, but is not automatically reporting/contacting the SCE server. Additionally, checking the eventvwr, I noticed events that state that the computers serving management group XXX_MG with id (blah blah blah) is not heartbeating. What does this mean? Thanks again.
April 3rd, 2009 9:37pm

Hi,Looks like you are deploying your machines with an OS "Image" - could that be the case? If thats the case you need to clean up som eregsitry keys since the "automatic update agent" isn't sysprep aware (it is now when you use the latesed version).If i'm right, run the following before running sysprep: net stop wuauservREG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /fREG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /fREG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /fnet start wuauservwuauclt /resetauthorization /detectnowBjrn Axell MVP - Advisec ABhttp://blog.advisec.com
Free Windows Admin Tool Kit Click here and download it now
April 6th, 2009 12:21am

hey bjorn...you are correct. we are using imaged pcs, and it looks like this may be the reason for my problem. what do i do about the computers that are already deployed? is there an easy way for me to make these registry changes at once? when you mentioned the latest version, do you mean sp1?thanks for you helpon this. i will use your infofor our futureimages. thanks, again. H.
April 6th, 2009 10:34pm

hey bjorn...upon reading your post again, i read it wrong. when referring to the lastest version, you are talking about sysprep, right? not sce.
Free Windows Admin Tool Kit Click here and download it now
April 6th, 2009 11:41pm

Hi,You are right, it is the automatic update version. To fix it on your machines that you already deployed you can run the same commands as I wrote in my post:net stop wuauservREG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /fREG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /fREG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /fnet start wuauservwuauclt /resetauthorization /detectnowThis will fix it.Bjrn Axell MVP - Advisec ABhttp://blog.advisec.com
April 6th, 2009 11:58pm

awesome, bjorn....thanks for you help on all this. i will batch the script (duh..i knew that. lol.) anyways, thanks again.H.
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2009 12:08am

hey bjorn,i may have ended this thread too soon. when i run the script you provided onthe machines in question, the first two registry keys do not exist (AccountDomainSid & PingID). The third one (SusClientID), however, does exists. upon further investigation, igot word from one of our techs that we no longer use sysprep for our images, rather we use ghostwalk. is that the reason why the two keys do not exist? . ghostwalk is an application we run after the image has been deployed to reset the sid with a new computer name. we use norton ghost to deploy all images. does this make a difference? thanks, again for all your help.H.
April 7th, 2009 6:37pm

Hi, If the first two registry do not exist, you can only delete the third one. More info, you can refer to following KB: http://support.microsoft.com/default.aspx/kb/903262HTH.Jie-Feng Ren - MSFT
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2009 10:43am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics