ProjectWise username change

Sean,

 Ian is correct, it is possible to turn non-Windows PW users into Windows users and then to enable synchronization using PW User Synchronization Services.  You would rename the user to match the Windows user name, add the Domain information and then switch over to Windows-Synchronized as the user type. This capability I believe was added during the 8.9.4.x releases.

HTH,

John

Dear Sean,

 If I am not mistaken you could rename your existing "project wise" users to there new active directory names then add the synchronised users from the active driectory. (I have not tested this)

 I have done this with active directory groups and projectwise groups and it worked ok. Since I have already used the groups in many security settings on folders I did not want to delate all these rights and then recreate then with a new name.

It seam project iwse just looks for a name match (for uses there are some additional settings like domain etc)

Best Regards,

Ian Emery

Sean,

Glad to hear things are okay.

 If I can ask, what PW version are you running?

John

I did change the working directory and the users are now able to check out files.

 I left the 3 letter designation for users in ProjectWise and did not rename them, I created an AD group and sychronized the users in the group with ProjectWise but left the working directory alone which caused the problem.  The post by John makes sense and I had a feeling the original user was somehow linked in the database with the files but did not know where.  I now have 2 logins for each user in PW and that is ok since we do not have a lot of users yet.

 I appreciate the responses and thanks for helping.

To elaborate on John's note...

When you say you switched from using ProjectWise logical accounts to AD accounts with SSO, exactly how did you go about it?

1) Did you modify each user in PW such that the type was set to Windows, or did you just abandon those accounts, and switch over to AD accounts?

2) If you modified the PW accounts, which type did you set them to; "Windows", or "Windows Synchronized"?

3) And lastly, what is you configuration for Working Directory? Are you using the same for everyone (like c:\pw-wrkdir), or something that is user specific like c:\pw-wrkdir\user_name ?

Thanks,

Gary

Let me assume for a moment that you have created new user accounts for use with AD and SSO rather then modifying the existing three letter usernames.

 This means that you likely still have entries in the DMS_CHKL table that relate to files in the working directory for the three letter usernames.   This table records the file, node, working dir path and username for all files in working directories. 

Two different users can not copy files out to the same combination of  file, node and working dir path. This is to prevent accidental overwriting of files and other potential data "confusion".

So you can address this a couple of ways:

1. Change the working dir for the new AD users(like you already said works)

2. Remove the DMS_CHKL table entries for the users that are no longer used.

HTH,

John

Sean,

I have not seen this before, so if you do create a new working dirctory for a user that is now "synched" are they able to check out a file correctly?

Stephen,

Has anyone ran into an issue where you implemented a none SSO username to log into PW and then switched over to SSO and had users not able to check/open files from PW that they could previously open?

 All the PW users had a 3 letter username with password and we implemented Active Directory and switched to SSO for PW.  I have tried to purge all projects but that did not work and I even tried to delete the working folder and have PW recreate it (made sure all files were updated to server first of course) but did not work.  Should I just point everyone to a new working folder location or is there another fix?

TIA

Sean