Subtitles of the Movie

If you don't set up a Workstation Removal Policy then as workstations are re-imaged or retired from the network, you'll have all of this cruft buildup on the network, for lack of a better term, of workstations that don't actually exist anymore. The Workstation Removal Policy takes care of this for you if the workstation falls within the constraints of this Policy then the Workstation Removal Service will take it out of eDirectory. And again, it's not a huge deal. You do lose a little bit of inventory information of that workstation, but if a Workstation Object gets deleted, the next time the user reboots it's recreated and really no harm, no foul. So, we'll check the box to enable the Workstation Removal, and we'll hit Properties. Again, like the Workstation Import screen, the Workstation Removal Policy wishes to know what Containers do I look at? In this case we will add the Workstations Container, and if you wanted to remove workstations from every container under this you could check this box. Again, a lot of organizations have a single workstation removal policy that looks at the root and every subcontainer and when the policy schedule kicks off it just scans the entire tree to find the workstations that meet this criteria. We'll go to Limits. Days before removing unused workstations Ð very self-explanatory Ð when I kick off and scan my workstation OUs, if I find a workstation that has not logged in in more than 60 days I'm going to delete it. Here's the Schedule. By default, it starts today at 11 o'clock and runs for four hours. Whether or not it's removed all of the 60-day-old Plus workstations at the end of that four hours it stops and kicks off the next week, or the next day, or the next fortnight, whatever interval you wish to specify here. You can also limit the number of workstations removed to kind of stop the bleeding, if you will. You can say: every day I want you to remove no more than 100 workstations; that means your workstations will kind of build up if there's a lot of them that disappear, but you wouldn't have a date problem on a Server cause the Workstation Removal Service to just go remove every workstation in the organization. In most cases the defaults are good. Run once a week starting on whatever day you specify, in this case, February 27, 2009. Run between the hours of 11 pm and 3 am and remove any workstations that you happen to run across. So in this case we'll Apply the policy and hit Close, and we'll move on to Associations. You would think that after you created the Workstation Import and Workstation Removal Policies you're done. Not so much. You have to associate this policy with an Organizational Unit or a Server in order for the Policy to take effect. In this case we'll go to Associations and we will associate it directly with our Workstation Import and Removal Server. We'll hit OK, and then Apply that change and Close. There are two other small things you have to take care of once you've set all this up. The first is to go into the DNS for your Network, in our case our DNS is the Host File because I don't actually have a DNS Server running right now, and you will need to add your Workstation Import and Remove Server into DNS with the DNS name of zenwsimport. Unless you do this step no workstations will import and the simple reason why is that when the ZENworks Agent on the client workstation starts up and begins to import itself into eDirectory this is the name that the workstation uses to find its Import and Removal Service. If it cannot resolve this name then it doesn't know where to go to find the ZENworks Import Server. So, now that we've edited that, we'll save our Host File. You also have to go back to your Desktop Management Server, in our case we go back to the Services Control Panel and you have to Restart the Workstation Import and Workstation Removal Services. This is true on Windows, NetWare, or Linux Ð whatever platform it's running on. The simple reason for this is that the Workstation Import and Removal Services look for associated policies at Startup time. If it does not find these policies at the time the service starts it never looks again. In my opinion, this is kind of a failing. I really wish it would go back every so often and look for policies until it fund one, but I don't write the software, I just administer it. If you're interested in ensuring that the Import and Removal Services see the policy you can look in the Root of Drive C on a Windows Server, or in the Root of the Sys Volume on a NetWare Server and look at the ZENworks Removal Policy Log File. You'll notice that the last Time Stamp in here says: no removal policy found. You can't see the clock but I can tell you that that time was quite a bit ago. As workstations are imported and removed it will write out into this file exactly what workstation was imported and removed as it's doing the Import and Removal. And once you have followed all of those steps you now have ZENworks Workstation Import and Removal set up in your tree and you're ready to start the pulling the ZENworks for Desktop's Agent. And this concludes our discussion on setting up Automatic Workstation Import.