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 > > > > [image: Inline image 1] > > > > > > > > > > > > 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. > > > > > > > >
