Subtitles of the Movie

Now there are a couple of utilities you can look at on the workstation as well that can help you with workstation import and removal. Say, for example, you forgot to Associate your Policy, so you associate your policy; you stop and you restart the Workstation Import Service on your Workstation Import Server, but you don't really want to reboot the workstation and wait for it to do all of the stuff it's going to do just to come up and see whether it's actually going to import. Or, and this is generally the more common occurrence, say you have a workstation that needs to be imported, you're watching the log, and you want to force it to import. There are some utilities on the workstation that will allow you to do just that. So, we'll go back to our User Workstation, and we'll open up the Command Prompt and we will switch to the Directory Program Files, Novell, ZENworks, and in this directory there is a file named zwsreg.exe. This is a Command Line registration and removal agent so you can, again, force it to register on the schedule that you set, just to see exactly what happens. You can also use this Command Line Utility to force the workstation to Register with a particular workstation Import Server. Say, for example, you have another team that manages DNS for your network. They've screwed up that zenwsimport DNS entry, and they're all at lunch and you really need to get this workstation imported because it's for the CEO of the company. You can go onto this workstation and you can run zwsreg-unreg to unregister the workstation with eDirectory. This clears the registration Registry Entries on the Local workstation, which we'll look at in just a moment, so the workstation can be successfully registered with the Import Server that you specify. In this case we'll do zwsreg, and we won't specify any of these options but we will go through them. Import Server Ð just as it says the Server IP Address that you wish to connect to to do the importing. You can also specify an Import Policy on the Command Line. This way, if the import policy that's associated with this particular Import Server by default is not the policy that you want you can tell it: go find this policy and use it. And it is the full DN of the policy in the format.server policy et cetera. You have the importws, which tells the Import Server this is where I want you to create the new workstation independent of whatever's in the Policy. And if you happen to be running ZENworks version 3 you can import a ZENworks version 3 workstation object into your tree. In this case we'll just run it with the default: zwsreg, and it actually comes back and tells us: Successfully imported workstation. And there is the full workstation DN. If we go back to our zenserver, we'll actually see right here that it opened a new connection and requested a new workstation to be registered. In this case we didn't delete the old workstation object, so it was still there, so it just re-registered with the same name and didn't create a new object. So, back on our user workstation, let's go digging in the Registry to see exactly what Registry Keys get set when a workstation is successfully registered with eDirectory. We will start out at the key: HKEY LOCAL MACHINE SOFTWARE Novell Workstation Manager. You'll see that the Workstation Manager component is Enabled. If you ever wanted to Disable any of the components you could find the Registry Key that enables that component, set it to zero, and that disables Workstation Management, for example. And it tells you this is the dll that was used to actually register the workstation with eDirectory. Generally that's almost always going to be zenwsreg.dll, but if you have a custom dll and a custom import agent that you wrote using the API Toolkit, which I've never seen in a production network, you would have it entered here. We'll then go to the Identification Key, and here is the tree that we're registered with. There is the workstation ID which is the GUID of the workstation in eDirectory, and there is the actual Object of the workstation with the full OU appended. If you'll remember earlier where we used the Unreg switch with zenwsreg.exe it essentially just cleared all of these Registry Entries so the next time a workstation registration is performed, which is the next time the workstation reboots, or the next time we force it to register then since there's no Registry information in the Registry it performs a new Registration because as far as the workstation knows, it's not imported anywhere. So, hopefully this particular video has shown you more than you ever really wanted to know about the workstation import process and to ZENworks 7, and with that we will conclude our discussion of Troubleshooting Workstation Import.