IBM Communications Server for Windows
Version 6.1.3 FixPack 3
Readme

Table of Contents

1 About this update

2 National Language Support (NLS)

3 Server update information

4 Client update information

5 Uninstall information

6 Web site and support information

7 Notices and trademarks

Section Table of Contents
1.1 New in this fixpack
1.2 Product fix history
1.3 Files included

IBM Communications Server for Windows provides SNA connectivity for Windows systems, allowing it to connect to IBM z/OS Communications Server and other SNA implementations that support LLC, SDLC, X.25, Channel, and Enterprise Extender connections.

CS/Windows Version 6.1.3 FixPack 3 is an upgrade that includes FixPack 3 updates. It is not a full install, and requires that CS/Windows V 6.1.3 GA level, or FixPack 1, or FixPack 2 should be installed to install fixpack 3. Only fixpacks greater than FixPack 3 should be installed after this installation.

This document contains information supplementary to the online help and the publications. It describes such things as newly-added functions, hints, tips, restrictions, and corrections.

Thank you for choosing Communications Server!

[Return to top] [Table of Contents]

For details on new functions, see the "New function" subsections of the Server and Client update information sections. In addition, all APAR fixes since GA up to and including FixPack 3 are included.

[Return to top of section] [Return to top of document] [Table of Contents]

This update includes fixes to the CS/Windows 6.1.3 from GA.

Check the web sites listed in section 6 for the latest information about this product.

Notes:

1. This fixpack will be a pre-requisite of all future CS/Windows 6.1.3 APARs.
2. This fixpack should only be applied to CS/Windows 6.1.3 at GA level or with FixPack 1 or with Fixpack2. Only fixpacks greater than FixPack 3 should be installed after this installation.

[Return to top of section] [Return to top of document] [Table of Contents]

The Fixpack3 release includes the following files:

README.HTM	This ReadMe.htm is included in JR40207.EXE, JR40209.EXE and JR40210.EXE package, which describe about the fixes, new functions, and install instructions.
JR40207.EXE	Self extracting executable that contains Server.exe and nlspack.exe for FixPack 3 files to be installed on the CS/Widnows 6.1.3 Server or Fixpack 1 or FixPack 2 install.
JR40209.EXE	Self extracting executable that contains Client.exe and nlspack.exe for FixPack 3 files to be installed on the CS/Widnows 6.1.3 API Client or Fixpack 1 or Fixpack 2 install.
JR40210.EXE	Self extracting executable that contains FixPack 3 files to be installed for CS/Windows 6.1.3 Remote Admin Client install.

nlspack.exe:

Self extracting executable that contains FixPack 3 language files to be installed on the CS/Windows 6.1.3 Server and API-Client installation. The English version of this module is installed as part of the server or client install by default. If CS/Windows 6.1.3 was installed on non-English language machine, you must install the appropriate version of this NLS package after the server and client installation.

[Return to top of section] [Return to top of document] [Table of Contents]

Section Table of Contents
2.1 Files included
2.2 Install instructions

[Return to top] [Table of Contents]

nlspack.exe: Includes the language packages for all the languages, which CS/Windows 6.1.3 supports. Run the appropriate self extracting language pack with the -d option, so that the language files will be extracted with proper directory structure. CS/Windows supported on the following languages:

CHS : Simplified Chinese

CHT : Traditional Chinese

DEU : German

ESP : Spanish

FRA : French

ITA : Italian

JPN : Japanese

KOR : Korean

PTB : Brazilian Portuguese

[Return to top of section] [Return to top of document] [Table of Contents]

The NLS update can be integrated into and installed as part of the server or client update or can be installed separately after the server or client update by running instfix.bat present in the nlspack.exe.

2.2.1 Integrated with server or client update
2.2.2 Separate, after server or client update

[Return to top of section] [Return to top of document] [Table of Contents]

Instructions to update the server package with the NLS updates:

1. Replace the pcsnops.exe, adminstrings.dll and pcstrcres.dll in the server package with those included in the respective language pack of nlspack.
   Example: If you are installing the fixpack on French Operating system then replace those modules from nlspack present under ..\FRA\ directory.
2. Copy the file PCCFGXXX.DLL from the NLS package directory to the server package directory. Note, this file will not exist in the server package because it is unique for each language.
3. Update the server INSTFIX.BAT file with an appropriate rename and copy statement for the pccfgxxx.DLL module. (where xxx reflects the language). See existing rename and copy statements in INSTFIX.BAT for format.

Perform the installation of the server package update. See section 3 for instructions.

Instructions to update the API client package with the NLS updates:

1. Replace the setco.exe, testlu62.exe and tracedg.exe in the client update package with those included from the appropriate sub-directory of this package.
2. Update the client INSTFIX.BAT file with an appropriate rename and copy statement present in the client.exe. See existing rename and copy statements in INSTFIX.BAT for format.

[Return to top of section] [Return to top of document] [Table of Contents]

Server Install instructions:

1. Install the server updates first, following the instructions in section 3.
2. Stop the CS/Windows node and all applications that use CS/Windows.
3. Copy nlspack.exe of Server, which is present in JR40207.EXE to a temporary directory.
4. Run the nlspack.exe, which will extract all the language packs.
5. Choose the appropriate NLS package based on the CS/Windows language that is installed, and Run the respective language pack.
   Example: If you wanted to install Simplified Chinese language pack then Run chs.exe -d
   This will create a sub-directory chs and extract all the files under chs directory for Simplified Chinese language.
6. Review the comments in the INSTFIX.BAT file for specific usage instructions. For example:
   • INSTFIX chs (no parameters; environment variables will be used to locate the installation location)
   • INSTFIX chs> nlsfp3.txt 2>&1 (silent install)
   • INSTFIX chs "C:\Program Files\IBM\Communications Server" (specify the directory)
   • INSTFIX chs "C:\Program Files\IBM\Communications Server" > nlsfp3.txt 2>&1 (silent install, specify directory)
7. Reboot and start the CS/Windows node.

NOTE:
INSTFIX.BAT checks if a PCOMM version less than 5.7 CSD3 is installed and if true, does not update the Trace Facility. CS/Windows 6.1.3 would use the Trace Facility installed by PCOMM. If you have installed PCOMM 5.7 CSD3 or PCOMM 5.8 on CS/Windows 6.1.3, PCOMM will not install its Trace Facility. In this case, NLS_INSTFIX will update the CS/Windows 6.1.3 Trace Facility.

If versions of PCOMM prior to 5.7 CSD3 are installed, you will not have any of the CS/Windows 6.1.3 Trace Facility updates or enhancements.

Client Install instructions:

1. Install the client updates first.
2. Stop the all applications that use API-CLIENT.
3. Copy nlspack.exe of API Client, which is present in JR40209.EXE to a temporary directory.
4. Run the nlspack.exe, which will extract all the language packs.
5. Choose the appropriate NLS package based on the API Client language that is installed, and Run the respective language pack.
   Example: If you wanted to install Simplified Chinese language pack then Run chs.exe -d
   This will create a sub-directory chs and extract all the files under chs directory for Simplified Chinese language.
6. Review the comments in the INSTFIX.BAT file for specific usage instructions. For example:
   • INSTFIX chs "C:\Program Files\IBM\CS SNA API Client" (specify the directory)

[Return to top of section] [Return to top of document] [Table of Contents]

Section Table of Contents
3.1 APARs included
3.2 New function - server
3.3 Install instructions - server

[Return to top] [Table of Contents]

APARS included from FixPack 3
JR36468	TN3270 SSL FUNCTION DOES NOT WORK WHEN CSWIN INSTALLED WITH "ALL USERS" INSTEAD OF "CLASSIC" OPTION
JR37751	PCS3001E WITH SYSTEM ERROR 1813
JR41157	TRAP IN TN3270 SERVER
JR42892	TN3270 SERVER HANGS WHEN A BIND WITH USER DATA IS RECEIVED
JR44530	CRASH IN APPN.SYS
JR46197	TIGHT LOOP DUE TO STACK OVERFLOW CONDITION
JR46198	PCS5920E SEEN WHEN STARTING CSWIN FROM COMMAND LINE BUT NOT WHEN USING NODE OPS TOOL
JR46199	SLI_CLOSE AND SLI_BID ON API CLIENT PRODUCE WRONG RESULTS
JR35775	SLI_OPEN HANG AFTER LINK OUTAGE AND RECOVERY.
JR46201	CPIC API USES INCORRECT LU
JR46202	MEMORY LEAK IN TN3270 SERVER WHEN USING SSL
JR46205	PRINTER LOSES CONNECTION WHEN SSCP TAKEOVER OCCURS
JR46208	ASSERT IN NRTPAPI.C LINE 144
JR46209	PCS3001E PCS5501E STARTING TN3270 SERVER AFTER APPLYING IP FILTER TO RUNNING NODE.
JR46211	UNABLE TO ESTABLISH NEW SESSION AFTER TAKEOVER / GIVEBACK TO APPL. RESIDING ON VTAM BEYOND DLUS/NNS.
JR46218	SENSE 0805000B RECEIVED WHEN LOGGING IN TO 3270 APPLICATION
APARS included from FixPack 2
JR35280	Following CICS reset some TN3270 sessions to internal DLUR LUs could not be re-established
JR36022	PROBLEM WITH DOWNSTREAM FIXED PACING WITH DLUR WHEN WINDOW SIZE 0.
JR35283	LUS HANG IN PSLUIO-P STATE.
JR35284	SYSTEM CRASH PROCESSING SNA STOP COMMAND.
JR35285	ERROR WHEN ATTEMPTING TO CONFIGURE EICON CONNECTION.
JR34512	TRNSDT MISSING FILES.
JR36025	MEMORY LEAK IN KERNEL WITH NMVT ALERTS QUEUED.
JR36026	CS/Windows CRASH WHILE PROCESSING APPC DATA WITH INCORRECT LENGTH.
JR35775	SLI_OPEN HANG AFTER LINK OUTAGE AND RECOVERY.
JR36021	CRASH IN SNA_V5ROUTER.
APARS included from FixPack 1
JR28327	TN3270 SERVER MAY SEND TWO BID REQUESTS TO 3270 CLIENT.
JR28547	TRAP IN MSGIO.DLL WHEN ISSUING CSSTOP.
JR28562	MULTIPLE RTP PIPES WITH SAME COS BETWEEN 2 ADJACENT CONTROL POINTS.
JR28756	TRAP IN CSRCMDS.EXE WHEN STOPPING THE NODE USING CSSTOP.EXE.
JR28764	RAPIPIPE CREATED AND ACCESSED ANONYMOUSLY.
JR28819	TRNSDT INCORRENT TRANSLATION OF CHARACTER E086.
JR28884	XIDS FLOOD THE NETWORK WHEN DUPLICATE CP NAME USED.
JR29664	MEMORY LEAK IN APPNNODE.EXE WITH ALL INCOMING ATTACHES.
JR29793	NODEOPS UTILITY HANGS STARTING THE NODE OR AFTER SCREEN REFRESH.
JR30350	TRAP IN CSRCMDS.EXE WHEN STOPPING THE NODE USING CSSTOP.EXE.
JR32052	SDLC HANG CONDITION CAUSING ALL PROCESSING TO HALT.
JR32262	TN3270 SERVER LU HUNG AFTER OPERATOR CYCLES LU.
JR32589	INTERMITTENT TRAPS IN CSRCMDS WHEN ISSUING CSSTOP.
JR33070	SLOW PERFORMANCE RUNNING LU62 TRANSACTIONS ON SNA API CLIENT.

[Return to top of section] [Return to top of document] [Table of Contents]

New function added in FixPack 2
1. Active LUs Display
	Now, csdisplay can display all the LU's used by the LUA application or by the TN3270 Sessions with the new option of ALU. To check the active LUA & TN3270E session, type "csdisplay ALU" from the command Windows prompt. Example output of the "csdisplay ALU" as follows: a) When there is one LUA SSCP-LU and one LUA LU-LU Session active. csdisplay ALU LU Name        LUNAME05 PU Name        PUNAME NAU Address    5 Session Type   LU-LU LU Name        LUNAME09 PU Name        PUNAME NAU Address    9 Session Type   SSCP-LU Configured LUs         15 Active LUs                9 LUA(SSCP)             1 LUA(LU-LU)           1 TN3270(SSCP)        0 TN3270(LU-LU)      0 b) When there is one SSCP-LU TN3270 and one LU-LU TN3270 Session type. csdisplay ALU LU Name        BASELU02 PU Name        PUNAME NAU Address    2 Session Type   TN3270E SSCP-LU, 9.122.19.106 LU Name        BASELU03 PU Name        PUNAME NAU Address    3 Session Type   TN3270E LU-LU, 9.122.19.106 Configured LUs       15 Active LUs               9 LUA(SSCP)            0 LUA(LU-LU)          0 TN3270(SSCP)      1 TN3270(LU-LU)    1 c) When there is no SSCP Connected LU's or active LUA Application Seesions or active TN3270 Session. csdisplay ALU Configured LUs        15 Active LUs                9 LUA(SSCP)             0 LUA(LU-LU)           0 TN3270(SSCP)        0 TN3270(LU-LU)      0
2. Support for GSKIT TLS Renegotiation weak security
	Along with this release, the GSKIT package used for handling SSL secure sessions has a vulnerability update also included in the refresh image. If the CS/Windows product is using TN3270 Server with SSL support enabled, then the GSKIT APAR should be applied or required to install CS/Windows freshly using the Fixpack2 refresh image. After installing CS/Windows 6.1.3.2 and gskbas-7.0.4.27, you can override the new default by setting appropriate value to the RENEGOTIATION key in the TN3270_PORT_DEF section in the config file. RENEGOTIATION takes the value NONE (default), ABBREVIATED, FULL. There are 3 possible functions of the gskit library. (a) NONE         : No renegotiation permitted   (b) ABBREVIATED  : Abbreviated renegotiation permitted (c) FULL         : Full (or abbreviated) renegotiation permitted. The default is NONE. TN3270_PORT_DEF=(      PORT=800      SECURITY=1      CLIENT_AUTHENTICATION=1      SECURITY_LEVEL=HIGH      RENEGOTIATION=NONE ) The Communications Server for Windows provides secure encryption and authentication for TN3270 Server clients by using Secure Socket Layer(SSL). The SSL support is provided by the GSKIT common component from IBM (package name gskta). Refer to the document, JR36023_TLS_SSLv3_Update_CS.pdf, provided with this APAR on Fix Central or on the CS/Windows media provided through Fix Central or Passport Advantage. The JR36023 APAR can be found on the Communications Server for Windows product under the brand "WebSphere" on Fix Central at: http://www.ibm.com/support/docview.wss?rs=2262&uid=swg1JR36023
New function added in FixPack 1
1. Transaction Program Synchronization enhancement
	Previous version of Communication Server for Windows supports only three (Any, None & Confirm ) synchronization level. Added two more synchronization (SYNCPT Negotiable and SYNCPT Required ) to the transaction program definition. # SYNCPT Negotiable The transaction program supports a synchronization level of None, Confirm, or Sync-point. # SYNCPT Required The transaction program supports a synchronization level of Sync-point. The required synchronization level can be selected, when defining the Transaction Program from the basic panel of Node configuration application.
2. Snaformat enhance to format the Control Vector (X'82')
	The snaformat tools is been updated to format the CV'82' Subarea characteristics subfields, the formated trace will be presented in the .det file.

[Return to top of section] [Return to top of document] [Table of Contents]

Installing the fixpack on the system:

1. Download JR40207.EXE in Binary format into a temporary directory.

2. Run the JR40207.EXE, which will extract Server.exe and nlspack.exe
3. Run Server.EXE with -d option to extract all server files. There are executables included in this package, those are required for fixpack installation. The instfix.bat in current directory is required only for the fixpack installation.
   1. If you have SNA API Client Services (Split-stack API Client/Server), copy JR40209.EXE in the client workstation and see section 4 for install instructions.
   2. nlspack.exe contains non-English language updates. Customers running non-English versions of CS/Windows also need to install NLSPACK package seperately. To install the language pack refer section 2 for NLS install instructions.

4. New function updates have been included with this fixpack package. See section 3.2 for more details on the new updates.
   1. INSTFIX.BAT checks if a PCOMM version less than 5.7 CSD3 is installed and if true, does not update the Trace Facility. CS/Windows 6.1.3 would use the Trace Facility installed by PCOMM. If you have installed PCOMM 5.7 CSD3 and above on CS/Windows 6.1.3, PCOMM will not install its Trace Facility. In this case, INSTFIX will update the CS/Windows 6.1.3 Trace Facility.

      If versions of PCOMM prior to 5.7 CSD3 are installed, you will not have any of the CS/Windows 6.1.3 Trace Facility updates or enhancements.

      There is a problem with some versions of PCOMM prior to 5.7 CSD3 where using ADD/REMOVE PROGRAMS to remove PCOMM removes the Service APPNNODE from the REGISTRY. CS/Windows will NOT run successfully without this registry entry. While this problem has been resolved in later PCOMM versions you can do the following to address the problem.

      The recommended procedure in this situation is as follows:

      1. Remove PCOMM using Add or Remove Programs
      2. Remove CS/Windows 6.1.3
      3. Re-install CS/Windows 6.1.3
      4. Install PCOMM 5.8 (or PCOMM 5.7 CSD3 or later)
      5. Apply CS/Windows 6.1.3 Fixpack 2 maintenance upgrade

5. Stop Communications Server for Windows (including your node, Node Operations, Node Configuration, Log Viewer, and any other CS/Windows components you have started). Note that there may still be CS/Windows-related services running on the machine after stopping these applications, but this is normal and should not affect the installation of this fix pack package.
   1. Stop ALL Window applications on this box since a reboot will be required after running INSTFIX.BAT maintenance installation.
   2. Refer the INSTFIX.BAT for details on various installation options.

   INSTFIX.BAT can be run with the following options to preserve output to a log file, such as for silent install including errors in the log.

   INSTFIX > FIX_PACK.TXT 2>&1

   NOTE 1: INSTFIX.BAT issues
   "NET STOP APPNNODE" to stop APPNNODE Services.
   "NET STOP LDLCSERV" to stop LDLCSERV Services.
   "CSTRACE STOP" and "CSTRACE SHUTDOWN" to stop CSTRCSER trace Service.

   NOTE 2: INSTFIX will rename the current or target files being replaced to &file.pre6133, then copy the updated files.

   If for some reason you rerun INSTFIX.BAT, you will receive errors during each rename because the file.pre6133 file will already exist.The original copy of the file will be preserved in file.pre6133 and available as a backup for restore purposes.

   If for some reason you need to restore or backout this fixpack, you would have to manually rename the updated file names and restore the original files.

   NOTE 3: After all the files are copied, INSTFIX.BAT automatically issues
   "SERVICESTEST -c LDLCSERV" command to initialize LDLCSERV service.
   "NET START LDLCSERV" to start LDLCSERV service.

   NOTE 4: The default value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Communications Server\CurrentVersion\VersionNumber will be changed to 6133.

6. After running INSTFIX.BAT, confirm all the copy commands sucesses by redirecting the instfix.bat output into file or verifying it on the console. If they do NOT, then you must manually copy them after you REBOOT but prior to starting any IBMCS Services.

7. If you want to restrict the user(Non-Administrator) from controlling SNA resources like Stoping/Starting the node/link etc., you have to run the batch file below and follow the step (B) mentioned below.
   1. Run the batch "AccessControlSettings.bat"
   2. If you are running Windows XP or 2003 and above do the following: (For Windows NT and 2000, skip this step.)
      1. Run regedit to start the registry editor (start->run then type regedit).
      2. Navigate to HKLM\Software\IBM\Communications Server
      3. Right-click on Communications Server and select Permissions.
      4. Click the "Add" button.
      5. Click the "Advanced" button.
      6. Click the "Find Now" button.
      7. Select "IBMCSADMIN" from the resulting list and click the "OK" button.
      8. Click the "OK" button.
      9. Select "IBMCSADMIN" from the list.
      10. Check the appropriate box to allow "Full Control".
      11. Click the "OK" button.
      12. Navigate to HKLM\Software\IBM\OEM_CONFIG and repeat the steps from "3" to "11".
      13. Exit the registry editor.

8. Shutdown and Restart WINDOWS to reboot the machine.

9. You can now start IBMCS Node Operations and configure the new available functions.

[Return to top of section] [Return to top of document] [Table of Contents]

Section Table of Contents
4.1 APARs included
4.2 New function - client
4.3 Install instructions - client

[Return to top] [Table of Contents]

New APARs included in FixPack 2 since CSNT6.1.3 GA
JR36070	TRNSDT MISSING FILES.
New APARs included in FixPack 1 since CSNT6.1.3 GA
None.

[Return to top of section] [Return to top of document] [Table of Contents]

New function added in FixPack 2
None.
New function added in FixPack 1
APPC Cancel Conversation support
1.	The CANCEL_CONVERSATION verb is a control verb that will cancel a connection between a local LU and partner LU using a specific transaction program (tp_id) and a conversation (conv_id). The definition of the VCB structure for the CANCEL_CONVERSATION verb is as follows: typedef struct cancel_conversation { unsigned short opcode; /* verb operation code */ unsigned char opext; /* verb extension code */ unsigned char format; /* format */ unsigned short primary_rc; /* primary return code */ unsigned long secondary_rc;/* secondary return code */ unsigned char tp_id[8]; /* TP identifier */ unsigned long conv_id; /* conversation identifier */ } CANCEL_CONVERSATION; Please refer the Client/Server programming guide for usage of this verb.

[Return to top of section] [Return to top of document] [Table of Contents]

Installing the fixpack on the system:

1. Be SURE you have downloaded the 6.1.3 FixPack 2 APAR package (JR40209.EXE) in BINARY format.
2. Create a temporary directory, copy the JR40209.EXE, and Run JR40209.EXE, which will extract JR40209.exe and nlspack.exe for the API Client
3. Run JR40209.exe to extract all the API Client's updated files
4. Stop ALL running SNA API client applications on this machine. Check the Task Manager and stop any running API CLIENT exe's such as ATTMSG.EXE and LU62MGR.EXE.
5. INSTFIX.BAT is an installation batch file. INSTFIX.BAT will backup the files to a folder called *.pre6133, then install/copy the updated DLL's and EXE's to the supplied installation folder. View the comments included in INSTFIX.BAT usage instructions.

   Some examples follow:

   • INSTFIX "C:\Program Files\IBM\CS SNA API Client" (to install fixpack)
   • INSTFIX "C:\Program Files\IBM\CS SNA API Client" > CLINSTFIX.LOG 2>&1 (log to file)
6. nlspack.exe contains non-English language updates. Customers running non-English versions of API Client also need to install NLSPACK package seperately. To install the language pack refer section 2 for NLS install instructions.
7. After running INSTFIX, shutdown and restart the machine to complete the installation.

[Return to top of section] [Return to top of document] [Table of Contents]

Uninstallation of a fixpack is not supported. To revert to a previous level, uninstall the product completely, then install the GA level, then install the desired fixpack level.

Uninstallation instructions are in the Quick Beginnings book at http://www.ibm.com/software/network/commserver/windows/library/index.html

To ensure a complete uninstallation of the product, download the cleanup package (JR21546) from http://www.ibm.com/support/docview.wss?rs=2262&uid=swg24009834

If Personal Communications is installed on the same machine as Communications Server, you must uninstall Personal Communications before uninstalling Communications Server.

All applications using Communications Server should be terminated before you attempt to uninstall the product. Attempting to uninstall Communications Server while an application (such as APING or Personal Communications) is running will cause the uninstall to hang until the application is terminated.

[Return to top of document] [Table of Contents]

Product information

For the latest information about the IBM Communications Server family of products, visit the Communications Server Web site at http://www-03.ibm.com/software/products/us/en/commserver-windows. This Web site provides information and links to headline information, specification sheets, frequently asked questions, education, and much more.

Product support

For the latest support information, visit the Communications Server Support Web site at http://www.ibm.com/software/network/commserver/support. This Web site provides information and links to code fixes, tips, newsgroups, maintenance, and much more.

Technical notes

Search the hints and tips in the IBM Support database at http://www-947.ibm.com/support/entry/portal/overview/software/other_software/communications_server_for_windows.

Technical support

For technical assistance or questions, call the IBM support center for your country. For example, in the United States, call 1-800-IBM-SERV.

[Return to top] [Table of Contents]

AnyNet, IBM, S/390, WebSphere, and z/OS are trademarks or registered trademarks of IBM Corporation in the United States, other countries, or both.

Tivoli, and Tivoli License Management are trademarks of Tivoli Systems Inc. or IBM Corporation in the United States, other countries, or both.

Lotus and Domino are trademarks or registered trademarks of Lotus Development Corporation in the United States, other countries, or both.

Microsoft, Windows, Windows NT, Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008 and Windows 7 are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.

VMware is a registered trademark of VMware, inc.

[Return to top] [Table of Contents]