Subtitles of the Movie

This is ZENworks Desktop Management 7 and in this video we're going to discuss Troubleshooting Workstation Import. Now as you'll recall elsewhere in the Title we installed the ZENworks Desktop Management Agent on our target workstation and once it rebooted it should have imported into our eDirectory tree. If we go into ConsoleOne and we look in the OU that is specified in our Import Policy then you'll see our workstation is right here. We can double-click it and get a little bit of information about the workstation, the associated Policy Packages and the Inventory, which none of this has been set up yet because we haven't gotten to that part in the Tutorial. But otherwise we're well on our way to having a functioning workstation management infrastructure. However, what happens if all of this goes horribly wrong, that no matter your best begging and pleading you can't get this workstation to show up in eDirectory. We'll check two or three of the more common breakdowns in communications and hopefully if you check all of these you can get an idea of where the import process is breaking down. We'll start off with the most obvious one that most people forget. If you'll recall when we set up Workstation Import I told you that you had to have a Host Name of zenwsimport resolvable on the workstation that's going to be imported. Now most of the time, on a large network, you'll enter this into DNS and it won't be a problem. On smaller networks, like on this lab network for example I don't have a DNS Server, and so I've actually entered into the Host's file. You'll see right here, this entry: 10.1.1.1 zenwsimport. We'll double-check that this host file is actually being read by going out to a Command Prompt and pinging zenwsimport. You need to make sure that: a. the host name resolves to the correct IP address; and b. that that IP address actually responds to pings. That tests two things. Number one it tests that the DNS name does resolve, obviously. Number two, it makes sure that the IP Address that that name resolves to is actually reachable from your workstation. It can resolve all it wants; if it's not reachable by the workstation, import is not going to happen. So let's say that like this example the zenwsimport host name does resolve on the network. What's the next step you'd look at? The next thing you would look at is to look in the OU that has all of your Policies. You need to make sure that you have a Server Package defined and that that Server Package has a workstation import Policy and it is associated with the Organizational Unit, or the Server, that will be running the Workstation Import Service. If all three of those are not the case then the Workstation Import Server does not know which Policy applies to it. A common failing that I see when I troubleshoot workstation import on production networks is that people will set up the Server Package, they'll set up the Workstation Policy, they just won't Associate it with anything. Now you can set up as many or as few Server Packages that you wish to set up. I generally will create one package for every Import Server that I have running, assuming that I wanted to import into different OUs and I will associate the Server Policy Package directly with the Workstation Import and Removal Server. So, if zenwsimport resolves, we have a valid Server Policy Package, it is Associated properly, what's the next thing we can check? We can go to our ZENworks Server, like so, and we can make sure that the Workstation Import and Removal Services are actually running. Go to the Control Panel, Administrative Tools, Services and you go to the bottom and you search for ZENworks Workstation Import and Removal and make sure they're both Started. Obviously this is on a Windows box. On a NetWare box it is a little different. On a NetWare Server you can actually scroll through the Server Console and make sure that you see the Workstation Import Server and the Workstation Removal Server screen on the Screen List on the Server Console. If this is running you can then go to the root of Drive C and you have three log files that are written by default: the zen workstation import. log, zen workstation removal dot log and the zen for servers nt service log. In this case we will open up the zen workstation import log and if we'll maximize it so we can see everything, this logs everything that comes into the ZENworks Import Server. In this case you'll see the request where our new workstation was set up. It tells that it's a computer, it tells that it's a Pentium III and gives all the pertinent information necessary to import the new workstation. And you'll see the next line will say workstation container created workstation and Connection closed. If you did not have the Policy Associated, it would tell you in plain English: I see this workstation; I see it's requesting to be imported, but I don't have a Policy associated with me. If that's the case you have to create the Policy and associate it with the server and then you have to stop and restart the Import Service in order for it to recognize that new Policy that you've created.