server
Much simpler routing is accomplished without piles of send connectors and
targetaddress settings.
From: Mike Tavares [mailto:miketava...@comcast.net]
Sent: Sunday, June 19, 2011 3:53 PM
To: MS-Exchange Admin Issues
Subject: Re: Route company.com to multiple internal Business Units
Thanks
1
[mailto:miketava...@comcast.net]
Sent: Sunday, June 19, 2011 6:53 PM
To: MS-Exchange Admin Issues
Subject: Re: Route company.com to multiple internal Business Units
Thanks
1. Doesn’t surprise me. I already have ILM and Quest implemented for other
A/D sync related activities for some other domain
Sent from my LG phone
"Michael B. Smith" wrote:
[1] ILM/FIM are the automated solutions that MSFT has.
Quest and NetWrix both sell others.
I would suggest that you need a requirements analysis to determine exactly WHAT
you need. ☺
[2] If Exchange or something like postfix are the “masters o
(regardless of
the A/D they are a member of).
-Mike
From: Michael B. Smith
Sent: Sunday, June 19, 2011 5:38 PM
To: MS-Exchange Admin Issues
Subject: RE: Route company.com to multiple internal Business Units
[1] ILM/FIM are the automated solutions that MSFT has.
Quest and NetWrix both sell
[1] ILM/FIM are the automated solutions that MSFT has.
Quest and NetWrix both sell others.
I would suggest that you need a requirements analysis to determine exactly WHAT
you need. ☺
[2] If Exchange or something like postfix are the “masters of all domains” then
yes, it’s pretty easy to do. I
