WINDOWS TERMINAL SERVER THINCLIENTS FULL
WINDOWS TERMINAL SERVER THINCLIENTS WINDOWS

OS Streaming works as you stated instead of streaming the OS from the local hard drive (that's not called streaming, but it's still what it is), the client streams the OS from an image on a server. I'll answer you the way I see things, since there's a lot of hyped terminology in this business nowadays :) I'm not familiar with OS Streaming, but from what I just read, you basically stream an OS image across the network to a device to do all of the processing? What are you using for your end user device? How does this differ from VDI? My question is, what do you think is causing this white page flash? Do you think RemoteFX might fix it? My hope was to use the PII's as thick clients until they failed then replace them with Thin Clients, but since the white page flash was still and issue, I didn't investigate it any further. Other than the flash of a white screen after clicking on links within my EMR or Lotus Web apps, everything else worked perfectly on the thin clients.

WINDOWS TERMINAL SERVER THINCLIENTS WINDOWS

The first failed deployment was on a Windows 2000 Server, the second on Windows 2003 R2.

WINDOWS TERMINAL SERVER THINCLIENTS FULL

Same went for the EMR webpage.įor informational sake, I was deploying full Windows Desktops to the end users in both of these cases. I brought up an Internet Explorer screen, launched Lotus Web Access, and it worked flawessly, no flashing white screen. From the moment I started the RDP session everything seemed to move faster. I used a PII 400 256 Megs RAM XP box to RDP into my TS. Since I had more time to play with this test environment, I decided to use a thick client and see what kinds of results I would end up with.

As expected, Lotus web access gave me the flash of a white screen between clicks, but now I noticed the same issue for my EMR pages. The primary application this time was again Lotus Web Access and an internal EMR product that uses Adobe Flash to draw the screens. This time as test, I installed a Windows 2003 R2 TS box. Desktop PC's were never used to connect RDP to, so we have no idea if they worked better or not. The white flash was more than the customer could handle, and this solution was scrapped.įast forward to 2008. The issue is that when you clicked on a link the program window within RDP would flash solid white for about 1/3 of a second, more than enough time to be noticable, then display the desired page. While I didn't expect this to be a problem, in reality on a TS it became a show stopper. Lotus Web Access primarily used (2002) Java to build the screens. The primary application they wanted to deploy was Lotus Web Access (Webmail). I had a customer that wanted to deploy thin clients (IBM 8363's winCE) to their end users. I've setup two seperate Terminal Server (TS) solutions in past 8 years or and had found the same problem in both them, 6 years apart. I'm starting this new thread to stop hijacking another.

Windows terminal server thinclients