>I could simply change DNS name and voila each client would connect seamlessly. >This code is for a large hospital and changing DNS names like this does not >seem to be in the cards.
That what we did at the last place I worked. Alternatively, if your users are on Windows, you can push new .4DLink files to them in Windows login scripts. That worked effectively too and may be easier to implement in your environment. HTH, Tom Benedict > On Oct 4, 2019, at 09:40, Chuck Miller via 4D_Tech <[email protected]> > wrote: > > Hi all, > > We are ready to implement our new mirror code and are writing documentation > on this process. The one thing I have not figured out is how to turn the > mirror into production. > > The server itself is pretty easy as I have a record that has IP address of > production machine in a record. > > What I do not understand is how to update the clients. Production and Mirror > are on different subnets so the built client on the machine will not be able > to connect to without a change to 4Dlink file. > > What I was hoping was to use a DNS name and simply change the IP address it > points to so if I had > > Server_prod which pointed at 192.168.5.5 > Server_Mirros which pointed at 192.162.5.17 > > The IP’s are of course not the real ones in use > > I could simply change DNS name and voila each client would connect > seamlessly. This code is for a large hospital and changing DNS names like > this does not seem to be in the cards. > > Can anyone tell me how they are doing this > > Thanks and regards > > ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
