- This topic is empty.
-
Posts
-
Hi All,
As part of DR, I’m wondering how we could get our existing WTOS clients to redirect to another WDM/FTP server to pull the updated settings such as VDI Broker etc.
Normally, this could be achieved by updating the DHCP Scope options – however, we have some remote sites with routers that aren’t intelligent enough to hand out DHCP Scope Options.
Is there a way to put more than one FTP server into the configuration of these devices so that if it can’t pick up the first, it tries the second (at which point the second FTP will still under normal circumstances have WTOS.ini for production use whilst when DR is initiated, the WTOS.ini file replaced).
Thanks for your help!
Why not put the new FTP server Ip in the wnos.ini:
Fileserver=newIP
Rapportserver=newIPThis way by time each client will get the new Fileserver and WDM server. You can control in WDM if a client has checked in and got the new path in the network properties of each client.
CG
Hi ConfGen,
The current WDM server is at the production site . Therefore if I needed to initiate DR it means that the WDM server will be unavailable.
As I can’t control the DHCP Scope Options, if I built a new WDM at the DR site, I wouldn’t have any control over the already deployed clients – unless I manually added them all? This isn’t a problem for S90s as they access the connection broker via a web interface and use DNS which is easily updated. The problem is purely with the S10s as they’ll still hold the EnableLocal option thus looking for the old FTP server.
I suppose what I could do (if it allows it) is to configure the initial WTOS.ini at the production site to use a live and a DR DNS server . Then if I specify the WDM FTP server by DNS name in the WNOS.ini file and EnableLocal, it would then redirect to the new WDM server. Will try it now and see what happens.
Thanks
Thanks
- You must be logged in to reply to this topic.