Automating Sametime Community Server shutdown on Windows

Follow these instructions for the proper sequence of events for an automated shutdown of an IBM® Sametime® Community Server running on Microsoft Windows®.

About this task

If you try to automate the shutdown ofSametime Community Servers in batch files by using the Windows net stop command against Domino® without first shutting down Sametime services, then crash-on-shutdown events and long restart times can result. This sort of shutdown can also trigger crashes of other servers within a Community Services Cluster. These problems occur because the ST Community Launch service relaunches Sametime applications as needed. If Domino is stopped, then ST Community Launch works as designed and tries to relaunch the now-failing applications, with unpredictable results.

You can prevent these problems by creating your batch file with the proper sequence of events for an automated shutdown of the Sametime Community Server.

Procedure

Follow this order when you create your batch file:
net stop "Lotus Domino Server (CLotusDominodata)" 

<wait for service shutdown> 
Note: If your site has changed the service name from its default, then adjust the command accordingly. The Domino and Sametime services might require several minutes to shut down properly; this time is longer for high-volume servers. Best practices recommend performing the command manually first to observe the time required for shutdown.