Deployment Solution

 View Only

Changing AClient Settings for All Active Clients 

Jan 06, 2009 02:55 PM

Creating new default setting for the AClient and resetting all the clients to the new default

First let's change the default settings. Open a Deployment console and go to Tools - Options and the Agent Settings Tab. Select the Change Default Settings button. This looks just like the agent settings for the client. Modify it to fit your needs.

Changing the settings for current clients

In the Deployment console go to Tools - Remote Agent Installer. You can either specify a Password later or just use one. The username and password does not have to be correct because this information is not needed for what we are doing. Click Next.

This is where we want to change the agent settings to match our Defaults. Click Change Settings and change the settings to what the default settings were set to. (I am not sure why this does not just pull the default settings and use them.)

Once you have the settings set the way you want them click OK. Click Next twice. This is where normally you would select a computer you want to install the AClient on. Click Add and type in a bogus computer name. For some reason I like to use the name "testmonkey". Mainly because I know there are no computers with this name.

Do not click Finish, click Export. Leave the default file name because it does not matter and will be deleted next and leave the default location in the eXpress Share.

Click Save, OK and Cancel.

Now browse to the eXpress Share unless you saved it in a different location besides the default. Delete the client.rci file. Rename clients_testmonkey.inp to a more intuitive name like Agent_Settings.inp. Obviously testmonkey will be whichever name you used for the computer you put in to install the agent on. I suggest leaving this inp file in the eXpress Share as it will be easier to access.

Now go back to the Deployment Console and create a new job. In this new job add a copy file to task. The source path will be ".\AClient_Settings.inp" and the destination path will be "settings:aclient.inp". Make sure it is exactly like that, in all lowercase without the quotes. What this does is it installs it into the registry, hence the reason it does not have any drive location. Assign this to all the computers or a group of computers you want to change the default settings on, and use batches.

Even though the file size is only 2 kb, it would be a good idea not to run it on all the computers at once, unless you have less than 50 computers. The way I normally do batches is in batches of 15 every 5 minutes. The job will normally take 10 seconds to run, so this gives a large lead time between computers.

I recommend testing this on a few computers first that do not have the default settings and are currently connected to the Deployment Console. Run the job on them and verify the settings took by right clicking on the computer, select Change Agent Settings-Production Agent.

It should only take a few seconds for the settings to take, so once the job finishes, by the time you get to the Production Agent settings they should already be set. After you have verified that the job is working correctly you can either assign it to all computers, or to the group of computers that need the agent settings changed.

Statistics
0 Favorited
0 Views
1 Files
0 Shares
0 Downloads
Attachment(s)
jpg file
7451.jpg   3 KB   1 version
Uploaded - Apr 10, 2020

Tags and Keywords

Related Entries and Links

No Related Resource entered.