RE: RPC/HTTP Revisited
PEBKAC in the end – needed to enter a different entry in wild card cert for the msstd setting All working From: Duncan Turnbull [mailto:dun...@e-simple.co.nz] Sent: 21 April 2010 18:57 To: MS-Exchange Admin Issues Cc: MS-Exchange Admin Issues Subject: Re: RPC/HTTP Revisited One issue I had with installing a wild card certificate was in iiis expecting a client certificate for the rpc directory Somehow that changed during the certificate installation, I took this requirement off the rpc dir in iis and things came back to life. I found it using the rpc tools for server 2003, otherwise there were no error messages Then for some reason the setting would revert every few hours. Eventually rebooting evrything caused it to stick Good luck Cheers Duncan Sent from my iPhone please excuse the typos On 22/04/2010, at 2:58 AM, Michael B. Smith mich...@smithcons.com wrote: Use 2010. Honestly, I’ve no idea. If 2010 works, then it’s probably part of the security package rework that happened in 2010. Certainly not going to be backported… Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Clayton Doige [mailto:clayton.do...@gmail.com] Sent: Wednesday, April 21, 2010 10:49 AM To: MS-Exchange Admin Issues Subject: Re: RPC/HTTP Revisited OK, tried that, no joy. I'll document the settings in the client in this case: Digital Cert is a wild card and IT throws no errors when trying to connect Account Settings Tab: Mailserver = internal name of mail server (I am on the local LAN) Cached mode unticked username = * - this resolves when clicking check name internally More Settings General Automatically Detect Connection Type Ticked More Settings Security Encryption is ticked Kerberos/NTLM is the logon protocol RPC Proxy Settings https:// (domain name used to connect to webmail - MX record points to Web sense) Mutually Authenticate is ticked - target = msstd:*.webmaildomain Both HTTP connection types are ticked Authentication is set to basic Again, the above works with 2010, but not 2003 Thanks for any pointers Clayton On 21 April 2010 15:41, Michael B. Smith mich...@smithcons.com wrote: Try enabling encryption. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Clayton Doige [mailto:clayton.do...@gmail.com] Sent: Wednesday, April 21, 2010 10:40 AM To: MS-Exchange Admin Issues Subject: Re: RPC/HTTP Revisited directory and referral only come up and both just say connecting, it gets no further and just re-prompts for the password I should add that Outlook 2010 works just fine, but 2003 and 2007 don't On 21 April 2010 15:37, Jay Dale jay.d...@3-gig.com wrote: Are you using Basic or NTLM Authentication? What does outlook /rpcdiag say? Almost all the time when this happens it has either to do with permissions on the virtual directories in IIS or with the ports in the registry. Jay Dale I.T. Manager, 3GiG Mobile: 713.299.2541 Email: jay.d...@3-gig.com Confidentiality Notice: This e-mail, including any attached files, may contain confidential and/or privileged information for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any review, dissemination or copying of this e-mail and attachments, if any, or the information contained herein, is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. From: Clayton Doige [mailto:clayton.do...@gmail.com] Sent: Wednesday, April 21, 2010 9:35 AM To: MS-Exchange Admin Issues Subject: RPC/HTTP Revisited The other day I posted a question regarding rpc/http in an Exchange 2003 environment where the FE nlb cluster Exchange is sitting in a DMZ - turned out that Checkpoint was overriding some of the allow rules with it's smart defense stuff. Have a different problem now. I am on the local network with a fully patched Windows XP virtual machine, and a fully patched installation of Outlook 2003. If I set up a standard user profile and configure it without rpc/http no problems, as soon as I add the exchange proxy settings for rpc Outlook just continually prompts for a password, and goes no further (I am not asking Outlook to remember my password here - I want to have it accept it when I put it in) Any tips on what I am doing wrong here would be greatly appreciated. Clayton -- Regards, Clayton clay...@alsipius.com http://alsipius.com -- Regards, Clayton clay...@alsipius.com http://alsipius.com
Certificate Problem
We had a wildcard certificate that covered our domain expire on 4/17. Our Exchange server does not use this certificate, since it has a UC certificate. Now, when users are not in the office (doesn't happen in the office), Outlook presents a certificate warning mentioning the wildcard cert that has expired. I went to IIS on our Exchange server and verified the only certs installed are the default Exchange cert, and the UC cert - so I'm not sure where this is coming from? Any tips on how to troubleshoot? CONFIDENTIALITY NOTICE: This e-mail message (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorized review, use, disclosure, dissemination, copying, forwarding or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient but do not wish to receive communication through this medium, please so advise the sender immediately.
RE: Certificate Problem
A few thoughts, off the top of my head: IIS isn't authoritative for Exchange. Open the Exchange Management Shell and enter get-ExchangeCertificate and see if the wildcard certificate is listed there. Also, are you using ISA / TMG to publish Exchange? If so, you may have the wildcard cert listed there. Finally, do your users use Autodiscover or are the Outlook profiles manually configured? If manually configured, what do they have for the msstd: value? Two of these can be analyzed by www.testexchangeconnectivity.comhttp://www.testexchangeconnectivity.com. You might try it too. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Derek Rose [mailto:derek.r...@sten-tel.com] Sent: Thursday, April 22, 2010 6:47 AM To: MS-Exchange Admin Issues Subject: Certificate Problem We had a wildcard certificate that covered our domain expire on 4/17. Our Exchange server does not use this certificate, since it has a UC certificate. Now, when users are not in the office (doesn't happen in the office), Outlook presents a certificate warning mentioning the wildcard cert that has expired. I went to IIS on our Exchange server and verified the only certs installed are the default Exchange cert, and the UC cert - so I'm not sure where this is coming from? Any tips on how to troubleshoot? CONFIDENTIALITY NOTICE: This e-mail message (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorized review, use, disclosure, dissemination, copying, forwarding or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient but do not wish to receive communication through this medium, please so advise the sender immediately.
RE: Exchange PF on cluster
You can put the PFs on the cluster. There are some caveats around that if it were a CCR cluster, but they don't apply to a SCC cluster. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Benjamin Zachary - Lists [mailto:li...@levelfive.us] Sent: Wednesday, April 21, 2010 11:52 PM To: MS-Exchange Admin Issues Subject: RE: Exchange PF on cluster These are actual Public Folders for calendars, we have faxing folders routing there and dozens of departments (the PF store is about 50GB). On the cluster side this isn't an actual CCR cluster, I don't think, this is a standard 2 server with DAS attached storage. Only one server is active at any one time. We are about 75% Outlook 2007 and Outlook 2003 is almost phased out, maybe another 30-60 days. -Original Message- From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, April 21, 2010 7:36 PM To: MS-Exchange Admin Issues Subject: RE: Exchange PF on cluster There are several considerations. First, do you actually have real public folders or are you just using the PF database to hold the system folders? Can you answer that question first? Secondly, what versions of Outlook are being used in your environment? Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Benjamin Zachary - Lists [mailto:li...@levelfive.us] Sent: Wednesday, April 21, 2010 7:11 PM To: MS-Exchange Admin Issues Subject: Exchange PF on cluster Currently we have a 2007 active/passive cluster running on 2008 enterprise and it works well. We have a front end server that has been doing hub transport services with, the a/v and anti spam etc. We have recently migrated over to a new spam/av product which is acting as an smtp connector so all mail transactions are simply handed off from the front end server to the connector and vice versa. In our migration process I was asked about putting the Public Folders, which were being stored there and not the cluster, so we can debate on getting rid of that server entirely or converting it to vm, but basically get the public store off it. I poked around and saw some different mentions of problems with doing it, so wanted to know if anyone is doing it successfully. Thanks
Exchange 2010 Gotcha #3 - When The TrustedInstaller - Isn't
FYI: http://bit.ly/c1VVGU http://theessentialexchange.com/blogs/michael/archive/2010/04/22/exchange-2010-gotcha-3.aspx Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com
UC Cert's
All- Just reaching out to everyone here to see what vendor they're using to obtain their UC Certs? And what is the cheapest that you've found? I can't find anything under $1k for a 3 year term. Any suggestions? Thank you, John Bowles
RE: UC Cert's
http://www.digicert.com/unified-communications-ssl-tls.htm Jay Dale I.T. Manager, 3GiG Mobile: 713.299.2541 Email: jay.d...@3-gig.com Confidentiality Notice: This e-mail, including any attached files, may contain confidential and/or privileged information for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any review, dissemination or copying of this e-mail and attachments, if any, or the information contained herein, is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. -Original Message- From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Thursday, April 22, 2010 8:59 AM To: MS-Exchange Admin Issues Subject: UC Cert's All- Just reaching out to everyone here to see what vendor they're using to obtain their UC Certs? And what is the cheapest that you've found? I can't find anything under $1k for a 3 year term. Any suggestions? Thank you, John Bowles
RE: UC Cert's
Certificatesforexchange.com, a GoDaddy reseller run by another Exchange MVP that hangs around here (Simon Butler), is cheaper than GoDaddy themselves. :-) I think it's like USD $70 for a one-year term (five names), so that's well below $1K for three years. I also really like Digicert.com. I used them for my production domain (smithcons.com) and for several customers that wanted something higher assurance than GoDaddy, I think it was around USD $600 for a five-name three-year certificate. Full disclosure: Digicert gives discounts to Exchange and OCS MVPs. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Thursday, April 22, 2010 9:59 AM To: MS-Exchange Admin Issues Subject: UC Cert's All- Just reaching out to everyone here to see what vendor they're using to obtain their UC Certs? And what is the cheapest that you've found? I can't find anything under $1k for a 3 year term. Any suggestions? Thank you, John Bowles
RE: UC Cert's
Have you checked with godaddy.com? ~D~ -Original Message- From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Thursday, April 22, 2010 7:59 AM To: MS-Exchange Admin Issues Subject: UC Cert's All- Just reaching out to everyone here to see what vendor they're using to obtain their UC Certs? And what is the cheapest that you've found? I can't find anything under $1k for a 3 year term. Any suggestions? Thank you, John Bowles
[MALWARE FREE]Error #5.1.1
Hello, I have a client running Exchange Server 2003 and Outlook 2003 who just added a new user with a new email account in Exchange. The client computer is setup to access email via POP3 because this user will be on the road 100% of the time and the administrator does not want to use RPC Over HTTP because of previous issues with it and Exchange 2003. Currently this computer is attached to the corporate network via Ethernet cable while it is being configured and Outlook is configured to use POP3 only. Because of delivery issues he has deleted and recreated the user account and is experiencing the following problem: Email sent to the recipient from outside of the organization to either email address works perfectly. Emails can be sent from the recipient to other Exchange organization recipients without a problem too. Emails sent from a user who is a member of the organization bounces back with a #5.1.1 error on the jsm...@domain.com address. Email sent to a second email address associated with the user john.sm...@domain.com works fine. The preferred email address format is first initial and last name @domain.com. Because the administrator created, deleted, and recreated this domain user account and email account I am wondering this could have created this issue. The error is listed below: From: System Administrator Sent: Thursday, April 22, 2010 9:43 AM To: Mark Bennett Subject: Undeliverable: Test Your message did not reach some or all of the intended recipients. Subject: Test Sent: 4/22/2010 9:43 AM The following recipient(s) cannot be reached: Matthew Schramm on 4/22/2010 9:43 AM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. mail.domain.com #5.1.1 Any suggestions would be greatly appreciated. Thank you, Chris Chris Knieriem Potomac Computer Care 920 National Highway Cumberland, MD 21502 301-777-3914 cknier...@pccareonline.com Contact Potomac Computer Care for a SPAM and MALWARE firewall to protect your business email from threats.
RE: Error #5.1.1
Check the internal senders, are they using Outlooks 'auto complete' to address the message or grabbing them from the address book. The former will probably be grabbing the old account while the latter would grab the new one. Delete the offending entry in the senders outlook auto complete. -Original Message- From: Chris Knieriem [mailto:cknier...@pccareonline.com] Sent: Thursday, April 22, 2010 11:10 AM To: MS-Exchange Admin Issues Subject: [MALWARE FREE]Error #5.1.1 Hello, I have a client running Exchange Server 2003 and Outlook 2003 who just added a new user with a new email account in Exchange. The client computer is setup to access email via POP3 because this user will be on the road 100% of the time and the administrator does not want to use RPC Over HTTP because of previous issues with it and Exchange 2003. Currently this computer is attached to the corporate network via Ethernet cable while it is being configured and Outlook is configured to use POP3 only. Because of delivery issues he has deleted and recreated the user account and is experiencing the following problem: Email sent to the recipient from outside of the organization to either email address works perfectly. Emails can be sent from the recipient to other Exchange organization recipients without a problem too. Emails sent from a user who is a member of the organization bounces back with a #5.1.1 error on the jsm...@domain.com address. Email sent to a second email address associated with the user john.sm...@domain.com works fine. The preferred email address format is first initial and last name @domain.com. Because the administrator created, deleted, and recreated this domain user account and email account I am wondering this could have created this issue. The error is listed below: From: System Administrator Sent: Thursday, April 22, 2010 9:43 AM To: Mark Bennett Subject: Undeliverable: Test Your message did not reach some or all of the intended recipients. Subject: Test Sent: 4/22/2010 9:43 AM The following recipient(s) cannot be reached: Matthew Schramm on 4/22/2010 9:43 AM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. mail.domain.com #5.1.1 Any suggestions would be greatly appreciated. Thank you, Chris Chris Knieriem Potomac Computer Care 920 National Highway Cumberland, MD 21502 301-777-3914 cknier...@pccareonline.com Contact Potomac Computer Care for a SPAM and MALWARE firewall to protect your business email from threats.
RE: Renamed conference room (resource calendar) still shows old name
James: By removing from People's Calendars do you mean right click and choose DELETE. I am a little nervous about trying this since that command in the my calendars right above there actually deletes the folder containing the calendar. Tom From: James Winzenz [mailto:james.winz...@hotmail.com] Sent: Wednesday, April 21, 2010 6:21 PM To: MS-Exchange Admin Issues Subject: RE: Renamed conference room (resource calendar) still shows old name I'll bite. This is the same behavior you see if you rename a user in AD/Exchange - Outlook does not reflect the new name unless you update their profile, even though the address book shows the correct entry. Removing and re-adding the shared calendar in their list of People's Calendars should allow them to re-add it with the new name - it will not delete the actual calendar. Thanks, James Winzenz Subject: RE: Renamed conference room (resource calendar) still shows old name Date: Wed, 21 Apr 2010 17:15:05 -0500 From: tom.alver...@ngc.com To: exchangelist@lyris.sunbelt-software.com cricket noise ... cricket noise Bueller? Anybody? From: Alverson, Tom (Xetron) [mailto:tom.alver...@ngc.com] Sent: Tuesday, April 20, 2010 4:46 PM To: MS-Exchange Admin Issues Subject: Renamed conference room (resource calendar) still shows old name I have a few conference rooms that have mailboxes on an Exchange 2003 server for resource (calendar) scheduling. Some of the rooms have moved so I needed to change the names of the accounts a little. Despite changing the display name in AD, the displayed name on Outlook 2007 is still the old name. If a user who had never opened the calendar opens it now they will get the new name. Any user who had previously opened the calendar still gets the old name, even if they log into a brand new computer with Outlook 2007 (so the setting is not in a user profile, or an exchange profile on the local computer it must be stored on the server somehow). The old name is still shown in the People's Calendars on the left and also on the tab above the calendar itself. I was tempted to delete the calendar from the list of People's Calendars on the left side of Outlook but it looks like that might actually delete the whole calendar. I can right click on that list and choose rename and put any name in there I want (Including the new name). Is there some good way to fix this problem short of exporting all the calendar data and creating a whole new mailbox with the new name? Tom Hotmail is redefining busy with tools for the New Busy. Get more from your inbox. See how. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL :ON:WL:en-US:WM_HMP:042010_2
Re: Renamed conference room (resource calendar) still shows old name
You cannot delete a mailbox just by deleting the calendar in Outlook, that is only removing it from their Outlook. To delete a calendar/mailbox you must use ADUC and ESM. If you still don't believe us, then you can go the manual route in Outlook. Go to Tools/Account Settings, Double click on Microsoft Exchange Server, then select the More Settings button at the bottom right, then click on the Advanced tab, and remove it from the Mailboxes section. On Thu, Apr 22, 2010 at 10:23 AM, Alverson, Tom (Xetron) tom.alver...@ngc.com wrote: James: By “removing” from “People’s Calendars” do you mean right click and choose “DELETE”. I am a little nervous about trying this since that command in the “my calendars” right above there actually deletes the folder containing the calendar. Tom *From:* James Winzenz [mailto:james.winz...@hotmail.com] *Sent:* Wednesday, April 21, 2010 6:21 PM *To:* MS-Exchange Admin Issues *Subject:* RE: Renamed conference room (resource calendar) still shows old name I'll bite. This is the same behavior you see if you rename a user in AD/Exchange - Outlook does not reflect the new name unless you update their profile, even though the address book shows the correct entry. Removing and re-adding the shared calendar in their list of People's Calendars should allow them to re-add it with the new name - it will not delete the actual calendar. Thanks, James Winzenz -- Subject: RE: Renamed conference room (resource calendar) still shows old name Date: Wed, 21 Apr 2010 17:15:05 -0500 From: tom.alver...@ngc.com To: exchangelist@lyris.sunbelt-software.com cricket noise ……. cricket noise Bueller? Anybody? *From:* Alverson, Tom (Xetron) [mailto:tom.alver...@ngc.com] *Sent:* Tuesday, April 20, 2010 4:46 PM *To:* MS-Exchange Admin Issues *Subject:* Renamed conference room (resource calendar) still shows old name I have a few conference rooms that have mailboxes on an Exchange 2003 server for resource (calendar) scheduling. Some of the rooms have moved so I needed to change the names of the accounts a little. Despite changing the display name in AD, the displayed name on Outlook 2007 is still the old name. If a user who had never opened the calendar opens it now they will get the new name. Any user who had previously opened the calendar still gets the old name, even if they log into a brand new computer with Outlook 2007 (so the setting is not in a user profile, or an exchange profile on the local computer it must be stored on the server somehow). The old name is still shown in the “People’s Calendars” on the left and also on the tab above the calendar itself. I was tempted to “delete” the calendar from the list of “People’s Calendars” on the left side of Outlook but it looks like that might actually delete the whole calendar. I can right click on that list and choose “rename” and put any name in there I want (Including the new name). Is there some good way to fix this problem short of exporting all the calendar data and creating a whole new mailbox with the new name? Tom -- Hotmail is redefining busy with tools for the New Busy. Get more from your inbox. See how.http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2 -- Sherry Abercrombie Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clarke
Outlook Anti-Phishing Filters
Is there any way to determine which links in an email triggered the anti phishing filters in Outlook? We have had several emails coming in from consultants that have been flagged as suspicious therefore disabling all links. Being that there are multiple links in these emails, it would be nice to know which link(s) are triggering the filter. Thanks, Bob
RE: Renamed conference room (resource calendar) still shows old name
I wasn't worried about deleting the whole mailbox, I was just worried that instead of just deleting the shortcut to that resource calendar, that it might delete the folder itself of the contents of the folder (since I have full permissions to that folder). From: Sherry Abercrombie [mailto:saber...@gmail.com] Sent: Thursday, April 22, 2010 11:39 AM To: MS-Exchange Admin Issues Subject: Re: Renamed conference room (resource calendar) still shows old name You cannot delete a mailbox just by deleting the calendar in Outlook, that is only removing it from their Outlook. To delete a calendar/mailbox you must use ADUC and ESM. If you still don't believe us, then you can go the manual route in Outlook. Go to Tools/Account Settings, Double click on Microsoft Exchange Server, then select the More Settings button at the bottom right, then click on the Advanced tab, and remove it from the Mailboxes section. On Thu, Apr 22, 2010 at 10:23 AM, Alverson, Tom (Xetron) tom.alver...@ngc.com wrote: James: By removing from People's Calendars do you mean right click and choose DELETE. I am a little nervous about trying this since that command in the my calendars right above there actually deletes the folder containing the calendar. Tom From: James Winzenz [mailto:james.winz...@hotmail.com] Sent: Wednesday, April 21, 2010 6:21 PM To: MS-Exchange Admin Issues Subject: RE: Renamed conference room (resource calendar) still shows old name I'll bite. This is the same behavior you see if you rename a user in AD/Exchange - Outlook does not reflect the new name unless you update their profile, even though the address book shows the correct entry. Removing and re-adding the shared calendar in their list of People's Calendars should allow them to re-add it with the new name - it will not delete the actual calendar. Thanks, James Winzenz Subject: RE: Renamed conference room (resource calendar) still shows old name Date: Wed, 21 Apr 2010 17:15:05 -0500 From: tom.alver...@ngc.com To: exchangelist@lyris.sunbelt-software.com cricket noise ... cricket noise Bueller? Anybody? From: Alverson, Tom (Xetron) [mailto:tom.alver...@ngc.com] Sent: Tuesday, April 20, 2010 4:46 PM To: MS-Exchange Admin Issues Subject: Renamed conference room (resource calendar) still shows old name I have a few conference rooms that have mailboxes on an Exchange 2003 server for resource (calendar) scheduling. Some of the rooms have moved so I needed to change the names of the accounts a little. Despite changing the display name in AD, the displayed name on Outlook 2007 is still the old name. If a user who had never opened the calendar opens it now they will get the new name. Any user who had previously opened the calendar still gets the old name, even if they log into a brand new computer with Outlook 2007 (so the setting is not in a user profile, or an exchange profile on the local computer it must be stored on the server somehow). The old name is still shown in the People's Calendars on the left and also on the tab above the calendar itself. I was tempted to delete the calendar from the list of People's Calendars on the left side of Outlook but it looks like that might actually delete the whole calendar. I can right click on that list and choose rename and put any name in there I want (Including the new name). Is there some good way to fix this problem short of exporting all the calendar data and creating a whole new mailbox with the new name? Tom Hotmail is redefining busy with tools for the New Busy. Get more from your inbox. See how. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL :ON:WL:en-US:WM_HMP:042010_2 -- Sherry Abercrombie Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clarke
RE: Renamed conference room (resource calendar) still shows old name
Nope, deleting a calendar from People's Calendars will not delete the actual calendar itself. I have done it many times. It just removes it from the list of shared calendars you have open. Thanks, James Winzenz Subject: RE: Renamed conference room (resource calendar) still shows old name Date: Thu, 22 Apr 2010 11:32:15 -0500 From: tom.alver...@ngc.com To: exchangelist@lyris.sunbelt-software.com I wasn’t worried about deleting the whole mailbox, I was just worried that instead of just deleting the “shortcut” to that resource calendar, that it might delete the folder itself of the contents of the folder (since I have full permissions to that folder). From: Sherry Abercrombie [mailto:saber...@gmail.com] Sent: Thursday, April 22, 2010 11:39 AM To: MS-Exchange Admin Issues Subject: Re: Renamed conference room (resource calendar) still shows old name You cannot delete a mailbox just by deleting the calendar in Outlook, that is only removing it from their Outlook. To delete a calendar/mailbox you must use ADUC and ESM. If you still don't believe us, then you can go the manual route in Outlook. Go to Tools/Account Settings, Double click on Microsoft Exchange Server, then select the More Settings button at the bottom right, then click on the Advanced tab, and remove it from the Mailboxes section. On Thu, Apr 22, 2010 at 10:23 AM, Alverson, Tom (Xetron) tom.alver...@ngc.com wrote: James: By “removing” from “People’s Calendars” do you mean right click and choose “DELETE”. I am a little nervous about trying this since that command in the “my calendars” right above there actually deletes the folder containing the calendar. Tom From: James Winzenz [mailto:james.winz...@hotmail.com] Sent: Wednesday, April 21, 2010 6:21 PM To: MS-Exchange Admin Issues Subject: RE: Renamed conference room (resource calendar) still shows old name I'll bite. This is the same behavior you see if you rename a user in AD/Exchange - Outlook does not reflect the new name unless you update their profile, even though the address book shows the correct entry. Removing and re-adding the shared calendar in their list of People's Calendars should allow them to re-add it with the new name - it will not delete the actual calendar. Thanks, James Winzenz Subject: RE: Renamed conference room (resource calendar) still shows old name Date: Wed, 21 Apr 2010 17:15:05 -0500 From: tom.alver...@ngc.com To: exchangelist@lyris.sunbelt-software.com cricket noise ……. cricket noise Bueller? Anybody? From: Alverson, Tom (Xetron) [mailto:tom.alver...@ngc.com] Sent: Tuesday, April 20, 2010 4:46 PM To: MS-Exchange Admin Issues Subject: Renamed conference room (resource calendar) still shows old name I have a few conference rooms that have mailboxes on an Exchange 2003 server for resource (calendar) scheduling. Some of the rooms have moved so I needed to change the names of the accounts a little. Despite changing the display name in AD, the displayed name on Outlook 2007 is still the old name. If a user who had never opened the calendar opens it now they will get the new name. Any user who had previously opened the calendar still gets the old name, even if they log into a brand new computer with Outlook 2007 (so the setting is not in a user profile, or an exchange profile on the local computer it must be stored on the server somehow). The old name is still shown in the “People’s Calendars” on the left and also on the tab above the calendar itself. I was tempted to “delete” the calendar from the list of “People’s Calendars” on the left side of Outlook but it looks like that might actually delete the whole calendar. I can right click on that list and choose “rename” and put any name in there I want (Including the new name). Is there some good way to fix this problem short of exporting all the calendar data and creating a whole new mailbox with the new name? Tom Hotmail is redefining busy with tools for the New Busy. Get more from your inbox. See how. -- Sherry Abercrombie Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clarke _ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccountocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
RE: Two questions - Exchange 2003 2010
Unfortunately there seems to be some other issue. We simply can't get mail flowing from EXCH2003 to EXCH2010. It's obviously some sort of communication issue since the Public Folders aren't replicating either. The various settings in the default receive connector look correct. I've verified that port 25 on EXCH2010 is open to EXCH2003, but still no go. I've read some good documents on the various post-installations steps that should be performed and we've completed all of them. We may redo our test installation and see if we have better results. I guess this is why we set up test environments before tackling the real thing... From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-21-10 10:14 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Well, you've identified the problem. You shouldn't have disabled the default receive connector. If you take a look at it, you'll see on the Permission Groups tab, that Legacy Exchange Servers is one of the options. Exchange servers speak to each other using a number of extensions to the SMTP protocol. Those extensions are only allowed when you enable the permissions. The default receive connector allows those permissions from Exchange servers (2007/2010) and legacy Exchange servers (2003). However, the Internet receive connector should only enable anonymous. Generally speaking, most people just enable the anonymous permissions on the default receive connector so they can get by with a single connector. And to answer your other question - Outlook and Exchange preferentially communicate using MAPI, not SMTP. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Wednesday, April 21, 2010 8:45 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 I spoke too soon. The change allowed a manual telnet session to work, but mail initiated from Outlook still gets hung up. Does Exchange use standard SMTP/port 25 protocol for inter-Exchange email transfers, or does it use something different? From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: April-21-10 9:06 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 We did run the command but everything looked ok, at least to us. The Get-receiveconnector has so much information it's not entirely easy to decipher, this being our first Exchange 2010 server. I think I have narrowed down the problem though. When I tried a manual mail session using telnet exch2010 25 from exch2003, when I give the mail from:usern...@acadiau.ca, I get the error 530 5.7.1 Client was not authenticated. That gave me the clue I needed to at least find a workaround. During the 2010 install, a Receive connector was created in the Server Configuration Hub Transport section for handling mail coming from EXCH2003. I disabled that connector so that mail coming from exch2003 would arrive using the SMTP connector I had created for mail coming from the Internet. Since that one had no authentication requirments that solved the connectivity problem for mail coming from exch2003. That brings up another question. Should there be a separate Receive Connector for Exch2003 to Exch2010 mail (one which enforces authentication) and another one for normal (Internet) mail? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-21-10 8:29 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 That's why I suggested you execute this command, and examine all the information output from it: get-routinggroupconnector | fl This is a PowerShell command, you'll execute it from the Exchange Management Shell on the 2010 server. You might want to do the same thing with get-receiveconnector | fl and get-sendconnector | fl. While there are another potential knobs and switches involved, with the output from those 3 commands we will likely be able to identify any culprit or provide an additional lead to continue the investigation. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Wednesday, April 21, 2010 7:00 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 I thought I would add a bit more info to Tammy's first question. Our two test servers are called EXCH2003 and EXCH2010. After the 2010 installation, two connectors were created and appear when using Exchange System Manager. In the First Routing Group (associated with EXCH2003), the new routing connector was called EXCH2003-EXCH2010. In the Exchange Routing Group (created by the 2010 install), another connector was created called EXCH2010-EXCH2003. These connectors cannot be modified with Exchange System Manager (complains that
RE: Two questions - Exchange 2003 2010
You can enable protocol logging on the Exchange 2003 server and receive-connector logging on the Exchange 2010 server (connection logging is on by default). You can see from those logs why communication is failing. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Thursday, April 22, 2010 1:30 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Unfortunately there seems to be some other issue. We simply can't get mail flowing from EXCH2003 to EXCH2010. It's obviously some sort of communication issue since the Public Folders aren't replicating either. The various settings in the default receive connector look correct. I've verified that port 25 on EXCH2010 is open to EXCH2003, but still no go. I've read some good documents on the various post-installations steps that should be performed and we've completed all of them. We may redo our test installation and see if we have better results. I guess this is why we set up test environments before tackling the real thing... From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-21-10 10:14 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Well, you've identified the problem. You shouldn't have disabled the default receive connector. If you take a look at it, you'll see on the Permission Groups tab, that Legacy Exchange Servers is one of the options. Exchange servers speak to each other using a number of extensions to the SMTP protocol. Those extensions are only allowed when you enable the permissions. The default receive connector allows those permissions from Exchange servers (2007/2010) and legacy Exchange servers (2003). However, the Internet receive connector should only enable anonymous. Generally speaking, most people just enable the anonymous permissions on the default receive connector so they can get by with a single connector. And to answer your other question - Outlook and Exchange preferentially communicate using MAPI, not SMTP. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Wednesday, April 21, 2010 8:45 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 I spoke too soon. The change allowed a manual telnet session to work, but mail initiated from Outlook still gets hung up. Does Exchange use standard SMTP/port 25 protocol for inter-Exchange email transfers, or does it use something different? From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: April-21-10 9:06 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 We did run the command but everything looked ok, at least to us. The Get-receiveconnector has so much information it's not entirely easy to decipher, this being our first Exchange 2010 server. I think I have narrowed down the problem though. When I tried a manual mail session using telnet exch2010 25 from exch2003, when I give the mail from:usern...@acadiau.ca, I get the error 530 5.7.1 Client was not authenticated. That gave me the clue I needed to at least find a workaround. During the 2010 install, a Receive connector was created in the Server Configuration Hub Transport section for handling mail coming from EXCH2003. I disabled that connector so that mail coming from exch2003 would arrive using the SMTP connector I had created for mail coming from the Internet. Since that one had no authentication requirments that solved the connectivity problem for mail coming from exch2003. That brings up another question. Should there be a separate Receive Connector for Exch2003 to Exch2010 mail (one which enforces authentication) and another one for normal (Internet) mail? From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-21-10 8:29 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 That's why I suggested you execute this command, and examine all the information output from it: get-routinggroupconnector | fl This is a PowerShell command, you'll execute it from the Exchange Management Shell on the 2010 server. You might want to do the same thing with get-receiveconnector | fl and get-sendconnector | fl. While there are another potential knobs and switches involved, with the output from those 3 commands we will likely be able to identify any culprit or provide an additional lead to continue the investigation. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Wednesday, April 21, 2010 7:00 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 I thought I would add a bit more info to Tammy's first question. Our two test servers are called EXCH2003 and EXCH2010. After the 2010 installation, two
RE: Exchange PF on cluster
Thanks Michael, as always your input is appreciated. -Original Message- From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Thursday, April 22, 2010 6:53 AM To: MS-Exchange Admin Issues Subject: RE: Exchange PF on cluster You can put the PFs on the cluster. There are some caveats around that if it were a CCR cluster, but they don't apply to a SCC cluster. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Benjamin Zachary - Lists [mailto:li...@levelfive.us] Sent: Wednesday, April 21, 2010 11:52 PM To: MS-Exchange Admin Issues Subject: RE: Exchange PF on cluster These are actual Public Folders for calendars, we have faxing folders routing there and dozens of departments (the PF store is about 50GB). On the cluster side this isn't an actual CCR cluster, I don't think, this is a standard 2 server with DAS attached storage. Only one server is active at any one time. We are about 75% Outlook 2007 and Outlook 2003 is almost phased out, maybe another 30-60 days. -Original Message- From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, April 21, 2010 7:36 PM To: MS-Exchange Admin Issues Subject: RE: Exchange PF on cluster There are several considerations. First, do you actually have real public folders or are you just using the PF database to hold the system folders? Can you answer that question first? Secondly, what versions of Outlook are being used in your environment? Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Benjamin Zachary - Lists [mailto:li...@levelfive.us] Sent: Wednesday, April 21, 2010 7:11 PM To: MS-Exchange Admin Issues Subject: Exchange PF on cluster Currently we have a 2007 active/passive cluster running on 2008 enterprise and it works well. We have a front end server that has been doing hub transport services with, the a/v and anti spam etc. We have recently migrated over to a new spam/av product which is acting as an smtp connector so all mail transactions are simply handed off from the front end server to the connector and vice versa. In our migration process I was asked about putting the Public Folders, which were being stored there and not the cluster, so we can debate on getting rid of that server entirely or converting it to vm, but basically get the public store off it. I poked around and saw some different mentions of problems with doing it, so wanted to know if anyone is doing it successfully. Thanks
2003 fwds
So I have an odd situation I have never seen. An Exchange2000/ Win 2000 server has been upgraded to Exchange 2003/ Win2k3. There is a front end iis server running webmail and such. When the user uses webmail and fwds an email and then types in something and sends it the message blanks out and the recipient only gets the fwd not what the user typed in on top of it, basically it just gets stripped off. Apparently this is happening even on outlook inside the office. So if I send an email to someone they fwd (not reply) to me and then I fwd that to someone else and write additional text and the end user only gets the 2 parts of the message (original and 1st fwd) The user(s) are hitting fwd it opens a new windows on Outlook 2003, and then they have to go back and copy/paste the message. Im testing if this is happening with replies too . any ideas where to even look? Since the message gets delivered its not like im searching for missing items, just missing text within an item. Also, the Sent Items shows the text that is missing. Thanks
DAG Creation
All- I'm just a bit confused on the process of setting up a DAG within E2K10. After I create the DAG (DAG1). Once that is created, what is the process of finishing the DAG setup? - Create DAG -Create DAG Network (assign subnet(s) where each member resides) -Assign IP addresses to DAG -Create DB Copy Am I on point with this so far? Are there any other steps that I have left out? Thanks. John Bowles
RE: DAG Creation
Are you coming to my HA workshop at TEC'2010 in LA next week? :-) I cover this. :-) Henrik Walther has a really good series on setting up DAGs at msexchange.org. He covers all the steps and most of the considerations. Recommended. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: John Bowles [mailto:john.bow...@wlkmmas.org] Sent: Thursday, April 22, 2010 2:50 PM To: MS-Exchange Admin Issues Subject: DAG Creation All- I'm just a bit confused on the process of setting up a DAG within E2K10. After I create the DAG (DAG1). Once that is created, what is the process of finishing the DAG setup? - Create DAG -Create DAG Network (assign subnet(s) where each member resides) -Assign IP addresses to DAG -Create DB Copy Am I on point with this so far? Are there any other steps that I have left out? Thanks. John Bowles
RE: Renamed conference room (resource calendar) still shows old name
Thanks for the advice. I think I'll log into that mailbox and export the calendar folder first, just to be extra careful. Tom From: James Winzenz [mailto:james.winz...@hotmail.com] Sent: Thursday, April 22, 2010 12:37 PM To: MS-Exchange Admin Issues Subject: RE: Renamed conference room (resource calendar) still shows old name Nope, deleting a calendar from People's Calendars will not delete the actual calendar itself. I have done it many times. It just removes it from the list of shared calendars you have open. Thanks, James Winzenz Subject: RE: Renamed conference room (resource calendar) still shows old name Date: Thu, 22 Apr 2010 11:32:15 -0500 From: tom.alver...@ngc.com To: exchangelist@lyris.sunbelt-software.com I wasn't worried about deleting the whole mailbox, I was just worried that instead of just deleting the shortcut to that resource calendar, that it might delete the folder itself of the contents of the folder (since I have full permissions to that folder). From: Sherry Abercrombie [mailto:saber...@gmail.com] Sent: Thursday, April 22, 2010 11:39 AM To: MS-Exchange Admin Issues Subject: Re: Renamed conference room (resource calendar) still shows old name You cannot delete a mailbox just by deleting the calendar in Outlook, that is only removing it from their Outlook. To delete a calendar/mailbox you must use ADUC and ESM. If you still don't believe us, then you can go the manual route in Outlook. Go to Tools/Account Settings, Double click on Microsoft Exchange Server, then select the More Settings button at the bottom right, then click on the Advanced tab, and remove it from the Mailboxes section. On Thu, Apr 22, 2010 at 10:23 AM, Alverson, Tom (Xetron) tom.alver...@ngc.com wrote: James: By removing from People's Calendars do you mean right click and choose DELETE. I am a little nervous about trying this since that command in the my calendars right above there actually deletes the folder containing the calendar. Tom From: James Winzenz [mailto:james.winz...@hotmail.com] Sent: Wednesday, April 21, 2010 6:21 PM To: MS-Exchange Admin Issues Subject: RE: Renamed conference room (resource calendar) still shows old name I'll bite. This is the same behavior you see if you rename a user in AD/Exchange - Outlook does not reflect the new name unless you update their profile, even though the address book shows the correct entry. Removing and re-adding the shared calendar in their list of People's Calendars should allow them to re-add it with the new name - it will not delete the actual calendar. Thanks, James Winzenz Subject: RE: Renamed conference room (resource calendar) still shows old name Date: Wed, 21 Apr 2010 17:15:05 -0500 From: tom.alver...@ngc.com To: exchangelist@lyris.sunbelt-software.com cricket noise ... cricket noise Bueller? Anybody? From: Alverson, Tom (Xetron) [mailto:tom.alver...@ngc.com] Sent: Tuesday, April 20, 2010 4:46 PM To: MS-Exchange Admin Issues Subject: Renamed conference room (resource calendar) still shows old name I have a few conference rooms that have mailboxes on an Exchange 2003 server for resource (calendar) scheduling. Some of the rooms have moved so I needed to change the names of the accounts a little. Despite changing the display name in AD, the displayed name on Outlook 2007 is still the old name. If a user who had never opened the calendar opens it now they will get the new name. Any user who had previously opened the calendar still gets the old name, even if they log into a brand new computer with Outlook 2007 (so the setting is not in a user profile, or an exchange profile on the local computer it must be stored on the server somehow). The old name is still shown in the People's Calendars on the left and also on the tab above the calendar itself. I was tempted to delete the calendar from the list of People's Calendars on the left side of Outlook but it looks like that might actually delete the whole calendar. I can right click on that list and choose rename and put any name in there I want (Including the new name). Is there some good way to fix this problem short of exporting all the calendar data and creating a whole new mailbox with the new name? Tom Hotmail is redefining busy with tools for the New Busy. Get more from your inbox. See how. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL :ON:WL:en-US:WM_HMP:042010_2 -- Sherry Abercrombie Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clarke The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. Get busy. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccountocid=P ID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
Exchange 2010 on Win Server 2008
Hi guys, Quick question. Is there a benefit to running Exchange 2010 Enterprise on Windows 2008 Server Enterprise instead of Windows Server 2008 Standard? Thanks, Evan
RE: Exchange 2010 on Win Server 2008
Using a DAG requires server enterprise. That's the only difference. Sent from my HTC Tilt™ 2, a Windows® phone from ATT From: Evan Brastow ebras...@automatedemblem.com Sent: Thursday, April 22, 2010 4:04 PM To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Subject: Exchange 2010 on Win Server 2008 Hi guys, Quick question. Is there a benefit to running Exchange 2010 Enterprise on Windows 2008 Server Enterprise instead of Windows Server 2008 Standard? Thanks, Evan
Bad reminder
Exchange 2007 SP2 RU3 all roles server. I have an Outlook 2007 non-cached mode user who gets a reminder that pops up every day (not sure when it started) and he can't dismiss it. If he clicks on Open Item, he gets the following text. [cid:image001.png@01CAE225.1E3DE2C0] What's interesting is the subject is always the same, but the start time has been changing. Yesterday it was 1:30pm, today it shows as 1:49pm, like this: [cid:image002.jpg@01CAE225.1E3DE2C0] First thing I tried was to run Outlook.exe with /cleanreminders - I've done it several times with no success on this one. I've also switched his calendar into category view, but cannot find a matching subject line of the appointment that keeps popping up. He only has the one default calendar in his mailbox. He does have two Sharepoint (MOSS 2007) calendars linked into Outlook using SP lists, but they don't appear to have reminders enabled in any way, which makes sense. Any idea what else to try? I haven't tried recreating his Outlook profile since it doesn't make sense to me why that would help with a reminder issue, but I will if someone can tell me what it would/might fix. I'm ready to try migrating his mailbox to a different storage group and back if needed to see if it will drop any corrupt items. I'll be out for the weekend, but any suggestions will be welcome come Monday morning. Thanks, Bonnie inline: image001.pnginline: image002.jpg
RE: Bad reminder
Have you tried the all appointments view From: Miller Bonnie L. [mailto:mille...@mukilteo.wednet.edu] Sent: Thursday, April 22, 2010 5:07 PM To: MS-Exchange Admin Issues Subject: Bad reminder Exchange 2007 SP2 RU3 all roles server. I have an Outlook 2007 non-cached mode user who gets a reminder that pops up every day (not sure when it started) and he can't dismiss it. If he clicks on Open Item, he gets the following text. cid:image001.png@01CAE222.C13EBC40 What's interesting is the subject is always the same, but the start time has been changing. Yesterday it was 1:30pm, today it shows as 1:49pm, like this: cid:image002.png@01CAE222.C13EBC40 First thing I tried was to run Outlook.exe with /cleanreminders - I've done it several times with no success on this one. I've also switched his calendar into category view, but cannot find a matching subject line of the appointment that keeps popping up. He only has the one default calendar in his mailbox. He does have two Sharepoint (MOSS 2007) calendars linked into Outlook using SP lists, but they don't appear to have reminders enabled in any way, which makes sense. Any idea what else to try? I haven't tried recreating his Outlook profile since it doesn't make sense to me why that would help with a reminder issue, but I will if someone can tell me what it would/might fix. I'm ready to try migrating his mailbox to a different storage group and back if needed to see if it will drop any corrupt items. I'll be out for the weekend, but any suggestions will be welcome come Monday morning. Thanks, Bonnie image001.pngimage002.jpg
RE: Two questions - Exchange 2003 2010
Thanks for all your help. I must admit that I find the configuration of the various connectors a bit confusing. I know that it's really not that complicated, but trying to find documentation that explains how to set up something for our simple environment is not always easy. Most examples assume a more complex setup. I haven't come across anything that describes an environment with staff on an Exchange server, students on a Unix mail server, all with a company MX server on Unix. We want st...@acadiau.ca to go to Exchange 2010 server and stud...@acadiau.ca to go our Unix mail server. We have this working with our existing Exchange 2003 environment, but I haven't quite figured out all the Exchange 2010 settings to accomplish the same thing. I think I'm getting close though. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-22-10 3:55 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Depends on where you have smarthost configured. If it's on a smtp connector, that would be the proper behavior (but even that can be overridden if you've specified a masquerade host). If it's on the default smtp virtual server, that overrides everything. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Thursday, April 22, 2010 2:51 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 That revealed that puzzle. Mail destined to Exch2010 was being routed up to our Unix smart host. I thought that Exchange would first check to see if the recipient email address was present in Active Directory and route to the appropriate Exchange server before sending the mail to the smart host. I obviously have more reading to do. It's difficult when our single Exchange 2003 server was installed 7 years ago and you sort of forget how everything all works! From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-22-10 2:32 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 You can enable protocol logging on the Exchange 2003 server and receive-connector logging on the Exchange 2010 server (connection logging is on by default). You can see from those logs why communication is failing. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Thursday, April 22, 2010 1:30 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Unfortunately there seems to be some other issue. We simply can't get mail flowing from EXCH2003 to EXCH2010. It's obviously some sort of communication issue since the Public Folders aren't replicating either. The various settings in the default receive connector look correct. I've verified that port 25 on EXCH2010 is open to EXCH2003, but still no go. I've read some good documents on the various post-installations steps that should be performed and we've completed all of them. We may redo our test installation and see if we have better results. I guess this is why we set up test environments before tackling the real thing... From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-21-10 10:14 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Well, you've identified the problem. You shouldn't have disabled the default receive connector. If you take a look at it, you'll see on the Permission Groups tab, that Legacy Exchange Servers is one of the options. Exchange servers speak to each other using a number of extensions to the SMTP protocol. Those extensions are only allowed when you enable the permissions. The default receive connector allows those permissions from Exchange servers (2007/2010) and legacy Exchange servers (2003). However, the Internet receive connector should only enable anonymous. Generally speaking, most people just enable the anonymous permissions on the default receive connector so they can get by with a single connector. And to answer your other question - Outlook and Exchange preferentially communicate using MAPI, not SMTP. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Wednesday, April 21, 2010 8:45 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 I spoke too soon. The change allowed a manual telnet session to work, but mail initiated from Outlook still gets hung up. Does Exchange use standard SMTP/port 25 protocol for inter-Exchange email transfers, or does it use something different? From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: April-21-10 9:06 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 We did run the command but everything
RE: Two questions - Exchange 2003 2010
Depends on how you have it set up today. SOMEONE has to be authoritative resource for the domain's email addresses. Every version of Exchange since Exchange 5.5, including 2010, supports sharing SMTP address spaces. You can configure it the same in 2010 as you did in 2003. The only difference is instead of a custom recipient policy, you have a custom accepted domain, and (optionally) a custom send connector. Same concept, different names. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Thursday, April 22, 2010 6:22 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Thanks for all your help. I must admit that I find the configuration of the various connectors a bit confusing. I know that it's really not that complicated, but trying to find documentation that explains how to set up something for our simple environment is not always easy. Most examples assume a more complex setup. I haven't come across anything that describes an environment with staff on an Exchange server, students on a Unix mail server, all with a company MX server on Unix. We want st...@acadiau.camailto:st...@acadiau.ca to go to Exchange 2010 server and stud...@acadiau.camailto:stud...@acadiau.ca to go our Unix mail server. We have this working with our existing Exchange 2003 environment, but I haven't quite figured out all the Exchange 2010 settings to accomplish the same thing. I think I'm getting close though. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-22-10 3:55 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Depends on where you have smarthost configured. If it's on a smtp connector, that would be the proper behavior (but even that can be overridden if you've specified a masquerade host). If it's on the default smtp virtual server, that overrides everything. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Thursday, April 22, 2010 2:51 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 That revealed that puzzle. Mail destined to Exch2010 was being routed up to our Unix smart host. I thought that Exchange would first check to see if the recipient email address was present in Active Directory and route to the appropriate Exchange server before sending the mail to the smart host. I obviously have more reading to do. It's difficult when our single Exchange 2003 server was installed 7 years ago and you sort of forget how everything all works! From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-22-10 2:32 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 You can enable protocol logging on the Exchange 2003 server and receive-connector logging on the Exchange 2010 server (connection logging is on by default). You can see from those logs why communication is failing. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Thursday, April 22, 2010 1:30 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Unfortunately there seems to be some other issue. We simply can't get mail flowing from EXCH2003 to EXCH2010. It's obviously some sort of communication issue since the Public Folders aren't replicating either. The various settings in the default receive connector look correct. I've verified that port 25 on EXCH2010 is open to EXCH2003, but still no go. I've read some good documents on the various post-installations steps that should be performed and we've completed all of them. We may redo our test installation and see if we have better results. I guess this is why we set up test environments before tackling the real thing... From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-21-10 10:14 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Well, you've identified the problem. You shouldn't have disabled the default receive connector. If you take a look at it, you'll see on the Permission Groups tab, that Legacy Exchange Servers is one of the options. Exchange servers speak to each other using a number of extensions to the SMTP protocol. Those extensions are only allowed when you enable the permissions. The default receive connector allows those permissions from Exchange servers (2007/2010) and legacy Exchange servers (2003). However, the Internet receive connector should only enable anonymous. Generally speaking, most people just enable the anonymous permissions on the default receive connector so they can get by with a single connector. And to answer your other question - Outlook and Exchange preferentially communicate using MAPI, not SMTP. Regards, Michael B. Smith Consultant
RE: Two questions - Exchange 2003 2010
Got it working. Just had to change the accepted domain acadiau.ca from authoritative to Internal Relay. Everything is starting to make sense! From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-22-10 7:55 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Depends on how you have it set up today. SOMEONE has to be authoritative resource for the domain's email addresses. Every version of Exchange since Exchange 5.5, including 2010, supports sharing SMTP address spaces. You can configure it the same in 2010 as you did in 2003. The only difference is instead of a custom recipient policy, you have a custom accepted domain, and (optionally) a custom send connector. Same concept, different names. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Thursday, April 22, 2010 6:22 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Thanks for all your help. I must admit that I find the configuration of the various connectors a bit confusing. I know that it's really not that complicated, but trying to find documentation that explains how to set up something for our simple environment is not always easy. Most examples assume a more complex setup. I haven't come across anything that describes an environment with staff on an Exchange server, students on a Unix mail server, all with a company MX server on Unix. We want st...@acadiau.ca to go to Exchange 2010 server and stud...@acadiau.ca to go our Unix mail server. We have this working with our existing Exchange 2003 environment, but I haven't quite figured out all the Exchange 2010 settings to accomplish the same thing. I think I'm getting close though. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-22-10 3:55 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Depends on where you have smarthost configured. If it's on a smtp connector, that would be the proper behavior (but even that can be overridden if you've specified a masquerade host). If it's on the default smtp virtual server, that overrides everything. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Thursday, April 22, 2010 2:51 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 That revealed that puzzle. Mail destined to Exch2010 was being routed up to our Unix smart host. I thought that Exchange would first check to see if the recipient email address was present in Active Directory and route to the appropriate Exchange server before sending the mail to the smart host. I obviously have more reading to do. It's difficult when our single Exchange 2003 server was installed 7 years ago and you sort of forget how everything all works! From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-22-10 2:32 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 You can enable protocol logging on the Exchange 2003 server and receive-connector logging on the Exchange 2010 server (connection logging is on by default). You can see from those logs why communication is failing. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Thursday, April 22, 2010 1:30 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Unfortunately there seems to be some other issue. We simply can't get mail flowing from EXCH2003 to EXCH2010. It's obviously some sort of communication issue since the Public Folders aren't replicating either. The various settings in the default receive connector look correct. I've verified that port 25 on EXCH2010 is open to EXCH2003, but still no go. I've read some good documents on the various post-installations steps that should be performed and we've completed all of them. We may redo our test installation and see if we have better results. I guess this is why we set up test environments before tackling the real thing... From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: April-21-10 10:14 PM To: MS-Exchange Admin Issues Subject: RE: Two questions - Exchange 2003 2010 Well, you've identified the problem. You shouldn't have disabled the default receive connector. If you take a look at it, you'll see on the Permission Groups tab, that Legacy Exchange Servers is one of the options. Exchange servers speak to each other using a number of extensions to the SMTP protocol. Those extensions are only allowed when you enable the permissions. The default receive connector allows those permissions from Exchange servers (2007/2010) and legacy Exchange servers (2003). However, the
