23. November 2015 at 9:39 #42257
i´m using actual a WDM system in version 4.8 which is running on a XenCenter Server and all devices (C10LE) are connecting with DHCP Scope Settings to this server.
I must migrate the system to a vmware host and because of this migration the system gets an new ip address.
Does it works if i change the device configuration from DHCP Scope Settings to the DNS CNAME “wdmserver” and migrate the system with a v2v migration to vmware?
Will this scenario work?
Stefan23. November 2015 at 10:17 #42258
It depends on the firmware version of your C10LEs. Older firmware does not have the option to search for WDM using DNS. Manual and DHCP config was the only option.
– why do you not simply change the DHCP option tag?
– why do you have to migrate the server and not just install a new one?
Just changing the IP address of the server will not work. You will have to alter some DB entries also.
CG23. November 2015 at 10:27 #42259
the devices are using firmware 8.x
It would be easier to set the DNS CNAME than change the DHCP Settings in more than 175 DHCP Scopes.
Isn’t it quicker and easier to migrate the server as install a new system including database, etc.?
What needs to be changed in the database?
Stefan24. November 2015 at 11:26 #42264
Firmware version looks good. So technically a DNS resolution will work.
Depending on what you have configured on your WDM server, a new install could be easier.
Only if you have created tons of Views and Groups or several subnets or hundreds of packages, then I would recommend to migrate the server.
Other than that, do a clean install.
CG25. November 2015 at 11:48 #42267
two additional questions 🙂
Can i migrate the existing configuration like device configuration, subnets or licenses from the 4.8 wdm server to the new 5.0 wdm server?
If I change the IP address of the existing system, then the application and the database rapportdb are still working and the thinclients are able to continue working and used?
Best regards25. November 2015 at 13:49 #42269
Just changing the IP address of the server will result in WDM not working anymore.
You have to make additional changes. Check out the WDM Troubleshooting Guide in my Download section for details on migrating or the newly uploaded guide on changing the IP and server name.
Also in the Download section you will find a tool called WDM SQL Queries. This is helpful in exporting scripts and importing them later.
Subnets can easily be exported in the subnet view and imported in the Configuration Manager – Utilities.
Licenses have to be added manually.
CG25. November 2015 at 15:15 #42270
the File Changing-the-server-Name-and-IP-Address_v2.pdf could not be found!
Which additional changes?
Thank you very much 🙂
Stefan25. November 2015 at 18:49 #42272
CG20. January 2016 at 13:19 #42371
I will change the ip address and all thinclients must connect with the new DNS Alias (CNAME) to the new IP Address.
Should i create the DNS Alias in every subdomain where a device is?
I’m using Firmware 8.0_210 and in the wnos.ini is the parameter wdmserver=’hostname.fqdn’.
Or should i change or remove all dhcp scopes?
S.Huber20. January 2016 at 16:08 #42373
Why don’t you just change the wnos.ini setting? Or are you also pushing out DHCP option tag and/or DNS alias for WDM?
CG21. January 2016 at 8:51 #42374
now the devices are using the dhcp option tag but by changing the server IP address I would therefore change hundreds of DHCP scopes and so i would like to use the DNS Alias with the new ip address.
in my wnos.ini is the FQDN of the WDM Server configured and it will not change22. January 2016 at 15:16 #42377
Check out WDM – Configuration Manager – Preferences – Device Manager – Discovery
Here you see which option the clients are allowed to use to find the WDM server.
Enable only that one, that you want (DNS Hostname), make sure all client have checked in to WDM once afterwards.
Now you are good to go with your new server and your DNS Alias.
CG22. January 2016 at 15:35 #42380
where can i find this option in version 4.8?
http://1drv.ms/1WAPz1V22. January 2016 at 16:34 #42383
the option were introduced in a later WDM version. I think it was 5.0.
– You are using WDM 4.8
– You are using DHCP option tag in each scope to point the clients to the WDM server
– You are using DNS alias in each subdomain
– You are using WDMServer= in your wnos.ini
Bad idea. You should only use one way.
You should be able to go that way:
– Create one DNS alias in your domain or one per subdomain based on your network config
– Move the server and change IP address based on the provided documentation
– Reboot the clients.
As DNS is the most preferred method of finding the WDM server, all clients should find and use the migrated WDM server just fine.
- You must be logged in to reply to this topic.