Re: Export data from a disconnected mailbox?
Thanks Victor, that's what I was trying to avoid though. On Mon, May 12, 2008 at 5:56 AM, Victor Rodriguez [EMAIL PROTECTED] wrote: The easy way is to add a temp user and then connect the mail box to that user and export the pst file from ether the email client or the export mailbox command in the shell *From:* Alex Fontana [mailto:[EMAIL PROTECTED] *Sent:* Sunday, May 11, 2008 1:50 PM *To:* MS-Exchange Admin Issues *Subject:* Export data from a disconnected mailbox? Hi all, anyone know if its possible in E2007 to export the mail out of a disconnected mailbox with out connecting it to a user object? TIA, -alex -- This e-Mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-Mail in error please notify the sender via returned e-Mail. Please note that any views or opinions presented in this e-Mail are solely those of the author and do not necessarily represent those of the company. Although IDF operates anti-virus programs, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. ** Think before you print this message. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
iphone and corporate email
Can anyone point me in the right direction on how to configure an iphone to work with my corporate email (if it is possible)? I am running Exchange 2007 SP1. We are currently using Blackberry devices, but the new boss has an existing iphone he wants to use. Thanks in advance. Jonathan Jenkins ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
change of group type
Hi everyone, We have a windows 2000 domain which has trust relation to a windows 2003 domain. A few groups are universal distribution and are used for emails. We need to assign some permission to a file server and instead of creating new groups I was wondering if I can just simply change the group to security. Would that cause any problem in terms of email flow? Appreciated ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: change of group type
Not unless you have conflicting group names. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Ara Avvali [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 9:42 AM To: MS-Exchange Admin Issues Subject: change of group type Hi everyone, We have a windows 2000 domain which has trust relation to a windows 2003 domain. A few groups are universal distribution and are used for emails. We need to assign some permission to a file server and instead of creating new groups I was wondering if I can just simply change the group to security. Would that cause any problem in terms of email flow? Appreciated ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: iphone and corporate email
Here is my iPhone macro: First read this: http://msexchangeteam.com/archive/2007/07/10/446015.aspx Email only. No calendar, contacts, notes, etc. Just email. Next you need to configure IMAP on Exchange and open up the ports in Exchange. I would suggest IMAP over SSL for security. Here is a nice link: http://www.azaleos.com/blog/index.php?q=node/38 Finally configure the iPhone. If you want full blown ActiveSync, wait for iPhone 2.0 (due around June/July) From: Administrator [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 6:35 AM To: MS-Exchange Admin Issues Subject: iphone and corporate email Can anyone point me in the right direction on how to configure an iphone to work with my corporate email (if it is possible)? I am running Exchange 2007 SP1. We are currently using Blackberry devices, but the new boss has an existing iphone he wants to use. Thanks in advance. Jonathan Jenkins ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: iphone and corporate email
Request the ActiveSync beta from apple. Of course this require you setup the server with the CAS role to have access from the outside. So basically a OWA box. We are thinking about doing this as well. Since our upper management people are all about the newest toys, even if they do suck. From: Administrator [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 9:35 AM To: MS-Exchange Admin Issues Subject: iphone and corporate email Can anyone point me in the right direction on how to configure an iphone to work with my corporate email (if it is possible)? I am running Exchange 2007 SP1. We are currently using Blackberry devices, but the new boss has an existing iphone he wants to use. Thanks in advance. Jonathan Jenkins ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: iphone and corporate email
Will older iPhones be able to be upgraded to 2.0? Or is this a forklift upgrade? Thanks. Joe On Tue, May 13, 2008 at 9:49 AM, Martin Blackstone [EMAIL PROTECTED] wrote: Here is my iPhone macro: First read this: http://msexchangeteam.com/archive/2007/07/10/446015.aspx Email only. No calendar, contacts, notes, etc. Just email. Next you need to configure IMAP on Exchange and open up the ports in Exchange. I would suggest IMAP over SSL for security. Here is a nice link: http://www.azaleos.com/blog/index.php?q=node/38 Finally configure the iPhone. If you want full blown ActiveSync, wait for iPhone 2.0 (due around June/July) *From:* Administrator [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 6:35 AM *To:* MS-Exchange Admin Issues *Subject:* iphone and corporate email Can anyone point me in the right direction on how to configure an iphone to work with my corporate email (if it is possible)? I am running Exchange 2007 SP1. We are currently using Blackberry devices, but the new boss has an existing iphone he wants to use. Thanks in advance. *Jonathan Jenkins* -- Joe Fox Systems/Network Administrator Mobile# (716) 846-9308 http://www.linkedin.com/in/josephfoxjr The information contained in this e-mail message, including any attached files, is intended only for the personal and confidential use of the recipient(s) named above. If you are not the intended recipient be advised that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone at 716-846-9308 or by return e-mail. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: change of group type
Hi Michael, No we don't. so universal security is a safe way to go? Thanks From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 9:44 AM To: MS-Exchange Admin Issues Subject: RE: change of group type Not unless you have conflicting group names. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Ara Avvali [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 9:42 AM To: MS-Exchange Admin Issues Subject: change of group type Hi everyone, We have a windows 2000 domain which has trust relation to a windows 2003 domain. A few groups are universal distribution and are used for emails. We need to assign some permission to a file server and instead of creating new groups I was wondering if I can just simply change the group to security. Would that cause any problem in terms of email flow? Appreciated ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: iphone and corporate email
IIRC correctly currently the iPhone has no Exchange Support. It requires IMAP or POP3 access to the mail server. However Apple have licensed the ActiveSync technology and I believe that functionality is due shortly. Whether or not this will be a software upgrade to the current phone or a new device I'm not sure. Knowing how this usually works it will probably be a new device From: Administrator [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 15:35 To: MS-Exchange Admin Issues Subject: iphone and corporate email Can anyone point me in the right direction on how to configure an iphone to work with my corporate email (if it is possible)? I am running Exchange 2007 SP1. We are currently using Blackberry devices, but the new boss has an existing iphone he wants to use. Thanks in advance. Jonathan Jenkins Disclaimer: The Development Bank of Southern Africa exercises no control over information contained in any e-mail message originating from within the organisation. The Bank makes no representation relating to the completeness or accuracy and accepts no responsibility for any loss, damage or liability that is incurred by reliance on the content hereof by the recipient or any other party. Each page attached hereto must also be read in conjunction with any disclaimer, which forms part of it. Confidentiality: The e-mail is privileged and confidential and for use of the addressee only. Should you have received this e-mail in error, please return it to [EMAIL PROTECTED] Dissemination, disclosure, copying or any similar actions of the content of this e-mail is strictly prohibited. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
ActiveSync on WM driving me nuts
A few days back, I posted about OMA not functioning. Chalk up one to being half-asleep; although OMA is grouchy, ActiveSync is the actual problem with which I'm concerned. The problem, in more detail: * Phone fails to sync, giving error 0x85010014; * Event viewer shows event ID 3005 (source: Server ActiveSync); * IIS logs show error 500. Problem occurs regardless of default domain and realm (empty, NetBIOS, or Active Directory domain) settings on relevant IIS virtual directories. I've verified the allowed authentication methods. I'm not incorrectly forcing SSL on an internally-called-via-non-SSL-only virtual directory. OMA does not work; although it shows 200 in IIS logs, the page content complains about an internal server error. OWA works properly, as does RPC-over-HTTPS. Server is SBS 2003. Exchange is SP2; said service pack has been reinstalled. I've followed several different KBs, and made a few registry and metabase edits. If it's on Microsoft.com or Petri.co.il, there's a good chance I've already tried it. SharePoint 2 had been installed, but never put into production. I confirmed that NTAuthenticationProviders is Negotiate,NTLM. Rather than attempt to describe everything, I'll answer specific questions if anyone wants... Anything obvious that I might be overlooking? Eddy -- Everquick Internet - http://www.everquick.net/ A division of Brotsman Dreger, Inc. - http://www.brotsman.com/ Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita DO NOT send mail to the following addresses: [EMAIL PROTECTED] -*- [EMAIL PROTECTED] -*- [EMAIL PROTECTED] Sending mail to spambait addresses is a great way to get blocked. Ditto for broken OOO autoresponders and foolish AV software backscatter. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Exchange 2007 and SSL certs for internal and external use
Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.com) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: ActiveSync on WM driving me nuts
If I remember correctly, this is a cert issue. Specifically, you do not have the root cert for the server which issued the cert for the Exchange FE installed on the device. You need to install this, not the FE cert. CFee -Original Message- From: Edward B. DREGER [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:37 To: MS-Exchange Admin Issues Subject: ActiveSync on WM driving me nuts A few days back, I posted about OMA not functioning. Chalk up one to being half-asleep; although OMA is grouchy, ActiveSync is the actual problem with which I'm concerned. The problem, in more detail: * Phone fails to sync, giving error 0x85010014; * Event viewer shows event ID 3005 (source: Server ActiveSync); * IIS logs show error 500. Problem occurs regardless of default domain and realm (empty, NetBIOS, or Active Directory domain) settings on relevant IIS virtual directories. I've verified the allowed authentication methods. I'm not incorrectly forcing SSL on an internally-called-via-non-SSL-only virtual directory. OMA does not work; although it shows 200 in IIS logs, the page content complains about an internal server error. OWA works properly, as does RPC-over-HTTPS. Server is SBS 2003. Exchange is SP2; said service pack has been reinstalled. I've followed several different KBs, and made a few registry and metabase edits. If it's on Microsoft.com or Petri.co.il, there's a good chance I've already tried it. SharePoint 2 had been installed, but never put into production. I confirmed that NTAuthenticationProviders is Negotiate,NTLM. Rather than attempt to describe everything, I'll answer specific questions if anyone wants... Anything obvious that I might be overlooking? Eddy -- Everquick Internet - http://www.everquick.net/ A division of Brotsman Dreger, Inc. - http://www.brotsman.com/ Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita DO NOT send mail to the following addresses: [EMAIL PROTECTED] -*- [EMAIL PROTECTED] -*- [EMAIL PROTECTED] Sending mail to spambait addresses is a great way to get blocked. Ditto for broken OOO autoresponders and foolish AV software backscatter. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Exchange 2007 and SSL certs for internal and external use
Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one ( mydomain.com) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 and SSL certs for internal and external use
We do this by pointing all users to the external address regardless of where they are located. From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 9:42 AM To: MS-Exchange Admin Issues Subject: Exchange 2007 and SSL certs for internal and external use Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.com) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 and SSL certs for internal and external use
Another way might be a 'wildcard certificate'. One that handles *.domain.com, www.domain.com, domain.com, mail.domain.com, etc. A little more spendy though... From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:07 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com http://mail.mydomain.com/ ). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.com http://mydomain.com/ ) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com http://mail.mydomain.com/ and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Exchange 2007 and SSL certs for internal and external use
Yeah, cheap and easy is the split DNS road... TVK should know all about being cheap and easy... On Tue, May 13, 2008 at 8:18 AM, Sam Cayze [EMAIL PROTECTED] wrote: Another way might be a 'wildcard certificate'. One that handles *. domain.com, www.domain.com, domain.com, mail.domain.com, etc. A little more spendy though... -- *From:* Don Ely [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 10:07 AM *To:* MS-Exchange Admin Issues *Subject:* Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one ( mydomain.com) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Exchange 2007 and SSL certs for internal and external use
Why .local? On Tue, May 13, 2008 at 8:43 AM, Oliver Marshall [EMAIL PROTECTED] wrote: We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? *From:* Sam Cayze [mailto:[EMAIL PROTECTED] *Sent:* 13 May 2008 16:19 *To:* MS-Exchange Admin Issues *Subject:* RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *. domain.com, www.domain.com, domain.com, mail.domain.com, etc. A little more spendy though... -- *From:* Don Ely [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 10:07 AM *To:* MS-Exchange Admin Issues *Subject:* Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one ( mydomain.com) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 and SSL certs for internal and external use
A SAN cert will cover both your .com and .local. From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:44 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 16:19 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *.domain.com, www.domain.comhttp://www.domain.com, domain.com, mail.domain.com, etc. A little more spendy though... From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:07 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.comhttp://mail.mydomain.com/). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.comhttp://mydomain.com/) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.comhttp://mail.mydomain.com/ and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Associate an external account
As per MS KB 27 I understand that I must disable the current one but is not clear if it assigning permissions is doable from the GUI (mailbox rights) or I must go to command line or programming ! TIA GuidoElia HELPPC ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 and SSL certs for internal and external use
Olly, Check this article also: http://support.microsoft.com/default.aspx/kb/940726 It should help with checking and/or changing the URLs that your clients connect too. Tim From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:56 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Is there a way to do it without a new Cert? Just checked on the definition of split-dns and we already do that here to allow for internally hosted services, but that hasn't had any impact on the setup. From: Tim Vander Kooi [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 16:54 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use A SAN cert will cover both your .com and .local. From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:44 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 16:19 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *.domain.com, www.domain.comhttp://www.domain.com, domain.com, mail.domain.com, etc. A little more spendy though... From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:07 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.comhttp://mail.mydomain.com/). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.comhttp://mydomain.com/) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.comhttp://mail.mydomain.com/ and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 and SSL certs for internal and external use
Superb. Thanks mate -Original Message- From: Tim Vander Kooi [EMAIL PROTECTED] Sent: 13 May 2008 17:08 To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Subject: RE: Exchange 2007 and SSL certs for internal and external use Olly, Check this article also: http://support.microsoft.com/default.aspx/kb/940726 It should help with checking and/or changing the URLs that your clients connect too. Tim From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:56 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Is there a way to do it without a new Cert? Just checked on the definition of split-dns and we already do that here to allow for internally hosted services, but that hasn't had any impact on the setup. From: Tim Vander Kooi [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 16:54 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use A SAN cert will cover both your .com and .local. From: Oliver Marshall [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:44 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 16:19 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *.domain.com, www.domain.comhttp://www.domain.com, domain.com, mail.domain.com, etc. A little more spendy though... From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:07 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.comhttp://mail.mydomain.com/). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.comhttp://mydomain.com/) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.comhttp://mail.mydomain.com/ and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: iphone and corporate email
I believe there will be an upgrade, but better to ask of some iPhone pros. From: Joe Fox [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 7:04 AM To: MS-Exchange Admin Issues Subject: Re: iphone and corporate email Will older iPhones be able to be upgraded to 2.0? Or is this a forklift upgrade? Thanks. Joe On Tue, May 13, 2008 at 9:49 AM, Martin Blackstone [EMAIL PROTECTED] wrote: Here is my iPhone macro: First read this: http://msexchangeteam.com/archive/2007/07/10/446015.aspx Email only. No calendar, contacts, notes, etc. Just email. Next you need to configure IMAP on Exchange and open up the ports in Exchange. I would suggest IMAP over SSL for security. Here is a nice link: http://www.azaleos.com/blog/index.php?q=node/38 Finally configure the iPhone. If you want full blown ActiveSync, wait for iPhone 2.0 (due around June/July) From: Administrator [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 6:35 AM To: MS-Exchange Admin Issues Subject: iphone and corporate email Can anyone point me in the right direction on how to configure an iphone to work with my corporate email (if it is possible)? I am running Exchange 2007 SP1. We are currently using Blackberry devices, but the new boss has an existing iphone he wants to use. Thanks in advance. Jonathan Jenkins -- Joe Fox Systems/Network Administrator Mobile# (716) 846-9308 http://www.linkedin.com/in/josephfoxjr The information contained in this e-mail message, including any attached files, is intended only for the personal and confidential use of the recipient(s) named above. If you are not the intended recipient be advised that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone at 716-846-9308 or by return e-mail. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Exchange Failover Product..
Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated... Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Exchange Failover Product..
SCR? On Tue, May 13, 2008 at 12:49 PM, Chyka, Robert [EMAIL PROTECTED] wrote: Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated… Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Failover Product..
Not available in Ex 2003, only in 2007 SP1+ From: Steve Ens [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:56 AM To: MS-Exchange Admin Issues Subject: Re: Exchange Failover Product.. SCR? On Tue, May 13, 2008 at 12:49 PM, Chyka, Robert [EMAIL PROTECTED] wrote: Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated... Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Failover Product..
Double Take is good, NeverFail is good. Lots of people like Teneros, but I've never used it. At this point in the game (i.e., given how old Exchange 2003 is, and how old Exchange 2007 is); I would be installing Exchange 2007 and using SCR. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Chyka, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:50 PM To: MS-Exchange Admin Issues Subject: Exchange Failover Product.. Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated. Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 and SSL certs for internal and external use
Interestingly, I just installed SBS 2003 R2 for a new customer yesterday, and the SBS installation wizard actually suggested .local! I was surprised. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:47 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Why .local? On Tue, May 13, 2008 at 8:43 AM, Oliver Marshall [EMAIL PROTECTED] wrote: We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 16:19 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *.domain.com http://domain.com/ , www.domain.com http://www.domain.com/ , domain.com http://domain.com/ , mail.domain.com http://mail.domain.com/ , etc. A little more spendy though... _ From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:07 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com http://mail.mydomain.com/ ). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.com http://mydomain.com/ ) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com http://mail.mydomain.com/ and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: ActiveSync on WM driving me nuts
Did you look on MY blog? I've two or three posts on my experiences with debugging this error. They may, or may not, duplicate other content you can find. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com -Original Message- From: Edward B. DREGER [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:37 AM To: MS-Exchange Admin Issues Subject: ActiveSync on WM driving me nuts A few days back, I posted about OMA not functioning. Chalk up one to being half-asleep; although OMA is grouchy, ActiveSync is the actual problem with which I'm concerned. The problem, in more detail: * Phone fails to sync, giving error 0x85010014; * Event viewer shows event ID 3005 (source: Server ActiveSync); * IIS logs show error 500. Problem occurs regardless of default domain and realm (empty, NetBIOS, or Active Directory domain) settings on relevant IIS virtual directories. I've verified the allowed authentication methods. I'm not incorrectly forcing SSL on an internally-called-via-non-SSL-only virtual directory. OMA does not work; although it shows 200 in IIS logs, the page content complains about an internal server error. OWA works properly, as does RPC-over-HTTPS. Server is SBS 2003. Exchange is SP2; said service pack has been reinstalled. I've followed several different KBs, and made a few registry and metabase edits. If it's on Microsoft.com or Petri.co.il, there's a good chance I've already tried it. SharePoint 2 had been installed, but never put into production. I confirmed that NTAuthenticationProviders is Negotiate,NTLM. Rather than attempt to describe everything, I'll answer specific questions if anyone wants... Anything obvious that I might be overlooking? Eddy -- Everquick Internet - http://www.everquick.net/ A division of Brotsman Dreger, Inc. - http://www.brotsman.com/ Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita DO NOT send mail to the following addresses: [EMAIL PROTECTED] -*- [EMAIL PROTECTED] -*- [EMAIL PROTECTED] Sending mail to spambait addresses is a great way to get blocked. Ditto for broken OOO autoresponders and foolish AV software backscatter. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Exchange 2007 and SSL certs for internal and external use
Damn MS and their stupid .local crap!! On Tue, May 13, 2008 at 11:26 AM, Michael B. Smith [EMAIL PROTECTED] wrote: Interestingly, I just installed SBS 2003 R2 for a new customer yesterday, and the SBS installation wizard actually suggested .local! I was surprised. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com http://theessentialexchange.com/ *From:* Don Ely [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 11:47 AM *To:* MS-Exchange Admin Issues *Subject:* Re: Exchange 2007 and SSL certs for internal and external use Why .local? On Tue, May 13, 2008 at 8:43 AM, Oliver Marshall [EMAIL PROTECTED] wrote: We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? *From:* Sam Cayze [mailto:[EMAIL PROTECTED] *Sent:* 13 May 2008 16:19 *To:* MS-Exchange Admin Issues *Subject:* RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *. domain.com, www.domain.com, domain.com, mail.domain.com, etc. A little more spendy though... -- *From:* Don Ely [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 10:07 AM *To:* MS-Exchange Admin Issues *Subject:* Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one ( mydomain.com) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 and SSL certs for internal and external use
Wasn't it in early MS guidance for 2000 or perhaps it was 2003, that you use .local? The concept of split DNS was relatively new, if I remember correctly. From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:26 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Interestingly, I just installed SBS 2003 R2 for a new customer yesterday, and the SBS installation wizard actually suggested .local! I was surprised. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:47 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Why .local? On Tue, May 13, 2008 at 8:43 AM, Oliver Marshall [EMAIL PROTECTED] wrote: We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 16:19 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *.domain.com http://domain.com/ , www.domain.com http://www.domain.com/ , domain.com http://domain.com/ , mail.domain.com http://mail.domain.com/ , etc. A little more spendy though... From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:07 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com http://mail.mydomain.com/ ). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.com http://mydomain.com/ ) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com http://mail.mydomain.com/ and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Exchange 2007 and SSL certs for internal and external use
I noticed that when R2 first came out. All Domain setups should be like that. Too many dot coms for local domains. M - Original Message - From: Michael B. Smith To: MS-Exchange Admin Issues Sent: Tuesday, May 13, 2008 11:26 AM Subject: RE: Exchange 2007 and SSL certs for internal and external use Interestingly, I just installed SBS 2003 R2 for a new customer yesterday, and the SBS installation wizard actually suggested .local! I was surprised. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:47 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Why .local? On Tue, May 13, 2008 at 8:43 AM, Oliver Marshall [EMAIL PROTECTED] wrote: We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 16:19 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *.domain.com, www.domain.com, domain.com, mail.domain.com, etc. A little more spendy though... -- From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:07 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.com) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
OWA Customization
All- Is there aren article floating around somewhere that discusses customizing the OWA Logon and Logoff pages for 2003? I've seen a few blurbs here and there but haven't found a good one to base my work on. Thank you, _ John Bowles ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Exchange 2007 and SSL certs for internal and external use
yes. .local was MS guidance. On Tue, May 13, 2008 at 2:34 PM, Barsodi.John [EMAIL PROTECTED] wrote: Wasn't it in early MS guidance for 2000 or perhaps it was 2003, that you use .local? The concept of split DNS was relatively new, if I remember correctly. From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:26 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Interestingly, I just installed SBS 2003 R2 for a new customer yesterday, and the SBS installation wizard actually suggested .local! I was surprised. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:47 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Why .local? On Tue, May 13, 2008 at 8:43 AM, Oliver Marshall [EMAIL PROTECTED] wrote: We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 16:19 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *.domain.com, www.domain.com, domain.com, mail.domain.com, etc. A little more spendy though... From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:07 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.com) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com and attach a correct cert to both. Can this be done ? Olly -- ME2 ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: OWA Customization
Always the smart ass :) _ John Bowles - Original Message From: Kevin Miller [EMAIL PROTECTED] To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tuesday, May 13, 2008 3:17:15 PM Subject: RE: OWA Customization Yes there are some.. Keep looking = ] ~Kevinm WLKMMAS powered by 3Sharp, Always WLKMMAS What is your Zombie Plan? -Original Message- From: JB [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 12:11 PM To: MS-Exchange Admin Issues Subject: OWA Customization All- Is there aren article floating around somewhere that discusses customizing the OWA Logon and Logoff pages for 2003? I've seen a few blurbs here and there but haven't found a good one to base my work on. Thank you, _ John Bowles ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www..sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Exchange 2007 and SSL certs for internal and external use
What is the recommended naming convention then? _ John Bowles - Original Message From: Kevin Miller [EMAIL PROTECTED] To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tuesday, May 13, 2008 3:18:14 PM Subject: RE: Exchange 2007 and SSL certs for internal and external use Somewhere, but we retracted that after a short period of time… ~Kevinm WLKMMAS powered by 3Sharp, Always WLKMMAS What is your Zombie Plan? From:Barsodi.John [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:35 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Wasn’t it in early MS guidance for 2000 or perhaps it was 2003, that you use .local? The concept of split DNS was relatively new, if I remember correctly. From:Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:26 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Interestingly, I just installed SBS 2003 R2 for a new customer yesterday, and the SBS installation wizard actually suggested .local! I was surprised. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From:Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:47 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Why .local? On Tue, May 13, 2008 at 8:43 AM, Oliver Marshall [EMAIL PROTECTED] wrote: We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? From:Sam Cayze [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 16:19 To: MS-Exchange Admin Issues Subject:RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *.domain.com, www.domain.com, domain.com, mail.domain.com, etc. A little more spendy though... From:Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:07 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.com) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: ActiveSync on WM driving me nuts
CF Date: Tue, 13 May 2008 10:52:46 -0400 CF From: Carol Fee CF If I remember correctly, this is a cert issue. Specifically, you do CF not have the root cert for the server which issued the cert for the CF Exchange FE installed on the device. You need to install this, not CF the FE cert. That doesn't make sense. The problem occurs regardless of whether the WM device uses SSL or not... and a client-side problem shouldn't trigger a 500 in IIS. Eddy -- Everquick Internet - http://www.everquick.net/ A division of Brotsman Dreger, Inc. - http://www.brotsman.com/ Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita DO NOT send mail to the following addresses: [EMAIL PROTECTED] -*- [EMAIL PROTECTED] -*- [EMAIL PROTECTED] Sending mail to spambait addresses is a great way to get blocked. Ditto for broken OOO autoresponders and foolish AV software backscatter. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: ActiveSync on WM driving me nuts
MBS Date: Tue, 13 May 2008 14:30:07 -0400 MBS From: Michael B. Smith MBS Did you look on MY blog? I've two or three posts on my experiences MBS with debugging this error. They may, or may not, duplicate other MBS content you can find. No, I didn't. Thanks for drawing my attention to it. I'll take a peek. Thanks! Eddy -- Everquick Internet - http://www.everquick.net/ A division of Brotsman Dreger, Inc. - http://www.brotsman.com/ Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita DO NOT send mail to the following addresses: [EMAIL PROTECTED] -*- [EMAIL PROTECTED] -*- [EMAIL PROTECTED] Sending mail to spambait addresses is a great way to get blocked. Ditto for broken OOO autoresponders and foolish AV software backscatter. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: iphone and corporate email
the FW upgrade to 2.0 applies to all current Iphones models. That is the one that will bring full active sync on Exchange to the Iphone. From: Martin Blackstone [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:19 PM To: MS-Exchange Admin Issues Subject: RE: iphone and corporate email I believe there will be an upgrade, but better to ask of some iPhone pros. From: Joe Fox [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 7:04 AM To: MS-Exchange Admin Issues Subject: Re: iphone and corporate email Will older iPhones be able to be upgraded to 2.0? Or is this a forklift upgrade? Thanks. Joe On Tue, May 13, 2008 at 9:49 AM, Martin Blackstone [EMAIL PROTECTED] wrote: Here is my iPhone macro: First read this: http://msexchangeteam.com/archive/2007/07/10/446015.aspx Email only. No calendar, contacts, notes, etc. Just email. Next you need to configure IMAP on Exchange and open up the ports in Exchange. I would suggest IMAP over SSL for security. Here is a nice link: http://www.azaleos.com/blog/index.php?q=node/38 Finally configure the iPhone. If you want full blown ActiveSync, wait for iPhone 2.0 (due around June/July) From: Administrator [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 6:35 AM To: MS-Exchange Admin Issues Subject: iphone and corporate email Can anyone point me in the right direction on how to configure an iphone to work with my corporate email (if it is possible)? I am running Exchange 2007 SP1. We are currently using Blackberry devices, but the new boss has an existing iphone he wants to use. Thanks in advance. Jonathan Jenkins -- Joe Fox Systems/Network Administrator Mobile# (716) 846-9308 http://www.linkedin.com/in/josephfoxjr The information contained in this e-mail message, including any attached files, is intended only for the personal and confidential use of the recipient(s) named above. If you are not the intended recipient be advised that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone at 716-846-9308 or by return e-mail. _ 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. _ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Failover Product..
Going in a completely different direction here. How about Exchange 2007 with CCR? For the price of the upgrade you get your redundancy and the upgrade. From: Chyka, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:50 PM To: MS-Exchange Admin Issues Subject: Exchange Failover Product.. Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated... Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: OWA Customization
I did answer your question... ~Kevinm WLKMMAS powered by 3Sharp, Always WLKMMAS What is your Zombie Plan? -Original Message- From: JB [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 12:32 PM To: MS-Exchange Admin Issues Subject: Re: OWA Customization Always the smart ass :) _ John Bowles - Original Message From: Kevin Miller [EMAIL PROTECTED] To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tuesday, May 13, 2008 3:17:15 PM Subject: RE: OWA Customization Yes there are some.. Keep looking = ] ~Kevinm WLKMMAS powered by 3Sharp, Always WLKMMAS What is your Zombie Plan? -Original Message- From: JB [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 12:11 PM To: MS-Exchange Admin Issues Subject: OWA Customization All- Is there aren article floating around somewhere that discusses customizing the OWA Logon and Logoff pages for 2003? I've seen a few blurbs here and there but haven't found a good one to base my work on. Thank you, _ John Bowles ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www..sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Failover Product..
We're planning Exchange 2007 with CCR and SCR across data centers, so there :) From: Kennedy, Jim [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:49 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Going in a completely different direction here. How about Exchange 2007 with CCR? For the price of the upgrade you get your redundancy and the upgrade. From: Chyka, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:50 PM To: MS-Exchange Admin Issues Subject: Exchange Failover Product.. Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated... Thanks.. Btw we have a 50mbit mpls connection between sites.. This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: OWA Customization
Hey KM, what's your Zombie plan? Shook -Original Message- From: Kevin Miller [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 4:02 PM To: MS-Exchange Admin Issues Subject: RE: OWA Customization I did answer your question... ~Kevinm WLKMMAS powered by 3Sharp, Always WLKMMAS What is your Zombie Plan? ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: OWA Customization
http://msexchangeteam.com/archive/2006/08/30/428793.aspx Here.. Let me be your Google big boy... ~Kevinm WLKMMAS powered by 3Sharp, Always WLKMMAS What is your Zombie Plan? -Original Message- From: JB [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 12:32 PM To: MS-Exchange Admin Issues Subject: Re: OWA Customization Always the smart ass :) _ John Bowles - Original Message From: Kevin Miller [EMAIL PROTECTED] To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tuesday, May 13, 2008 3:17:15 PM Subject: RE: OWA Customization Yes there are some.. Keep looking = ] ~Kevinm WLKMMAS powered by 3Sharp, Always WLKMMAS What is your Zombie Plan? -Original Message- From: JB [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 12:11 PM To: MS-Exchange Admin Issues Subject: OWA Customization All- Is there aren article floating around somewhere that discusses customizing the OWA Logon and Logoff pages for 2003? I've seen a few blurbs here and there but haven't found a good one to base my work on. Thank you, _ John Bowles ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www..sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Exchange 2007 and SSL certs for internal and external use
It was in 2000 and the stupid MCT's today still teach it as I understand it, but I presume that is because the curriculum probably hasn't changed :P On Tue, May 13, 2008 at 11:34 AM, Barsodi.John [EMAIL PROTECTED] wrote: Wasn't it in early MS guidance for 2000 or perhaps it was 2003, that you use .local? The concept of split DNS was relatively new, if I remember correctly. *From:* Michael B. Smith [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 11:26 AM *To:* MS-Exchange Admin Issues *Subject:* RE: Exchange 2007 and SSL certs for internal and external use Interestingly, I just installed SBS 2003 R2 for a new customer yesterday, and the SBS installation wizard actually suggested .local! I was surprised. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com http://theessentialexchange.com/ *From:* Don Ely [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 11:47 AM *To:* MS-Exchange Admin Issues *Subject:* Re: Exchange 2007 and SSL certs for internal and external use Why .local? On Tue, May 13, 2008 at 8:43 AM, Oliver Marshall [EMAIL PROTECTED] wrote: We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? *From:* Sam Cayze [mailto:[EMAIL PROTECTED] *Sent:* 13 May 2008 16:19 *To:* MS-Exchange Admin Issues *Subject:* RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *. domain.com, www.domain.com, domain.com, mail.domain.com, etc. A little more spendy though... -- *From:* Don Ely [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 10:07 AM *To:* MS-Exchange Admin Issues *Subject:* Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one ( mydomain.com) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
OT: Exchange Failover Product..
I am all about your Direction. Exchange 2007 sounds like a much better solution, no offence to Stu... insert self promotion bit that made me laugh We had a customer ask us for references for an Exchange engagement today. As part of the reference package we sent them an Amazon book list. Out of 5 people on my team, four of us have published more than two books (Mostly about Microsoft Stuff) with our names as the author on them, and the fifth is working to get his first book out with his name on it. Also four of the 5 of us are MVPS. The customer seems to be ok with our references. /insert self promotion made me laugh ~Kevinm WLKMMAS powered by 3Sharphttp://www.3sharp.com/, Always WLKMMAShttp://www.wlkmmas.org/ What is your Zombie Plan? From: Kennedy, Jim [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:49 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Going in a completely different direction here. How about Exchange 2007 with CCR? For the price of the upgrade you get your redundancy and the upgrade. From: Chyka, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:50 PM To: MS-Exchange Admin Issues Subject: Exchange Failover Product.. Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated... Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: OWA Customization
So, you're looking for something better than the Technet article at match #1 here? http://www.google.com/search?q=customize+owa+2003 If that doesn't do it for you, nor any of the other matches, explain what the goals of my work are. More detailed questions = better answers. Carl -Original Message- From: JB [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 3:11 PM To: MS-Exchange Admin Issues Subject: OWA Customization All- Is there aren article floating around somewhere that discusses customizing the OWA Logon and Logoff pages for 2003? I've seen a few blurbs here and there but haven't found a good one to base my work on. Thank you, _ John Bowles ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Failover Product..
Yeah, well, I'm anti-cluster where Exchange is concerned. But all about recommending SCR. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Kevin Miller [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 4:49 PM To: MS-Exchange Admin Issues Subject: OT: Exchange Failover Product.. I am all about your Direction. Exchange 2007 sounds like a much better solution, no offence to Stu. insert self promotion bit that made me laugh We had a customer ask us for references for an Exchange engagement today. As part of the reference package we sent them an Amazon book list. Out of 5 people on my team, four of us have published more than two books (Mostly about Microsoft Stuff) with our names as the author on them, and the fifth is working to get his first book out with his name on it. Also four of the 5 of us are MVPS. The customer seems to be ok with our references. /insert self promotion made me laugh ~Kevinm WLKMMAS powered by 3Sharp http://www.3sharp.com/ , Always WLKMMAS http://www.wlkmmas.org/ What is your Zombie Plan? From: Kennedy, Jim [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:49 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Going in a completely different direction here. How about Exchange 2007 with CCR? For the price of the upgrade you get your redundancy and the upgrade. From: Chyka, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:50 PM To: MS-Exchange Admin Issues Subject: Exchange Failover Product.. Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated. Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: OWA Customization
I have a number of plans. My boy and I have spent the last few months working out details. It's been a great exercise in planning for him and I. He keeps wanting to head north because he thinks the Zombies will freeze and become corpsicles, if that does not work he wants to play A-team in the garage and build some massive battle rig with Zombie Mower blades all around it. ~Kevinm WLKMMAS powered by 3Sharp, Always WLKMMAS What is your Zombie Plan? -Original Message- From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:08 PM To: MS-Exchange Admin Issues Subject: RE: OWA Customization Hey KM, what's your Zombie plan? Shook -Original Message- From: Kevin Miller [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 4:02 PM To: MS-Exchange Admin Issues Subject: RE: OWA Customization I did answer your question... ~Kevinm WLKMMAS powered by 3Sharp, Always WLKMMAS What is your Zombie Plan? ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Failover Product..
I've been anti-cluster for a very long time. the only good cluster is a single node -Ed | I have always agreed with him Lately I have been building Clusters and putting VM's on them; I am starting to feel that that is the best way to do it. Your Cluster becomes a hardware pool with redundancy that you can place virtual machines on. You can optimize the hardware pool resource allocation to the virtuals on the fly; adding and removing ram and what not as needed. It makes it very simple to add more hardware to your servers, you just add another cluster node and move the VM to the new hardware, takes minutes in the users eyes. No need to migrate or fiddle with server names and IP address and crap like we have to do on dedicated hardware. ~2000$ for an 8 proc server with 16GB or ram, and ~2000$ for Windows server 2008 enterprise ( comes with 4 VM server cals, for 6k you can run datacenter and have unlimited VM's) to add a node that can support 1-10+ VM's depending on what you need. Well you have to storage in there. I just build a 4TB NAS running open filer ( 8 x 1tb drives in raid 0+1 for I/O) for like 3500$ or something. I am starting to like clusters, just not clusters but I still don't like clustered Exchange ~Kevinm WLKMMAS powered by 3Sharphttp://www.3sharp.com/, Always WLKMMAShttp://www.wlkmmas.org/ What is your Zombie Plan? From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 2:17 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Yeah, well, I'm anti-cluster where Exchange is concerned. But all about recommending SCR. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Kevin Miller [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 4:49 PM To: MS-Exchange Admin Issues Subject: OT: Exchange Failover Product.. I am all about your Direction. Exchange 2007 sounds like a much better solution, no offence to Stu... insert self promotion bit that made me laugh We had a customer ask us for references for an Exchange engagement today. As part of the reference package we sent them an Amazon book list. Out of 5 people on my team, four of us have published more than two books (Mostly about Microsoft Stuff) with our names as the author on them, and the fifth is working to get his first book out with his name on it. Also four of the 5 of us are MVPS. The customer seems to be ok with our references. /insert self promotion made me laugh ~Kevinm WLKMMAS powered by 3Sharphttp://www.3sharp.com/, Always WLKMMAShttp://www.wlkmmas.org/ What is your Zombie Plan? From: Kennedy, Jim [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:49 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Going in a completely different direction here. How about Exchange 2007 with CCR? For the price of the upgrade you get your redundancy and the upgrade. From: Chyka, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:50 PM To: MS-Exchange Admin Issues Subject: Exchange Failover Product.. Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated... Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Failover Product..
Clusters allow a well-managed server farm to go from 99.9% availability to 99.99% availability. Emphasis on well-managed. Those are, quite frankly, few and far between. In most shops that I've seen, clusters actually reduce availability. These days, you can install Exchange, configure it a little bit, set up your backups, and it'll just hum along for you for months and months without requiring you to touch it. Run a patch install at 3am on Sunday morning once a month, and you're done. If you buy good hardware for the server - you'll probably not have to touch it except when a disk needs replacing. And of course, you have SMART/SCSI monitoring, so you know when that happens, you pick up a phone and order a disk, it's hot-swappable and auto-rebuild. Or you have it in inventory because e-mail is a critical service. You're done. No frickin' way you get off that easy with a cluster. It requires a LOT more care and feeding. In certain (very rare) circumstances, I can believe that that expert care and feeding is worth 0.09% increased availability. But honestly, I don't think I've EVER seen one. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Barsodi.John [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 5:32 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. I can understand Anti-SCC, but why would you be Anti-CCR? From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 2:17 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Yeah, well, I'm anti-cluster where Exchange is concerned. But all about recommending SCR. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Kevin Miller [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 4:49 PM To: MS-Exchange Admin Issues Subject: OT: Exchange Failover Product.. I am all about your Direction. Exchange 2007 sounds like a much better solution, no offence to Stu. insert self promotion bit that made me laugh We had a customer ask us for references for an Exchange engagement today. As part of the reference package we sent them an Amazon book list. Out of 5 people on my team, four of us have published more than two books (Mostly about Microsoft Stuff) with our names as the author on them, and the fifth is working to get his first book out with his name on it. Also four of the 5 of us are MVPS. The customer seems to be ok with our references. /insert self promotion made me laugh ~Kevinm WLKMMAS powered by 3Sharp http://www.3sharp.com/ , Always WLKMMAS http://www.wlkmmas.org/ What is your Zombie Plan? From: Kennedy, Jim [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:49 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Going in a completely different direction here. How about Exchange 2007 with CCR? For the price of the upgrade you get your redundancy and the upgrade. From: Chyka, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:50 PM To: MS-Exchange Admin Issues Subject: Exchange Failover Product.. Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated. Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Failover Product..
I 100% agree with that.. ~Kevinm WLKMMAS powered by 3Sharphttp://www.3sharp.com/, Always WLKMMAShttp://www.wlkmmas.org/ What is your Zombie Plan? From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 2:51 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Clusters allow a well-managed server farm to go from 99.9% availability to 99.99% availability. Emphasis on well-managed. Those are, quite frankly, few and far between. In most shops that I've seen, clusters actually reduce availability. These days, you can install Exchange, configure it a little bit, set up your backups, and it'll just hum along for you for months and months without requiring you to touch it. Run a patch install at 3am on Sunday morning once a month, and you're done. If you buy good hardware for the server - you'll probably not have to touch it except when a disk needs replacing. And of course, you have SMART/SCSI monitoring, so you know when that happens, you pick up a phone and order a disk, it's hot-swappable and auto-rebuild. Or you have it in inventory because e-mail is a critical service. You're done. No frickin' way you get off that easy with a cluster. It requires a LOT more care and feeding. In certain (very rare) circumstances, I can believe that that expert care and feeding is worth 0.09% increased availability. But honestly, I don't think I've EVER seen one. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Barsodi.John [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 5:32 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. I can understand Anti-SCC, but why would you be Anti-CCR? From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 2:17 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Yeah, well, I'm anti-cluster where Exchange is concerned. But all about recommending SCR. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Kevin Miller [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 4:49 PM To: MS-Exchange Admin Issues Subject: OT: Exchange Failover Product.. I am all about your Direction. Exchange 2007 sounds like a much better solution, no offence to Stu... insert self promotion bit that made me laugh We had a customer ask us for references for an Exchange engagement today. As part of the reference package we sent them an Amazon book list. Out of 5 people on my team, four of us have published more than two books (Mostly about Microsoft Stuff) with our names as the author on them, and the fifth is working to get his first book out with his name on it. Also four of the 5 of us are MVPS. The customer seems to be ok with our references. /insert self promotion made me laugh ~Kevinm WLKMMAS powered by 3Sharphttp://www.3sharp.com/, Always WLKMMAShttp://www.wlkmmas.org/ What is your Zombie Plan? From: Kennedy, Jim [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:49 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Going in a completely different direction here. How about Exchange 2007 with CCR? For the price of the upgrade you get your redundancy and the upgrade. From: Chyka, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:50 PM To: MS-Exchange Admin Issues Subject: Exchange Failover Product.. Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated... Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Failover Product..
Saving rant/info post for later usage with management types that read CIO/Airplane magazines ;) Thanks troy From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 2:51 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Clusters allow a well-managed server farm to go from 99.9% availability to 99.99% availability. Emphasis on well-managed. Those are, quite frankly, few and far between. In most shops that I've seen, clusters actually reduce availability. These days, you can install Exchange, configure it a little bit, set up your backups, and it'll just hum along for you for months and months without requiring you to touch it. Run a patch install at 3am on Sunday morning once a month, and you're done. If you buy good hardware for the server - you'll probably not have to touch it except when a disk needs replacing. And of course, you have SMART/SCSI monitoring, so you know when that happens, you pick up a phone and order a disk, it's hot-swappable and auto-rebuild. Or you have it in inventory because e-mail is a critical service. You're done. No frickin' way you get off that easy with a cluster. It requires a LOT more care and feeding. In certain (very rare) circumstances, I can believe that that expert care and feeding is worth 0.09% increased availability. But honestly, I don't think I've EVER seen one. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Barsodi.John [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 5:32 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. I can understand Anti-SCC, but why would you be Anti-CCR? From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 2:17 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Yeah, well, I'm anti-cluster where Exchange is concerned. But all about recommending SCR. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Kevin Miller [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 4:49 PM To: MS-Exchange Admin Issues Subject: OT: Exchange Failover Product.. I am all about your Direction. Exchange 2007 sounds like a much better solution, no offence to Stu... insert self promotion bit that made me laugh We had a customer ask us for references for an Exchange engagement today. As part of the reference package we sent them an Amazon book list. Out of 5 people on my team, four of us have published more than two books (Mostly about Microsoft Stuff) with our names as the author on them, and the fifth is working to get his first book out with his name on it. Also four of the 5 of us are MVPS. The customer seems to be ok with our references. /insert self promotion made me laugh ~Kevinm WLKMMAS powered by 3Sharphttp://www.3sharp.com/, Always WLKMMAShttp://www.wlkmmas.org/ What is your Zombie Plan? From: Kennedy, Jim [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:49 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Going in a completely different direction here. How about Exchange 2007 with CCR? For the price of the upgrade you get your redundancy and the upgrade. From: Chyka, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:50 PM To: MS-Exchange Admin Issues Subject: Exchange Failover Product.. Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated... Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Failover Product..
Interesting take and completely understandable. Thanks. From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 2:51 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Clusters allow a well-managed server farm to go from 99.9% availability to 99.99% availability. Emphasis on well-managed. Those are, quite frankly, few and far between. In most shops that I've seen, clusters actually reduce availability. These days, you can install Exchange, configure it a little bit, set up your backups, and it'll just hum along for you for months and months without requiring you to touch it. Run a patch install at 3am on Sunday morning once a month, and you're done. If you buy good hardware for the server - you'll probably not have to touch it except when a disk needs replacing. And of course, you have SMART/SCSI monitoring, so you know when that happens, you pick up a phone and order a disk, it's hot-swappable and auto-rebuild. Or you have it in inventory because e-mail is a critical service. You're done. No frickin' way you get off that easy with a cluster. It requires a LOT more care and feeding. In certain (very rare) circumstances, I can believe that that expert care and feeding is worth 0.09% increased availability. But honestly, I don't think I've EVER seen one. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Barsodi.John [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 5:32 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. I can understand Anti-SCC, but why would you be Anti-CCR? From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 2:17 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Yeah, well, I'm anti-cluster where Exchange is concerned. But all about recommending SCR. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Kevin Miller [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 4:49 PM To: MS-Exchange Admin Issues Subject: OT: Exchange Failover Product.. I am all about your Direction. Exchange 2007 sounds like a much better solution, no offence to Stu... insert self promotion bit that made me laugh We had a customer ask us for references for an Exchange engagement today. As part of the reference package we sent them an Amazon book list. Out of 5 people on my team, four of us have published more than two books (Mostly about Microsoft Stuff) with our names as the author on them, and the fifth is working to get his first book out with his name on it. Also four of the 5 of us are MVPS. The customer seems to be ok with our references. /insert self promotion made me laugh ~Kevinm WLKMMAS powered by 3Sharp http://www.3sharp.com/ , Always WLKMMAS http://www.wlkmmas.org/ What is your Zombie Plan? From: Kennedy, Jim [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:49 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Going in a completely different direction here. How about Exchange 2007 with CCR? For the price of the upgrade you get your redundancy and the upgrade. From: Chyka, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:50 PM To: MS-Exchange Admin Issues Subject: Exchange Failover Product.. Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated... Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Exchange 2007 and SSL certs for internal and external use
Technically, whatever you want. Personally, I stick with a .com, .net. or a .org... On Tue, May 13, 2008 at 12:32 PM, JB [EMAIL PROTECTED] wrote: What is the recommended naming convention then? _ John Bowles - Original Message From: Kevin Miller [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 3:18:14 PM Subject: RE: Exchange 2007 and SSL certs for internal and external use Somewhere, but we retracted that after a short period of time… ~Kevinm *WLKMMAS* powered by 3Sharp http://www.3sharp.com/, Always WLKMMAShttp://www.wlkmmas.org/What is your Zombie Plan? *From:* Barsodi.John [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 11:35 AM *To:* MS-Exchange Admin Issues *Subject:* RE: Exchange 2007 and SSL certs for internal and external use Wasn't it in early MS guidance for 2000 or perhaps it was 2003, that you use .local? The concept of split DNS was relatively new, if I remember correctly. *From:* Michael B. Smith [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 11:26 AM *To:* MS-Exchange Admin Issues *Subject:* RE: Exchange 2007 and SSL certs for internal and external use Interestingly, I just installed SBS 2003 R2 for a new customer yesterday, and the SBS installation wizard actually suggested .local! I was surprised.. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com http://theessentialexchange.com/ *From:* Don Ely [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 11:47 AM *To:* MS-Exchange Admin Issues *Subject:* Re: Exchange 2007 and SSL certs for internal and external use Why .local? On Tue, May 13, 2008 at 8:43 AM, Oliver Marshall [EMAIL PROTECTED] wrote: We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? *From:* Sam Cayze [mailto:[EMAIL PROTECTED] *Sent:* 13 May 2008 16:19 *To:* MS-Exchange Admin Issues *Subject:* RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *. domain.com, www.domain.com, domain.com, mail..domain.comhttp://mail.domain.com/, etc. A little more spendy though... -- *From:* Don Ely [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 10:07 AM *To:* MS-Exchange Admin Issues *Subject:* Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one ( mydomain.com) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Exchange Failover Product..
My current gig has a cluster and I am in process of planning to make it cluster-no-more. I hate managing the fscker... Totally not worth it, but Dell suckered the company into thinking they needed it... On Tue, May 13, 2008 at 2:50 PM, Michael B. Smith [EMAIL PROTECTED] wrote: Clusters allow a well-managed server farm to go from 99.9% availability to 99.99% availability. Emphasis on well-managed. Those are, quite frankly, few and far between. In most shops that I've seen, clusters actually reduce availability. These days, you can install Exchange, configure it a little bit, set up your backups, and it'll just hum along for you for months and months without requiring you to touch it. Run a patch install at 3am on Sunday morning once a month, and you're done. If you buy good hardware for the server – you'll probably not have to touch it except when a disk needs replacing. And of course, you have SMART/SCSI monitoring, so you know when that happens, you pick up a phone and order a disk, it's hot-swappable and auto-rebuild. Or you have it in inventory because e-mail is a critical service. You're done. No frickin' way you get off that easy with a cluster. It requires a LOT more care and feeding. In certain (very rare) circumstances, I can believe that that expert care and feeding is worth 0.09% increased availability. But honestly, I don't think I've EVER seen one. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com http://theessentialexchange.com/ *From:* Barsodi.John [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 5:32 PM *To:* MS-Exchange Admin Issues *Subject:* RE: Exchange Failover Product.. I can understand Anti-SCC, but why would you be Anti-CCR? *From:* Michael B. Smith [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 2:17 PM *To:* MS-Exchange Admin Issues *Subject:* RE: Exchange Failover Product.. Yeah, well, I'm anti-cluster where Exchange is concerned. But all about recommending SCR. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com http://theessentialexchange.com/ *From:* Kevin Miller [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 4:49 PM *To:* MS-Exchange Admin Issues *Subject:* OT: Exchange Failover Product.. I am all about your Direction. Exchange 2007 sounds like a much better solution, no offence to Stu… insert self promotion bit that made me laugh We had a customer ask us for references for an Exchange engagement today. As part of the reference package we sent them an Amazon book list. Out of 5 people on my team, four of us have published more than two books (Mostly about Microsoft Stuff) with our names as the author on them, and the fifth is working to get his first book out with his name on it. Also four of the 5 of us are MVPS. The customer seems to be ok with our references. /insert self promotion made me laugh ~Kevinm *WLKMMAS* powered by 3Sharp http://www.3sharp.com/, Always WLKMMAShttp://www.wlkmmas.org/What is your Zombie Plan? *From:* Kennedy, Jim [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 11:49 AM *To:* MS-Exchange Admin Issues *Subject:* RE: Exchange Failover Product.. Going in a completely different direction here. How about Exchange 2007 with CCR? For the price of the upgrade you get your redundancy and the upgrade. *From:* Chyka, Robert [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, May 13, 2008 1:50 PM *To:* MS-Exchange Admin Issues *Subject:* Exchange Failover Product.. Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated… Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 and SSL certs for internal and external use
And is recommended by Microsoft: http://technet2.microsoft.com/windowsserver/en/library/4bb9f469-df87-4830-9 6a8-b28ec71bafa91033.mspx?mfr=true Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Kevin Miller [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 4:03 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Not .local.. A registered name is best in my world. ~Kevinm WLKMMAS powered by 3Sharp http://www.3sharp.com/ , Always WLKMMAS http://www.wlkmmas.org/ What is your Zombie Plan? From: JB [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 12:33 PM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use What is the recommended naming convention then? _ John Bowles - Original Message From: Kevin Miller [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 3:18:14 PM Subject: RE: Exchange 2007 and SSL certs for internal and external use Somewhere, but we retracted that after a short period of time. ~Kevinm WLKMMAS powered by 3Sharp http://www.3sharp.com/ , Always WLKMMAS http://www.wlkmmas.org/ What is your Zombie Plan? From: Barsodi.John [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:35 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Wasn't it in early MS guidance for 2000 or perhaps it was 2003, that you use .local? The concept of split DNS was relatively new, if I remember correctly. From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:26 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Interestingly, I just installed SBS 2003 R2 for a new customer yesterday, and the SBS installation wizard actually suggested .local! I was surprised.. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com http://theessentialexchange.com/ From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:47 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Why .local? On Tue, May 13, 2008 at 8:43 AM, Oliver Marshall [EMAIL PROTECTED] wrote: We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 16:19 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *.domain.com http://domain.com/ , www.domain.com http://www.domain.com/ , domain.com http://domain.com/ , mail..domain.com http://mail.domain.com/ , etc. A little more spendy though... _ From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:07 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com http://mail.mydomain.com/ ). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.com http://mydomain.com/ ) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com http://mail.mydomain.com/ and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 and SSL certs for internal and external use
Yes, it was in the early guidance. The VERY earliest guidance was .int - and then that was an oops moment, because that's actually a legal TLD. Then about Win2K release, the guidance was .local, but basically anything that wasn't a TLD; then IANA went and authorized 16 (or so, I don't remember) new TLDs. Then the guidance became - register the domain. Been that way since before 2003 was released. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Barsodi.John [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 2:35 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Wasn't it in early MS guidance for 2000 or perhaps it was 2003, that you use .local? The concept of split DNS was relatively new, if I remember correctly. From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:26 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Interestingly, I just installed SBS 2003 R2 for a new customer yesterday, and the SBS installation wizard actually suggested .local! I was surprised. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:47 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Why .local? On Tue, May 13, 2008 at 8:43 AM, Oliver Marshall [EMAIL PROTECTED] wrote: We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: 13 May 2008 16:19 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *.domain.com http://domain.com/ , www.domain.com http://www.domain.com/ , domain.com http://domain.com/ , mail.domain.com http://mail.domain.com/ , etc. A little more spendy though... _ From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 10:07 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.com http://mail.mydomain.com/ ). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.com http://mydomain.com/ ) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.com http://mail.mydomain.com/ and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 and SSL certs for internal and external use
Researching up a sweet blog post? ~Kevinm WLKMMAS powered by 3Sharphttp://www.3sharp.com/, Always WLKMMAShttp://www.wlkmmas.org/ What is your Zombie Plan? From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 6:05 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Yes, it was in the early guidance. The VERY earliest guidance was .int - and then that was an oops moment, because that's actually a legal TLD. Then about Win2K release, the guidance was .local, but basically anything that wasn't a TLD; then IANA went and authorized 16 (or so, I don't remember) new TLDs... Then the guidance became - register the domain. Been that way since before 2003 was released. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Barsodi.John [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 2:35 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Wasn't it in early MS guidance for 2000 or perhaps it was 2003, that you use .local? The concept of split DNS was relatively new, if I remember correctly. From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:26 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Interestingly, I just installed SBS 2003 R2 for a new customer yesterday, and the SBS installation wizard actually suggested .local! I was surprised. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:47 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Why .local? On Tue, May 13, 2008 at 8:43 AM, Oliver Marshall [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: We looked at a wildcard cert but that wont work as our internal domain is a .local and externally we are a .com. The users connection settings are pre-filled by Outlook 2007. Is this editable in AD so that we are able to change the server FQDN they connect to? From: Sam Cayze [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: 13 May 2008 16:19 To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 and SSL certs for internal and external use Another way might be a 'wildcard certificate'. One that handles *.domain.comhttp://domain.com/, www.domain.comhttp://www.domain.com/, domain.comhttp://domain.com/, mail.domain.comhttp://mail.domain.com/, etc. A little more spendy though... From: Don Ely [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 13, 2008 10:07 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2007 and SSL certs for internal and external use Split DNS On Tue, May 13, 2008 at 7:41 AM, Oliver Marshall [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi chaps, I have an Exchange 2007 server here on which we have setup an SSL certificate (in the name of mail.mydomain.comhttp://mail.mydomain.com/). This works great for users outside using Outlook 2007s Outlook Anywhere feature. However, internal users get a warning stating that the SSL cert name doesn't match the server. It's not the biggest issue, but it's...untidy. What's the best way to handle this? Obviously I can only attach one SSL cert to the Default site in IIS on the Exchange box and the internal domain (mydomain.local) is sufficiently different from the external one (mydomain.comhttp://mydomain.com/) that we can't get an SSL cert to cover both. Is there a way to create a new IIS site that still points at the same exchange folder structure as the current Default Site but that is set to accept a different hostname? That way I could have one site for the internal users hitting blue-server.mydomain.local and one for the external users hitting mail.mydomain.comhttp://mail.mydomain.com/ and attach a correct cert to both. Can this be done ? Olly ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Failover Product..
Expanded a bit to give definitions of clustering and the 9's of uptime. http://theessentialexchange.com/blogs/michael/archive/2008/05/13/clustering -on-exchange-server.aspx Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 5:51 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Clusters allow a well-managed server farm to go from 99.9% availability to 99.99% availability. Emphasis on well-managed. Those are, quite frankly, few and far between. In most shops that I've seen, clusters actually reduce availability. These days, you can install Exchange, configure it a little bit, set up your backups, and it'll just hum along for you for months and months without requiring you to touch it. Run a patch install at 3am on Sunday morning once a month, and you're done. If you buy good hardware for the server - you'll probably not have to touch it except when a disk needs replacing. And of course, you have SMART/SCSI monitoring, so you know when that happens, you pick up a phone and order a disk, it's hot-swappable and auto-rebuild. Or you have it in inventory because e-mail is a critical service. You're done. No frickin' way you get off that easy with a cluster. It requires a LOT more care and feeding. In certain (very rare) circumstances, I can believe that that expert care and feeding is worth 0.09% increased availability. But honestly, I don't think I've EVER seen one. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Barsodi.John [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 5:32 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. I can understand Anti-SCC, but why would you be Anti-CCR? From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 2:17 PM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Yeah, well, I'm anti-cluster where Exchange is concerned. But all about recommending SCR. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Kevin Miller [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 4:49 PM To: MS-Exchange Admin Issues Subject: OT: Exchange Failover Product.. I am all about your Direction. Exchange 2007 sounds like a much better solution, no offence to Stu. insert self promotion bit that made me laugh We had a customer ask us for references for an Exchange engagement today. As part of the reference package we sent them an Amazon book list. Out of 5 people on my team, four of us have published more than two books (Mostly about Microsoft Stuff) with our names as the author on them, and the fifth is working to get his first book out with his name on it. Also four of the 5 of us are MVPS. The customer seems to be ok with our references. /insert self promotion made me laugh ~Kevinm WLKMMAS powered by 3Sharp http://www.3sharp.com/ , Always WLKMMAS http://www.wlkmmas.org/ What is your Zombie Plan? From: Kennedy, Jim [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:49 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Failover Product.. Going in a completely different direction here. How about Exchange 2007 with CCR? For the price of the upgrade you get your redundancy and the upgrade. From: Chyka, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 1:50 PM To: MS-Exchange Admin Issues Subject: Exchange Failover Product.. Hi Everyone, I'm looking for a Exchange 2003 failover software product. Years ago I used Double Take at another job and wanted ot see if that was the way to go. Basically I want to put another exchange server at another site and have that box take over if the main exchange server ever goes down or has issues etc. we currently have only one exchange box. Any help is appreciated. Thanks.. Btw we have a 50mbit mpls connection between sites.. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Associate an external account in Exchange 2k3-reposted
As per MS KB 27 I understand that I must disable the current one but is not clear if assigning permissions is doable from the GUI (mailbox rights) or I must go to command line or programming ! I simply have to associate the mailbox and the old email address to another user in a trusted domain TIA GuidoElia HELPPC ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Associate an external account in Exchange 2k3-reposted
You do this in the Exchange Advanced/Mailbox Rights part of ADUC From: HELP_PC [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 May 2008 3:50 PM To: MS-Exchange Admin Issues Subject: Associate an external account in Exchange 2k3-reposted As per MS KB 27 I understand that I must disable the current one but is not clear if assigning permissions is doable from the GUI (mailbox rights) or I must go to command line or programming ! I simply have to associate the mailbox and the old email address to another user in a trusted domain TIA GuidoElia HELPPC ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
R: Associate an external account in Exchange 2k3-reposted
I thought so but I don't remember where I found that such a thing may product unexpected behaviour . Thanks GuidoElia HELPPC _ Da: Greg Mulholland [mailto:[EMAIL PROTECTED] Inviato: mercoledì 14 maggio 2008 7.53 A: MS-Exchange Admin Issues Oggetto: RE: Associate an external account in Exchange 2k3-reposted You do this in the Exchange Advanced/Mailbox Rights part of ADUC From: HELP_PC [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 May 2008 3:50 PM To: MS-Exchange Admin Issues Subject: Associate an external account in Exchange 2k3-reposted As per MS KB 27 I understand that I must disable the current one but is not clear if assigning permissions is doable from the GUI (mailbox rights) or I must go to command line or programming ! I simply have to associate the mailbox and the old email address to another user in a trusted domain TIA GuidoElia HELPPC ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
