What will be the behavior after I have decided to try out the ESM version?
- After an upgrade or a fresh installation, the default service desk instance will be the IT help desk. All existing data will be moved under the IT service desk.
- A maximum of 15 service desk instances can be created.
- Each instance will be on the enterprise trial edition, allowing one owner to be associated.
- The owner of an instance will have the privileges of an admin with the instance configuration access.
- Two portal licenses for two technicians with complete access and a validity of 30 days will be provided. To associate more users and test the instance in a real world scenario, contact email@example.com to apply license.
What is the behavior of a new service desk instance?
- All newly created service desk instances will be set with New status. This status is set by system.
- If licenses are applied then multiple owners can be assigned for an instance.Until then, only one instance owner can be assigned to an instance.
- When the instance owner access the instance for the first time, the status for the instance will automatically change to Pre-Production. While the instance is at this status, only the instance owner will be able to access the instance.
- From Pre-Production status, the instance owner can move an instance to the Production status after the configurations related to the instance are done. This will make the instance accessible all the users associated with it.
Can an Org Admin remove an instance owner?
- An Org Admin can only assign users as owners for new instances. Only an instance owner can remove another instance owner. So unless an Org Admin is the owner of the particular instance as well they cannot remove owners from an instance.
What happens if an instance owner is removed?
- If an instance owner is removed, then the user account will be immediately moved as a requester, provided if the user import in that instance is set to (ALL) or the user import criteria of the instance matches with the users' profile. Else, the instance will not be available for that user any more.
Can an Org Admin assign anyone to be an instance owner?
- Yes, an Org Admin can make anyone from the user list as the owner of an instance.
What will be the role of the user who is assigned as the owner of a service desk instance?
- The owner of a service desk instance will have the privileges of an SDAdmin along with the instance configurations permissions for that particular instance. All the previous roles assigned to that user will be removed.
Can I move a ServiceDesk Instance to "Retired" Status?
- Yes, Instance Admin/Owner has permissions to move an instance to Retired Status. By doing so, the whole instance will go into Read-Only mode, allowing only the Instance Admin/Owner to access the instance.
- Once an instance is moved to Retired status , it CANNOT be moved to Pre-Production or Production status.
Can I manually move a ServiceDesk Instance to "Expired" Status?
- No. ServiceDesk Instance can be moved to Expired status only by the application as it's an automated process. This happens only during expiry of the license.
- But once the license is applied to the instance, it rolls back to the previous status (Production) of the instance.
Will I be able to see requests across instances, all at once?
- As of now, it is not possible to view them on a single view. You may need to switch to the instance to view the corresponding requests.
Whenever a new version of ServiceDesk Plus is released, is it possible to selectively upgrade a few instances/service desks? Or should the entire application be upgraded?
- ServiceDesk Plus upgrades are common for the entire application and not specific to an instances.
Who can upgrade the instance? the OrgAdmin?
- ServiceDesk Plus does not support instance specific upgrade. The upgrade is global for the entire application. The upgrades can be performed by the administrator of the application who has access to the physical servers.
How are request Ids handled across instances? Also, when shifting tickets between instances how are the request IDs assigned to them. For example, if I move a request from the IT service desk with ID 15 from to the HR help desk, how would it be tagged?
How are the mail server settings handled across different instances?
- Each service desk instance can have its own mailbox that fetches emails from different accounts separately. Service Desk will process email from the first instance, once all the emails are fetched, it will proceed to the next instance.
When implementing a change or a project can technicians and users from various other departments be a part of the process? Say can a technician from the HR service desk instance be added as a member in a change or project in the IT service desk instance?
- Activities at each instance is specific for the individual instance, technicians and users from different instances cannot be part of activities within a specific instance.
Can sites be configured specific to each instance?
Can we migrate our current ESM setup from the cloud version of ServiceDesk Plus to the on-premises version?
- As of now data can be exported through the user interface from the Cloud version of ServieDesk Plus and imported into the on-premises version of SDP.
Can we backup the data of each instance separately?
- You can backup your help desk data in request and admin modules within an instance using instance-specific backup tools. Refer to the admin guide to learn how.
How to migrate data from one instance to another instance?
- You can export your help desk data in request and admin modules from an existing instance to a new instance using instance-specific backup and restore tools. This data migration is a two-step process involving manual backup of an existing instance and restoring it to a new instance. To learn more, refer to this guide.