I am running Avaya Agent for Desktop and need to deploy it to around 50 users at once. Any easy way to do this and keep all my auth codes and settings to the rest of the users??
If you have a software installation group that builds software installations, they should be able to build a package that installs the one-x Agent software, then when it's done installing, copy all the directories and files from the build that you did into the user's C:\users\%username%\appdata\roaming\avaya\one-x agent\2.5 directory.
Please note: when you create a profile it will save it under the C:\users\%username%\appdata\roaming\avaya\one-x agent\2.5\Profiles directory By default, the application names the profile with the name: default.
If you plan on having different configurations (profiles) for different groups, you should rename the directory default to a useful name like Customer Service or Sales.
You can create multiple profiles and have them all installed, but the user will have to select which profile they want to use from a pull down menu when they launch one-x Agent for the first time. After that it should be selected already and they just have to click OK to accept the profile that is displayed.
However, inevitably, someone will change the profile just to see what the other profile will do and this can cause help desk calls that aren't necessary. At companies I have worked for, we would have only the profile they would use installed, that way they couldn't screw it up. We would name the software installation specific to the group, such as: one-X Agent - Member Services or one-X Agent Provider Services. While this should prevent the wrong package from being installed, inevitably, someone from the help desk would install the wrong version, so there are pluses and minuses for both.
Also, one final note, unless you go in and change the xml settings files and change settings from true to false (different ways to do this, changing an entire setting group to ReadOnly='true' or individual settings to 'false') users will be able to go into the settings of the application and change things. Of course, there are pros and cons to this as well. If you lock it down, the help desk can't help the user and make changes to the settings unless they know how to edit the settings file. This isn't something I would rely on the help desk to be able to do. Also, the user can watch what the help desk is doing and access the files and screw around with it as well. You can't lock down the 2.5 or profile folder either, the application needs to be able to write to it under the user's profile.
Hopefully this helps.
- Stinney
“The man who asks a question is a fool for a minute, the man who does not ask is a fool for life.” - Confucius
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.