Running Exchange 2007 server in unsynchronized RU levels

We have Exchange 2013 with legacy 2007/2010. My 2007 servers are at RU10. one of my sites has a need to replace their edge server and wants to install a 2013 edge server, but the internal 2007 hub server will require RU13 to communicate with the 2013 edge.
Will updating that single hub server to RU10, and leaving the rest of my 2007 environment at RUY10 cause issues?
Tom

Hi Tom,
Thank you for your question.
We could make internal Exchange at different CU level, but it didn’t recommend by Microsoft, as Hinte’s said. Because there are some improvements at new CU for us to avoid issue, include communicate between internal Exchange 2007 server.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).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

Similar Messages

Exchange 2013 SP1 Readiness Checks: No Exchange 2007 server detected

Hi there,
We are planning to upgrade our current Exchange 2007 server with the new Exchange 2013 SP1. I have been following Exchange Server Deployment Assistant to assist me with this task. Only schema update (setup /PrepareSchema) had been done so
far. I didn’t run setup /PrepareAD command manually because I wasn’t sure if I need to provide ‘Organisation Name’ with it or not?! I have installed all of the prerequisites as noted in the Microsoft documentation.
Now, I am a bit confuse with the ‘Readiness Checks’ page during graphical user installation of Exchange 2013 SP1 setup on Windows 2012 R2. Windows 2012 R2 server has all available updates applied.
===
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
===
I get the message why setup wants to run preparation for the Ex2013 with the ‘Setup /PrepareAD’. But, why ‘No Exchange 2010 server role have been detected in this topology’?! Ok, in my case setup doesn’t detect Exchange 2007 server. Is that ok to proceed
with the installation or something else needs to be done first?
Thanks in advance.

I need Exchange guru advice here please. Since we already have Exchange 2007 SP3 RU 10 in our Windows 2008R2 Active Directory domain here I need to be 100% confident that pushing Exchange 2013 SP1 “Install” will not override our existing Ex2007 environment.
That would be a huge disaster!
Microsoft is saying that: “Microsoft Exchange Server 2013 Setup displayed this warning because
no Exchange Server 2010 or Exchange Server 2007 server roles exist in the organization.”
http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Ok, I get the message about if I continue with Exchange Server 2013 installation, I won’t be able to add Exchange 2010 or Exchange 2007 servers to the organization at a future date..., and why would I need to do that anyway?!
Microsoft wording about “some solutions may require the use...” are very confusing since we will require to consider “Coexistence or migration requirements"
Perhaps, before running Exchange 2013 SP1 setup I need to run setup for preparing AD without “Organisation Name” parameter?! Something like this:
setup /PrepareAD /IAcceptExchangeServerLicenseTerms

Errors Decommissioning Exchange 2007 Server

We are attempting to decommission an Exchange 2007 Server (single server). We have already gotten 2010 set up, installed, mailboxes moved and public folders moved. We went through and removed the replicas on the old server as well as removing the mailbox
database and public folder database.
From this point we are attempting to Uninstall Exchange 2007 using either the Wizard or through cmd using setup.com /mode:uninstall after navigating to the Bin folder in the Exchange server. Each time however, we get the same error regardless of how we are
doing it.
We uncheck all roles, hit Next, and it fails during the Readiness Check within 10 seconds on each role (Mailbox, Client Access, Hub Transport) each time saying: 'An error occurred while running the test. The Computer may be out of Memory, or the XML files
have been modified. Parameter name: ConfigurationFileLocation'
I've gone through using ADSI Edit and removed the server from the Configuration>Services>SiteDomain>Administrative Groups>Exchange Administrative Groups>Servers
and it was none existent in the Databases section.
Even after all of these steps I'm still getting the error about the memory or XML file issue. Is there a way to replace the XML files with 'clean' ones or a way to repair the existing ones? I'm just simply wanting to uninstall it at this point.
Thanks!

Hi,
From your description, I would like to clarify the following things:
1. It is not recommended to uninstall Exchange server in ADSIEdit.
2. The above error indicates that one of the xml files is corrupted, you need to re-download it for troubleshooting.
Hope my clarification can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

How to change domain name on Windows 2003 running Exchange 2007

Hi all,
I have a windows 2003 server running Exchange 2007. I am wanting to rename the domain, however when I search the web for the process to perform a rename of the domain I see "The domain rename operation is not supported in Microsoft Exchange Server 2007".
How can a domain name be changed? http://technet.microsoft.com/en-us/library/cc781575%28v=ws.10%29.aspx
The server runs active directory, dns, dhcp, and Exchange 2007.
This change is being inspired by the change with SSL certs where internal addresses like .local will no longer be supported in the third party certificate registrars. Recently we renewed our cert and did not include the .local URL. Now the internal
systems are getting warnings about the cert. I tried generating an internal self signed cert but it seems only one cert can be valid with exchange 2007 running on windows 2003. Thus the internal cert replaced the external cert and allowed
the internal systems to run without complaining about the cert but the external access was causing warnings. I reversed back to the third party cert. This cert has company.com and mail.company.com and autodiscovery. I believe if I rename
the server to server2.company.com the autodiscovery will allow the server2 to be mapped to company.com and the cert will be valid for internal clients.
Do I have this correct? Are there errors with what I have found so far?
Any suggestions about how to solve this issue short of getting a new server? How can I rename the domain?

Hi,
As you mentioned, the domain rename is not supported in Microsoft Exchange Server 2007.
About your question with certificate, we can change URLs to xxx.domain.com. More details about this workaround, please refer to:
https://support.microsoft.com/kb/940726?wa=wsignin1.0
Note: please make sure the same name with certificate.
Additional, Microsoft do not recommended to install Exchange server on a DC. I suggest install Exchange server on a member server. More details to see:
Installing Exchange on a domain controller is not recommended
http://technet.microsoft.com/en-us/library/ms.exch.setupreadiness.warninginstallexchangerolesondomaincontroller(v=exchg.150).aspx
Best regards,
Allen Wang

Exfolders.exe tool crashes on Exchange 2007 server

I've downloaded Exfolders.exe and I'm trying to run it on my Exchange 2007 server but it crashes everytime. I get an APPCRASH with a fault module name of kernel32.dll
http://gallery.technet.microsoft.com/Exchange-2010-RTM-<//wbr>ExFolders-c76c3649
I followed all the instructions step by step.
How do I fix this?

Hi,
You didn't see this information?
ExFolders must be run from an
Exchange 2010 server - it cannot be run from a workstation as PFDAVAdmin could. It can connect to Exchange 2010 or Exchange 2007, but not older versions.
PFDavAdmin is the tool to use on Exchange 2007
http://www.microsoft.com/en-us/download/details.aspx?id=22427
Martina Miskovic

Treo 755p can't sync w/Exchange 2007 Server - AirSAMStateMachine.c 1913 14594

We recently migrated to an Exchange 2007 server and would like our phones to start using ActiveSync. All our Windows Mobile phones have no problem at all. However, we have two users who have the Treo 755p (running Palm OS), and they can't synch.
After some research I believe this is likely an SSL issue, and so I tried downloading the Palm Certificates Tool and uploading the root cert (GoDaddy whom issues us the cert that we use on our Exchange server), but that didn't work. I tried the actual cert issues to us, and a bunch of other combos, nothing works. The error is the same on both phones. Disabling the SSL in the settings simply gives us another error: AirSAMStateMachine.c 1913 4682
Any ideas? Maybe I'm uploading the SSL certs wrong?
Post relates to: Treo 755p (Sprint)

I wouldn't give up so soon. Imag here. Part time Exhange Admin, snowboarder, and denture wearer.
Your IT crew may have installed the SSL certificate correctly, and then again, maybe not. I've seen a few 2007 migrations that have missed some crucial steps that are fairly easy to fix. And given the symptoms you're seeing, it sounds like they missed something (left the default self-signed exchange cert enabled - oopsie-dah)
Check with your IT staff and ensure they IMPORTED and ENABLED the SSL cert using the Exchange Management Shell. If they applied it via IIS console, that may be the problem right there. With luck, we can debunk and put an end to this godaddy panic. Tell your admin they can PM me for additional details if they need any.
Post relates to: Centro (Sprint)

Removing Exchange 2007 Server from Management Console List

Hello,
We have an organization with a single Exchange 2007 Server running in production. It is working fine.
However, we brought up another server (we'll call it the secondary server for purposes of this thread) and linked it into this organization several months ago. Our plans for this box changed and we have kept it powered off, unlicensed, and unused.
Now, when we manage our production server, the management console keeps complaining about how the secondary server is almost at the end of its trial period, needs licensed, etc.
Since we might or might not use the secondary server in the future, it is possible to "unlink" it (or set it dormant somehow) from the server list to stop the license warnings? Or is our only recourse to remove Exchange and take it down if we don't
intend to license it and bring it into production? Our hope is that it can wait in the wings until such time as we decide to user & license it.
What are the implications if we ignore the license warnings and continue not to use it? Will it impact management of the production server at all or just continue to annoy?
TIA, Tom W.
JTW

Hello,
"What are the implications if we ignore the license warnings and continue not to use it? Will it impact management of the production server at all or just continue to annoy?"
You should have all production servers licensed but after trial period expiration the server will have all Exchange capabilities and features. Also trial period expiration should not have any negative impact on your environment. The EMC will simply prompt
to license that server correctly.
"Our plans for this box changed and we have kept it powered off, unlicensed, and unused."
In my opinion it is bad idea to have Exchange server installed but powered off. Note that this server still resides as object in Active Directory and it may complicate any future modifications of your environment (migration to newer versions of Exchange
etc.). I think you should use this server to provide some kind of high availability (and provide proper license for it) or remove it completely.
Once again: trial expiration is not a problem from server's functionality perspective, Exchange server powered down - it can be a problem.

I have a problem connecting to my company exchange 2007 server from my IPAD2 the same settings worked with the IPAD1

Hi All
Can anybody help with this problem when trying to authenticate on the Microsoft Exchange Sever.
I have been trying to connect the mail client on the IPAD2 to my company email (Exchange 2007 server)
There appears to be an issue with the SSL settings for the IPAD 2 and Apples new OS
I know that it’s not supported but I also know that the previous version of the IPAD worked fine using the same settings.
Just to confirm I can access the email via Safari therefore I know that the Public Key is loaded in the web browser.
Can anyone confirm that the Public Key has been installed on the IPAD 2 email client?
Is there anyway to edit the SSL settings?
Thanks in advance fro your help
Regards
Pat

Try using Static IP and force a connection.
You can get the settings from your other devices that are connected to the router.

Exchange 2007 server problems

Hello everyone,
I am having some trouble with our Exchange 2007.
Since some days ago I am having extrange troubles with out Exchange 2007 server. Users are been asked to write their user and password very oftenly, and I don't know the reason. Additionaly I have realised the OAB is not downloading properly in any Outlook
client. If I try to do it I am given an error number0x8004010F
I have been checking exhange server 2007 event viewer and I found a 80040115 error saying OALGen found an error accessing public folders while trying to generate OAL
Another error comes out inmediately after saying to check if Public folder store is mounted and there are replicas of Address Lists folders.
Another event viewer error says there was a problema trying to update availability information for the public folder in the virtual machine NAMESERVER
We have other 3 Exchange 2003 servers which I cannot remove because of an application we are using, accessing to them. As long as I know public flders are stored in Exchange 2007 server and not replicated in any other server, so I don't know if this has
something to do with the error.
Any idea of what might be going on?
Thank you very much.
Best regards,
David.

I know I'm not addressing your direct issue, but at this point you need to seriously be looking at removing all Exchange 2003 boxes. Exchange 2003 has left extended support:
http://blogs.technet.com/b/rmilne/archive/2013/10/08/save-the-date-end-of-exchange-2003-support-t-minus-6-months.aspx
What exactly is it with this app that causes it to lock on to 2003 only?
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Delete old exchange 2007 server

Hi,
We have 2 exchange 2007 server(a and b) a is v very old hardware so we have configure new exchange 2007 name is b after configure create new data base and moved all mail box A to B server but if now server A is shutdown user prompting put user name and password.

Hi There,
You need move all the services to the server B before decommission server A.
The services that you need to move are:
Offline address book
Public Folders
System mailboxes (hidden)
Change OWA host name to point to server
When do.
Uninstall server A.
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Cannot connect to Exchange 2007 server on OS 3.1

Hi
Since I've upgraded to OS 3.1 on my iPhone 3GS I cannot connect to my Exchange 2007 server. The phone simply tells me "The connection to the server failed.".
What could this be? I've read the problems that 3G people are experiencing, but I've got the 3GS.
Is there anyway to debug this? The Exchange server works fine in Outlook and I can even connect to the web interface through Safari on the iPhone.
Any suggestions?
Best regards,
Thomas René Sidor

Hi,
Seems you have found the solution here:
http://social.technet.microsoft.com/Forums/exchange/en-US/5b7d250e-c995-4322-b1e7-5ad14ace81c5/cannot-connect-to-exchange-2013-server-prompt-for-username-and-password-that-are-not-accepted?forum=exchangesvrgeneral#d266273b-e04c-45a9-8b0f-8b48bf647a86
I'm post the answers here so that it will benefit for other community members who have similar qustions:
Install the
November
2012 Update for Outlook 2007 SP3 to resolve the problem.
Thanks for our MCC steve siyavaya.
Cheers,
Steve Fan
TechNet Community Support

Outlook 2013 randomly loses connection to Exchange 2007 server

Hello everyone,
I have received complaints from some of our users over the past couple of months about them not receiving mails or about sending mails which do not get delivered. A little bit of investigation into the matter showed me that Outlook 2013 had lost its connection
to the Exchange server. (Which is Exchange 2007 SP3 running on Windows Server 2008 / SBS2008, in case it matters.)
Which is bad enough in itself - none of our users running Outlook 2007 and 2010 had that problem - but it also does so in a rather inconspicuous manner, so the users did not notice. Closing and restarting Outlook helped every single time, but the users did
not notice when this happened, and telling them to just restart Outlook every hour or so does not seem like an overloy practical idea.
All of the clients encountering the problem are running Outlook 2013 on Windows 8/8.1 Pro. We do not have any clients running older versions of Outlook on Windows 8, so I cannot tell for sure if this problem originates in the OS or if it is an Outlook problem.
The first couple of times I encountered the problem, it was on laptops, so I suspected some power management issue initially. I made sure Outlook connected to the server via HTTPS, which it already did. Then I did not hear of the problem for about two months,
but recently, two of our users have run into the problem again, and while these were still Windows 8.1 machines, running, of course, Outlook 2013, they are plain desktop computers, not laptops, and I already toned down their power management settings, so I
do not think that it has to do with the problem.
Has anybody encountered a similar problem or even - more importantly - a solution? This problem is really frustrating, because our users are very sensitive to problems with their email, and the fact that this problem only occurs randomly and - all in all
- rather rarely, makes it very hard to track down.
Thank you all very, very much for any insights you might be able to share with me!

Hi,
Please ensure that Outlook 2013 clients retain their connection with the Exchange server using HTTP:
Have the Outlook 2013 user check the settings under FILE -> Account Settings -> Account Settings -> E-mail tab -> Select the account and click Change -> More Settings -> Connection tab -> Exchange Proxy Settings -> Make sure both
"On fast networks, connect using HTTP first, then connect using TCP/IP" and "On slow networks, connect using HTTP first, then connect using TCP/IP" are selected -> OK.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Demoting and Removing Exchange 2007 Server

Oh, I mistakenly saw 2003, and I thought you were removing Exchange 2003. My bad.
Run the uninstaller on the old system. It will take care of the rest. It will probably error out and give you reasons, clean up the reasons and run the uninstaller again. Once it's uninstalled properly, then you can power off the server and everything should be good. Don't forget your send connectors. I forgot that in my travels once.

At one of our locations we recently migrated all exchange mailboxes to a new Exchange 2007 on new OS platform, moving away from Server 2003. Everything to my knowledge has been migrated, users should be all connecting to new server, all connector headends have been updated, etc. As a test, I shutdown the old Exchange server (without uninstalling) but we ran into issues that day with Outlook constantly (every 5-10 minutes) asking for the user's password, slow loading of folder data, etc.; reboots/application restarts did not resolve. We turned the old Exchange server back on and all is now well. My theory is this is due to the schema still containing info about the old Exchange server. If I uninstall Exchange completely, thus removing it form schema, could I expect to have this issue resolved? Obviously I only get one chance on this, so...
This topic first appeared in the Spiceworks Community

Onsite Scanner Unable To Send Documents Through Exchange 2007 Server (SBS 2008)

I have an SBS 2008 server complete with Exchange 2007 in house and have configured Exchange 2007 to use the Exchange Online Protection (EOP) to process mail for malware, etc. This setup has worked great for the last year or so with no issues.
However, all of a sudden in the last couple of weeks our onsite copier can no longer send documents through email to anyone within the organization. The copier is a Kyocera TaskAlfa 3050CI and exists with the same network. The copier can scan
to a network folder without issue.
If I change the SMTP settings to use a gmail account instead of a local account I can send mail to outside email address. Even with this changed though I still can't send to our domain addresses.
I tried running a message trace from the Exchange Management Console but it doesn't find anything for hte given subject or date/time when I scanned the document.
I am not exactly sure what I should be checking or what piece of the puzzle is causing the problem here. Any ideas on what might be happening or how to correct it?
Thanks so much!

Hi,
Any update? Would you please let us confirm some questions as Howtodo mentioned. Please feel free to let us
know.
Based on your description, it seems that only the copier can’t send documents via emails. On your SBS 2008
environment, please check if some user accounts encounter the similar issue. In other words, did users also can’t send emails attached with documents? If the email was attached with a small size document, will the same result?
In addition, can find any relevant error or events?
Hope this helps.
Best regards,
Justin Gu

IPhone4 wont connect to my exchange 2007 server

I just purchased the new iPhone4. After moving from the 3G that was running fine I moved over to my new Iphone4. When setting up my Exchange account that runs on Exchange 2007 I see that the device registered on my exchange server fine and on the phone it will register the mailbox, but it will never update the Active Sync policy on my server or sync the device. On the phone side I get a "Cannot get Mail"
I tested this using my test account that is on the same mailserver and has the exect same policy and it works fine without a hitch.
Please help

http://support.apple.com/kb/TS1398

Running Exchange 2007 server in unsynchronized RU levels

Similar Messages

Maybe you are looking for