This article outlines the situations when a reboot is needed for ACC. Also, it provides information about how to reboot the system with the
sadmin command.
A reboot is needed in the following scenarios: Install / Upgrade / Disable
Windows
- Install Type: Fresh Install
- Enable Type: Full Feature Activation - (Reboots system)
- Reboot Needed: Yes (automatically with task)
- Install Type: Fresh Install
- Enable Type: Limited Feature Activation (restart of services only)
- Reboot Needed: No
Linux
- Install Type: Fresh Install
- Reboot Needed: Depends
- Yes (if Reboot endpoint is enabled)
- No (if Reboot endpoint is disabled)
Windows
- Install Type: Upgrade
- Current Mode: Update / Enabled / Observe / Inventory
- Reboot Needed: Yes (not automatic)
- Install Type: Upgrade
- Current Mode: Disable
- Enable Type: Full Feature Activation - (Reboots system)
- Reboot Needed: Yes (Automatically)
- Install Type: Upgrade
- Current Mode: Disable
- Enable Type: Limited Feature Activation (restart of services only)
- Reboot Needed: Yes (not automatically)
- Recommendation: Reboot is needed after the upgrade and before the enablement to reload newer drivers.
Linux
- Install Type: Upgrade
- Current Mode: Update / Disable
- Reboot Needed: Yes (not automatic)
Windows
- Install Type: Upgrade (failure)
- If upgrading / installing ACC 8.2.1 (and later) and install fails, MPT needs a reboot to clear out failed driver installs.
- Uninstall
- After the uninstall of any ACC 8.1.x and later, a reboot is needed to clear the SysCore files.
Other specific times that need a reboot:
Windows
- Current Mode: Enable / Observe / Update / Inventory
- Action: Change to Disable Mode
- Reboot Needed: Yes
Linux
- Current Mode: Enable / Observe / Update
- Action: Change to Disable Mode
- Reboot Needed:
Policy-based configuration that needs a reboot:
Windows
NOTE: The configurations below might need the reboot depending on the process or service that the action has taken.
Skiplist -
-f File operations passthrough attribute
-i Ignore path passthrough attribute
-v volume skipping
Attributes - Memory protection bypass (depends on process / services)
-c Bypassed from Critical Address Space Protection attribute
-h Attribute for inclusion in MP Compat Protection
-j Attribute to bypass from MP Compat Protection
-n Bypassed from DEP protection Attribute
-p Process context file operations bypass attribute
-v Forced Relocation Bypass Attribute
-m Blocked Interpreters in interactive mode.
Execution Control rules
How to force a reboot with the sadmin command in ePO:
- Create a client task (sc:run) command.
ssreboot -m "This is to reboot per upgrade in 5 minutes" -t 300
-m = message
-t = time in seconds
- Assign the task to the client.
How to force a reboot with the sadmin command in the standalone system:
- Recover CLI.
- Run the command below:
sadmin ssreboot -m "This is to reboot per upgrade in 5 minutes" -t 300
-m = message
-t = time in seconds