Exchange 2013 MB/CAS integration with legacy Exchange 2007 CAS/MB/Trans server

Hi All,
I have an existing running Exchange 2007 SP3 RU13 server acting as MB,CAS,Transport using a Barracuda SPAM for SMTP (MX Record is assigned to here), and a TMG2010 server performing all ActiveSync, Outlook Anywhere, and OWA connectivity.
I have built a new Exchange 2013 SP1 server that will (for the meantime) act as a MB & CAS server only.
I successfully migrated a testuser mailbox to the new EX2013 server from the EX2007 server. The problem is that once migrated, OWA and Outlook can't access the mailbox.
OWA form our URL gives the message: Outlook Web Access is currently unavailable. If the problem continues, contact technical support for your organization and tell them the following: No Client Access servers of the appropriate version can be accessed from
the Internet
If I run OWA from the EX2013 URL it works ok, but not for MBs on the EX2007 server.
I tested this configuration in a VM lab and it worked ok. All I had to do was move the mailbox, then run Outlook. Outlook automatically found the new server and opened the MB.
Basically what I need to do is move all our existing MBs from the old 2007 server to the new 2013 server. I want to continue to use the exisiting transport/CAS/EDGE services on 2007 without having to rebuild both the internal and external comunications
infrastructure at the present time.
How can I get the EX2013 server to act as the MB server for the EX2007 communications infrastructure?

Hi,
Please try to create a new user on Exchange 2013, and send/receive email via both Outlook and OWA to test whether the Exchange 2013 mail flow well.
If Exchange 2013 works well, please try to bypass the TMG on Exchange 2007 for a little while for testing.
Additionally, we can use CAS 2013 URL to proxy/redirect previous CAS, or publish both CAS 2007 and CAS 2013 to be internet facing server with separate URLs, as Ed suggested.
Thanks
Mavis Huang
TechNet Community Support

Similar Messages

Installing Exchange 2007 on a Windows Server 2008

Hello I am new to the Microsoft forum and I have a quick question and please let me know if im posting my question in the wrong place. Im doing a school project were you have two servers with Windows Server 2008 installed on them. The first server suppose
to have Active directory and domain services followed by dns which I did. The second server which I just found out suppose to have installed Netframework 3.0, Wpa and Desktop experience roles then install Microsoft Exchange 2007. Well my issue is when I try
to install exchange on my second server it keeps giving me a error message saying my Active directory cannot be contacted or may not exist and that my second server has the wrong security credentials. I've taken the steps that Microsoft has advise by checking
my domain. Which I used the command Dcdiag.exe on my first server and it saids the domain is able to be contacted. Also when I joined my second domain I made sure to put the domain name of the first server in all caps followed by /Administrator and my password
and it said welcome to the domain. So has anybody run into that type of error message when trying to install exchange 2007 on a separate server? Lastly forget to include I also have web server IIS installed on the second server as well. Exchange is then asking
for IIS 7.0 ? So any tips or troubleshooting would be helpful since my professor wasn't much a help and I gotta turn this lab stuff in by next week.
thanks gmoney38

Not sure I need to check that through the dns is working far as ive seen in the server manager . Because I remember before I did this one command for the dns and it said something was wrong with the host A record. So I went through the hierarchy of
windows to that file and opened it up through the notepad it showed my loopback ip address 127.0.0.1 and localhost and not my domain name which I choose contoso01.com so from a previous forum I read if you change the localhost name to that domain name
that it would help but im not sure if this would in my case. Thanks for answering my question Mr. Ed but I still need some more help through!
gmoney38 ps plus im using vmware for this project to have the two servers i wonder if this is why im having issues!

Exchange Integration with MSX-A on a Windows 2003 Server

Hi
We try to integrate Microsoft Exchange (Version 2003 SP1) into SAP Enterprise Portal 6.0 SR1. The MSX-A components are installed on the OWA System, a different Windows 2003 System with Outlook XP (SP3) on it.
The error displayed in the Calendar iView on the Portal:
"An internal error occurred while generating the XML from the MSX-A component"
From the "SAP EP Test Exchange Transport Setup" Tool an error occures on the "Data Retrieval" Test:
"An error occurred retrieving the data."
and in detail:
MAPI_E_LOGON_FAILED(80040111)
MS KBase http://support.microsoft.com/kb/181739/en-us didn't help. To resolution 3: Policy "Log on Locally" on a Windows 2003 doesn't exist anymore (?). "Deny Log on Locally" isn't given to relevant groups.
Thanks and best regards
Nicolaj

hi All
i am illustrating the process of integration the central notes to be referred and constraints .hope this definitely helps you please do not forget to give full points for this effort
with regards
subrato kundu
Process
Microsoft outlook Integration With SAP Enterprise Portal 6.0
(Process description)
These documents describe the entire process of integrating Exchange server with enterprise portal server to leverage the usage of lotus notes within the portal framework.
Step1: Create a System
o Choose System AdministrationSystem configurationSystem LandscapePortal ContentContent Provided by SAP. Right click on collaboration and then choose New From ParSystem.
o Select com.sap.netweaver.col.app.gw and choose next.
o Select a server (Microsoft Exchange server) and then choose next.
o Enter the System Name and ID (for ex Exchange) and choose next and then finish.
o Enter System Aliases by choosing system Alias from the display drown list.
o Enter the system Alias in the alias field and choose add and then save.
Step II: Create E-Mail Transport
 The email transport defines the SMTP server and other configuration required for sending e-mails. To configure an e-mail transport choose
 System AdministrationSystem ConfigurationKnowledge ManagementCollaborationGroupWare TransportsMail Transport
 SMTP Sever: The address of the SMTPServer for sending e-mails
 Sent Messages: You specify the folder on the server where the sent e-mail is to be store: -Sent Items on Microsoft Exchange Server.
 System Alias name: Alias that was defined for the groupware server in system configuration.
Step III: Check E-Mailing Service
This is a global service that is required for sending e-mails and which can be located by choosing System AdministrationSystem configurationKnowledge ManagementContent ManagementGlobal servicesMailing Service. This service needs to be active and an email transport must already have been created.
Microsoft Exchange Transports
The overall transport consists of two parts: MSX-J on the portal server and the MSX-A on the Exchange Server or a machine near to the Exchange Server.
MSX-J is the java part that runs on the portal server is deployed automatically on the portal server during installation, and implements the groupware API.It uses the Groupware APIs and repository development kit.
MSX-A is the active server page and sap exchange connector.dll running on a n iis server with Microsoft Collaboration data objects (CDO) and in the same domain as the exchange server or in a trusting domain .The ASP and DLL are Collectively CALLED MSX-A and is installed as part of the Outlook Installation. This needs to be installed on every IIS SERVER dedicated to the MS Exchange Server
 The Process flow is
1.TheMSX_J transport makes an HTTP(s) call to the MSX_A running on the IIS.
2.Microsoft Internet Information Server (IIS) uses Basic Authentication to authenticate user based on NT user/password against the Microsoft Exchange Server.
3.CDO uses the authentication token and fetches the data.
4.MSX-A converts the data into XMl and returns it to MSX-J
Installation of MSXA Components
You have to carry out these steps for every IIS that accesses the exchange server or the Outlook WEB Access 5.5 SP Server in the system landescape:
1.Locate the MSX-A component shipped with Exchange transport.
The components can be found in<irj>\root\WEB-INF\PORTAL\PORTALAPPS\com.sap.netweaver.coll.appgw\WEB INF\external\Exchange.
2 Locate an IIS that is in the same domain as the Exchange Server or in a trusted domain.
3.Create a folder on the IIS for example,c:\SAPExchangeTransport.
4.Copy the MSX-A Components to the folder you just created.
5.Register the DLL by using command regsrvr32 in the command prompt for example c:\winnt\sysytem32\regsvr32.exe c:\SAPExchangeTransport\SapExchangeConnector.dll
6.Create a new Iis Website or if using Outlook Web Access 5.5 sp4 create a virtual directory
Since most of configuration errors arise in the setup and configuration of the MSX-A components a separate test application is shipped with the connectivity, which allows you to check that the setup is correct.
1.locate SAPPXchTest.exe which is shipped with the exchange transports.The components can be found at <irj>\root\portalapps\com.sap.netweaver.coll.appl.gw\external\exchange.
2 copy the executable file to the machine on which the MSX-A component has been deployed.
3.Test the CDO version by launching the executable file on the machine on which msx-a was deployed.Choose Test CDO-Version .You should receive a success message .if you recive an error message follow the instructions given
4Test data retrieval by launching the executable file on the machine on which MSX-A was deployed choose TestData Retrieval Fill in necessary fields you should receive a success message but if you receive an error message follow the instructions given
5.Choose Save Results
6.open the log file indicted by the message
Notes
0000801234 Additional attachment in room created appointments
0000788151 Post Installation Steps for Groupware after an upgrade
0000763062 Problem creating an appointment with attachment
0000738965 E-mail address is mandatory for Groupware Integration
0000736644 Mandatory Steps for MS Exchange Integration
0000736541 Support information for MS Exchange Integration
0000732911 Integrating Outlook Web Access in Enterprise Portal 6.0
0000712902 SSO to Outlook web access using user/password does not work
Constraints
Constraints of Microsoft Exchange Connectivity
 The Microsoft Exchange transport currently only support items with types appointment and meeting request .Other types such as discussion and not currently not supported.
 Deleting an instance of a recurring appointment affects only that particular instance
 Calendar items in personal folder are not supported. Users can only view and modify items located on the exchange server from the iviews
 Public folders on the exchange server are not supported
 Calendar items are delivered as such if sent to recipients within the intranet .If the recipients is in different domain than the sender ,the format in which the items are delivered depends on the server responsible for sending the item in question

SharePoint 2013 on-premises integration with third party email account

the Email sending issue from SharePoint is causing too much time waste
First let me explain how our SharePoint is deployed
Sharepoint version : 2013
Deployment type : on-premise
Authentication : from Domain controller also hosted locally
domain name ; say domain.com this domain.com is same as our website address hosted on godaddy
SharePoint computer name on local DNS : sharepoint.domain.com
OS and IIS : 2008 r2 , IIS 7.5
Network firewall : 25 26 ports opened for sharepoint , both incoming and outgoing.
Server firewall : turned off
Email configuration Attempts by IIS 6.0
We tried following setting on IIS 6.0 SMTP local server properties
In General tab
qualified name was shown as : sharepoint.dts-solution.com
IP assigned : sharepoint server IP , advanced putted two entries of IP with ports as 25,26
In Access tab
Authentication : selected as Anonymous
Connection : All except below list : empty list
Relay : only the list below , one entry as 127.0.0.1 and other is local static IP of SharePoint server
in Delivery tab
outbound security : Basic authentication : accessed user in AD and given the right password, also checked with annonymous -not working
outbound connection: all default values and port = 25
Advance : fully qualified domain name = sharepoint.domain.com , DNS test showed success, rest every check box unchecked
On sharepoint central management settings
Outbound email = sharepoint.domain.com
from and reply to address = [email protected]
IIS 7.5 SMTP settings
In IIS 7.5 sharepoint application we added SMTP settings as smtp server = godaddy out going smtp , user name as [email protected] , password = godaddy password , port : godaddy outgoing port .
Godaddy account
Our website hosted on godaddy with same name as domain.com
open relay not possible on emails.
Results
After setting alerts on SharePoint sites and assigning tasks with alerts we receive email in queue folder but they never get forwarded. We just wish to use any of our email *.domain.com to send outgoing emails from SharePoint . Its been a while we have no
success.
Tech Learner

Hi,
As I understand, you are using SharePoint 2013 integrating with third party SMTP server which provides email function.
From SharePoint side, I'd suggest you refer to the link below to configure email integration:
http://technet.microsoft.com/en-us/library/ee956941(v=office.15).aspx
If you have already confirm that message is sent from SharePoint, while stuck in queue on SMTP server, then the issue might be related to relay on SMTP server. Since the issue is related to third party product, we do not have enough resource here,
I'd recommend you contact their support engineer for more assistance:
https://support.godaddy.com/help/category/154/email
https://support.godaddy.com/help/article/3552/managing-your-email-account-smtp-relays
Thanks for the understanding.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

MS Edge services wont start on exchange 2007 installation on a server 2008 r2 in a 2003 domain

Hi
I had a previous installation of exchange 2007 vanilla that I had to delete because of some errors on the nic card in a 2003 exchange environnement migration preparation. I've build a brand new 2008 R2 and i'm trying to install a new exchange 2007 SP1. When
the service edge try to start it seems that it doenst want to get install. I've disable IPV6 from the nic and still the same problem. Is there something that need to be removed in the AD because of my previous 2007 installation ?
thanks

Hi,
I find this for your reference:
I would install Exch 2007 with SP3 slipstrreamed. The download for SP3 is the full installation of Exchange. The fact that Exch 2007 with SP1 is not R2 compatible, you will run into problems.
http://www.microsoft.com/downloads/details.aspx?FamilyID=1687160b-634a-43cb-a65a-f355cff0afa6&displaylang=en
"Clean installations of Exchange 2007 SP3 on a new server are possible by using this download in the same manner as you would install Exchange 2007 RTM, Exchange 2007 SP1 or Exchange 2007 SP2.
More details in the following similar thread:
Exchange Server 2007 SP3
http://social.technet.microsoft.com/Forums/en-US/03e7cabd-a002-4920-b2f7-d6d1dd61c76f/exchange-server-2007-sp3?forum=exchangesvrdeploylegacy
Thanks
Mavis Huang
TechNet Community Support

Lync 2013 On Premises integration with Exchange Online Unified Messaging

I am working on deploying Lync 2013 Server on premises and integrating it with Exchange Online. We do not use Exchange on premises.
My question is how to integrate with Unified Messaging specifically. Other functions like Calendar, call logs seem to be working fine.
There are many guides online on how to do this, and I have read many and attempted to follow with no luck. All seem to assume that UM has already been deployed on prem which I don't have. Is this possible to integrate Lync with Exchange Online without having
and Exchange deployment on premises first.
Another source of confusion is the Office Voice Access number and how Lync clients dial voicemail. Where does this go if somebody dials internally (from Lync) and externally (from PSTN)? Exchange online or Lync on prem? And if Lync, then my guess would be
Lync forwards on to Exchange Online UM somehow. Do I have to purchase a number from somewhere because of it being on 365 or can I use a spare DID?
From my tests so far, when I call voicemail as any user, it seems to dial that same user and then the call fails.
Hopefully someone can shed some light on this for me.

You can integrate Exchange UM with Lync Server 2013.
Please check the deployment process at http://technet.microsoft.com/en-us/library/gg398968.aspx
Lisa Zheng
TechNet Community Support

SharePoint 2013 on-premises integration with goDaddy Email account

Hi Everyone ,
We wish to integrate our on premise SharePoint 2013 notifications and other related stuff with our Domain emails hosted on GoDaddy servers.
We are unable to find the related support content on internet.
We have integrated email via SMTP with our outlook already. So far my understanding is that we have to add SMTP settings in IIS Sharepoint Application and then adding these settings in Central admin settings.
Tech Learner

Hi,
Based on your description, my understanding is that you want to configure the outgoing email setting and incoming email setting in SharePoint 2013.
You can use the SMTP server for your outgoing email and incoming email settings in SharePoint 2013.
Please refer to the links below:
Configure outgoing email for a SharePoint 2013 farm:
http://technet.microsoft.com/en-us/library/cc263462(v=office.15).aspx
Configure incoming email for a SharePoint 2013 farm:
http://technet.microsoft.com/en-us/library/cc262947(v=office.15).aspx
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Sharepoint 2013 on-premise integration with MDM solution on Mobile

Hi,
Can sharepoint integrate with a MDM solution on the mobile based on device certificates?
Thanks
Naresh

Hi Naresh,
i would like to suggest you to open a thread also at MDM forum, perhaps there is a clue regarding the device certificate: http://social.technet.microsoft.com/Forums/en-US/home?forum=winphonemgmt&announcementId=048fe18a-0606-4079-a1ec-0fc5bd9a1f1d
for more info regarding the certificates you may check at this article:
http://technet.microsoft.com/en-us/library/bb633120.aspx
please correct me if i am wrong, as i know sharepoint may not have the integration to MDM using OOB feature.
if should the certificate able to set at mobile and system center perhaps sharepoint also able to accept it since it may also use SSL.
Regards,
Aries
Microsoft Online Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Outlook 2010 Will Not Connect to Exchange 2007 on SBS 2008 Server

Good Morning,
I have a user who cannot connect to the exchange server on SBS 2008 with outlook 2010. When they start outlook, it shows disconnected and will not connect for a minimum of 20 minutes to an hour. Any suggestions on how to fix this would be appreciated.
I have rebuilt their profile, but that does not fix the issue.
Thank you,
Lee F.
Lee Feldman SMB Consultant

Hi,
Thanks for posting in the forum.
Regarding the current issue, since you have recreated the user profile without any issue, I suspect that it’s mainly caused by the network issue. At this time, please first check the TCP/IP
configurations as Larry mentioned. Then, please also refer to the article below for details about how to troubleshoot Outlook connectivity issue.
Troubleshooting Microsoft Exchange: Outlook Connectivity Issues
http://blogs.technet.com/b/mspfe/archive/2011/04/12/troubleshooting_2d00_microsoft_2d00_exchange_2d00_outlook_2d00_connectivity_2d00_issues.aspx
Hope this helps.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Andy Qi
TechNet Community Support

Oracle IdM integration with Microsoft ILM 2007/FIM 2010

We currently have ILM 2007 in our environment with limited usage at the moment. We are looking at purchasing Oracle Identity Manager to implement an enterprise wide IAM solution.
We were wondering if it is possible to continue using ILM like a middleware between our AD forests and the Oracle IdM. Where the Oracle IdM is the overarching IAM solution and Microsoft ILM 2007/FIM 2010 is like the metadirectory for our AD forests.
Is this possible without installing the Oracle Management Connector on any of our DCs and using ILM as the directory that Oracle IdM connects to. All AD account provisioning/de-provisioning, acct updates, password sync/reset will be initiated from the Oracle IdM to ILM and then implemented on AD. In order words no direct interaction with AD domain controllers from Oracle IdM, everything will go to ILM and ILM in turn applies it to AD.
Is this possible?
Is there a custom connector that will work with ILM 2007/FIM 2010
Is this a simple customization or something that can be problematic and expensive?
Any feedback is much appreciated
Thanks

user1106726 wrote:
We currently have ILM 2007 in our environment with limited usage at the moment. We are looking at purchasing Oracle Identity Manager to implement an enterprise wide IAM solution.
We were wondering if it is possible to continue using ILM like a middleware between our AD forests and the Oracle IdM. Where the Oracle IdM is the overarching IAM solution and Microsoft ILM 2007/FIM 2010 is like the metadirectory for our AD forests.
Is this possible without installing the Oracle Management Connector on any of our DCs and using ILM as the directory that Oracle IdM connects to. All AD account provisioning/de-provisioning, acct updates, password sync/reset will be initiated from the Oracle IdM to ILM and then implemented on AD. In order words no direct interaction with AD domain controllers from Oracle IdM, everything will go to ILM and ILM in turn applies it to AD.
Is this possible?yes
>
Is there a custom connector that will work with ILM 2007/FIM 2010Yes, if you write one you will have a custom connector
>
Is this a simple customization or something that can be problematic and expensive?It won't be simple. Problematic and expensive maybe, depends on how good you are with OIM and ILM

Remove Exchange 2007 from an Exchange 2013 coexistence.

Hey everyone,
I've just installed Exchange 2013 on a new server and all is working great. It is currently in coexistence with our old Exchange 2007 server. I've since shut the server down and Exchange 2013 has been working without issue. However, I haven't
been able to find any articles on this matter so I figured I would ask the question here.
How do you remove Exchange 2007 from the coexistence. Do I just uninstall Exchange 2007 from the old server and it will remove itself from the server and the domain? Any help/link on this matter would be greatly appreciated.
Thank you,
Chris

Hi Simon,
I am about to do the same exercise as Chris, I just would like some clarity.
1) When you say mailbox Database, do you mean make sure there are no more mailboxes that you want to move over, or are you actually meaning delete the physical DB on the exchange 2007 server.
2) If there is no use of public folders does anything need to happen?
Thanks,
Terry

Failled Exchange 2007 to SP3 how can I continue to upgrade to Exchange 2013

I have domain with 2 - 2003 (32bit) DC, 1 - 2008 (64bit) DC (not a good candidate for Exchange 2007) and 1-2008(64bit) DC with Exchange 2007. The Exchange server has ran out of hard drive space and the equipment needs upgrading. Several
attempts were made to update to SP3 but it failed.
The option to move the Exchange 2007 to another server is null. Will Exchange 2013 read 2007 mailboxes? Is there a way to move the Exchange 2007 Mailboxes to Exchange 2013 thru a co-existence scenario?
PraxisHousing

Hi Praxis,
Thank you for your question.
By my understanding, if we didn’t update Exchange 2007 to SP3, we will not install Exchange 2013 in organization. We didn’t upgrade to Exchange 2013.
We could expand hard drive space. If the failed error is concerned about drive space, we could move mailbox databases to other drive or other things in order to shrink drive space to update to SP3. As you said, we could move Exchange 2007 to a new
server.
If the error is about others, we suggest you post error to
[email protected] for our troubleshooting. We could refer to the following link:
https://social.technet.microsoft.com/Forums/en-US/04449b40-9911-4e73-8ae7-810627f94112/exchange-2007-sp2-upgrade-to-sp3
We could refer to the following steps to migrate Exchange 2007 to Exchange 2013:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Exchange 2007 RTM support with Windows Server 2012 R2 Domain Controller

Hi All,
I have not found any TechNet Article which states about the Windows Server 2012 R2 Active Directory domain controller operating system support with Exchange 2007 RTM, can some one please let me know that does Exchange 2007 RTM supports Windows Server 2012
R2 domain controller operating system, we are in the process of upgrading the domain controllers to 2012 R2 but not the forest and domain functional level to 2012 R2.
thanks
If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync

There are several likely reasons for this. The most significant is that Exchange 2007 RTM is no longer supported (outside ot extended support, which is not going to include adding support for new operating systems):
http://support2.microsoft.com/lifecycle/default.aspx?LN=en-us&p1=10926
You'll note from the following -
http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx - that only Exchange 2007 SP3 is currently supported in any environment.
HTH ...

Exchange 2003 sp2 to exchange 2007 sp1 upgrade error

Hi,
We had Windows 2003 DCs and Exchange 2003 servers. We migrated AD DCs to windows 2008 R2 at parent domain.
We have one parent domain and 10 child domains in remote sites .3 remote sites have been migrated to windows 2008 R2.
Now at parent domain I am trying to install exchange 2007 SP1 on a server with windows 2008 R2 SP1. I am facing certain issues:
1. When I run setup /PrepareSchema on this new exchange server , the organization check fails with error stating that : cannot find at least one DC running windows 2003 SP1 or later in DC=xyx,DC=com. This could be the result of moving DC objects in AD. Check
that at least one DC running windows server 2003 SP1 or later is located in the "Domian Controllers" OU and rerun setup".
2. When I try to install exchange server 2007 , I get the following error
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported
by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Can any one shed light on this issue.
Regards
Syed
sa

You cannot install Exchange 2007 SP1 on Windows 2008 R2 SP1 as it is unsupported.
Only version of Exchange 2007 supported when OS is Windows 2008 R2 or R2 SP1 is Exchange 2007 SP3.
Where are you installing Exchange ? child or parent domain ?
2. When I try to install exchange server 2007 , I get the following error "Object
cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Above error indicates that Exchange setup is trying to modify
a version of an object which might have been created when organization is prepared for Exchange 2010. don't you have exchange 2010 Servers already in your environment ?
Please give more information about your current email infrastructure
and whether if you are installing exchange on parent or child domain?
Pavan Maganti ~ ( 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!!

What is best practice for integration with freight forwarders?

Hello,
We are looking into the possibilities for automatically exchanging data with one of our freight forwarders. We will send them our shipment information and they will send back shipment status and date information including some additional information like the house bill. Sending the shipment data from our SAP (ECC 6) system is no issue, we have done that before. What is new to us is receiving back the status updates from the forwarder. Is there a kind of best practice of where to store this information on the shipment (or in a separate tabel) and what standard function module or BADI to use for this?
We are using ECC 6.0 sales and distribution, but no transportation management or SCM modules.
Would, like to hear the experiences of people who have done this type of intergration with their forwarders.
Regards,
Ed

SAP have added SAP TM 8.10 as a separate package which is also integrated with R/3 which means, a separate server is required if SAP TM needs to be implemented which will take care of your expectations. For more information on this, search in Google so that you will get couple of documentations on this topic.
G. Lakshmipathi

Exchange 2013 MB/CAS integration with legacy Exchange 2007 CAS/MB/Trans server

Similar Messages

Maybe you are looking for