We help IT Professionals succeed at work.

Exchange 2003 Public Folders are very slow responding after migration from Exchange 2000

bilalaha asked
Medium Priority
Last Modified: 2012-08-14
I have recently migrated from Excahnge 2000 to Exchange 2003 using the New Hardware method
I followed microsoft KB artcle 307917 as a guide and all worked fine.  I shutdown my old exchange server to make sure that everything is working fine before removing the old server.

When I click on Public Folder (Not much data/public folders), it takes about two minutes to open the folder.  I checked all the folders in ESM and they all have one copy on the new mail server.  The Only place I see both Servers listed in ESM is when I expand Folders nder the Administrative Group and Select Properties of the Public Folders.  It show both Servers under public stores associated to the folder tree, but there is no option to remove.

Did I mish anything?

Thanks in Advance.

Watch Question

President/Principal Consultant
With both servers still technically available, its going to cause issues like that until you remove it. Verify you have completed all the steps and take the plunge!


I have completed all the steps, and shut down the old exchange 2000.  It has been down for a few days and everything seem to be working fine, except for the speed of opening the public folder, pulling the address list and downloading the free/busy time.  Slow but works.

Is there anything else I need to check before taking the plunge?
Stacy SpearPresident/Principal Consultant

No, the speed issue should go away after the removal of the old server.


I will be removing the old exchange server early tomorrow after a full back has been done.

I will let you know how it goes.


I started the removal process, but I get an error message :
The Component "Microsoft Exchange Messaging and Collaboration Services" cannot be assigned the action "Remove" because:
-One or more users currently use a mailbox store on this server.  These users must be moved to a mailbox store on a different server or be mail disabled before uninstalling this server.

I do not have any mailboxes in the mailstore except SMTP (OLDSERVERNAME --{4Dcae92.........}, System Atendant and SystemMailbox and I can not remove any.

I also have some empty public folders that I do not need.  Rightclicking does not give me the option to delete.  

What am I missing here?
Stacy SpearPresident/Principal Consultant

:) The old ghost accounts thingy. The code below will identify these so you can change their server using ADUC.
Shows anything that is mail enabled, but doesnt have a mailbox 
Dim rootDSE, domainObject, conn, cmd 
Set rootDSE=GetObject("LDAP://RootDSE") 
DomainContainer = rootDSE.Get("defaultNamingContext") 
Set fs = CreateObject ("Scripting.FileSystemObject") 
strDate = Year(Now) & "-" & Right("0" & Month(Now),2) & "-" & Right("0" & Day(Now),2) 
Set userFile = fs.CreateTextFile ("test_" & strDate & ".csv") 
Set conn = CreateObject("ADODB.Connection") 
conn.Open "Provider=ADsDSOObject;" 
Set cmd = CreateObject("ADODB.command") 
cmd.ActiveConnection = conn 
cmd.Properties("Cache Results") = False 
cmd.Properties("Page Size") = 5000 
cmd.CommandText = "<ldap:>;(&(mail=*)(msExchHomeServerName=*)(!(homeMDB=*)));adspath;subtree" 
Set rs = cmd.Execute 
userFile.Write "displayName,CN,mail" 
userFile.WriteLine "" 
While Not rs.EOF 
Set oUser = GetObject (rs.Fields(0).Value) 
userFile.Write chr(34) & oUser.cn & chr(34) & "," & chr(34) & oUser.givenName & " " & oUser.sn & chr(34) & "," & oUser.mail & ",smtp:" & oUser.mail 
        userFile.WriteLine "" 

Open in new window


I found the mailbox and moved it so it is now lettinng me remove.  I was able to find out which account was still on the old server by cheching the ADUC.  Article at: http://www.amset.info/exchange/migration.asp

I will remove excahnge tomorrow morning after the backup complete.

Will I need to reboot the new server or just remove the old server from the domain after I  uninstall exchange?
Stacy SpearPresident/Principal Consultant

No reboot of the new one needed, just uninstall the old one.


Done.  Everything went very smooth.


Explore More ContentExplore courses, solutions, and other research materials related to this topic.