SysAid Tip - Upgrading the SysAid Agent without Re-Deployment
 
Author
Message
Eli
SysAid Customer Relations
61
 
Hi MichelleU,

Can you please provide us with a screenshot of your settings in the SysAid Deployment Tool. To further assist you with this issue.

Looking forward to your response.

Eli
SysAider
10
 
Haim wrote:A Tip from Sarah Lahav, the Head of Ilient Support Team

To save you time and efforts, from version 5.0 and up, you can easily upgrade the SysAid agent without having to re-deploy SysAid to your network.

1.Go to Preferences->Asset Setting-> Asset Update
2. From the Command dropdown menu, choose Upgrade client version.
3. Choose which asset or asset group to run the upgrade on.
4. Set the date for the next upgrade.
5. Choose how often to repeat the automatic upgrade.
6. Click the Add button, or the Run Now button to upgrade immediately.

For instance, if you have SysAid 5.0.03 version, your client will be automatically upgraded to SysAid 5.0.06, even if the workstation is off.

I've followed these steps, and the individual agents for my machines have not updated. Does the end user need administrative rights in order for the agent to update?
SysAid Wiz
2449
 
Hello SCLARK.

Although the end user does not need to be an administrator on his machine, however, the user need to have permissions to install software on that machine.

Best regards.
Haim
Pushing IT forward
SysAider
10
 
Thank you. We do not permit our end users to install software, so this is not an option for us. Looks like we'll have to do it manually.
SysAid Wiz
2449
 
Hello SCLARK.

You can also preform the upgrade process using the deployment tool so you wouldn't have to install the agent on each and every machine.

Best regards.
Haim
Pushing IT forward
SysAider
40
 
I've had this feature on for quite sometime and haven't seen any clients update.

Does the sysaid serivce have to be running as a domain admin or similar?
SysAid Wiz
2449
 
dpfalk,

The server does not need to be installed on a domain controller for this process to run.

It is possible that there is a connection issue between the server and the agent which prevent them from being updated, in that case, your assets will also wont be updated.

You can check it by looking in the "activity log" tab of your assets to see when they were last updated.
If they are not being updated regularly, there is probably a connection issue and you should open a service request with our support by sending an email to helpdesk@sysaid.com so we can further investigate the issue.

Best regards.
Haim
Pushing IT forward
SysAider
7
 
MichelleU wrote:I know this is an old thread, but I am having the smae problem. The F11 key seems to always be mapped, even if I change the shortcut key to NONE and redeploy the agent via the Deploy tool.
I've done more testing and if I change the shortcut key to anything else (for example CTRL+ALT+h) and redeploy the agent, the F11 key and ALSO the combo of CTRL+ALT+h bring up the web page.
I need to stop this.
Does anyone have the answer.


I'm having the same issues as Michelle was. I originally deployed the SysAid agent using default settings (F11 hotkey) but realized that was conflicting with other pieces of software on our network. I then used the Deployment tool to remove sysaid from all machines. I then changed the settings in my deployment tool to use Shift+Z for hotkey. Now when I deploy it seems as though F11 still works, as well as Shift+Z. Is this a registry setting that does not get removed when uninstalling SysAid?
SysAid Wiz
2449
 
Hello jhelland.

The previous hotkey should have been removed when un-deploying SysAid.
Please check if you have two desktop shortcuts for SysAid on your desktop, perhaps the old shortcut was not removed.

Also, please try to restart the machine since changing the hotkey require a restart in some cases

Best regards.
Haim
Pushing IT forward
Super SysAider
85
 
MichelleU wrote:I know this is an old thread, but I am having the smae problem. The F11 key seems to always be mapped, even if I change the shortcut key to NONE and redeploy the agent via the Deploy tool.
I've done more testing and if I change the shortcut key to anything else (for example CTRL+ALT+h) and redeploy the agent, the F11 key and ALSO the combo of CTRL+ALT+h bring up the web page.
I need to stop this.
Does anyone have the answer.


I had a similar problems ones, but its quiet simple to fix. This was because there was TWO shortcuts on the desktop for the SysAid agent. So try and check if all SysAid shortcuts are deleted before redeploying...

EDIT: Missed the 2 page! didn't see Haim already wrote this Doh

This message was edited 2 times. Last update was at Jul. 06, 2009 06:10 AM

SysAider
5
 
So, what credentials is SysAid using when it does the "upgrade Client version" task? Do you have to log into SysAid as the SysAid admin, and what permissions would you need on the workstation (presuming the same as when you installed the agent to begin with?

EDIT, jumped into the thread halfway down, didn't see the permissions discussion.

This message was edited 1 time. Last update was at Oct. 01, 2009 07:01 PM

SysAid Wiz
2449
 
Pancho,

Your users should have at least the option to run and install software, in companies where it is not permitted, it is recommended not to use the auto upgrade to avoid any error messages poping up to your users.

Regards.
Haim
Pushing IT forward
SysAider
38
 
I have un-deployed the agent that was installed using F11 hotkey. I re-deployed using CTRL+F11, and F11 still works as well as CTRL+F11. I checked HKLM\Software\Ilient\Agent and only the CTRL+F11 code is listed. What to do next?
--------------------------
SysAid n00b
SysAid Wiz
2449
 
jsposato,

it usually require a restart to the machine to apply the hotkey changes.

Regards.
Haim
Pushing IT forward
SysAider
38
 
Here's what I've noticed. If you un-deploy re-deploy the agent with different access keys, BOTH will be active until a reboot. After reboot, my first accesskey no longer works. It would seem logical if you think about it. The accesskey is registered when the agent service starts (maybe restarting the agent would also work?) and probably can't de-register the old access key until there are no locks on system fiels, etc.

This has worked in my environment.


EDIT: Sorry Haim, didn't see your reply. It would seem that a restart of the computer would be required. Perhaps this should be added to the documentation?

This message was edited 1 time. Last update was at Oct. 27, 2009 08:31 AM

--------------------------
SysAid n00b