I got the final TOC today and was told FINALLY that the printers have the manuscript. I'll post the TOC on my blog when I have time.
I would recommend that you put Edge into a domain - however, it needs to be a completely separate forest than the one in which you have Exchange installed. In fact, I think that is a setup check. OpsMgr should have no issues with this whatsoever. You'll simply need to identify one server as a gateway server and give it alternate credentials for the "remote domain". Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php From: Russ Patterson [mailto:rus...@gmail.com] Sent: Friday, January 23, 2009 11:59 AM To: MS-Exchange Admin Issues Subject: Edge server in a domain Morning All - We're getting ready to implement an E2k7 Edge server. At present, it's in a workgroup on its own, and we haven't even done a subscription as yet, i.e. the bits are installed, but no ports have been opened. We've run into a few difficulties (not insurmountable, but a bit time consuming) with this scenario, especially with monitoring software (Argent and soon, hopefully SCOM.) My question is this: Anyone have experience with putting an Edge server in a domain? - Our DMZ is a child domain in our forest (root is completely empty except for the DC/GC;) quite separate but for the required port openings..... I apologize for the lack of detail here; I'm not part of that team. Would we have trouble with an AD sync from our users domain because the Edge server wasn't in a workgroup? Anyone have any knowledge they'd like to share? Michael, I'm eagerly awaiting your book about SCOM ;) Thanks all - Russ Patterson ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
