Typically only stopping the
AdminService before rebooting, will show as
'not running' as soon as it has sent the stop request to the AdminServer process (java.exe)
- The AdminServer then needs to terminate managed resources and disconnect from running databases, this has not changed.
- Before rebooting the machine, managed databases need to be stopped because these will always and have always remained running (dbman -stop -all, proshut dbname -by -shutdownTimeout)
then stop the AdminServer (proadsv -stop, which does auto-stop all appservers unless the -keepservers flag is configured ) - Assuming the 'not running' state of the AdminService, does not imply resources have shut down and consequent repercussions when the machine re-starts are often exacerbated when the restart is tied to software updates.
Since circa Windows 10+, all
"Server reboot" is a little context-sensitive with respect to how Windows Power Options are configured specifically in relation to when the
"Fast Startup" feature is turned on, which is similar to the
Fast Boot feature in preceeding Windows 8.
- This can result in not shutting down AdminServer and managed Databases, as when "Turn on fast startup" is enforced - the system does not actually shutdown when rebooted.
- To Disable the "Fast Startup" feature to shutdown the Windows machine completely:
Control panel > Power options > Choose what the power buttons do > Shutdown settings > uncheck the "Turn on fast startup" Option
The Windows Fast Startup feature also affects shudown and restart actions. For further information refer to Article:
