My past experience has been if necessary files are not able to download from available DPs for some reason or BITS creates a background job, it automatically gets created. Setup log shows the retry attempts.
Cesar A. Meaning is NOT in words, but inside people! Dr. Myles Munroe My iPad takes half the blame for misspells. > On Jul 16, 2014, at 7:00 PM, Magnus Tveten <[email protected]> wrote: > > Hmmm yeah WMI looks ok and the client installs fine... > Maybe there was an initial issue which triggered the task to be created.... > > However I think the reason it does not get cleaned up is that it has been > created in the wrong spot... > > <image002.png> > > I would not expect that the path is supposed to be > > \Microsoft\Microsoft\Configuration Manager > > I think it should have been > \ Microsoft\Configuration Manager > > And sit in the same spot as the other two tasks, then it probably would have > been managed to be removed after it was used. > > > MAGNUS TVETEN > SERVER SUPPORT ENGINEER > CO CITRIX/SERVER > > Insurance Australia Group Limited > Lvl 1, 23 Lakeside Drive, Burwood > Burwood East VIC 3151 > Australia > > T +61 3 8804 3226 F +61 X XXX XXXX M +61 411 010 460 > E [email protected] > www.iag.com.au > > PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL. > From: [email protected] [mailto:[email protected]] > On Behalf Of elsalvoz > Sent: Thursday, 17 July 2014 10:32 AM > To: [email protected] > Subject: Re: [mssms] SCCM client uninstalling and reinstalling itself > > it is a normal behavior for the client install unless /noservice is > specified. This means there was a failure during one of the installation > attempts and the task gets automatically created and keeps on trying. it is > interesting that it is stuck retrying after the install is successful. you > can delete using the schedule task command line tool. > > WMI ok on those boxes? > > > On Wed, Jul 16, 2014 at 3:55 PM, Magnus Tveten <[email protected]> > wrote: > Hmmmmm > We actually have a client on a win7 box that does the exact same thing.... > And sure enough there is that scheduled task too... > > Hmmm found this.... > http://social.technet.microsoft.com/Forums/en-US/dc879316-557c-4739-9c5a-a19d416ced5a/configuration-manager-client-retry-scheduled-task-not-removed?forum=configmanagerdeployment > that post did not really get anywhere.... > > our ccrretry.box is empty, and the client keeps re-installing successfully > > > MAGNUS TVETEN > SERVER SUPPORT ENGINEER > CO CITRIX/SERVER > > Insurance Australia Group Limited > Lvl 1, 23 Lakeside Drive, Burwood > Burwood East VIC 3151 > Australia > > T +61 3 8804 3226 F +61 X XXX XXXX M +61 411 010 460 > E [email protected] > www.iag.com.au > > PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL. > From: [email protected] [mailto:[email protected]] > On Behalf Of Ryan Shugart > Sent: Thursday, 17 July 2014 7:23 AM > To: [email protected] > Subject: RE: [mssms] SCCM client uninstalling and reinstalling itself > > Event Viewer had nothing, but I think I found what triggered it. In Task > Manager, there’s a task called “Configuration Manager Client Retry Task” that > is set to run every 5 hours 43 minutes after the hour. The commandline is > C:\Windows\ccmsetup\ccmsetup.exe /ForceInstall /config:MobileClient.tcf > /RetryWinTask:1 > I need to figure out how that got there, but I’ll bet that’s what was causing > problems. Why the SCCM client set up a task to reinstall itself, or why > anything would, since the healthchecks were passing is odd. But hey. > Ryan > > From: [email protected] [mailto:[email protected]] > On Behalf Of Philip George > Sent: Wednesday, July 16, 2014 3:07 PM > To: [email protected] > Subject: Re: [mssms] SCCM client uninstalling and reinstalling itself > > You can check the ccmsetup log to find more on what triggered it or the event > viewer should also have the details on what could have triggered this. > > > > On Wed, Jul 16, 2014 at 1:32 PM, Ryan Shugart <[email protected]> wrote: > Hi: > Thanks for your idea. The scheduled task history got wiped > when the client installed and reinstalled itself, but its set to run once a > day at midnight. So unless it took over 7 hours to complete a check I don’t > think that was it unless something kicked it off. Does this store a log > separate from the client logs? > Ryan > > From: [email protected] [mailto:[email protected]] > On Behalf Of Philip George > Sent: Wednesday, July 16, 2014 2:12 PM > To: [email protected] > Subject: Re: [mssms] SCCM client uninstalling and reinstalling itself > > > Hi, > > You can check the scheduled task there is a client health check that runs > that might have caused this, this runs ccmeval which runs various checks > > http://systemcenterfan.wordpress.com/tag/ccmeval-exe/ > http://support.microsoft.com/kb/2796086 > > <image003.png> > > > > > > > On Wed, Jul 16, 2014 at 12:29 PM, Ryan Shugart <[email protected]> wrote: > Hi: > I have a Windows Server 2008R2 machine on which at about 7:45 AM this > morning the SCCM client mysteriously decided to uninstall itself for no > reason. Then, a few seconds after it uninstalled, it reinstalled. It did > this again at about 12:45 this afternoon. Unfortunately during the install > all the client logs are getting wiped so I can’t go see why it felt the need > to uninstall itself. All I can see in event viewer is the Windows Installer > service removing the client then reading it, I can’t see where it got that > directive from. My first thought is the client health check, however the > SCCM server reports that last ran at 12:07 this morning and returned a > verdict of healthy. So, I’m not too sure where to go looking. We only found > out about this because in the removel and reinstall the deployment history > was wiped, so several deployments were reran and the machine restarted on us. > Any idea what would cause this? > Thanks. > Ryan > > Ryan Shugart > LAN Administrator > MiTek USA, MiTek Denver > 314-851-7414 > > > MiTek Holdings, Inc., 2011-2014, All Rights Reserved > ________________________________ > This communication (including any attachments) contains information which is > confidential and may also be privileged. It is for the exclusive use of the > intended recipient(s). If you are not the intended recipient(s), please note > that any distribution, copying, or use of this communication or the > information in it is strictly prohibited. If you have received this > communication in error, please notify the sender immediately and then destroy > any copies of it. > > > > > > > > The information transmitted in this message and its attachments (if any) is > intended only for the person or entity to which it is addressed. The message > may contain confidential material and /or personal information. If you have > received this in error, please contact the sender and delete this e-mail and > associated material from any computer. > > > > The information transmitted in this message and its attachments (if any) is > intended only for the person or entity to which it is addressed. The message > may contain confidential material and /or personal information. If you have > received this in error, please contact the sender and delete this e-mail and > associated material from any computer. >
