To ensure that other users with provisioning permissions cannot modify your setup, you can lock:
Any user with provisioning permissions (e.g., a provision, system, or admin-level user) can add locks and unlock any lock that he or she locked.
Admin-level users can also unlock any lock (no matter which user applied the lock). However, they cannot modify resources that other users locked. If they wanted to modify a locked resource, they would need to unlock it first, then modify it.
Lock icons are shown if:
If an entire component is locked, a lock icon is shown at the component level. A tool tip indicates who added the lock.
If a component instance cannot be provisioned due to a locked asset (e.g., another user locked the entire component or locked a virtual asset deployment used in the selected component instance), a lock icon will be added that instance's label. A tool tip indicates who added the lock and what asset is locked.
If a lock will not interfere with provisioning (for instance, a .pva is locked), the associated instance will not show a lock to any users.
To lock a component—as well as lock all artifacts that used in that component and all of that component's instances:
If the component includes already-locked artifacts, CTP will display a warning dialog describing the conflicts.
To unlock a component that you previously locked—as well as unlock the associated artifacts and component instances that you previously locked:
You can also lock and unlock specific components in Edit mode:
To lock all environment components and all artifacts used in those components:
To unlock all environment components and all the associated artifacts that you previously locked:
You can also lock and unlock specific entire environments in Edit mode:
There are a number of ways to lock or unlock specific artifacts:
You can also view a list of artifacts that you have locked—as well as unlock them—from the user profile page (choose User Profile from the login menu on the top right).
After a user locks or unlocks Virtualize server artifacts using Virtualize desktop, that Virtualize server needs to be refreshed in CTP in order for CTP to show those lock changes.