A user launches a MS Word RDP webApp that uses the wnSSOclient and then closes that terminal server window incorrectly.  The user then launches a MS Excel RDP webApp which also uses wnSSOclient, the previous winword session comes back up.

Customer Situation:

• Two applications using wnSSOclient MS Word and MS Excel

• Customer would close the window (not the application) on one application (Word) 
• The customer would open the second application (Excel) 
• The terminal server would launch the first application (Word) 

• Two applications using wnSSOclient MS Word and MS Excel
• Customer launches one application (Word)
• The customer would open the second application (Excel) 
• The Word window will close, and the Excel window will open to the previous Word session

Reason: 
• Terminal server notices the disconnected state, the user, and the application and thinks "hey I've already got that program wnSSOclient running for that user"

• Similar behavior if you disconnect from a program like Paint without logging out, it will reconnect you to the same session of Paint with your last picture open

Fix: 
• You can just not use the wnSSOclient; since the customer isn't closing the application correctly anyways

OR 

• Have multiple copies of the wnSSOclient6 files on your Terminal Server, one for each application

• You can copy both wnSSOclient6 files into another directory, for example, c:\util\msword and add it to the Published Apps list

• Make sure to add this new location in the wnSSOclient path field of the corresponding webApp