|
Thel posted:Fuuuuck Exchange. From someone who is a co-owner of IT company and TPM that has done hundreds of Exchange 2007 and 2010 implementations, Exchange 2007 and 2010 suck massive elephant cock. Also, gently caress PowerShell in its loving rear end. Sorry for the generalized rant, had to blow off steam. A recent implementation has gone awry yet again (certificate issues) and is causing massive grief, thank goodness this is a parallel spin-up to an existing 2003 environment. R-Type fucked around with this message at 16:37 on May 24, 2011 |
# ¿ May 24, 2011 16:30 |
|
|
# ¿ Apr 26, 2024 10:08 |
|
Hi all. I have a production environment with an Exchange 2007 implementation, 1 CAS/HUB server and a Exchange 2010 environment in implementation, with 3 CAS/HUB servers and 4 mailbox servers. What would be the best way in the interim to configure SMTP traffic to flow back and forth from the production environment to the 2010 environment, leaving the production environment configured the way it is for now (mail flows from smarthost to 2007 CAS server) ? The project plan is to have both environments running in parallel, conduct trials and gain acceptance to migrate users and services. It's been years since I've done 2003 and lately I've been more tied up with project management and running the business. I've had to pick up on this project due to a resource failing to clear a NRC background check, so I apologize for the ignorance.
|
# ¿ May 22, 2012 20:04 |
|
Linux Nazi posted:If they are entirely separate organizations / administrative groups / active directory deployments, then you would simply configure send connectors with specific address space parameters. This deployment is within the same organization / domain as the 2007 exchange environment.
|
# ¿ May 23, 2012 19:24 |