Domain change migration

[admin@gzbg.de]

Hello OPSI-experts,

I did the following:
After a domain change from gzbg to glaubenszentrum and from gzbg.local to glaubenszentrum.local was made, there were also some other changes necessary like nameserver etc.
Then I changed those values via 1stboot.py.
Now the problem is that there are 2 depot-servers available and in the new one (glaubenszentrum) there are no clients and there is also no software available.
What is necessary to migrate those clients and the software?
Do I need to migrate something else?
Is it possible to delete the old depot-server gzbg after this migration has taken place? How?
Or is there an easier way to do the migration at all?

Best regards
Ruben

[ueluekmen]

Hi Ruben,

first of all create a new backup with opsi-backup.

Then you can go to your configserver shell and try the following:

Delete the new empty depot:

Code: Alles auswählen

opsi-admin --no-depot -d method host_delete <new-depot-id>

Then try to rename the old one:

Code: Alles auswählen

opsi-admin --no-depot -d method host_renameOpsiDepotserver <old-depot-id> <new-depot-id>

[denmarknian]

What about the fully qualified domain names, how can it be migrated to the ne domain? thank you.

[denmarknian]

By the way the fully qualified domain name is in the opsiclientd.conf ,hostkey. How can it be replaced without reinstalling the agent?

[n.wenselowski]

Hello,

to migrate change a clients FQDN through the configed you should find an option like "renameClient". But then you need change the configuration on your client aswell!

This can be scripted!
Steps should be to first connect to the client via JSONRPC, then replace the hostname and then you can call the method host_renameOpsiClient on your opsi-server.

If you want us to build an automatism for this you can contact us with an existing support contract


With kind regards

Niko

[admin@gzbg.de]

Hello,

thank you for your answer and sorry for my late reply. Now I have the problem, that if I execute the following command:
opsi-admin --no-depot -d method host_delete opsidemo.glaubenszentrum.local
the depotserver still exists.
What is wrong about that command?
Here are the attributes of the depotserver:
"masterDepotId" : null,
"ident" : "opsidemo.glaubenszentrum.local",
"networkAddress" : "192.168.168.0/255.255.254.0",
"description" : "",
"inventoryNumber" : "",
"ipAddress" : "192.168.168.11",
"repositoryRemoteUrl" : "webdavs://opsidemo.glaubenszentrum.local:4447/repository",
"depotLocalUrl" : "file:///var/lib/opsi/depot",
"isMasterDepot" : true,
"notes" : "",
"hardwareAddress" : "00:50:56:be:f5:13",
"maxBandwidth" : 0,
"repositoryLocalUrl" : "file:///var/lib/opsi/repository",
"opsiHostKey" : null,
"type" : "OpsiConfigserver",
"id" : "opsidemo.glaubenszentrum.local",
"depotWebdavUrl" : "webdavs://opsidemo.glaubenszentrum.local:4447/depot",
"depotRemoteUrl" : "smb://opsidemo/opsi_depot"

Best regards
Ruben

[n.wenselowski]

Hello Ruben,

please check if the log shows any errors or failures.
opsi-admin --help should show you the appropriate parameters.


With kind regards

Niko