Removing templates and scopes

hs-caution

Do not copy a provisioned spoke database for use on other devices.  Inconsistent sync results will occur as the hub database identifies the data each spoke database has already synced.

All provisioning and deprovisioning must be completed through the SYNC Add-in to ensure that all objects are created and removed correctly.

Do not remove templates or remote scopes unless local scopes have been deprovisioned from all spoke devices. If a remote scope is removed, corresponding local scopes cannot be used, and reprovisioning the remote scope will lead conflicts on each record.

<< Click to Display Table of Contents >>

Navigation:  SYNC Add-in > Setup >

Removing templates and scopes

hs-caution

Do not copy a provisioned spoke database for use on other devices.  Inconsistent sync results will occur as the hub database identifies the data each spoke database has already synced.

All provisioning and deprovisioning must be completed through the SYNC Add-in to ensure that all objects are created and removed correctly.

Do not remove templates or remote scopes unless local scopes have been deprovisioned from all spoke devices. If a remote scope is removed, corresponding local scopes cannot be used, and reprovisioning the remote scope will lead conflicts on each record.

Deprovisioning can take considerable time depending on the size of the scope and other factors such as server performance and connection speeds.  It’s not uncommon for timeout issues to occur during deprovisioning, requiring the command timeout to be set to 0 (unlimited).


hmtoggle_arrow1How To: Deprovision a template

hmtoggle_arrow1How To: Deprovision a remote scope

hmtoggle_arrow1How To: Deprovision a local scope