Subtitles of the Movie

The first Policy Page we come to in the Workstation Import section of the Server Package Policy is the Workstation Containers Page. On this page you will need to list every container in your eDirectory tree that this particular Workstation Import Policy Package will be allowed to create workstations. Obviously if you had multiple import servers on your network you wouldn't want them stepping on each other by creating Workstation Objects where they shouldn't just because a client happened to hit the wrong Server, so this is a good way of limiting exactly where those workstations can be created. In this case we have just a single workstation OU, so we'll choose Workstations and hit OK, and there are the Workstation Containers, all one of them. Next, we have the Platforms tab. The Platforms tab allows you to set settings for all the different platforms of workstations that could be imported into eDirectory. You can set settings for All the platforms, or if you wanted to have a different set of settings, for example, for Windows 95 clients to be imported into a special workstation's OU that doesn't get any Policies then you could define Win 9X and set up a special set of Policies just for Windows 95 and 98 workstations. In this case we'll modify General again, because we want this to apply to any Windows OS that will register a Workstation Object in eDirectory. The first setting up here is: Allow Importing of Workstations. If you just wanted to disallow importing of workstations without turning off the service you could go into the policy and uncheck this box and that would effectively turn off the service even though the service is actually still running. Again, most organizations leave this checked all the time and if they really don't want to import workstations they go stop the service on the Import Server. The next setting is where do you want the Workstation Objects to be created? Do you want to create it in the Container that the Import Server's running in? Do you want to create the Workstation Object in the Container that the user is in? Or, do you want to create the Workstation Object in the Container that this particular Policy is associated to? Or, you can specify a Container, that is, None of the Above. If we left this at Server Container, for example, and looked at this box we can specify relative paths inside the selected Container. For example, our Workstation's Container is under our Server Container, so we could type: workstations, and that would create all of our workstations in the Workstations OU that is under the Container that the Workstation Import Server is set at. You can see how this would get confusing pretty quickly. Most organizations will have either one of two settings. They will choose User Container and then they will have a Workstations Container in every OU for every site so that a user that's logging in in San Jose gets their workstation imported into the Workstations OU that's under the San Jose Container, or they will import all of their workstations into a single Container and redistribute them from there. In this case we're going to select the Container, workstations.vtc, because again, we've got all of two workstations in our lab environment. The next tab is Naming. This tells the Workstation Import Server how to name the workstation that's being imported. The default name is the computer and MAC Address. This is a little misleading because even though it says the Workstation Name will be computer plus MAC Address, if you were to import a workstation with this workstation name it would look something like that. It doesn't put the Plus sign in there even though the workstation name has the Plus sign up there. In most cases I will modify the default workstation name and add a user-defined string, which is an underscore usually, and move it up so that you have computer underscore MAC Address. Obviously there are many options for the field. You can have the user's name, the container, the IP Address, the DNS name, the type of CPU, but again, in 90 percent of the implementations I've done computer underscore MAC Address works just fine. Something else to realize is that this workstation name is set at the time of import, meaning that if you change the Computer Name or the MAC Address on the workstation after it's been imported the name in eDirectory will still reflect what the Computer Name and MAC Address was at the time of import. Obviously you can just delete that old workstation object and the next time the workstation reboots it will reimport with the new name and MAC Address, but it's just important to remember that the Import Server does not go back and change the workstation object once it's created. The last tab is Groups. If you have workstation Groups set up to, say, automatically distribute Policies or automatically distribute Application Objects you can say whenever this workstation is created, automatically put it in this Workstation Group and the next time it refreshes Policies and Applications it will get our standard set of applications.