Autodiscover after deploying Exchange 2013 CAS in a Exchange 2007 organization

I am deploying Exchange 2013 CAS in a Exchange 2007 organization. Will all the clients be directed to the Exchange 2013 CAS servers for autodiscover. Will there be any issue with outlook clients connecting to their mailbox servers in Exchange 2007

All clients should be pointed to the Exchange 2013 CAS for the autodiscover service. This means:
A. For local clients
You need to modify the autodiscover Internal URI on the Exchange 2007 server and point it to Exchange 2013. For example, if you are using split-brain DNS on the Local Network and mail.yourdomain.com is resolved to Exchange 2013 local IP, the Exchange 2007
Autodiscover Internal URI should be "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
Exactly the same way, you should modify the Exchange 2013 Autodiscover Internal URI and use the same address "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
B. For remote clients - all clients will hit the Exchange 2013 CAS first (ex. mail.yourdomain.com)
If the user's mailbox is on Exchange 2007 server, the correct XML will be generated and provided, and the user will be proxied for Outlook Anywhere/ActiveSync and redirected for OWA/WebServices
If the user's mailbox is on Exchange 2013 server, the correct XML will be generated and provided
Bottom line - based on the location of the user's mailbox, Exchange 2013 will generate and provide the correct XML file (there is not proxying involved in providing the Autodiscover info).

Similar Messages

New Exchange 2013 CAS server in existing Exchange 2007 Organization

Dear Friends,
We have exchange 2007 SP3 with CU13 installed with single copy cluster for database and 1 OWA server for CAS/HT. We will migrate from current to Exchange 2013SP1. As we want to have HA, we have installed 2 new Exchange 2013 SP1 CAS server on widnows 2012
R2 after preparing our organisation for Exchange 2013. The setup went smooth without any error and successfully installed CAS with management tools. After installation it ask to reboot the server which we did. Now after reboot, we are not able to run Exchange
Management Sell. It never connects to the new server. In our old 2007 EMS also doesn't list any exchange 2013 server. We are also not able to connect to new CAS servers with below URL:
https://servername/ecp/?ExchClientVer=15
Its says site under maintenance. Please advise what to check. We were thinking of deploying CAS 1st and make it co-exist with Exchange 2007 before deploying Exchange 2013 mailbox server which will be setup in DAG. What are we doing wrong.
Thanks in advance!!

Dear Friends,
We have exchange 2007 SP3 with CU13 installed with single copy cluster for database and 1 OWA server for CAS/HT. We will migrate from current to Exchange 2013SP1. As we want to have HA, we have installed 2 new Exchange 2013 SP1 CAS server on widnows 2012
R2 after preparing our organisation for Exchange 2013. The setup went smooth without any error and successfully installed CAS with management tools. After installation it ask to reboot the server which we did. Now after reboot, we are not able to run Exchange
Management Sell. It never connects to the new server. In our old 2007 EMS also doesn't list any exchange 2013 server. We are also not able to connect to new CAS servers with below URL:
https://servername/ecp/?ExchClientVer=15
Its says site under maintenance. Please advise what to check. We were thinking of deploying CAS 1st and make it co-exist with Exchange 2007 before deploying Exchange 2013 mailbox server which will be setup in DAG. What are we doing wrong.
Thanks in advance!!
If you have only the 2013 CAS installed and not the mailbox role, then nothing will really work. Remember, in 2013, the mailbox role does all the work, the CAS is simply a proxy for the most part.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Deploy exchange 2013 with current Exchange 2007 organization

Dear All
our company will update exchange 2007 to exchange 2013, on AD site we already update Forest functional level and Domain functinal level to Windows 2003 ( can not up to windows 2008 yet because have some ad that run windows 2003 server
) but one thing that I'm not sure, between migration we can not full tranfer mailbox form exchange 2007 to exchange 2013 in one time, we need to migrate on night time manybe one day we can migrate only 100 user per night, my question is
1. which exchange 2013 server role that we will install first ( mailbox or CAS)
2. on migration time, can we let's user used exchange 2007 to main of OWA and SMTP or not? we need all user's mailbox tranfer to exchange 2013 complete first after that we will switch OWA and SMTP

1. Mailbox, or install both on the same server at the same time. (Edited: First I said CAS, which used to be true, but now you need the Mailbox role to run PowerShell, so you have to install Mailbox first. Consider a dual-role server,
however, because there aren't a lot of cases where you need separate CAS and Mailbox role servers.)
2. You cannot. Exchange 2013 mailbox users must use the Exchange 2013 CAS. You can have users use their respective CAS while migrating, but that requires two sets of URLs and is therefore more confusing for the end user. I recommend planning
to deploy Exchange 2013 CAS, a legacy URL for Exchange 2007, and switch your hostnames to Exchange 2013. This is all spelled out in the Exchange 2013 documentation.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Decommissioning 1st OCS 2007 R2 FE after deploying Lync 2013

Hello,
We have done a successful deployment of Lync 2013 that interoperates with OCS 2007 R2. Now we want to start decommissioning OCS 2007 R2 step by step. We have four OCS pools on different sites and I want to decommission the first OCS. 2007
r2 FE. I´ve tried to follow the deactivation order suggested by different bloggers and MS site:
http://www.ucprofessional.com/2011/04/decommisioning-ocs-2007-r2-after.html
http://technet.microsoft.com/en-us/library/dd572548%28v=office.13%29.aspx
However when I want to deactivate any service like Application Host or A\V Conferencing Server I receive the next message,
even if I have domain\enterprise admin rights as well as RTCUniversalServerAdmins membership :
Remove Active Directory Object CN=UC AppServer Services
Failure
[0x80070005] Access is denied.
Remove Active Directory Object CN=LS AV MCU
Failure
[0x80070005] Access is denied.
We have a parent root domain, and this FE is joined to one of its child domains. I still have other three pools but I don´t want to touch these other three until I can decomm this first FE and its pool. I don´t have any users in this.
How could I deactivate these services on this first FE server and have my AD clean? what might be happening that the deactivation process doesn´t do its job?
Thank you for any feedback.
MC

Is the account you used to deactivate OCS 2007 R2 Servers in root domain or child domain?
Your problem is more of a permission issue.
Try to use an account created in root domain to deactivate OCS 2007 R2 servers.
Lisa Zheng
TechNet Community Support

Autodiscover issue in exchange 2007

Hello,
I had everything setup and working with autodiscover for years now. When I applied Exchange 2007 SP3 Rollup Update 12 now when I create a new user and it should automatically create the profile within outlook 2007. It does not create it. I tested the autodiscover
from my own outlook and it says everything is fine. I am not sure what has changed to stopit from working.
I have the following
Windows 2003 Standard 64bit
Exchange 2007 SP3
OUtlook 2007 Clients
Any ideas?
Thanks

When I applied Exchange 2007 SP3 Rollup Update 12 now when I create a new user and it should automatically create the profile within outlook 2007.
Hi,
About the content above, I have a different opinion. (If I misunderstand, please correct me.)
When Outlook runs for the first time (not add a user into Outlook), the profile is created automatically using the name "Default Outlook Profile."
The created profile runs whenever we start Outlook.
When we add additional accounts into Outlook, we should create new profiles manually.
In addition to the profile issue, is there any other issue?
Something like Outlook cannot connect to Exchange server or etc. ?
Feel free to contact me if there is any question.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Contact list not show after migration Exchange 2007 to 2010

Hello.
I have a old infraestructure with exchange 2007 and new organizacion with exchnage 2010
If I migrate a mailbox from 2007 to 2010 I can open the mailbox on 2010 without problems,
From owa works correct active sync and outlook work correct, I can send a receive mails but, from outlook client I can not see the Global Address list.
Step by step:
User with mailbox over exchange 2007.
Outlook, owa active sync.. all is working fine and I can see the Global Addres list from owa and from outlook.
Move mailbox from 2007 to 2010
Completed ok without errors
The user mailbox on 2010 working fine, I can access by owa by outlook and active sync and from owa I can see the Global Addres list but from outlook I can not see the GAL.
I've tried diferents outlook versions: 2003 2007 and 2010 but I can not see the GAL
If I try to download de GAL from Outlook I see outlook download the correct list and complete ok without erros but not show on outlook.
I don't know why..
Exchange 2007 with sp3 and 2010 with sp3 too.
Any idea how could resolve this problem?
Thanks in advance¡

Hi
Did you migrate your address list or create a new one? Move-OfflineAddressBook "Default Offline Address Book" -Server <your Exchange 2010 server>
Get-OfflineAddressBook | fl *server*
Set-OfflineAddressBook "\Default Offline Address Book" -VirtualDirectories "your exchange server\OAB (Default Web Site)"

Exchange 2007 to 2013

hello
i am trying to migrate exchange 2007 to exchange 2013 but what a bout spam filtring feature which installed in hub and cas server
how can i enabled in exchange 2013 and copy all configuration
what a bout accepted domain how can i migrate it ?
Receive connectors ? how can i migrate it?
MCP MCSA MCSE MCT MCTS CCNA

I see a lot of confusion here - both in the way the questions are asked, and in the incorrect and misleading answers.
The anti-spam feature in Exchange 2013 is performed by the Connection Filtering agent. It is not available in the Exchange 203 CAS or MBX roles. Exchange 2013 SP1 re-introduced the EDGE server role (about a year and a half after the RTM) and the
missing connection filtering agent (the anti-spam feature or module as DareDevil says).
Hence, you have the following options:
1. Install and configure an Exchange 2013 EDGE server.
2. Install a 3rd party Anti-Spam product.
3. Use the Anti-Spam services of an external company - all inbound e-mail should go through the servers of this company.
4. Install and use a linux server in the DMZ for the Anti-Spam filtering (that works amazingly well, and you'll be surprised how many companies are using this option).
As a matter of fact, Yasser, you've asked four questions, not just one. The accepted domains, that are already configured in you existing Exchange 2007 organization, are configured automatically on the Exchange 2013 servers - you don't have to perform this
task manually.
Depending on your deployment - [CAS+MBX] or separate [CAS] and [MBX] servers, you'll have the minimum required receive connectors configured as well. If you have custom receive connectors, you'll have to re-create them manually. The same way, if you
have custom transport rules,you'll have to export/import them manually as well.
You'll have to create manually the Exchange 2013 Internet send connector(s) or add the Exchange 2013 CAS to the existing one(s).
By default, the Anti-Malware feature is enabled when you install Exchange 2013, but if you are planning to use a third party product, you can disable it.
Step by Step Screencasts and Video Tutorials

Active Sync not Working - Exchange 2013 with Exchange 2007

Hi
Recently we introduced Exchange 2013 servers to our existing Exchange 2007 organization. The servers are just configured with default self-signed certificate and URLs are pointing to server FQDNs.
Everything is at default as far as configuration is concerned in Exchange 2013.
After just introducing the Exchange 2013 CAS servers was checking the ActiveSync functionality using a new mailbox created on Exchange 2013. We have not yet published our Exchange 2013 servers to
Internet (before even doing that, want to ensure ActiveSync is working). We're connecting using our Private network and trying to make a connection to CAS FQDN. Checked a iOS7 (iPad) and a Windows Phone device, both of them configure successfully (with the
certificate warning, which is obvious) but when it comes to synchronizing the contents they fail saying "Cannot Get Mail. Connection to Server Failed"
Checked the IIS Logs on CAS server and found that the device makes a successful connection - as is indicated by successful configuration but thereafter nothing happnes on the device and no error
logged in Event Viewer as well. Could it be that the mailbox server is denying the connection....how to check. How to go ahead with the troubleshooting.
Everything else expect ActiveSync is working perfectly. Tries accessing the ActiveSync VD using the link
HTTPS://Server_FQDN/Microsoft-Server-ActiveSync, this pops-up a window asking for credentials – which is normal behavior indicating ActiveSync virtual directory is good.
Thanks
Taranjeet Singh
zamn

Hey Guys
Just to update here my initial testing revieled that if I run Test-ActiveSyncConnectivity by not specifying the -URL parameter like this:
Test-ActiveSyncConnectivity -MailboxCredential (get-credential User1) |FL
the command fails for an obvious reason as shown in the result. The command is getting the mailbox server name in the ActiveSync URL returned automatically:
ClientAccessServer
: SITE-MBX-02.ABC.COM
Scenario
: Options
ScenarioDescription
: Issue an HTTP OPTIONS command to retrieve the Exchange ActiveSync protocol version.
PerformanceCounterName
: DirectPush Latency
Result
: Failure
Error
: The OPTIONS command returned HTTP 200, but the Exchange ActiveSync header
                           (MS-Server-ActiveSync) wasn't returned. The request likely did not reach a
Client Access
server, either because
- A proxy server intervened (check the headers below for any that may have been
returned by a proxy)
-The virtual directory could not be reached:
https://SITE-MBX-02.ABC.COM/Microsoft-Server-ActiveSync
                     - The virtual directory does not point to a Client Access server:
https://SITE-MBX-02.ABC.COM/Microsoft-Server-ActiveSync
If however, I manually provide the -URL parameter value with FQDN of CAS server:
Test-ActiveSyncConnectivity -URL
https://SITE-CAS-02.ABC.COM/Microsoft-Server-ActiveSync
-MailboxCredential (get-credential User1) |FL
it succeeds.
We have our CAS and Mailbox servers installed on separate systems - no colocation.
This is strange and makes me curious to find out, where does the command without -URL parameter is getting the ActiveSync URL that has mailbox server in it. I checked that the new Exchange 2013 CAS servers have InternalURL parameteres populated with their
own FQDNs and the ExternalURL is empty for now.
Need help in drilling down this further.
Thanks
Taranjeet Singh
zamn

Exchange 2007 to 2013 Migration Outlook Anywhere keeps asking password

Hi all,
i'm migrating an Exchange 2007 Server with all roles installed on a Windows Server 2008 R2 to 2 Exchange 2013 SP1 Servers (1 Cas and 1 Mailbox) installed on Windows Server 2012 R2.
I installed Exchange 2007 SP3 RU13 for coexistance and everything was ok until i switched to the new 2013 CAS.
After that the client using Outlook Anywhere started asking for password.
I configured the Outlook Anywhere with these settings:
Exchange 2007:
OA Hostname mail.domain.com
Client Authentication NTLM
IISAuthenticathion Basic, NTLM
SSL Required True
Exchange 2013
OA Hostname mail.domain.com
Client Authentication NTLM (Both internal and external)
IISAuthentication Basic, NTLM
SSL Required True (both internal and external)
Before switching to 2013 Cas everything works smoothly and the Outlook clients receive NTLM as HTTP Proxy authentication.
After switching to 2013 Cas, test users migrated on 2013 Mailbox Server are ok, but Outlook users on Exchange 2007 Server get Basic as HTTP Proxy authentication and continue asking for credentials.
In the Exchange 2007 server i configured the host file to resolve servername and servername.domain.local with the ipv4 address to avoid issues regarding IPv6 with OA in Exchange 2007.
Using Microsoft Connectivity Test i receive the error "RPC Proxy can't be pinged - The remote server returned an error:
(500) Internal Server Error"
Any Ideas?
Thanks for your Help

Run this and post the result
https://testconnectivity.microsoft.com/
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
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.

Help With Migration From Exchange 2007 To Exchange 2013

We have an Exchange 2007 Server with Service Pack 3 and Rollup 12 applied.
I installed a new Exchange 2013 Server and then immediately applied CU3.
I am following this Technet article:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
The only deviation from the instruction I have had to do is in Part 2, section 4 “Configure offline address book (OAB)”.
Instead of entering:
Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2013)"
I had to enter:
Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2012)"
I believe this is due to the fact that the writer installed from an Exchange 2013 CU1 disk and I only had Exchange 2013.
Also when I tried to run:
Move-OfflineAddressBook -Identity "Default Offline Address Book" -Server SRV-EX2013
I get the following error:
Move-OfflineAddressBook : Failed to create the 'ExchangeOAB' folder on the target server 'SRV-EX2013'. Two possible reasons for the failure are that the System Attendant Service is not running or you do not have permission to perform
this operation. Error message : 'Catastrophic failure (Exception from RESULT: 0x8000FFFF (E_UNEXPECTED))'.At line:1 char:24+ Move-OfflineAddressBook <<<<
-Identity "Default Offline Address Book" -Server SRV-ex2013+ CategoryInfo
: InvalidResult: (Default Offline Address Book:OfflineAddressBookIdParameter) [Move-OfflineAddressBook], LocalizedException
+ FullyQualifiedErrorId : 9250969C,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveOfflineAddressBook
However when I looked at the address books in EAC I could see that “Default Offline Address Book (Ex2012)” was the default and that it contained a copy of the Global Address List. So I did nothing else about it.
I am now at Part 3, section 7 “Move Mailboxes” and it keeps failing.
I am using the EAC so that I at least see the error as using the powershell brings back no results.
Anyway it Syncs the 18 items in the mailbox then fails with:
Data migrated: 936.7 KB ‎(959,145 bytes)‎
Migration rate: 0 B ‎(0 bytes)‎
Error: MigrationPermanentException: Error: An error occurred while updating a user object after the move operation. --> Unable to generate the e-mail address. Unable to load address module ‎'C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\address\SMTP\AMD64\inproxy.dll‎'
for address type ‎'SMTP‎'. Additional message: ‎'Access is denied‎'.
Help??
Tony

Hi,
You can't configure Exchange 2013 to generate other OAB versions, and the OAB generation occurs on the Mailbox server on which the organization mailbox resides.Therefore, to move OAB generation in Exchange 2013, you must move the organization mailbox. You
can only move the OAB generation to another Exchange 2013 mailbox database. You can’t move OAB generation to a previous version of Exchange.
And please refer to the following articles :
Moving OABs between Exchange versions
If you want to upgrade from exchange 2007 to exchange 2013,I recommend you refer to the following article:
Upgrade from Exchange 2007 to Exchange 2013
Exchange version
Exchange organization coexistence
Exchange 2007
Supported with the following versions of Exchange:
Update Rollup 10 for Exchange        2007 Service Pack 3 (SP3) on all Exchange 2007 servers in the
organization, including Edge Transport servers.
Exchange 2013 Cumulative        Update 2 (CU2) or later on all Exchange 2013 servers in the
organization.
Install Exchange 2013 in an Existing Exchange 2007 Organization
You can install a Microsoft Exchange Server 2013 server into an existing Exchange Server 2007 organization, and then move the Exchange resources, such as mailboxes, public folders, and connectors, to Exchange 2013. However, you can't perform an in-place
upgrade from Exchange 2007 to Exchange 2013.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

From Exchange 2007 to exchange 2013

hi everyone,,
I need a video with brief description of how to deploy exchange 2007 to four servers exchange 2013
please to help,
thnx

Hi,
For your reference, here are some articles and step by steps migration from Exchange 2007 to Exchange 2013:
Upgrade from Exchange 2007 to Exchange 2013
https://technet.microsoft.com/en-us/library/jj898581(v=exchg.150).aspx
Part 1: Step-by-Step Exchange 2007 to 2013 Migration
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Additionally, we can use Microsoft Exchange Server Deployment Assistant for deployment help. It is a web-based tool that asks you a few questions about your current environment and then generates a custom step-by-step checklist that will
help you deploy different versions of Exchange Server for different types of scenarios:
https://technet.microsoft.com/en-us/office/dn756393.aspx
Regards,
Winnie Liang
TechNet Community Support

Upgrade exchange 2007 to exchange 2013 on SBS 2008

Hi,
I need to upgrade EX07 to EX13 on small business server 2008, So I am looking for the documents or steps which will help in Implementation.
Thanks in advance!
-av

Hi,
Any update about the issue?
In-place upgrade is not possible. According to the MS article:
When you're upgrading your existing Exchange 2007 organization to Exchange 2013, there's a period of time when Exchange 2007 and Exchange 2013 servers will coexist within your organization. You can maintain this mode for an indefinite period of time, or
you can immediately complete the upgrade to Exchange 2013 by moving all resources from Exchange 2007 to Exchange 2013, and then decommissioning the Exchange 2007 servers. You have a coexistence scenario if the following conditions are true:
Exchange 2013 is deployed in an existing Exchange organization.
More than one version of Microsoft Exchange provides messaging services to the organization
Upgrade from Exchange 2007 to Exchange 2013
https://technet.microsoft.com/en-us/library/jj898581%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
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 Support, contact [email protected]

Removing Exchange 2007 from SBS 2008 after Migrating to Office 365 Mid Sized with DirSync and SSO

We have recently completed off a Migration of Exchange 2007 to Office 365 Mid Sized platform.
I now need to decomission the old SBS 2008 server as they have moved to a Windows Server 2012 R2 server setup for DC, File and print and application servers.
I need to know what are the ramifications of removing the Exchange 2007 server from the SBS 2008 server and will this remove the LegacyDN details from AD and cause any issues with internal emails between users using Outlook linked through to Office365.
I understand that after removing Exchange 2007 there will be no friendly GUI to update and maintain proxyAddress, targetAddress and LegacyDN addresses, I am comfortable doing this in ADSI edit or with a script.
Will this remove the x500 addresses relating to the on premise Exchange Orgainisation and just leave behind the x500 addresses for Exchange Labs which I assume is the x500 addresses for the Azure AD intergration for Office365.

Hi ,
Thank you for posting your issue in the forum.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Applying OS SP2 to existing Windows Srv 2008 SP1 w/ Exchange 2007 SP3 w/RU 5, before installing RU13

We are in the process of planning the deployment of Windows Server 2008 SP2, latest MS updates, and update rollup 13 for Exchange 2007 SP3. Looking to migrate to Exchange 2013 & Exchange online in the future
Are there any issues that we need to be aware of before proceeding with the big updates. Exchange is running fine, but we're not able to fully patch these servers unless SP2 is installed. Thanks a bunch.
Environment:
running Exchange 2007 SP3 with update rollup 5 for all of our email servers (CCR, HUB/CAS w/WNLB). The OS installed for all of these are Windows 2008 SP1 (6.0.6001
Service Pack 1 Build 6001), latest MS critical updates are the only recent updates installed.
We also have Forefront Security for Exchange that I might remove.

Hello,
Do you mean you want to upgrade Windows Server 2008 SP1 to Windows Server 2008 SP2, and then upgrade Exchange 2007 SP3 with rollup 5 to rollup 13? If so, the OS not being upgraded to a new version.
If you want to deploy Exchange 2007 SP3 with rollup13, you must install Windows Server 2008 SP2 on a computer that does not have Exchange installed, and then install Exchange 2007 SP3 with rollup 13, and move your mailboxes to new Exchange Server.
Based on your environment, you need to upgrade a clustered mailbox server, you must build a new failover cluster using Windows Server 2008 SP2 as the operating system for all nodes, and then migrate the data from the old cluster to new cluster.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2007 SP3 Search Problems

I reset all the search indices on my mailbox databases. Event viewer has told me the crawl is complete and everything checks out when I do “test-exchangeSearch”
from PS. However, the index folders are considerably smaller than the original ones, (1.3GB vs 7GB) and only about 1% of database size. Multiple users can prove to me that searches are incomplete and not returning reliable results when just doing basic folder
searches from Outlook 2007. help!
Ian

After speaking with a senior MS Engineer, if you already have SP3 applied and tried to reinstall the search as I outlined above, you have corrupt your Exchange install and the ONLY option is to rebuild the box. After reinstalling Windows and Exchange, the
proper procedure to get search working perfectly is outlined below:
4. If you haven’t already,
upgrade toExchange Server 2007 Service Pack 3.
Exchange 2007 SP3 includes several major Search-related fixes and upgrades MSSearch 3.0 to MSSearch 3.1. This is a highly significant
upgrade.
5. Update to the latest available Rollup Update.
There are some very significant search fixes in the Rollup Updates for Exchange 2007 SP3. Some of these fixes are absolutely essential to install.
For example, Exchange 2007 SP3 Rollup Update 2 includes a fix that allows Exchange server to index emails even when the attachment cannot
be parsed – this is the number one call generator for Exchange 2007 search support cases.
To restate, upgrade to the very latest available Exchange 2007 SP3 rollup update, as there are many more search fixes available in the latest
rollup updates.
6.
Install IFilters and register them – follow ALL the steps below.
Install Filter Pack 1.0, which allows Exchange 2007 to index Office 2007 documents:
2007 Office System Converter: Microsoft Filter Pack
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20109
7. Install the hotfix which addresses a known issue when search crawls a .vsd file.
960502 Description of the 2007 Office system hotfix package (Offfiltx.msp, Visfilter.msp): December 16, 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;960502
Additional Information on the hotfix:
960166 Error message when a search process crawls a .vsd file on a Windows 64-bit operating system that is running the 2007 Office Filter
Pack: "The filtering process has been terminated"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;960166
8.
Register the Filter Pack 1.0 IFilters. This is a manual process with Exchange 2007 but we have created a script to automate the process.:
944516 How to register Filter Pack IFilters with Exchange Server 2007
http://support.microsoft.com/default.aspx?scid=kb;EN-US;944516
9. Install Filter Pack 2.0 which allows Exchange to index Office 2010 attachments as well as some additional file types.
Download details: Microsoft Office 2010 Filter Packs
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5CD4DCD7-D3E6-4970-875E-ABA93459FBEE&displaylang=en
10. Register IFilters 2.0 with Exchange 2007.
How to Register IFilters 2.0 with Exchange 2007 and Exchange 2010
http://technet.microsoft.com/en-us/library/ff354976(EXCHG.80).aspx
11. Disable signature verification for the Exchange 2007 search services by putting 127.0.0.1 crl.microsoft.com in the HOSTS file.
Certificate Revocation List
When the Microsoft .NET Framework 2.0 loads a managed assembly, the managed assembly calls the CryptoAPI function to verify the Authenticode signature
on the assembly files. The CryptoAPI function checks a Certificate Revocation List
(CRL) that is available at http://crl.microsoft.com
. This action requires an Internet connection.
The
Microsoft Search Indexer service (Microsoft.Exchange.Search.ExSearch.exe)
is a managed assembly that is loaded by Microsoft .NET Framework 2.0. After installing Exchange 2007 SP3, if the Exchange server or DNS cannot resolve
http://crl.microsoft.com for any reason
the outgoing HTTP requests may be dropped and an error message is not returned. This delay causes the CRL to time out and cached CRLs will expire. This affects the Microsoft Search Indexer service in such a way that any new email fails to be indexed.
Instructions to Modify HOSTS file on the Exchange 2007 Server
Add the following:
127.0.0.1 crl.microsoft.com – here are the instructions:
a. Go Start – Programs and choose Command Prompt and choose Run as Administrator.
b. Within the Command Prompt, change to this directory (the drive will be the one where you installed the OS):
C:\Windows\System32\drivers\etc\hosts
c. Add the following entry to the HOSTS file:
127.0.0.1 crl.microsoft.com
d. Save the HOSTS file.
13.
Rebuild Indexes
using ResetSearchIndexes.ps1
How to Rebuild the Full-Text Index Catalog
http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspx
a. Go Start – Programs and choose Exchange Management Shell and choose Run as Administrator.
b. Change to this directory (the drive will be the one where you installed Exchange 2007):
C:\Program Files\Microsoft\Exchange Server\Scripts
c. It is suggested that you rebuild indexes for one or a few databases at a time – use the following command to rebuild the indexes for 1
databases called dbname1 and dbname2:
.\ResetSearchIndex.ps1 –force dbname1 dbname2
d. It is suggested not to run the following command unless you have 1 Exchange 2007 server only in your environment because it will cause
all databases on all Exchange 2007 (and all Exchange 2010 servers, if there are any) to be reindexed at that same time:
.\ResetSearchIndex.ps1 –force all
14.
Monitor the Application Event Log for Event ID 110 for a particular database.
This will indicate the new index is complete for that database.
15. After receiving Event ID 110 for a database, check to see if the size of the CatalogData folder for that database is the expected
5% to 10% of the database size. If the size of the CatalogData folder is significantly smaller than that or if the size is a few kb or a few mb, go
to Step 17.
16. After you have received Event ID 110 and the size of the CatalogData folder is normal, test searching in Outlook online mode
and OWA to make sure search is working.
<strike>
</strike>
Ian

Autodiscover after deploying Exchange 2013 CAS in a Exchange 2007 organization

Similar Messages

Maybe you are looking for