Allanore
asked on
Where does Windows Server 2008 R2 store passwords?
I am running into an issue on a terminal server running windows server 2008 R2 where one of my users is getting prompted that their password is expired when they use a specific function in their great plains application. After changing their password they will get the prompt again and again.
I have recreated their local profile (removed the registry key and renamed their user folder) the issue still occurs. If I log into the server with another domain account they have no issues. This has happend to 2 users so far on this server and the work around has been to recreate the domain account and name it differently.
I have even gone through the registry and removed anything associated with this domain accounts SID. No luck.
Is there some place that windows server 2008 R2 stores passwords for applications that i am not deleting? Or some local password expiration policy?
Or could this just be an issue with the great plains application? I have tested this on our other terminal server that runs 2008 standard and the issue doesn't occur so its specific to this local Win 2008 R2 terminal server.
I have recreated their local profile (removed the registry key and renamed their user folder) the issue still occurs. If I log into the server with another domain account they have no issues. This has happend to 2 users so far on this server and the work around has been to recreate the domain account and name it differently.
I have even gone through the registry and removed anything associated with this domain accounts SID. No luck.
Is there some place that windows server 2008 R2 stores passwords for applications that i am not deleting? Or some local password expiration policy?
Or could this just be an issue with the great plains application? I have tested this on our other terminal server that runs 2008 standard and the issue doesn't occur so its specific to this local Win 2008 R2 terminal server.
ASKER
Its windows server 2008 so i think its called credential manager. I checked there and removed everything in there.
What module of GP are they accessing when they get the prompt? What version of GP? What happens if you run GP under the problem users profile using "RunAs"
ASKER
When they are in the sales section and start processing batch invoices, everytime they save an invoice they get the prompt.
GP is version 10.0
When i Right click on the GP shortcut and Run As another user i do not get the error.
GP is version 10.0
When i Right click on the GP shortcut and Run As another user i do not get the error.
If you log in to the TS server as the problem user ... but log in to GP as a different user?
Also .. log in as a known good user and log in to GP as your problem user.
Also .. log in as a known good user and log in to GP as your problem user.
ASKER
It looks like it doesn't matter if i log in with a working user. No matter what, if I click GP and run as the problem user i will get the password expiration error.
If i log in as the problem user and run as a working user, Great Plains works.
It seems like Great plains is tied somehow to that domain acount. The weird thing is that it is only on one terminal server. The other server with GP installed works fine with no issues.
If i log in as the problem user and run as a working user, Great Plains works.
It seems like Great plains is tied somehow to that domain acount. The weird thing is that it is only on one terminal server. The other server with GP installed works fine with no issues.
So .. are we still at the point where this only happens on the terminal server? Or on all installs for this account?
If on all installs ....
GP 10 you have to use SQl accounts correct? This looks like you are having a GP user issue tied to SQL. If you copy your problem GP user on to a test account and try that .. does replicate the issue?
If still just on TS ... then I would be looking at the ODBC connection (permissions? 32 vs 64 bit? Multiple connections etc)
If on all installs ....
GP 10 you have to use SQl accounts correct? This looks like you are having a GP user issue tied to SQL. If you copy your problem GP user on to a test account and try that .. does replicate the issue?
If still just on TS ... then I would be looking at the ODBC connection (permissions? 32 vs 64 bit? Multiple connections etc)
ASKER
This issue only happens on the terminal server. Can it be an ODBC permissions issue if they can login to GP and do things still? They just get the expired password prompt when saving invoices.
ASKER
I took a look at Microsoft Dyanmics GP with process explorer. Looks like when you open this program as another user, it will create their user folder in C:\users| and then dump a bunch of information into their user folder.
I am wondering if the great plains install is corrupt and is corrupting certain cached data on the invoicing portal of the application.
I am wondering if the great plains install is corrupt and is corrupting certain cached data on the invoicing portal of the application.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The weird thing, if I rename their domain user account everything works fine.
I will try removing all their printers on the TS and see if this makes a difference.
I will try removing all their printers on the TS and see if this makes a difference.
http://technet.microsoft.com/en-us/library/cc778542%28v=ws.10%29.aspx