| Author |
Message |
|
|
Thank you everyone for your support.
As Saar mentioned, My new workplace is with a company that use SysAid, so you will see me around in the community from time to time.
|
|
|
Hey BigKev,
I'm not exactly sure why it's happening, please contact our support team at helpdesk@sysaid.com and we will be glad to further investigate the issue.
Regards.
Haim
|
|
|
Hello SysAiders,
After a long time as a part of the SysAid family, it's time for me to move on.
I had a great time working in this amazing company and in particular the support department and with you, the community members.
I've been the community admin since it was first founded two years ago, and it grew so much since then!
According to the latest SysAid annual survey, the community is the first place most of you come to ask questions and look for info on SysAid, and it's all thanks to all the users who come to discuss and share their knowledge with other SysAid admins.
Working with the community was always a treat for me, a way to talk with SysAid users in a more casual manner and getting to know some of you more personally.
I'll be still around in the upcoming days to say goodbye and ease in the new community admins.
See Ya 
Haim
|
|
|
Hey Abdou.
When deploying SysAid as a part of a ghost, you must do some preparations before taking the ghost image.
After installing the agent, stop the agent service, then go to \HKEY_LOCAL_MACHINE\Software\Ilient\Agent registry key\
Change the value of "FirstTime" to "Y" and delete the "MachineID value".
Once those conditions are met, you can take the image and the agent will no longer report all to the same asset.
Regards.
Haim
|
|
|
lwyatt,
If both admins are trying to update the same request at the same time, then the error will come up as intended.
To avoid the issue from happening, You can instruct your admins to assign the requests to them self when they are working on it so other admins will not see it in their queue.
Regards.
|
|
|
Hey Dag.
Database migrations are preformed by our support team as part of the support services we provide.
If you are using the full edition of SysAid and your support agreement with SysAid is valid, you can contact our support team at helpdesk@sysaid.com and we will be glad to provide you with additional instrcutions.
Regards.
Haim
|
|
|
SLR,
This option (to use the attachments field in the general details tab) is a workaround for attachments you need available after the action item is closed.
We have moved your feedback to SysAid's product manager so this can be changed for future requests.
Regards.
Haim
|
|
|
Hello henrycow,
Please contact our support team at helpdesk@sysaid.com so we can further investigate the issue and assist you resolving it.
Regards.
Haim
|
|
|
MethosFrost,
This was indeed resolved in 6.5, if you are still having this issue, please contact our support at helpdesk@sysaid.com so we can further assist you.
Regards.
Haim
|
|
|
lwyatt,
This is a good point.. never tried to schedule report with Java applets and run it before.
I've forwarded the issue to our senior support, they will investigate the issue and will keep you updated through your SR.
Regards.
Haim
|
|
|
motc7,
The 6.5 agent should work correctly on Windows 7.
In order for us to further investigate the issue, please contact our support team at helpdesk@sysaid.com and we will be glad to further investigate the issue.
regards.
Haim
|
|
|
hmm... they are working just find for me... maybe you don't have java plugin for your browser?
Regards.
Haim
|
|
|
Hey Andy.
What you want to do cannot be made in just one IF statement since there is a logical problem with this request.
The correct syntax to be used is:
#if(${IsNewSr}==false || ${isClosedSR}==false)
#end
The issue with that specific request is that unless the ticket is new AND closed at the same time, every SR will always be either "not new" or "not closed" (even a new SR is not closed so this rule will trigger or a closed request which is also not new, and the statement will run).
To resolve it, just replace the || (or) with && (and)
#if(${IsNewSr}==false && ${isClosedSR}==false)
#end
Regards.
Haim
|
|
|
Under Preferences > end user portal
Look for "Asset user determined by" and change the drop down to "Login" and save the changes.
regards.
Haim
|
|
|
Matth,
At the moment, there is no option to limit the access when using the desktop shortcut, since opening requests is the agent's purpose.
The way I offered you is a workaround , and the only current way to prevent users from accessing the end user portal when using the desktop shortcut.
Regards.
Haim
|
|
|
