Avaya One-X User Profile Issue

[mcclaj]

The issue we are running into is that Avaya One-X Communicator for its extension/server information is profile specific. For every user who is logged into those PC’s already we are having to copy the configuration files over to each and every profile manually for this to work correctly; which is just not a feasible solution since there are xxx number of computers with multiple users who log into these systems on a given day.

I tried to copy over the configuration files over to the default profile under the location C:\Users\Default Profile\Appdata\Roaming\ Avaya\Avaya one-X Communicator, but if a new user logs into that PC the information does not get migrated to their windows profile location, and just a default generic configuration file is created when they try to open up the Avaya One-X Communicator client. Any suggestions to get this working will be greatly appreciated. Thank You.

[druddehe]

The issue we are running into is that Avaya One-X Communicator for its extension/server information is profile specific. For every user who is logged into those PC’s already we are having to copy the configuration files over to each and every profile manually for this to work correctly; which is just not a feasible solution since there are xxx number of computers with multiple users who log into these systems on a given day.

I tried to copy over the configuration files over to the default profile under the location C:\Users\Default Profile\Appdata\Roaming\ Avaya\Avaya one-X Communicator, but if a new user logs into that PC the information does not get migrated to their windows profile location, and just a default generic configuration file is created when they try to open up the Avaya One-X Communicator client. Any suggestions to get this working will be greatly appreciated. Thank You.

Hi, we have the same problem. Sometimes I even notice that users lose their settings. I then have to complete this process.

We avoided the problem using our deployment software. We dump the files using a script in the correct location like you mentioned.This has to be done via a portal on the pc. the user can then login.

It's not ideal..It would have been great if the server settings & dial plan were system settings, instead of user settings

[sumit007]

Avaya One-x User profile issue

Hi Mcclaj,
I have a working solution for it. In my case customers requirement is Need to freeze the extension and password so that agent could not change the ext. by themselves.
So i modify a XML file according to requirement and put it in a Admin drive of PC locally and make a batch file for copy. As there is a free seating environment of agent any agent can sit anywhere so when an agent login with their credentials the batch file run at startup and copy the XML to agents profile. By doing this agent only put their agent id and password and reset of thing will greyed out i.e. Agent can't make a change.

Although Modifying XML and doing above stuff is not recommended by Avaya as modification of XML leads you to corruption of One-x Agent.

Please Make sure that the changes you are doing ; you must know that what are you doing.