We just upgrade the K1000 to version 7.2.101.  I started deploying the new version of agent to the machines and I have gotten reports of the machines rebooting.  Is anyone else experiencing this issue?

Thank you,

Mark
Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answer Chosen by the Author

1
this is a known limitation with the 7.2 agent.
This happens in one of two cases:
1. you installed a MSI or similar (for instance patching) with a /noreboot flag. The agent install does not use these flags so the system reboots.
2. you are using metering. Since the agent installation cannot grab a special file used by metering it needs to reboot.

This will be fixed with the soon to be released 8.0 
Answered 09/13/2017 by: Nico_K
Red Belt

  • for the second issue you can find the KB here:
    https://support.quest.com/kace-systems-management-appliance/kb/232553
Please log in to comment

Answers

0
I haven't seen it in our environment. Have you checked the event logs on any of the computers that experienced the reboot? If the agent upgrade caused the restart that should be indicated in the logs.
Answered 09/13/2017 by: chucksteel
Red Belt

Please log in to comment
0
We did check the logs on the PC and it shows KACE initiating the reboot. 

The processmsiexec.exe has initiated the restart of computer xxxxxPC on behalf of userNT AUTHORITY\SYSTEM for the following reason: No title for this reason could befound

Reason Code:0x80030002

Shutdown Type:restart

Comment: TheWindows Installer initiated a system restart to complete or continue theconfiguration of 'Quest KACE Agent'.

Answered 09/13/2017 by: msouva
White Belt

Please log in to comment
0
We had a similiar problem in one of our offices. The problem was only present for those clients where the Monitoring was active.
Answered 09/13/2017 by: Alex_
White Belt

Please log in to comment
Answer this question or Comment on this question for clarity