Setup first Exchange 2013 with mixed mode exchange 2007/2010

my company has exchange 2007 hub and edge and exchange 2010. I'm planning to retire all exchange 2007 first follow migrate to exchange 2013. so I have few questions as below ?
1. Do I need to unsubscribe hub 2007 from edge first before uninstall ? Currently we have 2 hubs (2007 and 2010). How can I remove hub 2007 from exchange edge server 2007 ?
2. let say once my landscape just have exchange 2010, is it installing our first exchange 2013 will impact our mail flow ? my understand there is NO impact until we switch over 'mail IP' to CAS 2013. am I correct ?
3. what is minimum requirement for co-exist with exchange 2013 for exchange 2010 ? is it enough with SP3 or I need to apply SP3 RU5 ? in deployment assistant, the requirement is SP3 RU5 but most article i read just mention SP3.
thx.

1. I would remove the edge subscription for sure. Then it isn't strictly necessary to uninstall Exchange Edge if you're just going to flatten the box anyway because that server isn't in Active Directory except through the Edge Subscription process.
I'm not sure what you're asking about "NO impact".
2. The coexistence requirements are clearly documented in TechNet. I'll leave it to you to search it since you can do that just as well as I can. That said, I would recommend that you go ahead and install the latest rollup on all your servers
first.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

Exchange 2007/2010/2013 UM coexistence

We currently have an Exchange 2007/2010 environment in production along with Lync 2010 (UM provided).
I have installed a number of Exchange 2013 server and will be migrating ( over a LONG time ) to the new system.
In the meantime, I need to have all services co-existent across all three Exchange versions.
It looks like I have everything workign now except UM for Lync 2010.
I tried adding the Exchange 2013 server into the existing 2007/2010 dial plan and am having issues.
Here is what i did.
EAC
- Installed certificate on all Exchange 2013 servers
- Enabled Unified Messaging on all the servers
- Select server
- Set TLS
- Associated 2007/2010 Dial Plan
- Set UM service on certificate on all servers
- Restarted UM service
- Did the above for all MB and CAS servers
- Wait about an hour
Lync fails to send calls to voice mail, giving me events 45024 and 44022 on the Lync FE stating that Lync could not connect to the Exch MB servers and the attempt to connect to UM failed.
Any suggestions?
Do I need to rerun the following ?
- Exchucutl.ps1
- Ocsumutil.exe
Thanks!
Tom

When I go into the Exchange EAC Unified messaing / UM IP Gateway screen I see the Um IP Gateways configured in the legacy Exchange systems and had hoped that these existing gateway definitions would suffice.
Does exchucutil.ps1 need to run from a 2013 Exch server to initialize these gateways in Exch 2013?
On my fist attempt, VM was failing for my 2007/2010 users. I had not even started to test with a 2013 user. I successfully backed out by dis-associating the dial plan in the Exchange EAC console from all the Exch 2013 servers.
If I run exchucutil.ps1, try again, and it fails, what is my backout plan? Do I need to rerun exchucutil.ps1 on a legacy Exchange system? or will merely dis-associateing the diual plan in Exchange 2013 again suffice.
Thanks Tom
After typing this, I realize that this is probably more of an Exchange question so I posted the question there. I apologize now for any cross posting misbehavour.
Posted to -
http://social.technet.microsoft.com/Forums/exchange/en-US/6fbfad13-3480-46c6-804d-3757110e61c7/exchange-um-coexistence-exch-20072010-and-exch-2013?forum=exchangesvrunifiedmessaging

How can I remove the first exchange server 2010 without any problems in DC

Hi,
our actually exchange is running on windows server 2008R2 with exchange 2010. I already install & configured a second Exchange 2010 server in the same domain. I also moved every mailbox to the new server. Now I have to deactivate the first server and
I don't know, if I have to do something or can I deactivate the "old" server without any issues.
If I can deactivate it, how can I do this? Is it enough to uninstall exchange 2010 on the server and after that I uninstall the windows server? Did I have to change something before?
Thanks,
Mesut Uygun
btw. sorry for my bad english

Hi MesutU,
When you remove first Exchange Server 2010 in your organization, please confirm finish following steps:
1. Move all mailboxes (including discovery and arbitration) to another server
2. Move all Public Folder replicas
3. Move OAB generation server
4. Update SMTP flow from internet
5. Update OWA/IMAP/POP/OA access from internet.
6. Update any routing group connectors if 2003 is present
7. Turn the old server offline for some days to check whether the new server works well.
More information about How to Remove the First Exchange 2007 Server in a Coexistence Scenario (even if the version of Exchange server is different), for your conference:
http://technet.microsoft.com/en-us/library/bb310767(v=exchg.80).aspx
Best Regards,
Allen Wang

Historical Reports on CCX 7.01sr5 with "mixed Mode" on db

Hej.
In the release note from CCX 7.01sr5 is one of the changes the the database is supported with mixed mode on the security.
I have set that up, but when i try to run the Historical Reporting Tool, it says that Mixed mode on the DB is not supported.
Does anyone have a work around for this
Regards
Thomas

Hi
Yep - it's also in the release notes as far as I remember.
See this similar post : https://supportforums.cisco.com/message/3053064#3053064
Aaron
Please rate helpful posts...

Outlook 2011 for Mac with Microsoft Exchange 2007/2010

Hi,
For already a fews days I am troubleshooting a Mac Outlook 2011 <> Exchange sync issue. I've got exact the same symptoms in two totally different environments.
- Environment one:
Exchange 2007 SP3 RU 14 (8.3.379.2)
Outlook 2011 14.4.7
- Environment two:
Exchange 2010 SP1 RU 8 (14.1.438.0)
Outlook 2011 14.4.7
Problem:
Autodiscover and EWS synchronisation test from Microsoft Exchange Connectivity Analyzer is succesfull. Configuring an new (Exchange) e-mail account with Outlook2007/2010/2013 fully based on autodiscover works with no errors.
Configure Outlook 2011 based on autodiscover when connected to the internal LAN works. Configure Outlook 2011 based on autodiscover or by hand doesn't work from WAN.
I am unable to synchronize Outlook 2011 with Exchange when WAN connected (No error in logging). I am able to synchronize OS X Mail (Default OSX Mail client) with the same Exchange server.
Conclusion: the autodiscover function that Outlook 2011 uses does not work from WAN, the autodiscover function that Outlook 2007/2010/2013 and Exchange Connectivity Analyzer is using does work from WAN. Do I need to configure something special for synchronization
with Outlook 2011 other than explained above when working from WAN?
When testing EWS with 3th party tooling(EWS Editor) and Exchange Connectivity Analyzer everything is working as it should be. (all mailbox data is shown). If you need any more information about the context I am happy to provide.
Regards,
Mikkie van Falier

Hey hpujary.
Welcome to the BlackBerry Support Community Forums.
At this time, only contacts can be synchronized with BlackBerry Link software and a BlackBerry 10 Smartphones. The functionality to provide more options for PIM synchronization may be added in the future. I cannot say for certain that the issue outlined in KB27248 is resolved for BlackBerry 10 Smartphones as the functionality does not exist to confirm.
Cheers.
-Sawks
Come follow your BlackBerry Technical Team on Twitter !@BlackBerryHelp
Be sure to click Like! for those who have helped you.
Click Accept as Solution for posts that have solved your issue(s)

Troubleshooting and Introduction for Exchange 2007/2010 AutoDiscover - Details about "Test E-mail AutoConfiguration"

AutoDiscover is a new feature in Exchange 2007, to provide access to Microsoft Exchange features (OAB, Availability service, UM) for Outlook 2007
clients or later.
We can determine whether problems related to AutoDiscover via OWA.
For example:
OOF is not working in Outlook Client but it is working in OWA.
When we realized this issue is not related to Outlook Client side and network side after performing some troubleshooting steps, it should be something
abnormal on AutoDiscover.
There is a common tool to check AutoDiscover in Outlook, Test E-mail AutoConfiguration.
Today, we will introduce AutoDisocver and “Test E-mail AutoConfiguration” in details. Hope it is helpful for AutoDiscover troubleshooting and self-learning.
1. Differences between “Test E-mail AutoConfiguration” and other tools
The “Test-OutlookWebServices” cmdlet allows us to test the functionality of the following services:
Autodisocver
Exchange Web Services
Availability Service
Offline Address Book
When we run “Test-OutlookWebServices”, it returns all the web services’ states.
However, some information are useless for some scenarios.
For example:
We just want our Exchange 2010 Server working internally. So it is unnecessary to enable Outlook Anywhere.
However, when we run “Test-OutlookWebServices”, it returns Outlook Anywhere errors because the Outlook Anywhere does not need to been enabled.
In contrast, using “Test E-mail Autodiscover” is more intuitive.
If there is any problems, it will return error code from the test result, like 0x8004010F etc. We can do some research from TechNet articles or MS
KBs.
Although it is difficult to say where the specific problem is just via the error codes, we can combine with IIS logs to perform troubleshooting and
find the root of problem.
2. How to use “Test E-mail AutoConfiguration” Tool
a. Open Outlook, we can find there is an Outlook Icon at the right bottom of System tray. Holding down “Ctrl” button and right click the Outlook Icon, we will see “Test E-mail
AutoConfiguration” option. Please see Figure 01.
Figure 01
b. Click “Test E-mail AutoCofiguration” and input user name, uncheck the “Use Guessmart” and “Secure Guessmart Authentication” checkboxes, then click “Test”. Please see
Figure 02.
Figure 02
c. “Test E-mail AutoConfiguration” result panel and log panel. Please see Figure 03 and Figure 04.
Figure 03
Figure 04
3. How to understand “Test E-mail AutoConfiguration” result
According to the Figure 03, we found there are many URLs in the “Test E-mail AutoConfiguration” result panel. Let us understand the details of these
URLs.
If we these URLs are not the correct ones, we can re-setting or re-creating them via commands.
- Internal OWA URL:
https://vamwan310.vamwan.com/owa/
OWA internal access.
- External OWA URL:
https://mail.vamwan.com/owa/
OWA external access.
- Availability service URL:
https://vamwan310.vamwan.com/EWS/Exchange.asmx
Free/Busy, OOF and meeting suggestions.
- OOF URL:
https://vamwan310.vamwan.com/EWS/Exchange.asmx
Out of Office access.
- OAB URL:
https://vamwan310.vamwan.com/OAB/023ef307-b18a-4911-a52c-de26700f6173/
OAB access.
- Exchange Control Panel URL:
https://vamwan310.vamwan.com/ecp/
ECP access.
4. AutoDiscover Tips
- AutoDiscover Service itself is a web application running on the AutoDiscover virtual directory (not a server service) designed to provide connection information to various
clients.
- The AutoDiscover service is automatically installed and configured when CAS role is added to any Exchange Server.
- AutoDisocver virtual directory is created in IIS within the Default Web Site.
- A Sercive-Connection-Point (SCP) object is created in AD.
- The SCP contains a URL to the AutoDiscover service. This is for intranet clients so they do not have to use DNS to locate the AutoDiscover service.
- In AD this object is located at the following location:
DC=<domain>, CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Administrative Groups, CN=Exchange Administrative
Group, CN=Servers, CN=<CAS Name>, CN=Protocols, CN=AutoDiscover, CN=<CAS Name>
- Setup creates the AutoDiscover URL based on the following structure:
<CASNetbiosName>.domain.com/AutoDiscover/AutoDiscover.xml
If a PKI certificate is not already present, a self-signed certificate is installed on the Default Web Site.
To help allow this certificate pass the Issues to test it is set up with a Subject Alternative Name containing urls.
If a PKI certificate is present, that certificate is utilized and configured for use in IIS.
The Outlook Provider is used to configure separate settings for the Exchange PRC protocol (internal to network), Outlook Anywhere (Exchange HTTP protocol), and WEB:
EXCH, EXPR, WEB
The
EXCH and EXPR setting are vital for the proper configuration of Outlook.
5. AutoDiscover Workflow
General Process flow:
There are various components surrounding the AutoDiscover Service and all are necessary to complete a request. Including IIS, AutoDiscover service
itself, the provider, and AD.
a.
Client constructs service URL and submits Autodiscover Request. First attempt to locate the SCP object in AD. So, DNS is not needed.
b.
IIS Authenticates User.
c.
Is the Autodiscover service in the appropriate forest?
+ If YES.
    1)
Parse/Validate Request
    2)
Is there a provider that can service the Request?
++ If YES
      a)
Config provider processes request and returns config settings.
      b)
Return config setting to client
++ If NO
Inform client we cannot process request
+ If NO.
Redirect client to Autodiscover service in the appropriate forest.
Methods to find Autodiscover services: SCP and DNS
Domain-joined
a. Find SCP first.
The SCP contains the URL to the AutoDiscover service.
URL: https://CAS01.contoso.com(CAS’ FQDN)/AutoDiscover/AutoDiscover.xml
If more than one SCP object is found in AD (it means there are multiple CAS servers in the Exchange organization), Outlook client will choose one of the SCP entries that
are in the same site to obtain the AutoDisocover URL.
b. If we cannot find SCP object, then Outlook client will use DNS to locate AutoDiscover.
Outlook parses out the domain (SMTP suffix) via your EmaiAddress, then attempts to connect to the predetermined order of URLs via the suffix.
For example: If my email address is
[email protected]
Outlook tries POST commands to the following order of URLs:
https://contoso.com/autodiscover/autodiscover.xml
https://autodiscover.contoso.com/autodiscover/autodiscover.xml
NOTE: The URLs above is by design, hardcode
and cannot be changed.
c.
If those fail, Outlook tries a simple redirect to another URLs in IIS:
http://contoso.com/autodiscover/autodiscover.xml
http://autodiscover.contoso.com/autodiscover/autodiscover.xml
If none of these URLs work then DNS is most likely not set up correctly.
We can test that by pinging one of the above URLs.
If that is successful, we must ensure the URLs contoso.com or autodiscover.contoso.com are actually pointing to the CAS server.
If the ping fails then there is a chance that DNS is not set up correctly so be sure to check that the URLs are even registered.
NOTE: If contoso.com is a non-CAS server,
we should add a Host record with just AutoDiscover. And point that entry to your CAS server that is running AutoDiscover.
d.
If still failed, we can use DNS SRV lookup for _autodiscover._tcp.contoso.com, then “CAS01.contoso.com” returned. Outlook will ask permission from the user to continue
with AutoDiscover to post to https://CAS01.contoso.com/autodiscover/autodiscover.xml
Non-Domain-joined
It first tries to locate the Autodiscover service by looking up the SCP object in AD. However the client is unable to contact AD, it tries to locate
the Autodiscover service by using DNS.
Then, same as step b, c, d in
Domain-joined scenario.
6. How to change the AutoDiscover
service location order forcibly?
By default, Outlook client locates AutoDiscover service in that order above.
We can also change the order forcibly.
a.
If we want to locate AutoDiscover service via one of the autodiscover URLs, please running following command in EMS:
Set-ClientAccessServer -identity <servername> -AutodiscoverServiceInternalUri https://autodiscover.contoso.com/autodiscover/autodiscover.xml(URL
that you want)
b. If we want to locate AutoDiscover service via
SRV record, please follows this KB to set up SRV:
http://support.microsoft.com/kb/940881
7. How to check AutoDiscover Healthy
a. We should make sure the AutoDiscover
is healthy before using AutoDiscover to perform troubleshooting.
b.
We can browse following URL in IE explorer:
https://autodiscover.vamwan.com/autodiscover/autodiscover.xml
If it returns “code 600”, that means AutoDiscover is healthy.
Screenshot as below:
c. AutoDiscover itself returns errors to the requesting client if the incoming request does not contain the appropriate information to complete a
request.
The following table explains the possible errors that could be returned.
Error Value
Description
600
Mailbox not found and a referral could not be generated.
601
Address supplied is not a mailbox. The provided email address is not something a client can connect to. It could
be a group or public folder.
602
Active Directory error.
603
Others.
The 600 “Invalid Request” error is returned because a user name was not passed to the service. That is OK for this test because this does confirm
the service is running and accepting requests.
d.
If AutoDiscover service is not working well, I suggest re-building the AutoDiscover Virtual Directory for testing.
Steps as below:
1) Running following command in EMS to remove the AutoDiscover VD (we cannot delete it via EMC):
Remove-AutodiscoverVirtualDirectory -Identity "CAS01\autodiscover(autodiscover.contoso.com)"
Please refer:
http://technet.microsoft.com/en-us/library/bb124113(v=exchg.141).aspx
2)
Running following command in EMS to verify whether we have removed the AutoDisocver VD successfully:
Get-AutodiscoverVirtualDirectory | FL
Please refer:
http://technet.microsoft.com/en-us/library/aa996819(v=exchg.141).aspx
3)
Running following command in EMS to re-creating a new AutoDiscover VD:
New-AutodiscoverVirtualDirectory -Websitename <websitename> -BasicAuthentication:$true -WindowsAuthentication:$true
Please refer:
http://technet.microsoft.com/en-us/library/aa996418(v=exchg.141).aspx
8. Common issues
a. Outlook Disconnection
Issue and Troubleshooting
Issue:
Sometimes the Outlook clients cannot connect to the Exchange server after migrating to a new Exchange server or changing to new CAS. The Outlook clients
always connect to the old CAS server.
Troubleshooting:
To solve this issue, we should change the SCP via following command:
Set-ClientAccessServer -Identity
<var>CAS_Server_Name</var> -AutodiscoverServiceInternalUri
https://mail.contoso.com(newCAS’FQDN)/autodiscover/autodiscover.xml
b. Autodiscover
Certificate issue
Tips on Certificate:
Exchange requires a certificate to run an SSL protocol such as HTTPS. We can use the certificate that supports subject alternate names (SAN) in Exchange.
This is to allow the certificate to support resources that have different names, such as Outlook Anywhere and the Autodisocver Web application.
Issue and Troubleshooting
Issue:
We receiver the Certificate Principal Mismatch error when we use a SAN certificate.
Troubleshooting:
1) Please determine the FQDN that the client
uses to access the resource. Steps as below:
OutlookàToolsàAccount
SettingsàE-mailàclick
the Exchange accountàChangeàMore
SettingsàConnectionàExchange
Proxy Settingsànote the FQND that list in the
Only connect to proxy servers that have this principal name in their certificate box.
2)
Please using EMS to determine the value for the CerPrincipalName attribute: Get-OutlookProvider
This command returns the result for the EXPR name.
3)
Please re-setting the CertPrincipalName attribute to match the FQDN via following command:
Set-OutlookProvider EXPR –CertPrincipalName: “msstd:<FQDN the certificate is issued to>”
9. Resource for reference:
Autodiscover and Exchange 2007
http://technet.microsoft.com/en-us/library/bb232838(v=exchg.80).aspx
White Paper: Understanding the Exchange 2010 Autodiscover Service
http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx
Certificate Principal Mismatch
http://technet.microsoft.com/en-us/library/aa998424(v=exchg.80).aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

HI,
I get following? when run the test? user is login to Domain A but accessing exchange in Domain B?

Exchange 2007/2010 Console doesn't show up Exchange 2007 Databases after RBAC Implementation

I have implemented a RBAC model after which Exchange 2010/2007 Console won't show up Exchange 2007 Mailbox Databases.
Everything was working fine up until the Users were members of "Exchange Recipient Administrators" Group.
I have created Custom Roles based on PArent Roles, Mail Recipients, Mail Recipient Creation, Distribution Groups & Public Folders and assigned that to a universal security group "Helpdesk operations". I removed membership for Helpdesk operations
from "Exchange Recipient Administrators" Group and assigned the Custom Roles to "Helpdesk Operations" using the cmdlet below:
New-ManagementRoleAssignment "Custom Role" -SecurityGroup "HelpDesk Operations"
Exchange 2010 console shows Exchange 2010 Databases but not Exchange 2007 DAtabases. Exchange 2007 console doesn't show up any databases on New-Mailbox and simply displays a message "No Objects Found".
Even Get-MailboxDatabase REturns blank output on Exchange 2007 SHell. Please help me with this and let me know in case if there is something that i need to be looking at!
any help on this is much appreciated.
M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This
Information is provided is "AS IS" and confers NO Rights!!

Hi,
I recommend you use the following cmdlet and check the result.
Get-MailboxDatabase -Server "Exchange 2007 server name"
In my environment, if I don't specify the Server parameter on Exchange 2010 Management Shell, Exchange 2007 mailbox database can't be displayed. If I specify the Server parameter, Exchange 2007 mailbox database will be displayed.
What's more, please check if the account you use has been delegated the Exchange View-Only Administrator role.
Here is a thread for your reference.
Get-MailboxDatabase
http://technet.microsoft.com/en-us/library/bb676367(v=exchg.80).aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Lync2013 EWS URLs for Exchange 2007/2010 Coexistence

Hi
Last weekend we deployed and activated our new Exchange 2010 CAS. The 'old' Exchange 2007 CAS is still there, using the legacy URL method, since mailboxes are mostly still located on 2007 Mailbox servers.
In other words, clients connect to the Exchange web-services on the 2010 CAS, and depending on where their mailbox is located (2007 or 2010 Mailbox-server) they either stay with the 2010 CAS or get re-directed to the 2007 CAS (legacy.company.com)
Internal and External URL's are the same, for both the primary and the legacy URL's. All is well, no issues with Outlook clients or OWA, EWS, Activesync.
Enter Lync 2013.
Since the change this weekend, we're getting Outlook/Exchange Integration errors. Checking the Lync Configuration Information (CTRL-Click system tray icon), I can see the EWS Internal/External URL's being used by the client. These URL's point to the 2010 CAS.
So why the error ?
Does the 2010 CAS re-direct Lync clients to the legacy URL, just like it does with OWA/Outlook clients ?
Does it even have to, to supply EWS data for mailboxes on 2007 servers ?
Can I change the EWS URL's, and have them point to the legacy URL, but only for Lync clients ? (and change it back later)
Already checked a mailbox on Exchange 2010, it's Lync user does not get the integration error. So the problem is definitely related to mailboxes on 2007, that need the old CAS server during coexistence. Also, before the CAS 2007 server worked fine, providing
EWS to Lync clients.
Eventually, the plan is to move the mailboxes from 2007 to 2010, but this error puts pressure on that plan. It will take at least 2 or 3 weeks, during which time clients continue to get the error until they are moved.
I'm kinda stuck here.

Lync uses DNS to find autodiscover to obtain EWS URL.
Which server did the DNS record Autodiscover point to?
You can run the command Get-AutodiscoverVirtualDirectory to get the EWS internal URL and external URL on the server the Autodiscover pointing to.
2010 CAS can’t redirect Lync client to the legacy URL.
Lisa Zheng
TechNet Community Support

Difference between exchange 2007 & 2010 server roles

What are the improvements in Exchange 2010 Role Wise as compared to Exchange 2007 ?
Aditya Mediratta

http://office.microsoft.com/en-001/exchange/microsoft-exchange-server-version-comparison-email-server-FX103746692.aspx
http://exchangeserverpro.com/benefits-exchange-server-2010-compared-exchange-2007/
http://www.techrepublic.com/blog/10-things/10-reasons-to-migrate-to-exchange-2010/#.
http://blogs.technet.com/b/ucando365talks/archive/2014/02/28/exchange-server-2013-vs-2010-vs-2007-quick-comparison-notes-new-features-amp-concepts.aspx
http://powerwindows.wordpress.com/2010/07/26/exchange-server-2007-and-2010-comparison-chart/
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Exchange 2007 - 2010 Outlook doesn't autodiscover after mailbox move

We currently are in the process of migrating from Exchange 2007 to 2010. When I move a mailbox to 2010, Outlook (2010 in this case), fails to connect to the new environment. Restarting outlook does not help. I am forced to change the
servername in the mail applet. How can we make this happen automagically?

That URL points to the autodiscover.xml page on the 2010 CAS servers. Returns the typical
<?xml version="1.0" encoding="utf-8"
?>
- <Autodiscover
xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
- <Response>
- <Error Time="01:46:57.9070185"
Id="814683946">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData
/>
</Error>
</Response>
</Autodiscover>

Seeking an Exchange 2007/2010 UM & Avaya Phone System Reference

Hello all - and thank-you well in advance for any feedback that you can offer.
We have a 60-user client currently with an on-premise Exchange 2003 host and an Avaya S8300 CMS server used with the Modular Messaging Voicemail application.
We're proposing the implementation of a new dedicated Exchange 2010 system with the mailbox and CAS/HT roles off-site in a co-located facility, with an on-premise Exchange host with the Unified Messaging role installed solely for the purpose of integrating
with the Avaya phone system. There will be a dedicated site-to-site VPN tunnel for communication purposes and the goal is to replace the Avaya MM host with Exchange UM, maintaining their existing integration functionality and benefiting from the added features
in Exchange UM.
Has anyone successfully implemented such a solution, or observed one in production?
Thanks,
Seth

Hello Seth,
I know this post was submitted a long time ago, where is the location of your office?
-Patrick
[email protected]

Exchange 2007/2010 Environment (In Migration Currenty) Outbound Mailflow issues

Hello,
I have an issue that started Friday and keeps progressing. On friday my Spam filter started freaking out with numerous emails I though it was the filter but it appears it is one of the servers instead. The errors stopped and I thought I was good
however I then realized no email was flowing. I checked and found on the 2010 server my disk space had dropped low (under 1gb) and it shutdown my transport, I increased the size now has (40gb free) and restarted the transport services and bang I had
email for a few hours. However that was shortlived I am getting the following errors in the 2007 server queue now:
Date Received: 12/15/2013 9:32:43 PM
Expiration Time: 12/17/2013 9:32:43 PM
Last Error: 452 4.3.1 Insufficient system storage
Queue ID: MAIL\3
Now, I've check on the 2007 server I have 100gb free on the C drive and 500gb free on the D drive which stores the database. So I have no storage issues, I was also getting errors in the event log for backflow issues stating I was out of storage space.
However everything is good now on both servers. My 2010 server has 40gb free on the C drive now and 290gb free on the D drive now. For the heck of it I tried to disable the resource monitoring on the 2007 server for now, however I get the same
error message when trying to send email still. I even went as far as rebooting the server.
This whole weekend has gone from bad to worse, anyone have any suggestions or please tell me what additional information would be needed to help troubleshoot this?
Thanks,
Greg

Hello,
Please check if the Mail.que file grows larger on HUB transport server. If so, please delete it as the following article:
http://msexchangeguru.com/2011/06/02/mail-que/ (Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information)
Please disable anti-virus software temporarily to check the result.
And please check if there is any error in application log.
Cara Chen
TechNet Community Support

Exchange 2007/2010

When will the Exchange gateway support newer versions of Exchange?
Thanks,
Al

Using 2003 as a bridgehead server - today.
T
On Thu, 12 Nov 2009 14:10:07 GMT, "Al Hidalgo"
<[email protected]> wrote:
>When will the Exchange gateway support newer versions of Exchange?
>
>Thanks,
>
>Al
Tim
Tim Heywood (NKP)
NDS8
Scotland
(God's Country)
www.nds8.co.uk
In theory, practice and theory are the same
In Practice, they are different

Exchange 2007 2010 coexist autodiscover fails

We are migrating from 2007 to 2010. Autodiscover is not working on the 2010 CAS servers (4 of them).
SMTP=[email protected]
Attempting URL
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml found through SCP
Autodiscover to
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml starting
GetLastError=o; httpStatus=500
Autodiscover request completed with http status code 500
Autodiscover to
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml Failed (0x80004005)
If I browse to the page, it returns the normal XML - error 600 Invalid request page.
The AutoDiscoverServiceInternalUri is set to
https://autodiscover.newpagecorp.com/Autodiscover/Autodiscover.xml on both the 2007 and 2010 CAS servers.
If we point our autodiscover DNS record to the 2007 CAS servers, 2007 mail users function just fine. If we point it to 2010 CAS servers, autodiscover fails, for both 2007 mail users and 2010 mail users (we only have 3 test users migrated)
Please help!
Thank you!

Just noticed this in the event log:
Log Name:      Application
Source:        System.ServiceModel 3.0.0.0
Date:          4/24/2014 7:06:02 PM
Event ID:      3
Task Category: WebHost
Level:         Error
Keywords:      Classic
User:          SYSTEM
Computer:      server.domain.com
Description:
WebHost failed to process a request.
Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/32001227
Exception: System.ServiceModel.ServiceActivationException: The service '/Autodiscover/autodiscover.xml' cannot be activated due to an exception during compilation. The exception message is: A binding instance has already been associated to listen
URI 'http://server.domain.com/Autodiscover/Autodiscover.xml'. If two endpoints want to share the same ListenUri, they must also share the same binding object instance. The two conflicting endpoints were either specified in AddServiceEndpoint() calls, in a
config file, or a combination of AddServiceEndpoint() and config. . ---> System.InvalidOperationException: A binding instance has already been associated to listen URI 'http://server.domain.com/Autodiscover/Autodiscover.xml'. If two endpoints want to share
the same ListenUri, they must also share the same binding object instance. The two conflicting endpoints were either specified in AddServiceEndpoint() calls, in a config file, or a combination of AddServiceEndpoint() and config.
   at System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost)
   at System.ServiceModel.ServiceHostBase.InitializeRuntime()
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   --- End of inner exception stack trace ---
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath)
Process Name: w3wp
Process ID: 8256

Migrating Exchange 2007 SP1 to Exchange 2013

Follow the Exchange Deployment Assistant to the letter and you will not have issues.http://technet.microsoft.com/en-ca/exdeploy2013/Checklist.aspxAnd my guide:You need to make sure your OutlookAnywhere and AutoDiscover settings are setup properly along with Split-DNS. OutlookAnywhere and Split-DNS are vital for future-proofing your Exchange configuration and making it work properly now, regardless if you use Exchange 2007, 2010, or 2013. For Exchange 2013, OutlookAnywhere is a requirement and Split-DNS is Best Practice. If you are on Exchange 2007 or 2010, and you do not have OutlookAnywhere enabled, enable OutlookAnywhere and follow this guide.You should always use NTLM over Basic authentication, as Basic sends the username and password in the clear, and NTLM is Windows Authentication. On Exchange 2013, you also have a new option...

This is a slightly daunting task I must admit. I am migrating an old exchange 2007 SP1 installation over to 2013 SP1 and looking for good advice and/or tips. I am finding the whole thing slightly unnerving as there seems to be about a million caveats give or take a few thousand. There seems to be about the same amount of tips, tricks and guides as well, but sadly they are not quite consistent and some are down right contradicting each other.I'm reading similar questions here on spiceworks, and it seems like I'm reading about one horrible episode after another. By now, I assume most have migrated already, so I though I might pick some brains and figure out the best way to do this ;)Might software like CodeTwo Exchange Migration or Dell Migration Manager be a good idea? Are there maybe similar tools available as well?Any feedback is very...
This topic first appeared in the Spiceworks Community

Setup first Exchange 2013 with mixed mode exchange 2007/2010

Similar Messages

Maybe you are looking for