RE: Looking for anti-clustering arguments
Jason, We have been running one of our Exchange servers as an E2K3/W2K3 cluster for a few months now and will be going live with all our Exchange servers on clusters in a few months as soon as Sophos release a cluster-aware version of Mailmonitor. Virus protection is all that has stopped us going live now. Sure it doesn't protect against database corruption but that's what you do backups for. The real beauty of a cluster is that you can take one of the pair down for hardware or software maintenance without users moaning about downtime. Believe me its not harder to administer and its certainly no worse than a non-clustered Exchange server, do go for the 2003 version because its much better than 2000 - both O/S and Exchange. Regards Brian Brian Davies - Network Operations Manager University of East London E-mail: [EMAIL PROTECTED] Tel: 0208 223 2091 Mobile: 07711 198349 -Original Message- From: Jason Clishe [mailto:[EMAIL PROTECTED] Sent: 24 November 2003 22:11 To: Exchange Discussions Subject: Looking for anti-clustering arguments OK, I know the majority of this list is against clustering Exchange. But does anyone have some sound reasoning behind this argument that could be used to convince someone at the executive level? I don't think many executives are too compassionate for the it's harder to administer argument. And I need more ammo than just saying that clusters won't protect you from database corruption anyway. Thanks Jason _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchanget ext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: OWA Front/back end in Cluster
I think Ed must have had a bad day!! Try looking at the IIS authentication settings of your back-end servers (possibly front-end as well) and set the authentication to disable anonymous and enable Integrated Windows and/or Basic (and set the domain). Regards Brian Brian Davies - Network Operations Manager University of East London E-mail: [EMAIL PROTECTED] Tel: 0208 223 2091 Mobile: 07711 198349 -Original Message- From: Ed Crowley [MVP] [mailto:[EMAIL PROTECTED] Sent: 11 November 2003 03:56 To: Exchange Discussions Subject: RE: OWA Front/back end in Cluster While you're doing all that, you might as well enable brick backups, have all your users download all their mail to their PSTs using POP, collect your mail from your ISP using a POP remailer, and have your file-based virus scanner scan the M: drive. Ed Crowley MCSE+Internet MVP Freelance E-Mail Philosopher Protecting the world from PSTs and Bricked Backups!T -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of M2web Sent: Monday, November 10, 2003 10:20 AM To: Exchange Discussions Subject: OWA Front/back end in Cluster I have setup an Active/passive cluster with a front end/backend config behind a firewall. Firewall has been configured to pass HTTP to the front end server. If on a computer outside the firewall I type the URL of the OWA, I get the Windows authentication screen but having entered the username and password the URL changes to the inside FQN of the EVS and I get a blank white screen. However if I do the same thing from a computer from within the firewall I still get the FQN of EVS in the URL address but I also get the OWA! What have I not done or done that it is causing this? _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchanget ext_mode=lang =english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang= english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Migrating to Exch 2003
Yes, you will have to follow the procedure for removing the first Exchange 2000 server. Note that you do NOT have to promote your 2003 member serve to a DC if you don't need it as a DC. In fact I wouldn't recommend it. Having said this, we've run the upgrade Win2K to Win2K3 and E2K to E2K3 in-line upgrade on several of our severs and it works fine, so you don't need to move to new hardware if you don't want to. Just stick the CDs in and follow the wizards. If you've got a Front-end Server you MUST upgrade this first before any Back-end servers. Regards Brian Brian Davies - Network Operations Manager University of East London E-mail: [EMAIL PROTECTED] Tel: 0208 223 2091 Mobile: 07711 198349 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 04 November 2003 11:48 To: Exchange Discussions Subject: Migrating to Exch 2003 I am moving to Exch 2003. The method is to upgrade 2k AD with adprep, promote a 2003 member serve to a DC, install Exch 2003 on it and move the mailboxes from the Exch 2k to the Exch 2003 server. After the upgrading to Exch 2003 I want to remove the Exch 2k server from the network. My question is - do I have follow the procedure in MS knowledge base article 307917 (how to remove the first Exchange 2000 server computer from a site) when moving to Exch 2003? _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchanget ext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Move E2K servers between AD containers?
Brent, Computers isn't a container in AD - it's a folder and therefore can't have a policy applied to it. The only policy that will apply to Computers is the default domain policy so it doesn't matter where you move your Exchange server the default domain policy will still be applied unless you block policy inheritance on the OU you put the Exchange servers into, but then you must re-apply all the required policy objects on the new OU. Yes you can move servers to any OU you like but you must make sure the right policies are being applied. Regards Brian Brian Davies - Network Operations Manager University of East London E-mail: [EMAIL PROTECTED] Tel: 0208 223 2091 Mobile: 07711 198349 -Original Message- From: Leeann McCallum [mailto:[EMAIL PROTECTED] Sent: 01 November 2003 04:19 To: Exchange Discussions Subject: RE: Move E2K servers between AD containers? We've moved all ours to different OU's. No problems at all other than having to restart the services. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of MS Exchange List Sent: Saturday, 1 November 2003 9:05 a.m. To: Exchange Discussions Subject: Move E2K servers between AD containers? Hello, E2K: 2 Servers, same site/group, SP3+September'03 Rollup+recent critical security patch, Scanmail 6.1, native OS: w2K, SP4 + all critical fixes , native The powers that be would like to move all the Servers into a new OU Servers container in AD. They're trying to deploy some policies against the default Computers container the Exchange servers currently exist in, so want the Exchange Servers out of it. It seemed to work OK in the lab after moving and rebooting. I know some of the Exchange Groups can't be moved out of the Default Users container. Any problem moving Exchange Servers between containers? They are not DCs. Thank you, Brent _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchanget ext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] # Notice: This e-mail message is only intended to be read by the named recipient. It may contain information which is confidential, proprietary or the subject of legal privilege. If you are not the intended recipient please notify the sender immediately and delete this e-mail. You may not use any information contained in it. Legal privilege is not waived because you have read this e-mail. For further information on the Beca Group of Companies, visit our web page http://www.beca.co.nz # _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang= english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchangetext_mode=lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
