• Why is store.exe consuming all our available resources?

    We are running Exchange 5.5 on Windows 2000 and until recently we didn't seem to have any issues. Lately, however, I have been noticing the store.exe process seems to consume all the available resoures. I can reset the information store and it slowly climbs again to full usage. I have defragged the...

    ITKE407,620 pointsBadges:
  • Microsoft customer upgrades inevitable

    With the economy improving, companies will -- finally, after three years -- bite the bullet and move up the food chain from NT 4 and Exchange 5.5 to newer versions of those products.

    ITKE407,620 pointsBadges:
  • Users get Microsoft to blink first

    If you've been putting off migrating from Exchange 5.5, breathe a little easier. Microsoft is going to cut you some slack.

    Jhogan800 pointsBadges:
  • What’s the best anti-spam product on the market?

    We are currently running TrendMicro's antivirus and content filtering software. The anti-spam filtering is only catching about 70% of the spam. In your opinion, what anti-spam product is best? We have five Exchange 5.5 servers running in offices around the country.

    SearchWinIT2,435 pointsBadges:
  • Microsoft: End is near for Exchange 5.5

    Just like it's doing with NT 4.0, Microsoft is getting ready to pull the plug on Exchange 5.5. This isn't exactly what the 60% to 70% of customers who haven't made the move to Exchange 2000 wanted to hear, and it gives a new charge to the life cycle debate.

    Margie Semilof4,330 pointsBadges:
  • Restrict searches in Exchange 5.5

    How to keep people from seeing addresses they shouldn't.

  • Disable EHLO in Exchange 5.5 and 2000

    How to disable EHLO in Exchange 5.5 and 2000 and why you would need to.

  • Nonsensical message counts in Exchange 5.5

    How to solve the problem of nonsensical message counts in Exchange 5.5.

  • Registry-related Exchange replication failure

    Exchange 5.5 and Exchange 2000 use a certain registry key to govern how replication behaves. If this key is damaged or has an invalid value written to it, replication may fail.

  • Rolling back a failed upgrade

    You are in the middle of upgrading from Exchange 5.5 to 2000, and something goes wrong. What do you do? This tip gives some step-by-step advice.

    Brien Posey13,860 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.