Ical delegate color control for exchange 2007

I have found a way to change the colors of Exchange 2007 Delegate calendars/tasks!
It's a bit involved but...
inside your /library/calendars folder you will find calendar folders with the extension .exchange. Inside each of these folders is an info.plist file, and one or two other folders (one for calendars, one for tasks) which also have info.plist files. Each of these info.plist files include an attribute called Color.
With iCal closed, you can edit these plist files to the color you want them to be, rename/delete the Calendar Cache file from ~user/library/calendars and restart ical! Deleting the cache causes the info for all calendars to be reloaded/downloaded, but the new colors will take effect when this has completed.
Note: the info.plist immediately inside the <calendar-id>.exchange folder is the delegate name on the left hand side. The info.plist inside the subdirectories control the color of the calendar and tasks....it is possible for them to not match so update them all!

Doug,
Thanks for the info. I have the same problem in Mountain Lion. Your workaround is not persistent. Something is overwriting the plist files to change the color back to the original. Any suggestions? Thanks for your help.

Similar Messages

Receive Connector stopped working after Update Rollout 2 for Exchange 2007 SP2

One of the Exchange 2007 servers receive connector has stopped working since installing the latest rollout update for Exchange 2007 SP2 - for some reason the following error is received (when troubleshooting on the adjacent server) :
"Remote server server.domain.co.uk failed the mail acceptance test. MAIL FROM command: Respond = 530 5.7.1 Client was not authenticated."
Most admins will know you usually get this when first setting up Exchange and the receive connector not allowing anonymous connections. But our setup has been working for well over a year with no problems. Even enabling anonymous connections still doesn't fix the problem.
Our setup is 2 exchange servers across 2 sites, with the problematic server never receiving email from the internet, only from the other Exchange server (which is internet facing). The above error is received when the internet facing server is relaying email over to the problematic server. Though in the message queue the following error is received:
"SMTPSEND.DNS.NonExistantDomain; nonecistant domain"
After testing DNS that all seems fine, so I don't believe it's a DNS problem.
Any ideas why this would happen?
Thanks,
Matt

Hi Matt....
To receive e-mails from the external servers or domains or clients, you can setup a new receive connector on Hub Transport Server. To do this task, you can go through the steps mentioned in this blog....
https://mailsolutions.wordpress.com/2015/02/06/resolving-error-530-5-7-1-client-was-not-authenticated-with-receiver-connector/
Hope this will work
Thanks

GroupWise 7.0 API Gateway is supported for Exchange 2007?

Can someone confirm that GroupWise 7.0 API Gateway is supported for Exchange 2007?
I found a note in a guide that stated it was not YET supported as of 1/27/2008.

bwalker2,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Legacy Namespace for Exchange 2007 to 2013 co-existence

We are migrating from Exchange 2007 to 2013, during the co-existence phase, where is the legacy.{domain.com} namespace used? We are at the point now that we want to move all services over to the Exchange 2013 CAS servers, however... GPO settings
are used to point outlook clients to mail.{domain.com} for Outlook Anywhere. If DNS is updated to point mail.{domain.com} to the Exchange 2013 servers, will there be an issue with connectivity for people still on the Exchange 2007 servers? Do these people
need to point to legacy.{Domain.com} or will mail.{domain.com} proxy the connection to the legacy namespace? I would like to know if the GPO settings will interfer with the settings that Autodiscovery provide back.
I have read a bunch or articles on the approach, but I am still fuzzy on where legacy.{domain.com} comes into play.
Thanks in advance for your help.

In coexistence with exchange 2013 and legacy version the request happens in 2 types.
For Exchange 2010 –
Exchange 2013 does a Proxy for owa and ews requests for users in exchange 2010.
For Exchange 2007 –
Exchange 2013 does redirection for owa and ews requests for users in Exchange 2007.
Certificates:
All the required SAN entries for UM,webservices and activesync should be created.
Add external owa legacy URL to the public certificate and install it on both Exchange 2007 and
Exchange 2013 only then owa redirection will work.
You need to Include internal Legacy. Domain.com on Exchange 2007 Certificate for OWA co-
Existence.
Following change needs to be done in Firewall
External OWA URL should be directed to exchange 2013 Internet Facing CAS.
External EWS URL should be directed to exchange 2013 Internet Facing CAS.
External Autodiscover URL should should be directed to Exchange 2013 CAS.
External ActivesyncVirtualDirectory should be directed to Exchange 2013 CAS.
External UMvirtualDirectory should be directed to Exchange 2013 CAS.
Create new NAT rule on firewall for Legacy.domain.com to Exchange 2007 CAS. You can do this as well.By doing this users will be able to log on directly using the URL https://legacy.domain.com/owa with
a mailbox on Exchange 2007.
External and Internal DNS settings
Public DNS - Map all of your external public DNS records (ews,owa,activesync etc.,) to your
exchange 2013 public IP if you have dedicated one for 2013 or FQDN of your internet facing CAS server.
Example:
Current external owa URL (contoso.domain.com) – point it to dedicated exchange 2013 public ip or internet facing exchange 2013 CAS FQDN.
Current External Autodiscover – point it to dedicated exchange 2013 public ip or internet
facing exchange 2013 CAS FQDN
Internal DNS – Configure the Exchange 2007 to point SCP AutoDiscoverURI to Exchange 2013 Client
Access FQDN by changing DNS entry for Autodiscover.domain.com to exchange 2013 CAS sever Ip
address
The internal DNS records should point to the internal host name and IP address of your Exchange
2013 Client Access server
Make sure that legacy.contoso.com resolves to CAS2007 in internal and external DNS.
Authentication Settings:
This part is little bit tricky. You need to plan according to your organization. If you have FBA configured in TMG or ISA server then you need to configure accordingly.
Set the owa virtual directory authentication only to Basic in exchange 2007.
In exchange 2013 set owa virtual directory to only (Windows Authentication) or only (form-based authentication) or only (Basic, No redirection, SSL Enabled) depends according to your setup.
Things to check:
If you have redirection configured in IIS on the Exchange 2007 Server Make sure that the above
Virtual Directories doesn’t have it configured.
If you have FBA enabled on ISA or TMG then disable FBA on Exchange 2013 CAS else users will be prompted twice for authentication
For further references you can refer my article below
http://exchangequery.com/2014/09/24/owaews-configuration-in-exchange-20132007-coexistence/
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 Thanks Sathish (MVP)

OWA Blank Logon Page After Update Rollup 12 for Exchange 2007 SP3

Hello
After installing Update Rollup 12 for Exchange 2007 SP3, can no longer access OWA - internally or externally through Internet Explorer - I just get a blank page (with IE). If I use Chrome or Firefox, and it uses the basic logon, I get a page with just
text, and am able to logon successfully. I have looked at several related forums, but have not found a fix yet. I've seen several people with similar issue have had success by copying contents from a previous owa folder version to the latest one, then running
Updateowa.ps1 and restarting IIS. This did not resolve the issue for me.
Another forum suggested running remove-owavirtualdirectory and
new-owavirtualdirectory, however I haven't attempted that yet, as I'm unsure how I could reverse the changes that the command runs if things get worse.
Any assistance will be appreciated.

Hi,
I encountered a same situation,after recreating
the virtual directory, the issue was solved.
The following article for you reference:
How To: Recreate OWA Virtual Directory – Exchange 2007
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

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

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

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

ICAL: Subscribe to other users Exchange 2007 calendars

Hi all,
I didn't see a category for iCal in the list for 10.6, so I hope this is a good place to put this post.
Is there any way to subscribe, from iCal, to other Exchange 2007 users' calendars?
Thank you!

After a bit more research, it turns out that this feature from Entourage or Outlook is NOT supported in Exchange support for Snow Leopard. Too bad.

Mail Sender Adapter for Exchange 2007 IMAPS account

Hi everybody,
I have the following todo:
I configured a Mail Sender Adapter that is supposed to fetch mails from an IMAP account.
The mails contain text files with data to be processed by XI 3.0 SP 22.
The mail server is Exchange 2007 and requires IMAPS. IMAP is not enough. I read the notes
- 893590 - XI 3.0 Mail sender adapter with IMAP or POP with SSL problem
- 856599 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 Mail Adapter
and configured the sender apapter as follows:
URL:                     imaps://<ip address>/owa
Authentication method:     Plain
User:                    <domain>\<user>
Password:                       topsecret
Poll Interval: 5
The first challenge is to setup the adapter with SSL. To do so, I added the Exchange server's
root SSL certificate in the default truststore service-ssl via the KeyStorage service.
This is necessary, as far as I know, to successfully validate the Exchange server's trusted
certifacate which is being transfered to XI during SSL handshake.
Since the communication channel in RWB is in status error with following message:
mail client job stopped completly
exception caught during processing mail message; java.io.IOException: invalid IMAP status response; not finding * STATUS, but 001I NO owa doesn't exist.
mail client job scheduled,
I do not know how to setup SSL for IMAPS. I successfully tested a PING to the Exchange server.
Are there already experiences with Exchange 2007?
What I have to do to fetch mails from an Exchange 2007 IMAPS folder/account with a Mail Sender Adapter?
Kind regards,
Andreas

Hi,
It should be imap and not imaps.
You can try imap://xxx.xxx.de:993/Inbox
Make sure that port 993 is correct. If you have doubt, then you may try 143 which is default port instead of 993 in the above url.
regards,
ganesh.

BPA shows domain prepped for Exchange 2007 SP1 after SP3 install

Hello,
I have a Client with a domain that is at 2003 domain functional level and 2000 forest level.
The client had Exchange 2007 SP1 and I have just upgraded it to SP3. There is one CAS, one Hub Transport, and one Mailbox Server (All three had Exchange 2007 SP1).
The domain and forest were prepped earlier by someone else and when I ran the installation program, it didn't pop up any errors on any of the servers.
The upgrade to SP3 is in preperation to Exchange 2010. Everything is working ok. I have checked:
1) In ADSIEdit, Exchange System Objects properties: Object Version =11221.
2) In ADSIEdit, Services>Microsoft Exchange>Organization: Object Version =11222
3) In ADSIEdit, RangeUpper value of ms-Exch-Schema-Version-Pt object = 14625
However, When I run the Exchange BPA, it reports that the domain is prepped for Exchange Server 2007 Service Pack 1 (In informational items). This is an informational item and not a warning or alert. However, I am concerned. Is this normal, and will it affect
the migration to Exchange 2010?
Thanks,
HA

Hello Ha20,
Based on my experience, it will not affect the migration. However, it’s recommended to prepare the schema again to avoid any potential issues.
Thanks,
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]
Simon Wu
TechNet Community Support

Changes in ical won't update my Exchange 2007 server

If I make a change in ical, it doesn't update my server calendar. It works the other way round. Can anyone help? Is it possible to make this work? My server support line tell me Exchange 2007 doesn't support ical.

bump... and please help. I'm really lost on this. My calanders say they are publishing to mobile me but they are not!

Online Archive for Exchange 2007

Prior to upgrading to Exchange 2013 before end of year, we are currently undergoing a thorough cleanout of our Exchange 2007 environment. Sadly, we had some users with well over 100K items in their deleted items, so you can only imagine what the rest
of their mailboxes look like. While we implement proposed policies for Exchange, we need an online Exchange Archive (preferably free) to be as seemless as possible to the user, but something that can automatically move messages to the archive based
on whatever threshold we set: 3 months after delivery, 6 months after delivery, or whatever. We would also plan to import any errant PSTs into this archive.
I found
THIS article, but it only mentions a patch that we are well beyond. Is there anything in Exchange 2007 similar to the
archive in 2010?
Thanks,
Nelson

Hi,
In Exchange 2007, there is no online archive feature, this feature is available in Exchange 2010 or later.
If you want to keep items for some time, as a workaround, you can use the Export-Mailbox cmdlet in Exchange 2007 to export items to PST file.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Lync2013 EWS URLs for Exchange 2007/2010 Coexistence

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

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

Best Migration Method for Exchange 2007 with multiple accepted domains

We are trying to determine which method would be best for us as we migrate to O365. Scenario as follows:
1) Multiple accepted domains (each in their own OU in AD); example: domainA.com, domainB.com
2) Exchange is 2007; clients will be upgrading the Outlook 2013
3) Would like to be able to sync mailboxes starting anytime but be able to cut over a domain at a time.
Tested so far with staged migration but it appears that with this, there is a change in the TargetAddress sending all mail to the O365. Even changing MXs didn't redirect the message as it reaches the Exchange box and immediately goes to O365.
We haven't tried the cutover as we're only able to test with the production box and if that somehow cutover the entire box, we'd be .. well, it wouldn't be good.
Anyone had any experience so that our #3 point would be doable, that would be great.
Thx
George

Hi George,
According to your description, I understand that the issue is related to Exchange migration from Exchange 2007 to Exchange Online for Office 365. This forum focuses on some general discussion about Office 365 ProPlus which
is the version of Office that comes with many Office 365 plans. Therefore, I suggest we can post the issue in Microsoft Exchange Online (Office 365) forum for more professional suggestions:
http://social.technet.microsoft.com/Forums/en-US/home?forum=onlineservicesexchange
Hope you can find the solution soon.
Regards,
Winnie Liang
TechNet Community Support

Color Controls for Calibration?

Is there any way to access color controls so that I may calibrate my 23" CD with a Colorvision Spyder and PhotoCal software? The Apple calibration routine is pretty vague, and I need the CD to match a calibrated CRT sitting next to it. Thanks.

"...if some software can adjust the colors, why can't I?"
You can if you want to run the Apple color calibration tool (Sys Prefs / Displays / Color / Calibrate). But if you want to use the Spyder, you have to use the Spyder software which is designed to work with the device.
DD

This is for Exchange 2007 but can't find a place to post it. It may apply here I don't know. What exactly happens when you suspend LCR?

OK. I searched out here and found things close to what I need: how to suspend and restore LCR but I need another answer. I have gotten a new backup solution (Unitrends) and the Microsoft exchange write appears twice. I'm guessing one is for my first storage
group and one is for LCR. Anyway it appears the software is trying to use the replication writer which is causing my backups to fail. Here is my question: what EXACTLY happens when I suspend the LCR (Suspend Storage Group Copy)? Does this affect regular exchange/email
transport and receiving at all? Basically if I disable it will mail continue to flow as normal with no adverse affects? And what EXACTLY happens when I disable LCR. What if I decide I don't need it. Will disabling it affect normal email operations? Basically
will either of these options in ANY way interfere with normal mail flow? Thanks.

Hi,
Based on my knowledge, suspending LCR doesn't affect the mail flow. If there is no need for LCR, you can disable LCR, and then please manually delete the LCR storage group and databaase fles.
For more information about LCR, please refer to
Local Continuous Replication.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Ical delegate color control for exchange 2007

Similar Messages

Maybe you are looking for