I am trying to migrate existing clients on an old server to redirect to a new server and corresponding relays. I put the new masthead file in the wwwroot folder of the new relay I want the clients to point to. In this segment of the network, the clients can not talk to the server, but must talk through the relay due to network config. I tried running the fixlet called switch "BES Client Action Site Masthead - BES>=7"and changed the script to point to the url of the new masthead on the new relay. The client’s status just stays at “pending download”. I did test this url on client machines to ensure they can get to it. When going to the url in a browser, the masthead file appears. Why are the clients just in pending download status? Do I need to specify the new relay in this fixlet since they can’t talk directly to new server? Any help is greatly appreciated, as I have to get 3000 clients moved as soon as possible. Thanks!
No responses? Need to get this completed asap. All clients are just sitting at pending download status, and have not run the script to switch the masthead. Any input is greatly appreciated!
When the Switch Masthead task is used, the clients essentially re-register with the new server, so they need to be able to communicate with it.
I believe there is a way for clients to perform their initial registration through a Relay, but I wasn’t able to find a link to the document. I think what I remember was doing it through a DMZ Relay, but any relay should work.
When I have done this in the past to move a system from my prod to test environment, I made a copy of the fixlet you specified and put it in my custom site. I then modified the download URL to point to a location of the masthead file on the target TEM server (really does not matter, as long as it is an accessible URL).
Now I wonder if what is happening is that the system is moving to the new server, but not reporting back because it is no longer a client of the old system. I would imagine that you may never see a system report complete, as the last step of the fixlet is to stop the service and start it again and at that point it would be a client of the new server.