Migrating Networker Server to Active Directory

[ghorton]

I migrated our backup server from our NT4 domain to our Active Directory domain. Which means the FQDN of the machine changed I Have also noticed a few other things.

One of the instances for the backup server now has a different client ID, also now specified as a FQDN.

During last nights back noticed that kept getting now messages for now savesets in media database and the daemon log has continuing without index header for backupserver.fqdn

Does anyone now of any issues with migrating a Networker server from one domain to another.

 

[605]

You can do 2 things:
- add the appropriate name in the Alias field for your NW server client.
- delete the client resource and re-create it. At this time you may also set the (old) client ID.

 

[ghorton]

Came back to this at the end of last year.

Made a group with all containing all clients and performed an index backup.
Changed services to manual
Went through all server name changes, dns changes and restarts.
Edited the \nsr\res\servers file on all clients to the new fqdn name and restarted the Networker remote exec service on all clients.
Restarted Networker on server.
New client created with fqdn.

I think this would have been alright if I didn't have the earlier problems. Had to point the indexes on the new client to the correct location