If the demo MCC Deployment Server is assigned a static IP address,
then you can assign the same static IP address to the Production MCC
Deployment Server, therefore you don't have update the agents on the
devices. They will all continue to point to the Deployment Server.
This is possible if you are using static IP address assignment, and
assuming you can switch their IP addresses - i.e. the Demo and
Production system exist on the same network. The steps are:
You are done!
You can setup multiple MCC Deployment Servers to manage your devices.
You can use this feature to balance and distribute the load off one
server to multiple licensed servers, and/or shift the work from one
server to another, in case one goes down.
This assumes you are licensed to connect two deployment servers to
your system. If you are not, then you can't use this option, as adding a
secondary server wouldn't be possible. The steps are:
You can configure the MCC agents on the devices to connect to a
secondary IP address, which could be internal or external. All traffic
routed to this alternative IP address will route to the same MCC
Both servers have to have the same Site ID and both have to have the
Under Demo Deployment Server Properties, you can add secondary IP
address of the production server. This will automatically push the new
server IP address to the terminals.
On the Production Deployment Server Properties, you would only want
one IP address of this machine, not the demo server.
On the Production Deployment Server, create a generic add devices
rule to allow any device to connect to this production MCC system. Here
are the steps to do this:
Once the rule is created, devices will automatically switch to
connect to the Production Deployment Server.
Once all terminals have migrated, you can shut down the Demo
While the devices are still connected to the demo MCC Deployment
Server, you can create a new package containing the agent profile which
would connect to the new production MCC Deployment Server. Then you can
ship this to the connected devices, and then switch the servers.
This assumes that the demo and production MCC Deployment Servers are
using different databases, so devices existing on the demo server don't
exist on the production server. The steps below help you add these
devices to the production server automatically. The steps are: