We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Help with Exchange 2007 Best Practices Analyzer:

Medium Priority
798 Views
Last Modified: 2012-06-27
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.
Comment
Watch Question

Commented:
well the first one points to you moving the log files

for the 2nd
see
http://support.microsoft.com/kb/288894

Author

Commented:
Here are the scan reports.

1st-scan.htm
Recent-Scan.htm

Author

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...
Jian An LimSolutions Architect
CERTIFIED EXPERT
Top Expert 2016

Commented:
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 :)




Author

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
Solutions Architect
CERTIFIED EXPERT
Top Expert 2016
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.