I believe he is trying to plan in the event the link is unavailable....
From: Jim Majorowicz [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2008 11:37 AM To: NT System Admin Issues Subject: RE: Exchange with a vitualized DC at remote location? Yeah, but if they're authenticating now over link won't they still be able to on a restart? From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2008 10:22 AM To: NT System Admin Issues Subject: RE: Exchange with a vitualized DC at remote location? Thanks for chirping it, I kinda saw this coming, I figured I might have to set the Exchange services to manual, and start them manually after reboot, or script a delayed a startup... From: Barsodi.John [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2008 12:05 PM To: NT System Admin Issues Subject: RE: Exchange with a vitualized DC at remote location? A problem I see is on a reboot. If exchange is installed locally on the host and the DC/GC is in the VM guest, then the Exchange servers will fail to start upon boot. From: Garcia-Moran, Carlos [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2008 5:56 AM To: NT System Admin Issues Subject: RE: Exchange with a vitualized DC at remote location? We have our DC's and Exchange running on a virtual environment in our DR site granted we run solely ESX there, but a Virtual is a Virtual. You can use VMware server which is free and runs on windows and it will work the same way. Don't use GSX if you have an old copy lying around. We've been doing this for 1+ year w/o a problem. 500 Users Exchange 2K3 btw. From: Jim Majorowicz [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2008 12:13 AM To: NT System Admin Issues Subject: RE: Exchange with a vitualized DC at remote location? I don't see any reason *NOT* too.... From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 17, 2008 3:57 PM To: NT System Admin Issues Subject: Exchange with a vitualized DC at remote location? Open for thoughts: Perhaps I could move my Exchange server to a remote site / collocation. Now, I have a dedicated VPN link between the collocation center and our office, which does have a DC, 2 actually. But exchange will want a DC/GC to chat with if the link ever fails. To avoid buying more hardware and save on collocation costs, what if I just fire up a DC/GC inside a VMware Server (GSX, not ESX) on the exchange box? The box has PLENTY of horsepower, and a DC for 30 users can't need than 512mb of ram, right? What do you think? Cross posted to Exchange list, sorry. Thanks Sam _________________________________________________________ This e-mail, including attachments, contains information that is confidential and may be protected by attorney/client or other privileges. This e-mail, including attachments, constitutes non-public information intended to be conveyed only to the designated recipient(s). If you are not an intended recipient, you are hereby notified that any unauthorized use, dissemination, distribution or reproduction of this e-mail, including attachments, is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify me by e-mail reply and delete the original message and any attachments from your system. _________________________________________________________ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
