| Author |
Message |
|
|
G'Day Mark,
I don't have a specific template for you, but my suggestion to you would be to send your customers an email indicating that general support will only be provided on requests submitted via the EUP. Urgent requests can be reported via phone call. You can also indicate that request submitted through the EUP will receive priority over any other requests. Outline the benefits of the EUP, where your customers can view the status of requests, find solutions from the FAQ and supervisors can view requests submitted by their staff. Are you going to use the incoming email integration?
Regards,
|
|
|
G'Day,
The best practise would be to provide every en user with their own login. This will assist you in determining who logged the new request and provide you with statistical data with regards to which customer is consuming the most of your time. Also the problem end users will become apparent very quickly.
|
|
|
G'Day,
You can use the permission setting user and groups only for this purpose. This will limit the visibility and modification rights to only the requests directly assigned to the admin or the admin groups they belong to.
Let me know if you require any further assistance.
|
|
|
Brad,
This is the case and the hotkey should open the End User Portal.
Please do the following;
1. Go to Start > Programs > SysAid > Deploy SysAid > Edit -> Settings.
2. Change the Log Level to Debug and click on OK.
3. Now redeploy the agent to a problematic client.
After deployment is complete, you will have a "SysAidLog_CURRENT-DATE.txt" file in the [C:\Program Files\SysAid\logs] directory on the client computer.
The log file should indicate what is causing the error. Please send an email to helpdesk@sysaid.com attaching the log file.
|
|
|
Sean,
Can you providfe a screenshot? Or maybe send me a PM with your contact details.
|
|
|
G'Day Jose,
Welcome and please post any questyions you have. We will be happy to answer them for you.
|
|
|
Good Day Geek girl,
Click on the blue design cog. Select the maintenance tab from the dropdown at the top and then check the visisble checkbox.
Save and it should be back.
|
|
|
G'Day,
You are really funny. I had a good laugh about the anus.
You can get the version of SysAid by going to ..\SysAidServer\root\WEB-INF\conf\server.ver
That will tell you the version of your SysAid.
You can remove the customised frame header page. Please check in the Customise > appearance for a customised HTML entry.
|
|
|
G'Day,
You need to create a MST (Transform) file from the MSI using ORCA. The MSi and MST must then be placed in the group policy for the software installation to work.
See the instructions at http://www.ilient.com/msi.htm
|
|
|
G'Day,
You find the current release and license type in the top right hand corner of the page when you are logged into SysAid.
|
|
|
G'Day,
You can firstly create an administrator group in Sysaid and place all the relevant admins in the group. You can then assign, where applicable, all new SR's to the specific admin and the admin group using the routing rules. The person working on the SR will get updates as well as the group.
Send me an email or a pm if you would like to discuss the options further.
|
|
|
G'Day,
Firstly, there is nothing wrong with using a consultant, but make sure you check their credentials.
I not so sure that the consultant owns the code and you can make changes yourself.
|
|
|
G'Day,
Here is an example of the number retrieved by the agent related to the hard drive.
WDC WD7500BPKT-75PK4T0
Looking at the information I find searching for this number in Google indicates that it is the model number and not the serial number.
|
|
|
G'Day,
You can use a service account created for the purpose, but you must remember that this account must have local administrator privileges on the devices/PC's you are deploying to.
|
|
|
G'Day Jacen,
This is possible in SysAid. You can create admin groups is SysAid, make administrators memebers of the groups.
All the members in the group will get a notification when a SR is assigned to their group.
|
|
|
