Subtitles of the Movie

This is ZENworks Desktop Management 7 and in this video we're going to discuss Installation Prerequisites. Now, ZENworks Desktop Management 7 can be installed on three different software platforms. It can be installed on either the traditional NetWare OS that Novell has put out historically. It can be installed on a Windows server, or it can be installed on Novell's Open Enterprise Server, or SUSE Linux. We'll go over the software requirements for all three platforms. First, though, we'll make a quick stop at the Hardware Requirements, since the hardware requirements for all three software platforms are pretty much the same. ZDM7 requires a Pentium III 1 Gigahertz processor. It requires 1 Gig of RAM for 200 concurrent users of ZENworks Desktop Management. You can scale thereafter as appropriate, but honestly I have seen machines that have 4 Gig of RAM that can very easily service 3000 client workstations, so RAM is not really a requirements, or rather I should say, a great amount of RAM is not really a requirements. And it requires 20 Gigs of Hard Drive space for the Inventory Database. Again, if you're not going to be using the Workstation Inventory piece of ZDM7, you can get away with as little as 10 Gigs or 5 Gigs. So, we'll start out with the software requirements for the NetWare 6 Operating System. If you are running ZDM7 on NetWare 6, you have to have at least NetWare 6 Service Pack 4 installed on your server. You have to have at least eDirectory 8.7.1 installed on your NetWare 6 server. If you're going to be using this server as the middle tier server, which we'll get into elsewhere in the Title, you have to have at least eDirectory 8.7.3. In my opinion it's always best to have the latest version of eDirectory on your server that you are currently licensed for, that's currently 8.8. However, if you can't just go upgrading your eDirectory all willy-nilly, you can get away with 8.7.1. You have to have Version 1.4.1 of the Java Virtual Machine for NetWare 6 installed. As previously, I recommend the latest version of the JVM that the NetWare 6 Operating System will support. And, you have to have the LDAP Services for eDirectory running. If you're installing ZDM7 on NetWare 6.5 then you have to have at least NetWare 6.5 Service Pack 1.1 installed on your Desktop Management server. You also have to have a minimum of eDirectory 8.7.3. Again, we recommend the latest version that the Operating System supports, and you have to have the LDAP services for eDirectory up and running. If you're going to install ZDM7 on a Windows 2000 server you have to have at least Windows 2000 SP4 installed; you have to have the Novell Client 4.9 Service Pack 1A installed Ð again, this is the minimum. I recommend the latest version that is in general release. I wouldn't recommend a Beta version because Novell's Beta Clients sometimes have really weird issues that can't easily be tracked down. And you have to have LDAP running for eDirectory 8.6.2 or later. They recommend a 7.1 or later, and again, my recommendation is to run the latest version that you're licensed for. If you're installing on a Windows 2000 Server and you have eDirectory installed on that Windows server then you have to make sure that the location that eDirectory's installed into is shared as Sys. If you've used netWare Operating Systems in the past you will understand the significance of the Sys share, and the one point that most people overlook when they're installing eDirectory for ZDM7, you have to install eDirectory on Drive C on your Windows Server. This goes against a few of the Best Practices for installing Windows Servers, namely that only the operating system goes on Drive C and everything else goes on other volumes. Unfortunately, this is just a limitation of the ZENworks Desktop Management server. You only have this limitation if you're installing the workstation imaging services. If you're not using Workstation Imaging then in theory you can put eDirectory on Drive D, or Q, or wherever you want to put it. Again for best compatibility I recommend putting it on Drive C even though a lot of Windows admins just cringe thinking about that. The last requirement is, is that if you're running Terminal Services on the server it has to be running in Remote Administration mode instead of Remote Application mode. If it's running in Remote Application mode instead of Remote Admin mode then the install will appear to complete properly, however, the services won't run properly and you'll just have weird problems that will take you weeks to track down; just a good point of order Ð make sure that it's in Remote Admin Mode.