Redeploy a ztC Edge system if you already deployed and configured the system, but you need to reset its network settings to prepare it for deployment on a different network or subnet, possibly at a new location.
You typically redeploy a new ztC Edge system if you need to prepare it with settings and virtual machines (VMs) for an end user, but then you need to reset the network settings so the end user can deploy the system at their site for the first time (in a similar manner to using the Windows Sysprep utility to prepare a Windows system for its first end-user deployment, or Out-Of-Box Experience (OOBE)).
After configuring the system for the end user, you initiate a redeployment in the ztC Console. The system subsequently clears the system and node network settings, shuts down any VMs that are running, and powers down the system. The system retains its non-network system settings and the VMs that you configured, but it is now prepared for deployment as described in
When you redeploy a ztC Edge system, note the following restrictions and workarounds:
Disable any NFS/CIFS shares before redeploying a system.
Active NFS/CIFS shares interfere with the redeployment feature. Disable the shares until you finish configuring the network settings on the new network.
System reboot needed when setting new static system IP address.
A system loses access to the secondary node if you redeploy and shut down the system, start it up in a new location, and then configure a new static system IP address. To regain access to the secondary node, reboot the system by opening the System page and clicking Reboot. Rebooting the system refreshes the gateway settings on the secondary node and allows it to connect to the system.
To redeploy a ztC Edge system
Product Support and Downloads