Skip to main content

How to Enable the Exchange 2007 SP3 users Password Reset Tool

 How to Enable the Exchange 2007 SP3 Password Reset Tool


Applies to: Exchange Server 2007 SP3


This topic explains how to use Registry Editor to enable the Microsoft Exchange Server 2007 Password Reset Tool.


Microsoft Office Outlook Web Access (OWA) includes a feature to let users change their passwords. However, this feature requires that users log on to OWA to change their passwords. In a scenario in which a user password has expired, or in which users have to change their passwords when they first log on, users cannot log on to OWA to access the password change feature. In earlier versions of Microsoft Exchange , an administrator could configure the IISADMPWD Web application to help users. To do this, the administrator could direct users who had expired passwords to an anonymously-accessible Web page to reset their passwords. IISADMPWD is not available in Windows Server 2008. Therefore, the password reset functionality may be unavailable for Exchange 2007 users in a Windows Server 2008-based environment.
Exchange 2007 SP3 adds a new feature to the Client Access server (CAS) role. This feature creates a new Internet Information Services (IIS) 7 module that detects expired passwords, and redirects users to a new change password page. By default, this feature is disabled. To enable the password reset feature, you must set a registry key.

To enable the password reset feature
  1. Log on to the Exchange server that is running the CAS role by using an account that has local administrator rights.
  2. Start Registry Editor, and then locate the following registry subkey:
    HLKM\SYSTEM\CurrentControlSet\Services\MSExchange OWA
  3. Create the following DWORD value if it does not already exist:
    Value name: ChangeExpiredPasswordEnabledValue type: REG_DWORDValue data: 1
  4. Exit Registry Editor.

Note: The password reset functionality is enabled when ChangeExpiredPasswordEnabled is set to a nonzero (0) value. If this registry value is missing or is set to a value of zero, the password reset functionality is disabled.

To download Exchange server 2007 SP3 follow this Microsoft link.
http://www.microsoft.com/downloads/details.aspx?FamilyID=1687160b-634a-43cb-a65a-f355cff0afa6&displaylang=en

Comments

Post a Comment

Popular posts from this blog

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Recreating a VMFS-3 or VMFS-5 partition table in ESXi 5.x

For this kind of issues you need to engage VMware support on this, following any part of this article could lead to more complex situation if not ran by an expert.   Symptoms Datastore does not mount because of a lost or overwritten partition table.   Purpose When a VMFS partition is created in ESX 3.x or ESX 4.x, it has a Master Boot Record (MBR) partition map. The MBR is written to the first 512 B block (LBA0) and contains the information where the (VMFS) partition starts and ends. ESXi 5.0 introduced VMFS-5, which uses a GUID partition table (GPT) for new datastores. When a VMFS-3 partition is created in ESXi 5.x and is later updated to VMFS-5, the original partition map (MBR) is maintained. If the partition information of a VMFS datastore is deleted or overwritten (for example, by a Windows system with direct access to the same disks), it is impossible to determine if the partition map was GPT or MBR. The only time you can be sure that a GPT partition map was used is if th...
Post a Comment
Read more