Patching the Windows 2000 Server Operating System on S8100 Media Servers, IP600 Communications Servers, & DEFNITY ONE Communications Systems

Transcription

1 Patching the Windows 2000 Server Operating System on S8100 Media Servers, IP600 Communications Servers, & DEFNITY ONE Communications Systems Abstract This document provides guidance on how to apply Microsoft patches to S8100 Media Servers, IP600 Communications Servers, and DEFINITY ONE Communications Systems running the Windows 2000 Server operating system. 1

2 Table of Contents 1. Introduction Cautions and Warnings Downloading the Patch via Terminal Services Installing the Patch via Terminal Services...7 2

3 1. Introduction This document applies to Media Servers running the Windows 2000 Server operating system only. The IP600 Internet Protocol Communications Servers and DEFINITY ONE Communications Systems running software release 10, and S8100 Media Servers running Communication Manager 1.2 or later use the Windows 2000 Server operating system. Henceforth, The IP600, DEFINITY ONE, and S8100 products are referred to collectively as Media Servers. This document provides the steps required to obtain the MS Windows 2000 Server operating system patch directly from Microsoft and install it on the Media Server. However, the document can be used generically to apply other Microsoft operating system patches and upgrades. This document assumes the Media Server has Internet connectivity. If this is not the case, the Microsoft patch must be obtained from a separate system and FTP ed onto the Media Server. 2. Cautions and Warnings NOTE: Terminal Services is incompatible (does not work) with a Netscape browser. If IE 6.0 SP1 or greater, or Windows XP is running on the client used to perform the steps in this document, and the Media Server software release is earlier than Communication Manager 1.3 (i.e., release 10 or Communication Manager 1.2), Avaya Product Support must be contacted to apply Media Server software patch number 5368 prior to attempting to use Terminal Services. NOTE: It is important to verify you are on the latest Windows 2000 Service Pack prior to installation of any Microsoft Security patches. The steps specified in this document can also be used to upgrade the Windows 2000 Service Pack. NOTE: When applying operating system patches always follow best practices, which include saving translations, backing-up critical data, preparing a back out plan, and targeting least critical servers first. Application of operating system patches often requires a system reboot. Contact Avaya Product Support with any questions or problems. 3. Downloading Patches via Terminal Services Launch an IE browser from a system on your corporate Intranet Enter the following in the Address bar of the browser: o Server IP Address/tsweb where Server IP Address is the actual IP address of the Media Server (e.g., /tsweb in the following examples o Server Name/tsweb where Server Name is the domain name of the Media Server. The example in this document uses the IP address and not the domain name The page in Figure 1: Terminal Services Web Connection is displayed. 3

4 Figure 1: Terminal Services Web Connection Enter the Media Server IP address (e.g., ) in the Server: box Click the Connect button A Log On box is presented as shown in Figure 2: Log On Box 4

5 Figure 2: Log On Box Enter a User name and Password in the Log On box to access the Media Server desktop (Note: you must have a customer account on the system to access the desktop). After logging on, the Media Server desktop will appear as shown in Figure 3: Media Server Desktop. 5

6 Figure 3: Media Server Desktop Double click on the Internet Explorer icon on the desktop. This launches IE on the Media Server desktop The browser must be configured with the appropriate proxy server settings to allow the Microsoft patch download page to be accessed o This can be done on IE 6.0 by accessing Tools->Internet Options from the toolbar. Then select the Connections tab. Then click on the LAN Settings button. Set the proxy configurations appropriately to allow connections outside your corporate Intranet Navigate to the appropriate patch download on the Microsoft support web pages using the Media Server browser. The patch used in this example is MS See Figure 4: Microsoft MS Patch Download Page for an example. 6

7 Figure 4: Microsoft MS Patch Download Page Click on the Download button Save the patch to the following folder on the Media Server: D:/LucentPub/ftproot/Patches When the patch is successfully downloaded close the IE browser on the Media Server 4. Installing the Patch via Terminal Services After closing down the browser once the patch is downloaded, the desktop is still accessible via Terminal Services (see Figure 5: Media Server Desktop) 7

8 Figure 5: Media Server Desktop Double click on the My Computer icon Navigate to D:/LucentPub/ftproot/Patches NOTE: When applying operating system patches always follow best practices, which include saving translations, backing-up critical data, preparing a back out plan, targeting least critical servers first, contact Avaya product support with any questions. Make sure the system is backed up and a back out strategy is in place (see note above) Double click on the patch executable (Windows2000-KB x86-ENU.exe) to launch the Setup Wizard NOTE: The Setup Wizard prompts to reboot the system after the patch is applied. You should NOT reboot the system via the Setup Wizard prompt. This could cause system corruption. Instead, you must reboot the system from the bash shell using the reboot nice command for the patch to take effect (Left click on the Start button located in the lower left of the desktop and select Run. Enter bash and click OK in the Run window. This launches a bash window. Enter reboot nice at the bash prompt in the window and press the Enter key). This will cause a brief 3 5 minute service outage. If the system does not come back up after the reboot you should contact Avaya product support immediately. 8

9 Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. 9