IBM introduced the multi-user setup option starting with Notes 6. Third, it's a tremendous waste of space to have the same files duplicated for every user. If something happens to delay the Notes client's access, the client will throw up errors or even crash. Second, the Notes client accesses the notes.ini file a lot. This could be scripted, but it's still a pain and had to be done during off hours. You have to install the new version of Notes then copy all the files in the data directory to all the individual user data directories. The solution in Notes R5 was to map a drive letter, such as H:, and put the data directory there, then map the same drive letter for every user who logged in and copy the base Notes data directory. This poses a problem in a shared environment since you can't have everyone using the same notes.ini. ![]() ![]() Lotus was no exception.Īs you know, all configuration files are in the Notes data directory, such as C:\Program Files\lotus\notes\data. As such many application vendors were caught off guard by its meteoric rise in popularity. Since multi-user Windows OS's didn't exist until 1998, this is a pretty new segment of the market. (Maybe my friend Eric will chime in and offer some of his reasoning.)ĭeploying Lotus Notes on WTS and Citrix (the old way) In the environment I support we did not determine a need for the extra features Citrix brings to the table. I will admit I have no experience with Citrix. Citrix also offers special packages for delivering web apps and for working with WAN or slow data links. The ICA protocol has better compression and performance than RDP. Microsoft uses RDP while Citrix uses ICA. So now you know that WTS originally came from Citrix so you may be wondering what the differnce is. It's also used as a basis for remote desktop sharing in Windows XP. Ultimately this paved the way for the more robust implementation of WTS in Windows 2000 Server and Windows Server 2003. This yielded the release of Windows NT 4.0 Terminal Services Edition in 1998. This was so successful that in 1997 Microsoft licensed Citrix technology so they could incorporate it into Windows NT. Shortly afterwards Citrix released WinFrame, which let multiple end users log into a server and run installed applications simultaneously. Microsoft wasn't interested in doing a multi-user OS either, but they were intrigued enough that in 1994 they gave Citrix a copy of the Windows NT 3.51 source so Citrix could deliver a third-party solution. IBM wasn't interested, so in the late 80's Ed left to form his own company, which he called Citrix.įast forward to the early 90's when Microsoft released Windows NT, their first 32-bit server OS. ![]() Ed Iacobucci was a developer on the IBM OS/2 team who was working on a multi-user version of OS/2. In the mid 80's GUI's were starting to take over the business world and OS/2 was one of the first to be embraced by businesses. The terminal simply took the stream of data from the mainframe and displayed it on the screen. A network device connected to the mainframe, which had everything the end user needed. The old mainframe terminal scenario was the same thing. If you have any additional questions please feel free to ask and I'll do my best to respond.Ī brief history of Windows Terminal Services (WTS) and CitrixThin client computing isn't anything new. I have written on the subject of deploying Notes on Windows Terminal Services before, so the intent here is to give a somewhat high level overview of thin client infrastructures and how Notes fits into them. A few people have been asking about this so I thought I'd compile it once.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |