Latest posts for the topic "Deploying"

Deploying

krob0328 — GMT

Is there a way to manually install the SR program to local computers without deploying them from the main computer?

Keith

Re:Deploying

simplydobermans — GMT

there are three ways that i know of to install sysaid agent to a computer
1) deploy sysaid, administration tool
2) login to sysaid with administrator account, from computer to install on, and go to and sysaid agent link
3) create a link for an email to send to user http://sysaid-server:port/download/FILE-needed

select the file needed that you would need to for your install,
SysAidAgent.exe
SysAidAgent.msi
SysAidAgentUpdate.exe
SysAidTools.exe
sysaid-linux.tar.gz

don't forget to give them your server info from the download page, it is need during installation

Your server URL

Your account

Serial key for your account

Re:Deploying

krob0328 — GMT

If I manually do it this way will I be able to see these users on my sysaid on my computer?

Deploying

Haim — GMT

Hey there.

The agent function the same way with all deployment methods, so there is no difference in the performance or information being sent between remote deployment or local deployment.

Best regards.
Haim

Re:Deploying

IT Manager — GMT

I just put together a script and used the GPO to deploy it to all my pc-s...

Deploying

maqsa — GMT

Hello Keith,

Goto

Documentation > Guide 3: Getting Started Guide > Page 20

(B. Automatic deployment with a login script for Windows)

And you can use the "SysAidAgent.exe" either by a wizard (wich will prompt you the config details) or creating a script with the configuration you decide...

Re:Deploying

CASISA — GMT

Hi all, i was trying to add this to the log in script but i keep gettin error 800A0400 on the first "\"

y:[b][color=red]\[/color][/b]sysaid\sysaidagent.exe /VERYSILENT /URL http://########## /account ########## /serial ################ /install once /AllowRegister N /AllowRemoteControl Y /SubmitSRShortcut SysAid /HotKey Alt + F11 /Interval 30 /ConfirmRC N /RandomMachineID N /AllowSubmitSR N

Does any1 knows what im doing wrong??

Thanks in advance, and sry for my english.

EDIT: Solved adding a "wshshell.run " before the whole sentence

[color=red]EDIT 2[/color]: I'm currently having problem with the shortcut, it doesn't create it at all, any idea?

Deploying

CASISA — GMT

Besides that, u can't install it if the end user is not an administrator, i did some runas etc... but im having to many problems to solve it, theres a SIMPLY way to install this stuff on the whole lan without going pc by pc?? the deploy system doesn't work for me, in some end pc's i just get "can't connect to computer bla bla"

Can any sysaid supporter help this out please??

Deploying

Haim — GMT

[quote=CASISA]Besides that, u can't install it if the end user is not an administrator, i did some runas etc... but im having to many problems to solve it, theres a SIMPLY way to install this stuff on the whole lan without going pc by pc?? the deploy system doesn't work for me, in some end pc's i just get "can't connect to computer bla bla"

Can any sysaid supporter help this out please??
[/quote]

What about group policy? is this possible in your network?
If so, please follow the below instructions:

The SysAidAgent.msi file can be downloaded at http://helpdesk.ilient.com/CustomPage.jsp?pageName=download.html&fileName=SysAidAgent.msi&EndUserLink. You can deploy the SysAid agent using the MSI package in two ways.

1. Using a login script with the following syntax:

msiexec /q /I SysAidAgent.msi SERVERURL="http://serverhost:8080" ACCOUNT=account SERIAL=serial

Replace account and serial with the appropriate information as it appears on the Downloads page of your SysAid.

Other optional parameters (with the default values) are as follows:

ALLOWREMOTECONTROL (default value="Y")
ALLOWSUBMITSR (default value="Y")
CONFIRMRC (default value="Y")
FIRSTTIME (default value="Y")
HOTKEY (default value="122")
INTERVAL (default value="30")
LOGLEVEL (default value="0")
PROXYPORT (default value="0")
PROXYSERVER (default value="none")
RANDOMMACHINEID (default value="N")
SUBMITSRSHORTCUT (default value="SysAid")

2. Using a group policy.

When you deploy the agent using a group policy, you need to edit the MSI package to include your unique parameters. You can edit the MSI package using Microsoft Orca (available at http://astebner.sts.winisp.net/Tools/Orca.zip).

a) Open SysAidAgent.msi using Orca and click on “Transform” -> “New Transform”.

b) Click on “Property” on the Table pane, and you should find the same parameters described above.

c) You must modify at least the ACCOUNT, SERIAL and SERVERURL parameters, and you can also modify the optional parameters.

d) When you finish, click on “Transform” -> “Generate Transform” and save the file as SysAidAgent.mst.

This MST file will be good for future versions as well, so make sure to keep a copy of it. Now you can use the MSI and MST files to publish the agent using a group policy.

best regards.
Haim

Re:Deploying

CASISA — GMT

Haim, 1st of all, many thanks to you, and yes, i can install it using group policy, i was just trying to figure out how to set the parameters...

You are the one!!!!!

Thanks alot! ill try this today!!

Really appreciated!

Re:Deploying

stheobald — GMT

Can you advise on how (if possible) to modify this script to delete all prior version installs of SysAid before the latest one is installed?

Re:Deploying

techguy — GMT

[quote=stheobald]Can you advise on how (if possible) to modify this script to delete all prior version installs of SysAid before the latest one is installed?[/quote]

Hi Stheobald, I am very sorry it appears that not one of your 4 postings to the forum ever received replies, I hope that you haven't given up on the community. Again this posting will hopefully attract a reply

Deploying

Haim — GMT

stheobald,
There is no need to remove previous version of the agent before installing a new one, as the agent will simply overwrite the previous version.

Best regards.
Haim

Re:Deploying

Chucky — GMT

Hello all,

Apologies for posting into an older topic but it seems to cover my question.

We're about to start our deployment of the Agent to our estate using Group Policy. I've tweaked the settings that I need to but it's been decided to change the shortcut key from F11 to CTRL+F11. In the transform file and in the agent Deployment PDF it states that F11 equals the value 122. How do I find out what value CTRL+F11 would equate to in order to enter this as the HOTKEY value within the transform?

Cheers.

Deploying

Haim — GMT

In order to set the HotKey value in the login script, you will need to find the decimal value for the HotKey. To find the value you need to put after the /hotkey switch, please follow the steps below:

On the machine with the administrator tool installed:

1. Open the deployment tool, go to Edit -> Settings.
2. Change the HotKey to what you want.
3. Deploy to one client machine.

On the client machine:

4. Confirm that the HotKey works.
5. Open regedit and browse to [HKEY_LOCAL_MACHINE\SOFTWARE\Ilient\Agent].
6. Find the DWORD "HotKey" and open it.
7. Make sure that you are viewing the decimal value, and not the hexadecimal value.

This decimal value is what you need to put after the /hotkey switch in the login script. It will set the value to what you specified in step 2.

Re:Deploying

Chucky — GMT

Thanks for the quick reply but you've misunderstood what I'm trying to do. I'm not using a login script - I'm wanting to know the value to put into the Transform file. Is the process the same to determine the assigned hotkey - [HKEY_LOCAL_MACHINE\SOFTWARE\Ilient\Agent]?

I have changed the hotkey to CTRL-F11 on my user account but in the above registry key it still says 122 - which it can't be as that is F11 on its own.

Any other ideas?

Many thanks.

Deploying

Haim — GMT

Hello Chucky.

The value for CTRL+F11 is 137, i checked it by doing the same procedure as i provided in the previous post.

Best regards.
Haim

Re:Deploying

Chucky — GMT

Thanks Haim,

I managed to do the same yesterday but for some reason on our system the CTRL+F11 short cut equates to 634 decimal. It does work and it's been deployed to machines so maybe there are two values?

Thanks for your assistance with this though.

C.

Deploying

Haim — GMT

Chucky

Sorry for misleading you, the correct value is indeed 634 (i mistakenly deployed with a different hot key)

Please try to restart that machine after the re-deployment, in some cases it's required so the hotkey change will reflect.

Best regards.
Haim

Re:Deploying

tootntotum — GMT

A quick add to this discussion:

While haim's method is definitely doable, there is an easier way to get the combination you want.

Locate the values you want to use in the microsoft virtual key codes table. Available here [url]http://bit.ly/d9I9eL[/url]

OPen calculator in scientific mode and select the HEX radial.
enter your first hex value
+
enter your second value
=
the key code needed.

If you dounbt the method, open calculator, set dec radial and enter 122
then switch to hex radial. the value will match microsofts table.

CTRl + F11 = 8B Hex and 139 Dec.

Re:Deploying

itayH — GMT

Hi tootntotum,

Excellent tip
Thanks.