why oh why did thy have to mke schema changes. This has caused me no end of grief.
I can’t just test and “Deploy” I need to get royal approval from hogworts. Do you know what, I passed all the tests they set just to get the first damm server installed.
Then they ganged up on me and kick the life out of me. End result, no SP1 this month or next by the looks of it!!!
you can really go off people sometimes, especially when you think they are on your side but they just smile as they slip the knife in
At last a Web Update Pack for ExBPA. You can get it from here:
Basically this download contains the latest XML and ExBPA.chm files. Use this package to update your existing installation of the Exchange Best Practices Analyzer.
You only need to apply it (if like almost every production server in the world) the server does not have internet access to download the update automatically.
It’s 3,348kb and contains 6 files
ExBPA.Config.xml -> v220.127.116.11
ExBPA.Permissions.xml -> 18.104.22.168
ExBPA.Readiness.xml -> 22.214.171.124
ExBPA.Transport.xml -> 126.96.36.199
So typically, on an Exchange 2007 Server, you will drop these in to C:Program FilesMicrosoftExchange ServerBinen
What is STRANGE is that if you have an Exchange Server 2007 on the Internet the latest files are as follows:
ExBPA.config.xml -> 188.8.131.52
ExBPA.E12.UnifiedMessaging.xml -> 184.108.40.206
ExBPA.Readiness.xml -> 220.127.116.11
ExDRA.Config.xml -> 18.104.22.168
ExMFA.Config.xml -> 22.214.171.124
ExTRA.config.xml -> 126.96.36.199
So what does one do? The ExBPA.config.xml is a totally different version? Should you apply it? Should I update everything except ExBPA.config.xml?
WHY do two different versions exist?