Reboot

Synopsis of functionality

Utilize Servers.txt and PubApps.txt for specific variables # will need to be updated #
Run from Central Location (Licensing Svr)

PRE JOB
Starts at beginning of Maintenance Window

Logs System Name, IP Address, OS and SP, logged on users to ~Temp and %Systemroot%\Temp
Appends Log or Creates New
Writes start time
Hosting Environment Reboot Script verifies logging off users.
records User Name, Declared executable from PubApps.txt to gracefully end; if it can’t in specified time then force
records contents of Pending File Rename Operations; if any
Parse Pending File Rename for Date / App install
initially tries graceful logoff of user, then will force user off line,
Stop Spooler, Delete Print Jobs
Delete temp / tmp files
empty all recycle bin
Write Finish time, and Operations completed

REBOOT Cycle
Verify (partner up or down) State. IF up and not in reboot process Start REBOOT
Write Reboot cycle Start Time
Writes event viewer information event, to signify Script is Logging off users / Rebooting
captures failed to stop processes, terminates them
upon reboot, verifies log file on ~temp and local match, writes finish time
verifies no errors on reboot, If errors on reboot, logs them
Time Check in minutes for server up verify; from Running server to reboot client. Set status
Condition 1 Server up, Success. Condition 2 no response, FAIL
Error handling: Failed reboot server won’t go down, EMAIL or SMS
Server rebooted, but specific services will not start (ima), EMAIL or SMS
Server rebooted, but generated more than 5 Error events in Event Viewer EMAIL or SMS
Notify Partner Completed, Secondary server can Start Reboot Process

POST JOB
Write Reboot Cycle Stop Time
Determines Success or Fail Success Report emailed; Fail report Urgent EMAIL or SMS
Email Condensed Report, Server Name, (Success / Fail)

Leave a Reply

Your email address will not be published. Required fields are marked *