Subtitles of the Movie

This is Citrix Access Gateway Advanced Edition 4.5 and in this video we're going to step through the user experience. Now we've gone through the course so far, we've set up a few very basic resources and we want to see what this looks like for your end user when they go through the Access Server Farm. So we'll open up Internet Explorer and I have our Sample Logon Point saved as a favorite. You notice its quite a long URL, elsewhere in the course when we talk about customization we will discuss how to make this URL shorter so that your end users don't either have to have a favorite saved or remember this long URL. Now again we're hitting the Sample Logon Point and if you'll recall our discussion of the Sample Logon Point brought out the fact that this is just an open Logon point, anyone that happens to find this Logon point and has an account in the Domain will be allowed to log on. This is not the ideal situation in production and as we go further through the course and we customize our Access Farm Implementation further then we will change this so that the Sample Logon Point is no longer active. In fact we'll delete it once we've set up our customized Logon Points. So in this we'll go ahead and log in as Administrator and we'll put in the Domain as VTC Training. We will ignore this for the time being because we don't have any applications running at Logon, but if you disconnected with applications running on the Presentation Server you could choose to automatically reconnect to those applications when you logged in. In this case we'll hit Logon and here is the Default Access Gateway that is scene just with the few resources that we've set up. Here's our File Shares that we've set and here's the Google Search Engine. So first we'll look at this website Resource. We'll click on the Google Search Engine and IE will spawn a new window and take us to Google. However if you'll look up in the address bar you'll notice that we're going to the Citrix Web proxy and you don't really realize that you're at Google you know except for the huge Google Logo right here. This is useful if you have intranet websites that you wish to publish to, external users, external to your organization. For example say you have vendors and remote parts of your footprint that you need to come in through the Access Gateway and enter Ticket updates and a Ticketing System, you can hide the internal URL of the Ticket Management System from the end user by simply running it through the Citrix Web Proxy. You'll notice that also all of the links on the web page, if you look down at the address that is linked to it, then in the bottom of the web browser window, you'll notice that they are all masked as well so you can't simply just hit the front page and then highlight one of these links to figure out where you happen to be. And again this because the Access Server actually goes to the Internet and gets the website on your behalf and then presents it to you through the Access Server Farm. This is where that option to strip out ActiveX and all the browser specific functionality would come into play if the front page of Google had ActiveX on it, we could choose to mask ActiveX and it just wouldn't be there and also we wouldn't be prompted to install ActiveX if our web browser did not happen to understand ActiveX. In this case we'll search for SharePoint, something nice and innocuous and you'll notice we can get the Google Search Results for SharePoint but if we happen to click on what is Microsoft Office SharePoint Server, which you'll notice is in the Domain Microsoft.com, which is not part of our Web Resource. If we click that we get an access denied message because we're attempting to go to a URL that is not in our Web Resource. Even though this comes up as an error from the Access Gateway, of course its acting as designed, simply because you're not allowed to go to that particular website. Again, this is not the best example of a Web Resource, again why would you put a Search Engine in a Web Resource and then not allow anyone to go to any links from outside the Search Engine, but it works well enough for our sample. So now we'll look at the File Share Resource, we have this user data which if you'll remember we used a Token in and if you highlight over the user data the Link Information will show you that the Access Server Farm translates the Token that we put in and shows you that it's going to user data Administrator. If we click this link we get another web browser, the Access Server will contact the Remote Server that holds the File Share for us and here is the Administrator File Share. There's nothing in it really, just a folder and a text document. You will notice that we have a location bar up here, just as we would in Windows Explorer. And if we were to highlight Administrator and try to go up one level we would get an access denied because we're not allowed to go to that particular level in the Web Resource. If we hover over this new document you'll notice that we can drop this down and choose to download the text document. We can also choose to upload or to search within the files in this folder. We go to File Source 1 which is our Install Source; you'll see much the same thing. Here is the License for the Access Gateway Server and here is the Folder that's underneath our File Share and again since it is under the Directory listed in the File Share Resource we're allowed to browse anywhere we want. You'll notice that the location bar in this case masks the actual server were talking to. Unlike with the File Share with the Token in it, this way we don't know exactly which server we're talking to and if we were to highlight this and hit go you'll notice we are taken to the root of the File Source 1. If we click Log Out we're prompted that, are you sure you wish to Log Out? And you hit OK and it closes the window and this concludes our discussion of the user experience with Web Resources.