I'd rather not have my users trying to change their password using this option, thinking they are changing theri Windows (AD) password.
Educate them instead, there is probably no way to disable that option. But how would they change their password from defaults, on their first login?
I wasn't really thinking of the initial logon so much as the normal password expiration pwd changes. We change our Windows passwords every 90 days and have several SSO solutions running (Lotus Notes, homegrown app for Intranet, soon PBA, etc). We like the Windows password change to drive everything for SSO. I know there will be some who think they can click the box at PBA logon and they are changing their Windows password.
Education is always good, but there's always someone who doesn't read their mail, blah, blah...
Helpdesks hate stuff like this.Message was edited by: mining on 2/2/10 3:17:19 PM CST
That's part of SSO integration evaluation. Making sure that there will be only one login prompt (from a single product) that will silently drive all other logins.
Always, under all circumstances. Then think about users that need to use multiple accounts and freely choose between them, at any time. And finally about users that most of the time act as members of the first group and only sometimes as members of second group. Now you need to manage that mix.That is reality...
Simon, does that hide the Change Password check box? To echo peter's question, how does this work with SSO and syncing Wondows password to EEPC? What if initial password is set to default and they are asked to change on first login?
You can hide this box in your theme.
In the GRAPHICS.INI file, find all the references to ChangePwdButton.Rect (I think there's one for each resolution you have). The value of this parameter will be four numbers separated by commas, ie: ChangePwdButton.Rect=267,269,399,289. These values are x1, y1, x2, y2, where x1 and y1 is the starting point on the page, and x2 and y2 are the end points. Well, if you set them to the same, then you're basically drawing them into a pixel that is 0x0, virtually making in invisible.
For example, if it's 267,269,399,289, change it to 267,269,267,269 (making x1=x2, y1=y2). You could probably also just make them 0,0,0,0 but I haven't tested it out yet.
If you need a more detailed walk through, I planned on blogging about it soon. This is probably not supported by McAfee any more than custom themes are (are they? who knows...) but it works none the less.
Yep. I tested this out and it works.
Editing the ini file looks like good workaround. At least for appearances.