Page 959 - CRESTRON HOME OS-3

Transfer Data using a Deploy Code (Recommended)

Use a deploy code to quickly and automatically transfer system data to a Crestron Home
processor. When a deploy code is used, system data is downloaded from the myCrestron
Residential Monitoring Service and then loaded onto the Crestron Home processor.
Requirements

l Transfer data using a deploy code between the control processors listed below:

TO

CP4-R MC4-R CP3-R PYNG-HUB

CP4-R Supported Unsupported Unsupported Unsupported

MC4-R Unsupported Supported Unsupported Unsupported
FROM
CP3-R Supported Unsupported Supported Unsupported

PYNG-HUB Supported Supported Unsupported Supported

IMPORTANT:
MC4-R system data cannot be transferred to a CP4-R.

l The Crestron Home processor must be connected to the myCrestron Residential
Monitoring Service prior to using a deployment code. Refer to Add the Crestron Home
Processor (on page 513) for details.
l The new control processor must be connected to the same network and have the same
subnet mask as the old control processor. Using a private switch and connecting all devices
to it is best.

l Write down the Hostname of the old control processor. The hostname will be needed when
setting up the new Crestron Home processor.
l Migrating from PYNG-HUB to a CP4-R or MC4-R control processor:

o Audio components, such as audio sources, endpoints, and routing, are not
transferred to the new control processor. The audio components must be manually
added to the system.

o Camera tiles do not display in the user interface after migrating to the new control
processor. To view the camera tiles, remove the camera and then add it again. For
details, refer to Cameras (on page 80).
l Add a wireless gateway (CEN-GWEXER) to the system if the old control processor had an
internal wireless gateway and the new processor does not have a gateway.

942 • Crestron Home™ OS Product Manual — Doc. 8525Z