Delete Issues and Purges¶
Whenever Unified CM and CUCX data is synced into VOSS-4-UC, it assumes management of the data and, as a result, that data would be deleted by any hierarchy delete performed in VOSS-4-UC. These deletes can fail if your Cisco Unified Communications Manager model dependencies don’t reflect the additional data contained in existing, provisioned dial plans brought into VOSS-4-UC.
There are two ways to prevent these delete failures from happening:
- Work with a Cisco System Integrator to update your HcsCucmWrapperCascadeDelPWF workflow to handle the dependencies in your existing dial plan.
- Perform a purge operation instead of a delete.
Purging deletes all users, subscribers, phone, profiles, and devices from a brownfield customer’s VOSS-4-UC while leaving these objects on the Unified CM and the Cisco Unity Connection.
To execute a purge:
Log in to VOSS-4-UC as a reseller administrator or higher.
Choose Administration Tools > Data Sync.
From the hierarchy drop-downs, select the customer whose data you need to purge. If the data was created at the Site hierarchy, the purge only takes place at site level.
Click HcsPurge-<IP address + fully qualified domain name + hostname>.
From the Sync Type drop-down, choose Purge Local Resources. All other default values remain unchanged.
Click Execute.
Repeat steps 4-6 for the Unified CM.
Verify that the instances and device models are deleted by checking Phones, Users, and Voicemail.
At this point, you can try again to migrate the customer into the Cisco Hosted Collaboration Solution by executing HcsPull from the same menu for Unified CM and Unity Connection, and then performing the Overbuild operations.
