Archive for the ‘MS Exchange’ Category

Decommissioning first Exchange 2003 server together with first AG

MS Exchange | Posted by p_lider March 24th, 2013

Recently I had to decommission the first Exchange 2003 server in our company. Our exchange organization had 2 Exchange 2003 SP2 servers and 2 Administrative Groups (each server in a separate AG). When searching the internet for help in doing that I have found the following article – http://support.microsoft.com/kb/822931.

This article describes almost everything what you should do except the following:

  1. What to do with “schema-root”, “OWAScratch{GUID}” and “StoreEvents{GUID}” system folders.
  2. How to delete the first AG when removing the last server from it.

 

Ad. 1. It is best to rehome mentioned system folders to the other server as you did with the OAB folders and others, so their content is removed from the server being decommissioned but stays on the other one. This would be the best way to get rid of them from the “Public Folder store” of the retiring server.

This is in contrast to simply deleting the folders – I noticed that deleting these folders can lead to strange behavior: they structure is being regenerated by the Exchange after decommissioning the first server however they do not have a replica so they cannot be used. This is not preventing the public folders from working fine, however this causes errors when looking at them using “Exchange System Manager”. I do not know if this can lead to some other, serious problems but seeing an errors in ESM is not a good sign I think.

When there are no mailboxes and public folder instances left on the decommissioned server and other steps mentioned in Microsoft’s article are already done then you can remove the “Public Folder Store” and “Mailbox Store” from it.

 

Ad. 2 If you want to remove whole Administrative Group which will be empty after decommissioning the server, then before uninstalling the Microsoft Exchange from the server follow these steps:

  1. Move the “Public Folders” tree to the other AG if it exists in the current AG being removed.
  2. Remove all the connectors from the routing groups stored within this AG and all connectors from other routing groups in other AGs which were connected to the routing groups in the AG being removed.
  3. Uninstall the Microsoft Exchange from the server being decommissioned in this group.
  4. Remove all routing groups from the AG.
  5. Remove all containers from the AG.
  6. Remove the AG.

Steps 1,2,4,5,6 are best to be performed using ESM on other Exchange server (anyone which is not being decommisioned).

“Object Required” error while changing passwords using OWA

IIS, MS Exchange, Windows Server 2003 | Posted by p_lider September 6th, 2010

After deploying MS Exchange 2003 server in your organization and configuring OWA to let users change their domain passwords you can face a strange issue. When users try to change their passwords, after clicking “OK” button they see an error message saying “Object Required” and their password are not being changed. This enigmatic error message means, that the MS Exchange cannot find a properly registered COM object in the registry. To solve the problem you must manually register the “iispwchg.dll” library on the MS Exchange server. The full command to do this is:

regsvr32 %windir%\system32\inetsrv\iisadmpwd\iispwchg.dll

The reason why MS Exchange does not register mentioned library by itself during the installation is unknown for me. However I noticed, that MS Exchange installers are written is such a way, so the administrators can demonstrate their knowledge and skills <ironic> before the MS Exchange product can start fully working.

Horror of MS Exchange 2010 installation

MS Exchange | Posted by p_lider August 23rd, 2010

Before you install MS Exchange 2007 or 2010 make sure, that IPV6 protocol is either fully enabled in all interfaces or fully disabled. Failed to do so will render your server to be almost inaccessible just after MS Exchange installation (the network provider services will not start or at least will start after very, very long delay). This is probably caused due to a bug (or mistake in design) in  MS Exchange networking services.

To make the bad thing worse, the MS Exchange 2010 installer do not install all the required Windows Server 2008 roles and features making the installation of MS Exchange even more complicated. Follow the following article to install all the necessary roles for your server to work properly: http://technet.microsoft.com/en-us/library/bb691354.aspx

Moreover, if you see “Topology” errors in Event Log after the Exchange server installation you have to add “Audit security log” right for user “Enterprise Exchange Servers” in a domain-wide Group Policy Object.

Anyone can tell me why Microsoft is doing this? Can’t the installer do everything which is needed for the product to work? Akhh…