For Windows servers, you could use a tool such as our Automate software.
Automate can potentially do steps 1 - 5 for you.
There are several hundnred built-in actions for Windows including Start/Stop services, connect to IBMi and run processes, run remote Windows processes via agent or by using remote PowerShell actions perhaps.
If you happen to use one of the HelpSystems scheduler products, Automate can also be scheduled to run directly from the IBMi.
If you're interested in a discussion let me know.
Otherwise you can download a trial here:
http://www.helpsystems.com/automate
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
message: 2
date: Thu, 19 Oct 2017 17:40:49 +0000
from: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
subject: Options for managing Windows and Linux updates on servers
connecting to the i
Because of the Equifax security breach and other security issues, our remote server update policy has been changed from once a month to every 48 hours, automatic updates enabled.
This is causing some issues with those servers connecting to the i.
Most, not all, require a managed, controlled recycle process.
1) Stop service on the I
2) Stop service on remote server.
3) Apply updates/reboot remote server.
4) Start the service on the remote server.
5)Start the service on the i.
If the remote server is a Linux box, we have tools for steps 2,3,4 from the i.
For Windows servers, not as easily done.
Any thoughts from the group for various options on how to manage these processes?
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
midrange.com
