• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 780
  • Last Modified:

Help with Exchange 2007 Best Practices Analyzer:

Hey all.

I decided to run the Exchange 2007 Best Practices Analyzer as the server wasn't setup by me but an outside IT company back in 2009.

It runs as a virtual machine with Server 2003 x64 and was assigned 2 CPUs along with 12GB of RAM.

The best practices analyzer at first showed quite a few things that weren't up to par.

I've attached the 1st scan which shows the original issues along with the most recent scan which was done this morning.

These are in HTM format which I hope reads properly for everyone.

In a nutshell, I increased the virtual memory, blocked all version of Outlook older than 2003 SP2, installed the Filter Pack and moved the transaction log files to another partition that wasn't being used on this server.

Now that I've done those things, new warnings come up such as this one:
The checkpoint file path for storage group 'First Storage Group' on server MAILSRVMS2 (E:\PROGRAM FILES\MICROSOFT\EXCHANGE SERVER\MAILBOX\FIRST STORAGE GROUP) does not match the transaction log path (F:\EXCHANGELOGFILES). This issue can cause extended downtime when disk failures occur

And this warning came up as well:
Some versions of MAPI clients are blocked on server mailsrvms2.Bonland.local. Verify that version '6.x.x.x' and version '8.x.x.x' clients are not blocked as the Microsoft Exchange System Attendant process uses these version identifiers for performing server functions. Current MAPI blocking setting: -5.9.9;7.0.0-11.6568.6568.

Am I missing something?

I'd like to go over some possible solutions for these.

Thank you.
0
homerslmpson
Asked:
homerslmpson
  • 3
  • 2
1 Solution
 
IanThCommented:
well the first one points to you moving the log files

for the 2nd
see
http://support.microsoft.com/kb/288894
0
 
homerslmpsonAuthor Commented:
Here are the scan reports.

1st-scan.htm
Recent-Scan.htm
0
 
homerslmpsonAuthor Commented:
@IanTh:
I only moved the log files because the initial report told me I should.

Then I move them and the next time I run it, it gives me a warning which to me means I shouldn't have moved the path to the log files to begin with...
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
Jian An LimCommented:
let's sort out the log issue first.

when exchange 2007 refer to logs, there is 2 component, database log and system log.
so you have move your database log to another drive, thats great. the next thing is to move your system log to the same location



http://technet.microsoft.com/en-us/library/bb125252%28v=exchg.80%29.aspx 


=====
then go back to your first question
how do you blocked all version of Outlook older than 2003 SP2 ?

Current MAPI blocking setting: -5.9.9;7.0.0-11.6568.6568.
you cannot block v6.x.x (which is exchange 2000/2003) and v8.x.x( which is exchange 2007), and v14 (which is for exchange 2010)

so the proper one should be
0.0.0-5.65535.65535;7.0.0-7.65535.65535:9.0.0-11.65535.65535

(from 0 to 5, 7 to 7, 9 - 11)

by doing so you should not have any issues :)




0
 
homerslmpsonAuthor Commented:
I'm going to move System files path to the same location as the Log files path tonight while no one is using the server (see image).  Does that make sense?

I changed the registry for the MAPI settings to the one you mentioned but when I run the best practice analyzer it still shows the same warning.  Is this normal?

Thanks!

Screenshot
0
 
Jian An LimCommented:
it make sense.

the reason behind is if you only have your log file without system file, the rebuild will not work correctly.

=====================

for the MAPI settings, it is normal, as long as you make sure your 6 and 8 is not included, you will be in the good hand.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now