It's Day Twenty-Three of our series. The Launch Event is just a couple of days away. Following on from yesterday's post on Terminal Services RemoteApps, today we're going to be providing a very brief overview of the Architecture of Terminal Server Web Access and the Web Connection Client.

As we showed you yesterday, after installing TS Web Access, a default page is included that users can use to find and launch RemoteApps. The page consists of a frame and a customizable Web Part. This Web Part can be incorporated into a Windows Sharepoint Services site as well (but this is not something that we're going to cover). TS Web Access works with Terminal Server RemoteApp to publish applications to end users, as we saw yesterday. The published applications are actually add-ins that are handled by the ActiveX control installed by default with the RDC 6.x client. By default, when TS Web Access is installed, the TS Web Access site installs to the Default IIS Web Site (to the /TS virtual path). The Remote Desktop Web Connection site is also installed to this same path. The installation path and client files are located in %windir%\web\ts. To connect to the TS Web Access page, use Internet Explorer and navigate to http:///ts where is the name of your TS Web Access server.