phone manager 3.2 userid

[srv1strat]

just installed ip office v3.2.53 with phone manager 3.2.28
phone manager profiles are saved to my documents\avaya\ip 400\phonemanager\profiles\extn
the file that appears to point to the profile location is my documents\avaya\ip 400\ phonemanager\profiles\userid.ini

my problem is.
on the clients network all users share the same networked "my documents" so each time a user logs on to phonemanager the userid file is set to the details of the last person to setup their phonemanager. i can redirect the profile itself to a different location but can't find an option to locate the userid.ini file anywhere but my documents.

anyone have any idea if it is possible to change the location of the userid.ini?

thanks

 

[aarenot]

what happens if you install phone manager when the work station is not connected to the network.

 

[dencom2]

Hi,

In that shared folder on the server make new folders with there ext number.
When they opend there PM save this profile to there folder.
When you open it the next time it will auto open the right one.

 

[srv1strat]

aarenot
if not conected to the network the userid.ini file is created in the default location my docs\avaya\ip 400\profiles
this is expected. when i log onto the network my docs is saved to the shared network location & the userid.ini is overwritten with whatever user details i've logged on as. the problem is that all users are sharing a common my docs folder on the server. i need to redirect phonemanager to look for the userid.ini file in a different location than my docs.

dencom2
the individual profile folders are getting created in the shared folder automatically when the user logs into phonemanager but the userid.ini file is saved in the root folder (my docs\avaya\ip 400\profiles) of the shared folder & is therefore common to all users.

 

[aarenot]

does it do this if you do not set up a home ext id.

 

[intrigrant]

You cannot start a PhoneManager on a user not logged in unless you select a station ID during the login of phonemanager.

 

[srv1strat]

sorry aarenot i don't understand the question. where / how do i set up a home ext id?

intrigrant
i'm starting to look a bit slow but i'm not sure i understand what point you are making.

thinking about the problem some more. is it possible to create individually named userid.ini files for each user rather than changethe location of the userid.ini file & have phonemanager look for those individually named ini files?

 

[intrigrant]

Sorry, this answer was for a different thread.

I presume users are logging on into a domain with a domain controller. User rights are then given by the domaincontroller and on the domaincontroller you can create logon and logon scripts for the users.
You must create a script when the user log off, rename the userid.ini file to %username%.ini and create a script to rename this file back to userid.ini when he/she logs on again.
You will have for each user a file called %username%.ini with his/her preferences in the shared folder.
If the userrights on these files are only for this user then nothing can go wrong.
I have done this on a Citrix environment for a lot of users were we had a problem with licensing PM Pro.

 

[srv1strat]

intrigrant,

i like the way you think.
i will not be able to test it out until monday but i'll let you know.

 

[srv1strat]

had another thought on this. does the userid.ini file get updated when phonemanager is closed or is it only accessed on startup of phonemanager?
thinking some more about your suggestion intrigrant. if a user closes & reopens phonemanager without logging off / on to the domain the userid.ini file they use will be the userid.ini of the last person to logon to the domain?
i'm thinking i might have to start phone manager with a script to rename the %username%.ini to userid.ini each time phone manager is started? is this possible? am i missing something important?
i'll put it on my list for monday.

 

[intrigrant]

Yes it is possible to create a script to start PM Pro but you cannot run a script when it is closed and yes if PM Pro is closed then the .ini file will be updated.
The scripting construction will fail if a user does not log out of the domain.
If you can find a programmer the he can create a loader for pm pro so that the loader starts PM Pro and the loader will stay active until PM Pro is stopped.