Subtitles of the Movie

This is Citrix Access Gateway Advanced Edition 4.5 and in this video we're going to talk about File Share Resources. Now as you'll recall from our overview of resources a File Share Resource is a File Share somewhere out on the network that the users will access through the Access Server Farm. In this video we're going to show you how to set up a File Share Resource as well as some of the gotcha's that you need to keep in mind when you're configuring said File Share Resource. So we'll go to the Citrix Access Management Console and we'll go to the File Shares Node which is already highlighted and you'll see that there is nothing over on the right because there are no File Share Resources yet. So we'll right click File Share Resources and we will say Create File Share. As with all resources we have to give it a name and a description, in this case I'll fill those in for us, like so and we'll hit Next. We're now brought to the Configure Share Locations, we're then brought to the Configure Share Locations, this dialog is where you enter all of the UNC Paths for your end users to access their File Shares through. That's the first little gotcha that I mentioned, is that all of your File Shares must be accessible through a UNC Path. You can't use mapped Drive Letters on your Administrative Workstation simply because the Access Server Service runs as a Service and doesn't run a log on script and so mapped drives mean nothing to that particular Service, it only knows about UNC paths. In this case we'll hit New and we'll put in a Display Name of File Source 1 and we'll put in the File Share Location as VTC -Press Serve -01 which is our Presentation Server that's in our lab and I have a Share Set Up on that named Source. There's not really anything particularly useful in there, it's just there for demo purposes. And we have an option down here to Publish Re-users and their list of Resources. As with Web Resources this makes it so this particular File Share is listed in the Access Management website or the Access Web Interface. Also as with the Web Resource you can define multiple UNC Paths in a single File Share Resource and you don't necessarily have to publish every single one of them. This is so again, if you have a File Share Resource that is on multiple physical servers and there's links in those resources back and forth, then you would put them all in the same File Share Resource. In this case we will go ahead and publish this for users and their list of resources and we'll hit OK. And you'll notice that it doesn't actually do a verification of whether that UNC Path actually exists. The UNC Path that you specify as the File Share Location doesn't actually have to exist at the time you set up the File Share Resource. Obviously it has to exist when the user accesses it and they have to have at least Read Access to it, but you don't have to have it online when you set this up. This is good if you're going to bring up a set of servers over a weekend, you can do all of this work ahead of time so that the entries are sitting there and all you have to do is turn on the policy and everybody gets all the File Shares all at once. Now we mentioned policies, within the policy you can define exactly what users can do with the files on this particular File Resource. Those policies do not override what's on the File System. For example, if in the policy you state that users can upload files to this File Share and modify files that are on File Share and they don't have the rights to do that in a File System, then obviously the File System wins, since all your Access Server Farm is, is a portal into your network and into those File Shares, it can't override what the user rights are. Again that's something else to keep in mind, just because you grant them full access here does not necessarily mean they have full access to that File Share. As with the Web Resources you can use Tokens, in this case we'll set up another File Share, we'll name this user data and we will put in that as the Server. Now let's go look at this File Share in the browser here. You'll notice we have user data and then under user data, right now, we have Administrator, we'll create some other user data folders under here when we do our lab. So it's not a big deal, you could just hard code this to be user data administrator and that would be the Administrator's User Data. What happens if you have say, 500 users that you need to get access to their user data? You would have to set up 500 different URLs and 500 different policies and 500 different File Share Resources or you can use Tokens. So we'll copy this to the Clipboard, we'll go ahead and put this in over here and we'll put in pound username and again all of these Tokens are in the documentation. We'll go over some of them through out the course of this course, but we won't go over all of them because they don't all apply. We'll also publish this in the users list of resources and so now we have both of those, we'll hit Next. We're also presented with the policy screen as we were with the Web Resource, in this case we'll create a default policy granting access to all users and we'll tighten those policies up elsewhere in the course. We'll hit finish and now we have our File Share Resource, File Install Source with that description that we entered and again you can expand this down and click on that and you get anymore information then you did from the Master File Shares Node. And this concludes our discussion of File Share Resources.