I was recently talking shop with another consultant that has a customer who's Dynamics GP password was valid when they logged in but expired after causing a batch posting interruption. Has this ever happened to you?
He submitted a support request to Microsoft to explain this issue and seek out a resolution. The response he received was:
As for ways to overcome the password becoming invalid mid-day, there are two options:
1. Keep the password synchronized (time-wise) with the windows password and use the windows password reminder as a GP password reminder
2. Use the GP Password Expiration Notification utility, freely available from the blog link below
http://mbsguru.blogspot.com/p/dynamics-gp-password-expiration-notice.html
Microsoft recommended the GP Password Expiration Notification utility with qualification, of course, that it is not something Microsoft created or provides support for. Even so, it's nice to see that this utility is serving the community well by helping to solve and prevent common problems.
If you haven't downloaded it already you should before you have to recover from a batch posting interruption because your password has expired.
Showing posts with label Password Expiration Prompt. Show all posts
Showing posts with label Password Expiration Prompt. Show all posts
20 August, 2010
Dynamics GP Password Expiration Notice
Last year, I posted a VST customization I thought I would sell to a client that would give users advanced notice that their GP Password was about to expire. That version was locked to only work in Fabrikam. Since that sale never materialized, I have unlocked it and am distributing it for free, "AS IS" with no warranties. You can download the unlocked version here! Just drop it in the GP\Addins directory. I have only tested this on version 10 of Dynamics GP.
The Dynamics GP Blogster has talked about why system administrators are not taking advantage of the password policy enforcement feature in Dynamics GP. If you or your customers are growing frustrated that your user's passwords are expiring without notice and IT is having to reset them frequently you might like this mod. It works like this...
For compatibility with SQL2005 I decided to store a Maximum Password Age with the Number of Days before expiration to begin notifying users that their passwords would expire. I could have integrated it with windows security policy or active directory to get these values directly but I didn't do that here. With SQL2008 you would only need to store the Number of Days before expiration to start notifying because you can query the DaysUntilExpiration LoginProperty in SQL2008. I wrote this work both ways depending on which version of SQL was running.
To capture the fields I needed I created a new Dynamics GP form in Visual Studio Tools that could be accessed from the Additionals Menu in Company Setup. I chose to store this data in the DUOS so that I didn't have to deal with creating any new tables. Therefore, you can setup each company to behave differently which could be a blessing or a curse.
Next, I added a NewHandler in VST on the SwitchCompanyCloseAfterOriginal event to compare the age of the users password to the maximum password age and days before notification captured in the PWExpirationNotice VST Form. If the user is due to be notified that their password would expire soon I present them with a message box...
... and then the User Password Setup window in which they could change their password on their way into the GP Company.
The prompt and User Password Setup window are only presented on the first login for a session. So, the users won't be nagged every time they change companies without shutting down GP first. They also aren't forced to change their password but rather given the option to do so easily at a convenient time so that they don't get locked out later.
The Dynamics GP Blogster has talked about why system administrators are not taking advantage of the password policy enforcement feature in Dynamics GP. If you or your customers are growing frustrated that your user's passwords are expiring without notice and IT is having to reset them frequently you might like this mod. It works like this...
For compatibility with SQL2005 I decided to store a Maximum Password Age with the Number of Days before expiration to begin notifying users that their passwords would expire. I could have integrated it with windows security policy or active directory to get these values directly but I didn't do that here. With SQL2008 you would only need to store the Number of Days before expiration to start notifying because you can query the DaysUntilExpiration LoginProperty in SQL2008. I wrote this work both ways depending on which version of SQL was running.
To capture the fields I needed I created a new Dynamics GP form in Visual Studio Tools that could be accessed from the Additionals Menu in Company Setup. I chose to store this data in the DUOS so that I didn't have to deal with creating any new tables. Therefore, you can setup each company to behave differently which could be a blessing or a curse.
Next, I added a NewHandler in VST on the SwitchCompanyCloseAfterOriginal event to compare the age of the users password to the maximum password age and days before notification captured in the PWExpirationNotice VST Form. If the user is due to be notified that their password would expire soon I present them with a message box...
... and then the User Password Setup window in which they could change their password on their way into the GP Company.
The prompt and User Password Setup window are only presented on the first login for a session. So, the users won't be nagged every time they change companies without shutting down GP first. They also aren't forced to change their password but rather given the option to do so easily at a convenient time so that they don't get locked out later.
22 December, 2009
Password Expiration Prompt - Using VST to Notify Users before their Password Expires in Dynamics GP
I was recently asked by another consultant to quote a modification that would give users advanced notice before their GP Password was going to expire. This customer was growing frustrated that their user's passwords were expiring without notice and IT was having to reset them frequently. The typical work around is to change your GP Password when you change your network password but that wasn't good enough in this instance. The customer ended up choosing to go with one of the ISV solutions instead of a custom solution for additional features but I went ahead and finished this in my "spare time" anyway.
To make this work with SQL2005 I had to store a Maximum Password Age and the Number of Days before expiration to begin notifying users that their passwords would expire. I'm sure you could integrate with windows security policy or active directory to get these values directly but I didn't do that here. With SQL2008 you would only need to store the Number of Days before expiration to start notifying because you can query the DaysUntilExpiration LoginProperty in SQL2008. I wrote this work both ways depending on which version of SQL was running.
To capture the fields I needed I created a new Dynamics GP form in Visual Studio Tools that could be accessed from the Additionals Menu in Company Setup. I chose to store this data in the DUOS so that I didn't have to deal with creating any new tables. Therefore, you can setup each company to behave differently which could be a blessing or a curse. Of course, you could change this to store the data in a custom table but it would also be nice if GP had a installation specific DUOS in the DYNAMICS database for this purpose. Hint, hint.
Next, I added a NewHandler in VST on the SwitchCompanyCloseAfterOriginal event to compare the age of the users password to the maximum password age and days before notification captured in the PWExpirationNotice VST Form. If the user is due to be notified that their password would expire soon I present them with a message box...
... and then the User Password Setup window in which they could change their password on their way into the GP Company.
The prompt and User Password Setup window are only presented on the first login for a session. So, the users won't be nagged every time they change companies without shutting down GP first. They also aren't forced to change their password but rather given the option to do so easily at a convenient time so that they don't get locked out later.
I chose VST over Modifier/VBA to ease deployment as much as anything. You can download the .dll for this mod if you want to try it out here. Just drop it in your Addins directory and it will work in Fabrikam.
To make this work with SQL2005 I had to store a Maximum Password Age and the Number of Days before expiration to begin notifying users that their passwords would expire. I'm sure you could integrate with windows security policy or active directory to get these values directly but I didn't do that here. With SQL2008 you would only need to store the Number of Days before expiration to start notifying because you can query the DaysUntilExpiration LoginProperty in SQL2008. I wrote this work both ways depending on which version of SQL was running.
To capture the fields I needed I created a new Dynamics GP form in Visual Studio Tools that could be accessed from the Additionals Menu in Company Setup. I chose to store this data in the DUOS so that I didn't have to deal with creating any new tables. Therefore, you can setup each company to behave differently which could be a blessing or a curse. Of course, you could change this to store the data in a custom table but it would also be nice if GP had a installation specific DUOS in the DYNAMICS database for this purpose. Hint, hint.
Next, I added a NewHandler in VST on the SwitchCompanyCloseAfterOriginal event to compare the age of the users password to the maximum password age and days before notification captured in the PWExpirationNotice VST Form. If the user is due to be notified that their password would expire soon I present them with a message box...
... and then the User Password Setup window in which they could change their password on their way into the GP Company.
The prompt and User Password Setup window are only presented on the first login for a session. So, the users won't be nagged every time they change companies without shutting down GP first. They also aren't forced to change their password but rather given the option to do so easily at a convenient time so that they don't get locked out later.
I chose VST over Modifier/VBA to ease deployment as much as anything. You can download the .dll for this mod if you want to try it out here. Just drop it in your Addins directory and it will work in Fabrikam.
Subscribe to:
Posts (Atom)