Novell ZENworks 6.5 Server Management - ZfS65
Novell ZENworks 7 Server Management - ZfS7
Installing over the top does not change the symptoms.
No DS replica existed on the server during the first install (see KB 10059335 ( https://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=10059335&sliceId=&dialogID=52160313&stateId=1%200%204746841), specifically the Fix statements, item 2).
The NetWare server was not a routing server before the MMS install.
Schema install was successful.
Schema verify fails with a -256 error.
Running \ZFS\SVRMGMT\ENGLISH\SETUP.EXE NO_SCHEMA_CHECK (see KB 10058497 (https://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=10058497&sliceId=&dialogID=52160313&stateId=1%200%204746841)allows the install to complete but does not resolve the symptoms.
Uninstalling / Reinstalling Novell ZENworks for Servers.
is the file SYS:SYSTEM\MMSLIC3.BIN. It is not necessary to delete
this file if un-installing / re-installing ZFS 3.0.x. If there is
any concern, delete it. If cleaning the files off the server,
delete it. When ZFS 3.0.2 is installed, this file is necessary for
the MMS Site Server to load.
List of ZFS DS objects:
Server Package [Manually created for TED/POL/INV. ZFD 3.x & 4.x may also have this object. The default name would be the same, but the name can be re-defined by the installer.]
Service Location Package [Manually created for TED/POL/INV. ZFD 3.x& 4.x may also have this object. The default name would be the same, but the name can be re-defined by the installer.]
Servername_ZenInvService [Created by the install for TED/POL/INV. ZFD 3.x & 4.x may also use this object. The ZFD object should be in a different container than the ZFS object.]
Server Software Packages
Site Database Administrator
Yellow Hard Hat objects:
Servername Site_Inventory Database Service
Database Object Editor
A slightly different process would be to uninstall by running the ZFS 3 Site Management Install, select "yes" to uninstall then delete all the ZFS 3 DS objects created automatically during the install and manually after the install before performing the new install. Use admin.root for the re-installl if installs with admin.root equivalent users have not been successful.
Formerly known as TID# 10072445