Subtitles of the Movie

So I won't bore you with all of the options I won't bother telling you what they all do, we'll just breeze through them real quick. Now we're back to this Property Value where we left off last time because we didn't have the Data Set imported. If we drop this down we now see we have Windows 2000 Updates as a Property Value available to us. You could if you did not have it imported already, you could choose new Data Set, you've seen this dialog before and then immediately use that Data Set. We chose to go the other way just so we could see all of the options that were available to us. In this case we'll hit Windows 2000 Updates, we'll click Finish and you'll notice that now our Scan Rule has our Data Set listed as a Property. This particular Scan Rule returns again, True or False depending upon whether all of the updates in the file are applied. So now we've seen what a List can do, let's look at a Map Data Set. So I have a Mac Address in CSV Data Set already set up here. We will open it with Notepad and right now I only have a single Mac Address put in here. With the Default Rules Set the Scan for Mac Address Rule uses this type of data Set to determine what group to put a machine in based upon the Mac Address it is connecting to the Access Server Farm with. You can then say well if you're connecting from one of these known workstations where would be Administrator Workstations then perhaps extra resources are available to you or perhaps you can logon to a specified Logon Point that gives you greater access into the network. Now one thing that's important to remember is that Maps cannot repeat values in the first column. It is a Map you're mapping this value to this value, you cannot map a single value in the left-hand column to multiple values in the right-hand column. It affects the reliability of the Scan Results, for example if we had this same Mac Address as Master Workstation and Slave Workstation then sometimes your workstation would be identified as the Master Workstation, other times it would be identified as the Slave Workstation, depending upon which order the Access Management Console or the Access Server parched the data in the CSV File. It's also important to note that while you can create an empty list inside the Access Management Console you cannot create an empty map inside the Access Management Console and all of the maintenance of these maps have to be done outside of the Access Management Console. So, now that we have our CSV File let's go and import this into the Access Management Console. So we'll again go to Endpoint Analysis, choose Manage Data Sets, click New, we will name this one Mac Addresses, hit Browse and choose our CSV and now we have another Data Set. If we were to hit Edit you'll see that the name and the value are entered. If we hit insert since the Access Management Console knows that this is a Map Data Set we're prompted for both columns of values. We won't enter one at this point. So as you see you can actually maintain it from inside the Access Management Console but it has to be created outside the Access Management Console. The reason for this is if we hit New and we just gave a Temporary Data Set Name and hit OK so that we can create an Empty List. If we Edit it you'll notice it defaults to a List Type of Data Set. This is why you have to create the Map Type Data Sets outside the Access Management Console so that the Access Management Console knows that the Data Set you're importing is a Map and not a List. Now for those that want to really delve into the inner workings of the Access Management Console, as we mentioned when we set up the application the application is entirely SQL Driven. So if you were to go into the SQL Manager and you were to open up a table named Generic Storage, you would find your Data Sets listed there with an ID. For example, there is the ID for the Windows 2000 Updates Data Set. If you were then to go back to the tables and open up a table named Generic Storage Data there's the Generic Storage ID and you'll notice that, that Generic Storage ID has the entries in it for our Windows 2000 Update List. It also has a unique ID that is generated by the Access Management Console, so I don't know that you could actually manipulate the contents of the List from inside your SQL Manager. But at the very least you could report on what's in the Access Management Console using SQL Reporting Services or just a Generic SQL Query that you might run on a schedule and output to a Text File. That way you could very easily get the information back out of the Access Management Console to compare to your Master List of installed patches and this concludes our discussion on Data Sets.