Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Thu, 8 May 2008 05:54:04 -0700,    group: microsoft.public.exchange.admin        back       


Password Expiration and notification in OWA 2003   
I have a quick question and I apologize if this is not in the correct 
newsgroup.  If it is not, please let me know where I should put this and I 
will make the correction.

We use Exchange 2003 and the majorioty of our users use OWA 2003 to access 
thier e-mail.  For many of them, this is thier only way of logging in (they 
share computers with other people) and about a year or so ago, they stopped 
getting password expiration notifications and we have a lot of user's 
passwords expiring without them knowing.  

I looked into this and it seems to be an IIS issue.  Accord to kb article 
297121 I should run the asdutil.vbs script to set the passwordchangeflags 
setting to 1.  I checked the current default setting and it is currently 6.  
KB article 920723 states that 6 is the default setting for IIS 6.0 (which we 
are running on our front end-servers) and that setting means that "Password 
changing and password expiration notification is disabled".  The last part of 
that statement seems to be true but the first part is not.  Our users CAN 
change thier AD password through OWA.  Here are my questions:

What does that "6" setting really mean?  Our users can change thier AD 
passwords but they are not getting the notifications.

What does the suggested "1" setting really mean?  What impact could that 
have on my Exchange servers?  (I don't think it will have a major impact, I 
just other people's experience and opinion before I make the change, if I 
make it at all)

If I do make the change, what do I need to do to have the change reflected?  
Do I need to stop and restart IIS?  Reboot my exchange front end servers?

Thank you for any and all help and guidance that you can provide.
date: Thu, 8 May 2008 05:54:04 -0700   author:   daviddmccullough

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us