RE: Options for managing Windows and Linux updates on servers connecting to the i

Which server is acting as the client and which is acting as a server? Difference being the Server listens for connections and the Client initiates the connection.


Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Thursday, October 19, 2017 10:41 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
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?