/build/static/layout/Breadcrumb_cap_w.png

New Kace Setup

I've been working to configure the Kace Service Desk section and have a few concerns;

1. Is it possible to make the comment field required? This way users will have to provide a lengthier description of the request
2. Can the UI be changed at all? Specifically, place some of the text boxes next to each other instead of straight down the page
3. With the resolution field 'Required on close', is it possible to create a ticket and close it right away? Resolution field only appears after ticket is saved.
4. For new users who first log in; is there a way to make all users part of a default role?


I think thats all for now. Any assistance is appreciated.
Thank you.

PS. Does Kace provide some KB articles that can be imported so as to assist with populating it?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: GillySpy 13 years ago
7th Degree Black Belt
0
1. It is not possible today to make the comment field required out of the box. You could implment this faq using FIELD_CHANGED='COMMENT' as an alternate (http://www.kace.com/support/kb/index.php?action=artikel&cat=8&id=1085&artlang=en)
2. You can reorder the fields, hide them, change the label but not the extent you mention of formatting them
3. No it is not possible if you have that required
4. When users are created they are assigned a role. If you are using LDAP you can setup their authentication source (settings-> user authentication) with a role that they will inherit on first-time login or you can import users in advance (adhoc or a schedule) and assign a role then too. If you are not using LDAP then they will get the built-in "user" role and you can only change that role on the user list.

If you go to kace.com/support you will find a lot of faqs. Here is one on appdeploy I recommend: http://itninja.com/question/dll-registration6
Posted by: cblake 13 years ago
Red Belt
0
PS. Does Kace provide some KB articles that can be imported so as to assist with populating it?
We do not have any KB articles for you to populate on to your appliance, because every organization handles break/fix solutions differently. These will have to be created from your existing toolset (Word docs, old tickets/emails, other systems, etc.)
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ