Exchange 2007 In SCR Setup

We have MS Exchange 2007 +SP3 Setup. Two sites in exchange 2007 in Standalone mailbox, one is in Mumbai and another placed in chennai. We have enabled SCR on both Servers, both server having passive copy of each other databases.
Last Friday, there was some power failure issue at chennai data center. Due power failure, chennai mailbox server having hardware issue and doesn’t up now. We have activated chennai server database on Mumbai Server having each database size more than
30GB.
Now We are looking for High Availability in terms of database copy on local another server or how to activate them on in case if we freshly install exchange 2007 mailbox in chennai datacenter.
Please provide BEST Solution on this.

Hi Shaikh
The steps are pretty simple
Recover the primary server
Delete all the storage groups and DB's on primary server
Create storage groups and DBS with the same name
Mount the DB's
Rehome the users or we can user Database portability as well.
Refer Scott's blog for further information
http://blogs.technet.com/b/scottschnoll/archive/2007/11/26/after-scr-activation-what-next.aspx
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Similar Messages

Restore Exchange 2007 SP3 to Windows 2008 R2 from Windows 2003

Perhaps I'm being dense, but I had Exchange 2007 SP3 installed on a Windows 2003 Server, and I've used "setup /mode:recoverserver" to restore it to a Windows 2008 R2 server... how do I restore the databases which I backed up with the Windows backup tool
on 2003?
I installed KB974674, the restore tool onto the 2008 R2 server but when I try and restore the backup it comes up with "this feature is no longer supported". Something I'm missing here?

These things marked as answers are not answers.
I have now thoroughly tested using setup /mode:recoverserver and it works fine going from Windows 2003 to Windows 2008 R2 with Exchange 2007 SP3, done several installations now without a problem.
"Setup /m:RecoverServer cannot be used across operating systems. A server that was originally running Windows Server 2003 can be recovered only on Windows Server 2003, and a server that was originally running Windows Server 2008 can
be recovered only on Windows Server 2008."
This appears to be wrong, unless someone can tell me why it's right (I haven't tried moving Unified Messaging yet). I've done it to 2008 R2 several times now and also in the other direction, from 2008 R2 to 2003, I can't find anything that didn't work
afterward, although I haven't really thoroughly tested OWA yet, I admit (but it does appear to be working).
I think that documentation is out-of-date as it doesn't mention R2 plus I think it was written before SP3 came out and that paragraph is just wrong.
Basically how I do it is like this:
Dismount databases from the 2003 server and copy the storage group folders to a network location or removable media.
Install the Windows 2008 R2 server using the same machine account that was being used by the 2003 server. Install the prerequisites needed for Exchange 2007 SP3 installation on 2008 R2 (note in addition to the IIS components and RPC over HTTP this
also requires the AD tools in RSAT, which I haven't found mentioned in technical documentation). Install the relevant windows updates.
Install Exchange 2007 SP3 using setup /mode:recoverserver Install the update rollup.
Copy the storage groups into the relevant folders on the new server and mount them. Migrate any relevant certificates (e.g. for ActiveSync).
Obviously then check it all over with the diagnostic tools and check it with EXBPA. The backups are obviously totally different, but really I think you should be using DPM anyway.
To me that was pretty easy to do, to be honest. About 1.5 on a scale of one to ten. Basically install it, recover it, copy over some files and mount them.
Seriously on a halfway decent server I've done it in under an hour.

Decommission Exchange 2007 Mailbox Server from Cluster

Hi! I realize this is an Exchange 2013 forum, however as I do not see any forums for older flavors of Exchange I'm going to post this here. If a better forum exists please let me know and I'll happily move to that forum for my answers.
I am just finishing a migration from Exchange 2007 to Exchange 2013. In the Exchange 2007 environment I have 2 CCR Mailbox Clusters. While working to decommission the first of the two clusters I successfully evicted the passive node, however
I mistakenly evicted the active node rather than removing it by running the Exchange Setup Wizard as outlined in the TechNet article "How to Remove the Active Mailbox Role from a CCR Environment".
Now, when attempting to uninstall Exchange 2007 using the Setup Wizard in Add/Remove Program I get the following error during the prerequisite check for the 'Mailbox Role':
Error:
Exchange server FQDN was not found. Please make sure you have typed it correctly."
Setup then completes.
Is there a way to cleanly uninstall Exchange 2007 and clean-up Active Directory?
Thanks!

Hi Jesse,
Thank you for your question.
We could run “ADsiedit.msc” in run, then navigate
Configuration [<domainController>.contoso.com]> CN=Configuration,DC=contoso,DC=com> CN=Services> CN=Microsoft Exchange> CN=<OrganizationName> CN=Administrative Group> CN=Exchange Administrative Group>CN=Server
We could check if mailbox server is existed in this container, we could remove it.
Notice: Before we remove it, we could make a backup for AD database. We suggest you call MS engineer for help.
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

SBS 2008 and Exchange 2007 intermittent Email Issues

Hello
I am having an issue with my SBS 2008 Server and Exchange 2007. After setup, the mail seems to work great for about a week, then the mail just quits working. To get it working again, all I have to do is reboot the server and mail starts working
again. When looking in the event logs, all I come across is transport.exe errors. Any ideas on why it works for 5-10 days, then just quits working? Any help or insight would be much appreciated.
Thanks All

Larry
Here are some of the errors that i am getting:
(Event ID 1022) (Source MSExchangeIS Mailbox Store)
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account NT AUTHORITY\NETWORK SERVICE; mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Josh.Lange.
Error: -1069
Client Machine: SERVERNAME
Client Process: edgetransport.exe
Client ProcessId: 0
Client ApplicationId: Client=Transport
(Event ID 1022) (Source MSExchangeIS Mailbox Store)
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account NT AUTHORITY\SYSTEM; mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SERVERNAME/cn=Microsoft System
Attendant.
Error: -1069
Client Machine: SERVERNAME
Client Process: Microsoft.Exchange.ServiceHost.exe
Client ProcessId: 0
Client ApplicationId: Microsoft System Attendant Service Let
(Event ID 1022) (Source MSExchangeIS Mailbox Store)
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account WIS\JLange; mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Josh.Lange.
Error: -1069
Client Machine: SERVERNAME
Client Process: w3wp.exe
Client ProcessId: 0
Client ApplicationId: Client=ActiveSync;UserAgent=Apple-iPhone5C1/1002.329;Action=User=jlange&DeviceId=ApplF18KM7FHFH1C&DeviceType=iPhone&Cmd=Sync
These are a few errors that i get when the mail isn't working. When it stops of the server, the outlook clients show the exchange server disconnected, and active sync will not work either. I can still remote to the server, so i dont think its
an internet connectivity issue. Let me know if you have any other questions. Again, the mail seems to work for about 5-7 days, then i have to reboot the server to get the mail flowing again. Any help or direction would be appreciated.
Thanks for Looking

Exchange 2007 - Setup POP3 access

We are currently running Exchange 2007 server. Users request for access via Outlook from home computers. Can someone point me in the direction to accomplish this? I've enabled POP and IMAP on the server, but not sure where to setup Incoming and Outgoing
mail server settings.

Testing Outlook connectivity.
The Outlook connectivity test failed.
Additional Details
Elapsed Time: 22449 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for
[email protected].
Testing Autodiscover failed.
Additional Details
Elapsed Time: 22448 ms.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service couldn't be contacted successfully by any method.
Additional Details
Elapsed Time: 22448 ms.
Test Steps
Attempting to test potential Autodiscover URL
https://co.hernando.fl.us:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 21291 ms.
Test Steps
Attempting to resolve the host name co.hernando.fl.us in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 24.129.129.232 Elapsed Time: 238 ms.
Testing TCP port 443 on host co.hernando.fl.us to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with the remote host.
Elapsed Time: 21053 ms.
Attempting to test potential Autodiscover URL
https://autodiscover.co.hernando.fl.us:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 655 ms.
Test Steps
Attempting to resolve the host name autodiscover.co.hernando.fl.us in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 24.129.129.220 Elapsed Time: 305 ms.
Testing TCP port 443 on host autodiscover.co.hernando.fl.us to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 120 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 230 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.co.hernando.fl.us on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=webmail.co.hernando.fl.us, OU=COMODO SSL Unified Communications, OU=Domain Control Validated, Issuer: CN=COMODO SSL CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB. Elapsed Time: 174 ms.
Validating the certificate name.
Certificate name validation failed.
Tell me more about this issue and how to resolve it
Additional Details
Host name autodiscover.co.hernando.fl.us doesn't match any name found on the server certificate CN=webmail.co.hernando.fl.us, OU=COMODO SSL Unified Communications, OU=Domain Control Validated. Elapsed Time: 1 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method.
The attempt to contact Autodiscover using the HTTP Redirect method failed.
Additional Details
Elapsed Time: 338 ms.
Test Steps
Attempting to resolve the host name autodiscover.co.hernando.fl.us in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 24.129.129.220 Elapsed Time: 32 ms.
Testing TCP port 80 on host autodiscover.co.hernando.fl.us to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 139 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.co.hernando.fl.us for an HTTP redirect to the Autodiscover service.
The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.
Additional Details
An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body of the response: You do not have permission to view this directory or page.HTTP Response Headers:
Content-Length: 58
Content-Type: text/html
Date: Mon, 28 Jul 2014 20:46:30 GMT
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Elapsed Time: 166 ms.
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
Additional Details
Elapsed Time: 80 ms.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.co.hernando.fl.us in DNS.
The Autodiscover SRV record wasn't found in DNS.
Tell me more about this issue and how to resolve it
Additional Details
Elapsed Time: 80 ms.
Checking if there is an autodiscover CNAME record in DNS for your domain 'co.hernando.fl.us' for Office 365.
Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning.
Tell me more about this issue and how to resolve it
Additional Details
There is no Autodiscover CNAME record for your domain 'co.hernando.fl.us'. Elapsed Time: 81 ms.

Update Rollup in Exchange 2007 SCR environment.

Dear Experts.
I am going to install Rollup 12 for Exchange 2007 SP3, so could you please confirm if any issue with Rollup 12 Exchange 2007 SP3?
Could you please advise to update Rollup in Exchange 2007 SCR environment with CCR.? I would appreciate. If you provide step by step
process, Thanks
Regards Vijaya Babu S | MCITP | MCTS | MCP| MCSA

Hi Vijaya,
Based on my known, Exchange 2007 SP3 Rollup 12 doesn't have a known issue so far.
About the steps of update Exchange 2007 SCR with CCR, please follow the above article Mike provided.
What's more, I recommend you make a complete backup of the clustered mailbox server prior to applying the update rollup and again after successfully applying the update rollup.
Here is an article for your reference.
How to Install Update Rollups in a CCR Environment
http://technet.microsoft.com/en-us/library/bb885047(v=exchg.80).aspx
Hope it helps.
If you need further assistance, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2007 setup, transitioning from Exchange 2003

Hello Exchange Experts,
I just setup a Exchange 2007 within our domain, transistioning from Exchange 2003, question: When I added the mailbox role on the setup of Exchange 2007, the mailboxes appeared instantly from our Exchange 2003..the connector I'm assuming automatically connected
during the 07 setup. Is this normal? I was under the assumption to migrate mailboxes from 03 to 07 Exchange, the wizard must be ran. All active mailboxes from 03 appear. I attempted to migrate one mailbox using the wizard, error after the wizard completed,
mailbox exists. Makes sense, just not understanding how the mailboxes flowed/migrated automatically without running the migration steps. Would someone explain? You could say, this migration is very new to me.
Thanks in advance!
James

Ronny, our company had an existing license for 2007. Of courser 2010 or 2013 would have been a better transition, but 2007 is it. The server 2007 has met all the criteria for the transition, spent last moth prepping everything on 2003 and 2007. I'm just
not understanding why the mailboxes appeared upon 2007 immediately after adding the mailbox role. The management console on 07 shows the mailboxes reside on 03 exchange server. I did not go through the process/wizard to move to 07. Perhaps because
during the installation of Exchange 07 created the connector from 2003? Maybe that's my question.
Mail flow is very responsive now, just wondering for the reasons of decommissioning exchange 2003 at a later date. Exchange 2003 is functioning now as a bridgehead, working perfectly now.
Thanks for your input.
James
Thanks Ronnie for your input! Issue resolved

Exchange 2007 and Snow Leopard Setup...HELP

I know this topic may have been covered in here previously but I have yet to find a solution.
Here is the background. Our CEO has a Mac Book and two weekends ago he updated to Snow Leopard and now wants to use the Mail client on his Mac rather than OWA to get his email. We have Exchange 2007 (I am the Admin) and have all the latest patches and Roll Ups installed. We run OWA without issue and have 10 iPhones working perfectly (i realized they use different technology to sync). I enabled EWS by following this link http://technet.microsoft.com/en-us/library/bb201695.aspx and this is the actual command i used:
Set-WebServicesVirtualDirectory -identity exchaname\EWS* -externalurl https://webmail.domain.com/EWS/Exchange.asmx -BasicAuthentication:$True
Seems to have run properly and there are no errors reported.
Now when I go to connect using the Mac it does not Auto Discover and I must enter manually. I enter what i think it needed and its not working. On the Account Information Tab I have the following:
Description: generic name
Email Address: [email protected]
Full Name: The Person's Name
Internal Server: webmail.domain.com *Not sure what should be here
External Server: Webmail.domain.com *Again not sure if this is correct
Username: AD user name Also tried domain\username
Password: AD password
Ougoing Mail Server: not sure what should be here
Next is the Mailbox behavior Tab:
Did not change anything
Advanced Tab:
Internal Server Path: EWS/Exchange.asmx
Port:80 SSL unchecked
External Server: EWS/Exchange.asmx
Port: 80 SSL unchecked
I get no connections and I am sure somehting is not correct in the above but I am lost and new to Exchange as it is. Also new to Mac's
Help Please

Looking for post.

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."

Outlook 2013 not automatically configuring Exchange (2007) account when running the Auto Account Setup

In previous versions, once I launched Outlook, it would automatically detect/passthrough my username and email address into the fields so that I could just click next and be done. In Outllok 2013 on Windows 2008 R2 this doesn't appear to be working even
thought I am able to successfully resolve my autodiscover domain.

Hi,
Is there any error when you can’t connect your Outlook 2013 to Exchange 2007?
If the autodiscover service is configured correctly, please change a computer to have a try. In this local windows 2008 R2, please check the following settings in Internet Explorer:
Click Settings > Internet Options > Connections > LAN settings, please make sure there is no proxy server set there. Only “Automatically detect settings” option is checked.
Regards,
Winnie Liang
TechNet Community Support

Inter-Org Mailbox moves from Exchange 2007 to Exchange 2013

G'Day All,
Is it possible to move Exchange 2007 mailboxes to Exchange 2013 in a different forest? Both environment has all the required patches and service packs.
There is a two way trust, and I don't want to introduce Exchange 2010 CAS in the source forest if I don't need to.
I have read the following article http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/ but it is not clear what is the required to setup in Exchange 2007. I have read many other articles to do with Exchange 2013 mailbox moves, endpoints,
etc, but non of them is clear of how does it work having Exchange 2007 source.
Thanks in advance.

Hi Atonal,
Could you please take a look at this technet blog that has been well elaborated about your concern :
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
The blog provides step-wise assistance while you are planning to move from exchange 2007 to 2013.
Here is another library available from technet team that includes all the terms while preparing mailboxes for cross-forest move request : http://technet.microsoft.com/en-us/library/ee633491%28v=exchg.150%29.aspx
Alternatively, you can checkout this proficient application (http://www.exchangemigrationtool.com/) in order to avoid any interruption and proceed hassle-free migration from exchange 2007 to 2013.

Move Mailboxes from Exchange 2007 to Exchange 2013 (Could not find a valid mailbox migration for esta organization)

Hi all, I am in full migration from Exchange 2007 to Exchange 2013 and everything went correctly.
I have migrated several mailboxes and are working well. But a few days ago, when I try to migrate a mailbox I get the following error and can not migrate:
"Could not find a valid mailbox migration for this organization"
Do you know that you can be?
regards
Microsoft Certified IT Professional Server Administrator

Hi,
From your description, the issue should be related to the migration mailbox. I recommend you check if the following account is existed in ADUC.
Migration.8f3e7716-2011-43e4-96b1-aba62d229136
If this account does not exist, you need to run setup /prepareAD and then enable this migration mailbox to check the result.
Hope this can be helpful to you.
Best regards,
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]
Amy Wang
TechNet Community Support

Upgrading from Exchange 2007 to Exchange 2013

Hi There,
I have two exchange serveres 2007 SP3 and they are ruining on Server 2008 Ent and 2008 R2 Ent.
I setup a server 2012 R2 and installed an exchange 2013 on it and a friend of mine helped me on setting up the new exchange server and migrating the mailboxes.
Now all the mail boxes are transferred to the 2013, and based on his recommendation I am in the stage of uninstalling exchange 2007 from my old servers.
I am reading about the process but based on the link below I have to do more things before uninstalling
http://www.exchangedictionary.com/articles/clean-uninstallation-of-exchange-2010-mailbox-server-guide
the instruction is for exchange 2010 and some shell commands are not working on shell 2007
I also found the link below:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
and I think I am at the stage 8 or 9, but I am not sure and also I do not know what to do if I am at the stage 8
Would you please advise me what shall I do to finish up the project or give me a link for it.
I have searched a lot but I was not able to find a straight forward instruction.
Thank you in Advance

Hi MAS,
Thank you for your reply
I found the instruction below:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-4-step-by-step-exchange-2007-to-2013-migration.aspx
but I am not sure if I am in the step of moving public folders or not. I have finished the migration of all mailboxes.
When I click on "Servers" I can see the results below:

Moving from Exchange 2007 to 2013 (leaving the DNS Server for it's own dedicated server)

Hello! I am quite new to Exchange and Server management in general. I will do my best to explain my situation.
I am looking to move my Exchange server off of our DNS server. When we installed them on the same server, we did not have the funds to buy 2 separate servers. I am told that it is best to separate the two. I have followed the Microsoft instructions for installing
the prerequisites for Exchange 2013 on a 2012 R2 server, and i am at the point where it wants me to configure AD LDS. As I have active directory running on the current server, I was a little hesitant to just install it without understanding what i am doing.
After the AD LDS is configured, I believe i can move forward with installing Exchange 2013 (all 3 roles will be hosted on the new server), export the mailboxes from 2007 server and import them into the new Exchange 2013 server. After 2013 is up and stable,
I plan on removing 2007 from the old server (DNS server).
What are my next steps after importing the mailboxes? Am i missing important details that I need to change or migrate?
My biggest fear is that nothing works after the installation and moving the mailboxes over. For that case, it makes sense to keep 2007 installed as a fallback for when my installation fails and all i have lost is just my time :)
Current Server:
Windows Server 2008 Standard (64 bit)
1. Roles: Active Directory, DNS, IIS
2. Software: Exchange 2007
New Server:
Windows 2012 R2 Server
1. Roles: ???
1. Software to install: Exchange 2013
Thank you for any help you can provide!

These are good resources, but i am still caught up with the active directory issue. Am I able to keep the old Domain/DNS/Active directory on it's current server and move Exchange 2007 off onto a new server (with Exchange 2013)?
In the first example, he is moving everything (domain controller, exchange, users, etc) onto a different server and decommissioning it.I've been told that it would be better practice to keep the domain and exchange on 2 different servers. Is this true?
I go to run commands like:
.\setup /PrepareAD /OrganizationName: orgname /IAcceptExchangeServerLicenseTerms
on the new exchange server, as a prerequisite and it doesnt recognize the command - even after following the steps before. Is this because the new server is not a domain controller? does it have to be? What are the best practices for setting up a server(s)
with exchange + domain controller?
Thanks for responding.

Exchange 2007 account won't go online

Hi,
I am running OS X 10.6.4 on my MacBook, with the latest versions of everything available through Software Update.
I am unable to get iCal to work with my Exchange 2007 account. I can add the account through preferences, but it never shows up in the left-hand pane where all the other calendars go. I don't run into this problem with my other Google calendar, so it seems to be specific to the Exchange calendar. Curiously, there is no error message from iCal, which acts as if the calendar is there but does not put it online. In the "Online Status" my Exchange Calendar is listed, but if I select to bring the account online nothing happens.
As it happens I've been trying to get iCal to work since upgrading to Snow Leopard last October. Previously I had a different problem, in which the Exchange Calendar would show up in the left-hand pane but would ask for a "valid email address" for the account. It seemed at the time that the problem was that my address is not published in the GAL, but this is something I have no control over personally, and the system admin won't publish it for me. I found it curious that iCal requires this, but Mail and AddressBook presumably do not, as they set up instantly when I upgraded to Snow Leopard and have both worked flawlessly ever since.
I haven't come across anyone with a similar problem when Googling the problem, so this is probably a long shot, but does anyone have some advice on what might help here or how I can go about troubleshooting this problem? Any help would be greatly appreciated!
Cheers,
nanoo

I had the exact same issue. Found nothing in the console logs other than "can't refresh account". Turns out my problem was wrong e-mail address with the exchange server. I used the exact e-mail address that this particular exchange expected and it added it to the panel on the left.
Our setup is a bit weird cause we have 2 exchange servers, but I let iCal figure out everything itself using the "old" exchange server and then afterwards went and edited the server settings to use the "new" server, and it kept working with these settings.
Just a bit annoying that iCal was so vague about what the problem was... Also didn't help that I upgraded and moved to the "new" server and changed my password all at once, so don't know what cause the problem in the first place.

Exchange 2007 In SCR Setup

Similar Messages

Maybe you are looking for