Next Topic

Previous Topic

Book Contents

Deactivation/Activation

There may be times when you need to deactivate a repository, then reactivate it. Reasons can include:

  • Imaging & Deployment is placed on hold for billing purposes.
  • Preventing the deployment of images to machines that were unintentionally booted up in the range specified for Auto Deployment.
  • Unexpected repository behavior that needs to be investigated.

Whatever the reason, you should be aware that:

  • Reactivation resumes the scheduled deployment of all images to agent machines that may have been placed on hold during deactivation. No agent machine image deployments are canceled by deactivation/activation.
  • Deactivation resets the "deploy status" of all non-agent machines specified in a PXE range for Auto Deploy. If the repository is re-activated and Auto Deploy is turned on, images will be re-deployed to all machines specified by the PXE range of IP addresses. Normally, once an image is deployed using Auto Deploy, the image is not re-deployed unless Auto Deploy is disabled, then re-enabled.