Public Folders are slow

Okay, we have recently migrated Exchange servers. The old: Exchange 5.5 SP3 on NT4 SP5. The new: Exchange 5.5 SP4 on Win2K Server. The new server is 800MHZ, 256MEG. It's performance is mildly sluggish but when we attempt to access public folders it take a minute or more and sometimes times out. The minute that I bring the other (old) server online, the Public Folders come up in a snap. Performance monitor says memory usage is fine as well as processor usage. However, I don't know what could be causing this bottleneck. Is this a configuration issue with public folders and Exchange or do I need to beef up the new server?
LVL 1
JconleyMCSEAsked:
Who is Participating?
 
TemlockConnect With a Mentor Commented:
You have rehomed all of your folders correctly?

1.) In ExAdmin, go to each folder and view properties.  ensure that they are homed to the server you expect.

2.) In ExAdmin, go to Site/Configuration/Servers/Private Information Store.  View properties and make sure that the "Public Folder Server" entry points to the server housing the public folders.
0
 
TemlockCommented:
The server sounds fine.  I have found that running 5.5 on a Win2K server requires a bit more tweeking to ensure that your client calls to the server are happening efficiently.  Are you using Active Directory on the server or in the environment?  If so, you may want to throw a probe between your server and client to make sure that the client is calling the server appropriately and not wasting time on NetBios or WINS if it's not being used in your Win2k environment.  You may want to consider either upgrading to Exchange 2k or downgrading your OS to WINNT4 SP6a.  

Let me see if I can find out some specific tweeks for you.
0
 
slink9Commented:
This is a link to a bunch of Win2k tweaks - http://thor.prohosting.com/~1cls/Win2k.html.  Maybe you will find it useful.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
JconleyMCSEAuthor Commented:
Thanks for your input Tem & Slink. We are indeed running AD. Unfortunately running Exchange 2000 right now isn't possible until we get permission from the powers that be. Downgrading the OS really isn't doable either. So how would I tell if the client is calling the server appropriately?

Slink, that link is dead. Thanks for trying though. Any other thoughts?
0
 
slink9Commented:
I don't know why it is dead.  It showed up dead when I clicked on it also.  I pulled it out of my history and it went to the same place.  Here are a few links from the page.

http://www.tweak3d.net/tweak/win2kmem/index.shtml
http://www.tweak3d.net/tweak/win2k/index.shtml
http://www.ntfaq.com/
0
 
JconleyMCSEAuthor Commented:
Okay, I've optimized Windows but it's still opening the folders without the original server online. Apparantly there is something on the old server that I have not brought over. Any thoughts?
0
 
slink9Commented:
I'm confused.  Maybe someone else can help.
0
 
JconleyMCSEAuthor Commented:
I meant to say it's still NOT opening the public folders without the original server online. Sorry for the confusion.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.