Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
zenworks 1.0 migration 2.0 1
- Thread starter bigstreet
- Start date
-
1
- #2
When installing ZenWorks 2.0 there are some precautions that should be taken first to ensure a clean installation without problems. Any objects created in Zen 1.1 will not have the added functionality of ZenWorks 2.0 objects but will remain operational as they are. Here is a guideline to answer some of the common questions and problems encountered:<br>
<br>
1. Install ZenWorks 2.0 after hours when users are not logged in.<br>
<br>
2. You should delete or rename the application objects created by previous ZENworks installs so that new ones will be created. The application objects created by the ZENworks 2.0 installation have new settings and options. In order for the ZENworks 2.0 installation to create the new application objects, objects with the same name must be deleted or renamed. <br>
<br>
3. Run DSREPAIR with the advanced option: REBUILD OPERATIONAL SCHEMA before installing Zen 2.0 and make sure DS is healthy.<br>
<br>
4. Print out the README.TXT on the ZenWorks 2.0 CD from the root directory and have it with you during the install to refer to if problems occur.<br>
<br>
5. Make sure no one is logged into NWADMIN or other programs that would keep files in the Public directory locked. ZenWorks will need to write over some of these files and errors will occur if they are open.<br>
<br>
6. Shortly after the installation, upgrade the clients using the new client provided on the ZenWorks 2.0 CD. Then you will get the inventory from the Clients when they log in. <br>
<br>
7. If you install ZENworks 2 without upgrading the Novell Client, the ZENworks 1.1 hardware inventory will continue to populate NDS TM by using the<br>
ZENworks 2 Inventory Policy. You can still view the ZENworks 1.1 inventory data in this situation only if you do the following before you install ZENworks<br>
2 (refer to the Installation and Upgrade Guide G. 25):<br>
1. Copy WMINV32.DLL and WMINVEX.DLL to a directory where they will not be overwritten. Both of these DLLs are located in the \PUBLIC\WIN32\SNAPINS directory.<br>
2. Install ZENworks 2.<br>
3. Copy WMINV32.DLL and WMINVEX.DLL back to the SYS:\PUBLIC\WIN32\SNAPINS directory. The 1.1 Workstation Manager (part of the old Novell Client) runs a scanner to populate the inventory information, which is then viewable with these DLLs.<br>
<br>
8. Zen 1.1 WS Inventory is otherwise unreadable in Zen 2.0. In ZENworks 1.1, the Workstation Inventory data was stored as objects and attributes in Directory Services. In ZENworks 2.0, the Workstation Inventory data is stored as records in a Sybase database. When ZENworks is upgraded from 1.1 to 2.0, the NWADMN32 snapins that manage the viewing and manipulation of Workstation Inventory are updated. The new snapins will read the information from Sybase and WILL NOT read the information from the old ZENworks 1.1 Workstation object attributes. The Novell Client is responsible to put the Workstation Inventory in either the Sybase database or into NDS. If a workstation is running an older client than what shipped with ZENworks 2.0, the information will still be sent to the Workstation object in NDS and will be un-viewable using the newer ZENworks 2.0 NWADMN32 snapin. Administrators should plan to update the workstation clients in their environment at the same time or shortly after installing the ZENworks 2.0 components on the server. Otherwise the administrators will be unable to view/manage the Workstation Inventory information. The following clients will place the Workstation Inventory information into NDS (as opposed to Sybase): Novell Client for Windows NT versions 4.30, 4.50, 4.51, 4.60. Novell Client for Windows 95/98 versions 2.5, 3.0, 3.01, 3.02, 3.10. There is not currently a way to automatically migrate the existing workstation information. This is not a significant issue because the next time the workstation logs in the inventory will be sent to the Sybase database (as long as they are using the client that shipped with ZENworks 2.0 or newer).<br>
<br>
9. Optional: Delete old Workstation Inventories stream file that consumes a great deal of space in the NDS database. See TID 2951109 for details. This ability has been provided in released version of ZENworks (added in the 5/14 beta build) via the REMINV1X.EXE utility. This utility is located in the PUBLIC\WIN32 directory (same as WSIMPORT and other similar utilities). It allows a user to browse/designate a context to begin searching for old inventory attributes and includes the option to search all sub-containers in the tree from the one specified. The utility will build a list of Distinguished Names (DNs) for all Workstation objects. It will then check to see if these objects have any of the old 23 ZEN 1.x inventory attributes. If they do, it will attempt to delete these attributes and reclaim the disk space they occupied by deleting the associated stream file or freeing space in the Value NDS table/file. The REMINV1X.EXE utility will attempt to perform all operations with the NDS privileges of the user who is currently logged-in. This utility will require that the logged-in user have Supervisor rights (either All Properties or Object) to be able to read/delete the necessary workstation attributes. <br>
<br>
1. Install ZenWorks 2.0 after hours when users are not logged in.<br>
<br>
2. You should delete or rename the application objects created by previous ZENworks installs so that new ones will be created. The application objects created by the ZENworks 2.0 installation have new settings and options. In order for the ZENworks 2.0 installation to create the new application objects, objects with the same name must be deleted or renamed. <br>
<br>
3. Run DSREPAIR with the advanced option: REBUILD OPERATIONAL SCHEMA before installing Zen 2.0 and make sure DS is healthy.<br>
<br>
4. Print out the README.TXT on the ZenWorks 2.0 CD from the root directory and have it with you during the install to refer to if problems occur.<br>
<br>
5. Make sure no one is logged into NWADMIN or other programs that would keep files in the Public directory locked. ZenWorks will need to write over some of these files and errors will occur if they are open.<br>
<br>
6. Shortly after the installation, upgrade the clients using the new client provided on the ZenWorks 2.0 CD. Then you will get the inventory from the Clients when they log in. <br>
<br>
7. If you install ZENworks 2 without upgrading the Novell Client, the ZENworks 1.1 hardware inventory will continue to populate NDS TM by using the<br>
ZENworks 2 Inventory Policy. You can still view the ZENworks 1.1 inventory data in this situation only if you do the following before you install ZENworks<br>
2 (refer to the Installation and Upgrade Guide G. 25):<br>
1. Copy WMINV32.DLL and WMINVEX.DLL to a directory where they will not be overwritten. Both of these DLLs are located in the \PUBLIC\WIN32\SNAPINS directory.<br>
2. Install ZENworks 2.<br>
3. Copy WMINV32.DLL and WMINVEX.DLL back to the SYS:\PUBLIC\WIN32\SNAPINS directory. The 1.1 Workstation Manager (part of the old Novell Client) runs a scanner to populate the inventory information, which is then viewable with these DLLs.<br>
<br>
8. Zen 1.1 WS Inventory is otherwise unreadable in Zen 2.0. In ZENworks 1.1, the Workstation Inventory data was stored as objects and attributes in Directory Services. In ZENworks 2.0, the Workstation Inventory data is stored as records in a Sybase database. When ZENworks is upgraded from 1.1 to 2.0, the NWADMN32 snapins that manage the viewing and manipulation of Workstation Inventory are updated. The new snapins will read the information from Sybase and WILL NOT read the information from the old ZENworks 1.1 Workstation object attributes. The Novell Client is responsible to put the Workstation Inventory in either the Sybase database or into NDS. If a workstation is running an older client than what shipped with ZENworks 2.0, the information will still be sent to the Workstation object in NDS and will be un-viewable using the newer ZENworks 2.0 NWADMN32 snapin. Administrators should plan to update the workstation clients in their environment at the same time or shortly after installing the ZENworks 2.0 components on the server. Otherwise the administrators will be unable to view/manage the Workstation Inventory information. The following clients will place the Workstation Inventory information into NDS (as opposed to Sybase): Novell Client for Windows NT versions 4.30, 4.50, 4.51, 4.60. Novell Client for Windows 95/98 versions 2.5, 3.0, 3.01, 3.02, 3.10. There is not currently a way to automatically migrate the existing workstation information. This is not a significant issue because the next time the workstation logs in the inventory will be sent to the Sybase database (as long as they are using the client that shipped with ZENworks 2.0 or newer).<br>
<br>
9. Optional: Delete old Workstation Inventories stream file that consumes a great deal of space in the NDS database. See TID 2951109 for details. This ability has been provided in released version of ZENworks (added in the 5/14 beta build) via the REMINV1X.EXE utility. This utility is located in the PUBLIC\WIN32 directory (same as WSIMPORT and other similar utilities). It allows a user to browse/designate a context to begin searching for old inventory attributes and includes the option to search all sub-containers in the tree from the one specified. The utility will build a list of Distinguished Names (DNs) for all Workstation objects. It will then check to see if these objects have any of the old 23 ZEN 1.x inventory attributes. If they do, it will attempt to delete these attributes and reclaim the disk space they occupied by deleting the associated stream file or freeing space in the Value NDS table/file. The REMINV1X.EXE utility will attempt to perform all operations with the NDS privileges of the user who is currently logged-in. This utility will require that the logged-in user have Supervisor rights (either All Properties or Object) to be able to read/delete the necessary workstation attributes. <br>
- Status
Similar threads
- Locked
- Question