Cool Solutions

Moving a ZAM server from one Windows Domain to another



By:

June 27, 2008 10:47 am

Reads: 6121

Comments:0

Score:0

Note: This information was extracted from this TID. You should review the actual TID before using this information, as the TIDs are sometimes updated after we highlight them.

The following things need to be taken into account when moving a ZAM Windows server from one Windows Domain to another:

  • Two of the ZAM Windows services use a Windows account for Login. The two services that need to be checked are “ZENworks Asset Management – Task Server” and “ZENworks Asset Management – Collection Server”. The “Log On” tab shows the account being used for login, and that should be changed from the old Windows Domain to the new one. The user accounts being used must have equivalent rights to the File Store share (only relevant on an Enterprise install).
  • Domain Rights can also be used for the Remote Client Install program launched from the ZAM Manager, but those credentials are not saved and are entered in during the actual install process from the GUI. No change needs to be saved anywhere other than remembering to use the new Domain for the rights used during the ZAM Client install.
  • If a hardware upgrade is being performed on the Collection Server or Task Server, make sure that the collection clients can connect to the new machine name of the new server, if a new name is going to be given. Be sure to “reassign” the workstations to the new Collection or Task Server.
  • Also note that outstanding inventory tasks will need to have completed before the transition is performed. In other words, if workstations still show as “checked out” in the Process Control Panel, then their associated inventory tasks will need to have completed before reassigning them manually to a new task server, or said associated tasks will be orphaned, will not get checked into the database, and the inventory scan will have to be performed again, for any workstations which had outstanding processes pending before the move.

    Note: For authenticated FTP File Stores, the File Store management may need to be temporarily changed to anonymous FTP to allow the transition to a new Windows domain.

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags:
Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS