It shouldn't be supported. If you don't recommend it, you shouldn't be
supporting it.
Just like this now clearly states they won't support an Exchange after
an eseutil without a move to a new database.
On 6/29/2015 11:00 AM, Michael B. Smith wrote:
I don't understand. It's supported but not recommended. What's wishy-washy
about that?
The reasons it isn't recommended are also well-documented (can't control memory
pressure from AD, Exchange will only have access to a single DC, must use the
AD NSPI interface instead of the Exchange NSPI interface, I/O priorities are
difficult to control, etc.).
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Susan Bradley
Sent: Monday, June 29, 2015 1:52 PM
To: [email protected]
Subject: Re: [Exchange] New Support Policy for Repaired Exchange Databases
Well I've/we've been trying to get them to codify not installing Exchange on a
DC in black and white policy and can't get them to do that. :-) That one they
still are more wishywashy than I'd like.
On 6/29/2015 10:47 AM, Michael B. Smith wrote:
It's been the recommendation since at least 2007. They’ve just codified it.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Susan Bradley
Sent: Monday, June 29, 2015 11:50 AM
To: [email protected]
Subject: [Exchange] New Support Policy for Repaired Exchange Databases
New Support Policy for Repaired Exchange Databases - Exchange Team
Blog
- Site Home - TechNet Blogs:
http://blogs.technet.com/b/exchange/archive/2015/05/01/new-support-pol
icy-for-repaired-exchange-databases.aspx
Didn't see this until recently.
