Subtitles of the Movie

This is ZENworks Desktop Management 7 and in this video we're going to discuss ZENworks Objects in eDirectory. At the very end of the ZENworks installation process that we went through elsewhere in the Title, the ZENworks installation process will create a few basic objects in eDirectory. Now, obviously these few objects that are created are not all of the objects in eDirectory that constitute a fully functioning ZENworks implementation, however, it's important to know what these starter application objects and policy objects are so that you can modify them if need be. All of the administration for ZENworks Desktop Management 7 is done inside Novell ConsoleOne. Now anyone that uses Novell products knows that ConsoleOne is kind of the Legacy Network Administration Tool and that all of their latest and greatest products generally don't have ConsoleOne Snap-ins; they want you to use iManager, which is a web-based administration tool. However, in the ZDM7 world you will live and breathe inside ConsoleOne. So obviously, these first few objects that are in the tree are installed in the tree when you install the service. There's your server object, you have LDAP Serve and Group, and your SSL Certificates, and then you have the objects that were created by the ZENworks installation here, near the bottom of the object list. These first two objects that you see here are application objects, and you can know that they are application objects by this distinctive Icon over to the left. We'll briefly look inside one of these application objects just to give you an idea of some of the property sheets that you have. There are all of the options for distributing files and folders, and the scheduling, et cetera. Here are the options to actually run the application; when it runs; how it runs; what operating system it runs on. Obviously we'll get into these a lot more in-depth when we discuss Application Distribution, but I go into it now just so you can see what the Property Sheets of an application object look like. The next object we're going to look at is the Desktop Management Database Object. The Desktop Management Database Object is created for every server that has a Desktop Management Database on it, obviously, that's why it's the Desktop Management Database Object. In our lab we will only have one Desktop Management Database but if you had a very distributed network with Desktop Management Database Servers scattered throughout the tree you would have one of these objects for every server that has the database on it, and these objects would be uniquely identifiable because it has the Server Name that the Database is stored on in the name of the Object. Obviously you could right-click and choose Rename, and rename the object whatever you want but it's been my experience that most organizations don't. These default objects serve well enough, so we'll check the Properties of the ZENworks Desktop Management Database. The first field is the Server DN. This is the full location of the Server in eDirectory. In this case our vtc-zenserver in DS is at the top level of our tree; it's in the VTC Organization. If you retired this particular Desktop Management Database Server and you needed this particular Object to point at a different Server, you could click this Browse button over here and go find whatever new server held the new database. In this case there's no other server, so we'll just hit cancel. The next field is the Server IP Address, or DNS name. It defaults to the name of the Server. In our case that's the name of the Windows box that is running the Desktop Management Database. You could drop that down and pick any of the valid names or IP Addresses for that particular box. In this case we'll leave it as VTC's Inserver, because that's what resolves on our network. And then you have three different sets of credentials for Read-Write, Read-Only, and Write-Only access to this particular Desktop Management Database. Most of the time you won't have worry about changing these, especially if you're using the default Sybase Database that comes with ZENworks. However, if you're running your Desktop Management and Inventory Databases on a Microsoft SQL Server, for example, you may have to fill in whatever credentials are given to you by your database administrator, or if you happen to be the database administrator as well you can simply set up these user names and passwords. These passwords are all the word: novell, all in lower case. That's documented in the documentation as well as with several TIDs on Novell's site that tell you how to recreate these user credentials should they ever get deleted. The next two Property Tabs are: Driver information for the Java Database Connectivity Driver, and the Open Database Connectivity Driver. In this case, RJDBC Driver Type is Sybase because that is the type of database that we're running on our Desktop Management Server, and unless you're really good with your database you generally will not change any of these options down here. If you were running on, say, Oracle, or SQL Server you could pick SQL Server 2000 and hit Default Settings to set these to the defaults, but again you'll rarely change these because the Port number and the flags and the service name generally are the default for the platform you're using. The same holds true for the ODBC Driver information. This is if you happen to be using an ODBC Driver instead of a JDBC Driver. To be honest, in all of the implementations of ZENworks 7 I've done, I've never had to fill out this property page. That's just honestly how little the ODBC Driver is used. So, we'll Cancel out of this and we'll move on to the next Object.