Lync Server Integration with Exchange 2013

Hello,
I have Exchange 2013 standard edition server installed and running successfully on a Windows 2012 machine. Now, I would like to have a Lync 2013 server integrated with it. I came across some links telling that its not possible to integrate Unified Messaging
in the Exchange standard edition and would need an Enterprise edition license. But, when I checked my ECP, I could see that UM is already there and its enabled.
So, Is it possible to integrate Lync 2013 with Exchange 2013 standard edition? What all things I need to take care of while Integrating? If someone could shed some light on this, that would be greatly appreciated.
Thanks and Regards,
Nash Burns

Yes you can integrate Lync 2013 with Exchange 2013 Standard, the only big difference between Exchange 2013 Standard vs Enterprise is the number of mailbox databases (5 vs 50).
Follow this link for information on integrating the two: http://technet.microsoft.com/en-us/library/jj688098.aspx (specifically integrating Lync with Exchange for Voicemail http://technet.microsoft.com/en-us/library/jj687983.aspx)
Having said that, the confusion may be related to User CALs. You need Exchange Enterprise User CALs to use the Unified Messaging components. (I believe they still work regardless, but
to be properly licensed and compliant you need to have the correct number of Enterprise CALs for the number of users that use UM)
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
www.lynced.com.au | Twitter
@imlynced

Similar Messages

Lync 2010 Integration with Exchange Online UM

Hi All,
Recently I have got the project to integrate Lync 2010 with Exchange Online UM, I have gone through the TechNet article but it seems very confusing and things are not very clear, can some please please help me out in this that how to setup this, what ports
do I need to allow from on premises to Exchange online UM.
There are some other questions as well which is not clear from TechNet.
1. Create SRV record, when I create the SRV record in external dns then in the host providing this service will be access edge fqdn is this correct.
2. Configure Edge Server for federation (do I need to run this on Edge server or on Lync FE Servers, I believe on FE SErvers is this correct, if yes then do I need to run the setup again on Edge server by exporting Topology or the replication will
do the needful)
3. To Create a hosting provider do I need to run this command on Edge or on Lync FE Servers.
4. To create a hosting provider you need to run the command
New-CsHostingProvider -Identity Fabrikam.com -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFQDN "proxyserver.fabrikam.com" -IsLocal $False -VerficationLevel UseSourceVerification
now from the above command -Identity what will be the Identity name it can be any thing or it should be some thing related to exchange online um.
for -proxyfqdn what will be the FQDN name here, from where I can get this name
5. Do I need to add or remove any domain names in office 365 if yes then what domain names it will be
6. If my sip address is abc.com then do I have to add this domain name in exchange online or do I need to add another domain name how this setup will be
7. if I will create any new domain in the dns in office 365 then do I need to add this domain name in my external dns if yes then which ip it will be pointed to.
Please guys help me out as I m new to exchange um online and I have never integrated it before.
Appreciate your help
If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync

1. Yes, create an SRV as per Lync documentation for external access to Edge.
2. Correct, all config is done on
Front End and will be replicated to the Edge servers. As long as your Edge servers are replicating successfully theere is no need to do a manual import.
3. Run this PowerShell on the Front End
4. Identity is a name to identify the hosting provider such as "Exchange Online". See http://technet.microsoft.com/en-us/library/gg398490.aspx
proxyfqdn for Exchange Online is exap.um.outlook.com
5. Your SIP domain will need to be added a a vanity domain in Office 365
6. Same as above, just add as vanity domain
7. Any added domains need to be setup as per Office 365 documentation, nothing special needs to be done for UM integration.
Check this out for more info - http://lyncinsider.com/instant-messaging/how-to-connect-lync-server-to-exchange-online-part-1/
Andrew Morpeth
Lync Server Specialist - Auckland, NZ
Check out my blog

Multiple owa sites on a single server 2012 with exchange 2013 (mailbox, cas)

hi,
I'm trying to
set up an exchange server 2013 on windows 2012 with all roles installed for 2 owa virtual directory, one for integrated windows authentication and the other for forms-based authentication.
I followed a tutorial for exchange 2010.
http://technicaljeditrials.info/2011/02/28/exchange-2010-multiple-owaecp-directories-part-1/
Step 1: IP Address
Obtain a second IP address and add it to the NIC of your server.
Step 2: DNS
Add a DNS entry for That secondary IP address for the name we will want to use in the new FBA OWA Web site.
I have chosen "testwebmail."
Be sure there is a valid SSL certificate (recommended to have UC or SAN
SSL certs) on the server Which has the new name "testwebmail" that will be used in the certificate.
Step 3: New Web Site
Create a new web site in IIS on the Client Access Server and bind it to the new IP address used in step 1.
Step 4: Adding Exchange Virtual Directories
The web site has been created and bound to the secondary IP address of our server.
Also the DNS record That will be used to access the OWA FBA new page was added to DNS.
The next step is to go into EMS and begin adding our virtual directories for OWA and ECP.
Login to the Exchange server and open the Exchange Management Shell.
Then run Get-Get-OWAVirtualDirectory and ECPVirtualDirectory to see the default OWA and ECP directories.
New-OWAVirtualDirectory -WebSiteName FBA -InternalUrl https://testwebmail.mylab.ad/owa
New-ECPVirtualDirectory -WebSiteName FBA -InternalUrl https://testwebmail.mylab.ad/ecp
Step 5: Configure the Virtual Directories
To configure the virtual directories we will disable FBA on the Default Web Site OWA and ECP virtual directories
Set-OWAVirtualDirectory -Identity "OWA (Default Web Site)" -WindowsAuthentication
$true -BasicAuthentication $false -FormsBasedAuthentication $false
Set-ECPVirtualDirectory -Identity "ECP (Default Web Site)"
-WindowsAuthentication $true -BasicAuthentication $false -FormsBasedAuthentication
$false
Step 6: iisreset
now if I access the default site I log in with
windows integrated authentication, but when I try to access the second site with forms authentication tells me username or password incorrect
Tell me you know where I'm wrong?
thanks
Greetings
Daniele

Hello,
Something like this:
New-OWAVirtualDirectory -WebSiteName "FBA"
Enable the Basic authentication via running the following command:
Set-OWAVirtualDirectory -Identity "yourservername\owa (FBA)" -BasicAuthentication $true
Restart the IIS admin service in services.msc
Thanks,
Simon Wu
TechNet Community Support

AD RMS 2012 integration with exchange server 2013

AD RMS 2012 integration with exchange server 2013
I would like to have a knowledge About this Topic
1.what is differrent if we use internal SSL certificate with Public Certificate and in this case i would like to use Mobile Phone I eed to import Root Certificate ?
2.Do I have problem? If I start to install AD RMS 2012 with SQL EXpress after that I want to chage it to SQL Server ?
3.when I use SQL Expres what I can do after Disk is full (10 GB)?
4.If AD RMS is down It will affect with email that it is already sent ?
5. Which Edition of outlook can produce IRM protected documents
6. To Use AD RMS Server 2012 through OWA, Outlook and Moblie Phone ,a CAL is required or not ?

Could you post the list of sites:
appcmd list site
The ones listening on port 80:
appcmd list site /bindings:http/*:80:
And on port 443:
appcmd list site /bindings:https/*:443:
Step by Step Screencasts and Video Tutorials

SBS2008: Move email from Exchange 2007 to new server with Exchange 2013

We have an old server (SBS2008) and plan to buy a new server with (Server 2012). I need to move all the exchange emails, contacts & calendars to the new server. We will no longer use the old server.
Is there a document or migration tool that will help me understand how to move this data form the old exchange server to the new one?
Old Server:
SBS2008 running Exchange 2007
New Server:
Server 2012
Exchange 2013
Any help is appreciated!

Hi Dave,
It can be done, and as Larry suggested you will consider two Server 2012 installs in order to achieve an environment that looks like your current SBS roles; Exchange 2013 on an Active Directory controller isn't a good long-term solution (SBS did this for
you in the past).
For your size operation, a virtual server host, with a Windows Server 2012 license, and two virtual machines would probably be a suitable design model. In this manner, you have Server 2012 license that permits 1 +2 licenses (one host for virtualization,
up to 2 Virtual Machines on same host).
There's no migration tool. That comes with experience and usually trial and error. You earn the skills in this migration path, and for the average SBS support person you should plan on spending 3x (or more) your efforts estimate in hours planning your migration.
You can find a recommended migration path at this link to give you an idea of the steps, but its not exactly point by point going to cover you off for an sbs2008 to server 2012 w/exchange 2013 migration. But the high points are in here. If it looks
like something you would be comfortable with then you should research more.
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
Specific around integrating Exchange 2013 into an Exchange 2007 environment, guidance for that can be found here:
http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
If that looks like something beyond your comfort level, then you might consider building a new 2012 server with Exchange 2013 environment out as new, manually export your exchange 2007 mailbox contents (to PST) and then import them into the new mail server,
and migrate your workstations out of old domain into new domain. Whether this is more or less work at your workstation count is dependent upon a lot of variables.
If you have more questions about the process, update the thread and we'll try to assist.
Hopefully this info answered your original question.
Cheers,
-Jason
Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP

Can't get OWA to work on Essentials 2012 R2 with Exchange 2013 on second server 2012 R2 std.

I have previously with success setup a working solution with server 2012 essentials, and a second server 2012 std. with exchange 2013, I did it following this guide: http://technet.microsoft.com/en-us/library/jj200172.aspx
Unfortunately I lost the server due to a cooling error which led to an un-repairable essentials 2012, since this was a new setup and also a test setup I didn't have any working backup solution setup at the time...tsk.tsk.
Since I had to make a complete do over I chose to try out the new R2 server editions, and set it up following the same guide, when it came to this part:
Download KB2732764 for ARR 2.5, and then install the update on the server that is running Windows Server 2012 Essentials.
Copy the SSL certificate file for Exchange Server to the server that is running Windows Server 2012 Essentials. The certificate file must contain the private key, and it must be in the PFX file format.
Note
If you are using a self-issued certificate, follow the instruction in the Exchange Server article Export an Exchange Certificate to export the certificate.
Open a command window as an administrator, and then open the %ProgramFiles%\Windows Server\Bin directory.
Based on you installation scenario, follow one of these steps to configure ARR:
If you are performing a clean setup, run the following command:
ARRConfig config –cert “path to the certificate file” –hostnames “host names for Exchange Server”
I noticed that the version of "Application request routing" had changed to version 3, so obviously I didn't need to dl the 2.5 update.. When I came to the part where I wa instructed to run arrconfig config etc. I noticed
that the ARRconfig file no longer where placed where the setup guide indicated, I then went ahead and tried som manual configuration regarding certificates and such. In the end I have a working solution where Exchange and OWA is working locally but OWA isn't
working outside my local domain, the link get's placed in the RWA and is indicating the correct link for the exchange server www.remote.clinten.dk I have a certificate which include to separate domain names aforementioned and remote.clinten.dk and
I get no errors indicating certificate errors, when I try to connect to www.remote.clinten.dk/owa from outside I get a 404 error, and when I connect to www.remote.clinten.dk I get the RWA login screen for the essentials RWA. Obviously I need to set up something
in ISS probably in the url rewrite section, but I can't seem to find the right setting.. Can someone help with this?
Btw. I have found the missing arrconfig file in c:\windows\system32\essentials" and tried to run the command as described in the guide "ARRConfig config –cert “path to the certificate file” –hostnames “host
names for Exchange Server”" but it doesn't seem to work, it just prompts with a guide for using the arrconfig command and examples of correct use, I also tried removing the "" from the guide, like this "ARRConfig
config –cert path to the certificate file –hostnames host names for Exchange Server",
when I ran it without the "" It didn't prompt me with anything nor did It indicate any errors, it did not however make my OWA work either..
I am aware that exchange 2013 atm. isn't officially supported on the R2 server, but the exchange works fine inside my domain, and the pop3/smtp also works from outside, since this Is a test environment, using only my own private domain and not a company
domain I figured it would be ok to run the risk.. ;)

Hi
found this on
https://social.technet.microsoft.com/Forums/en-US/1f099068-b3ed-44f3-a8c4-c22d760a8621/arr-broken-or-bad-syntax-exchange-2013-essentials-2012-r2?forum=winserveressentials
"Ok just an update for anyone else how has this issue.
The problem has been solved by Microsoft and I have included their findings below, but basically it comes down to a typo!
I often use notepad to have all the commands I need on hand, and I must have copied the command direct from the TechNet article or other website and customised the required fields. The issue with this is one of the characters did not “convert” - for want
of a better word. I should have retyped the whole command from scratch and it would have been right!
Thanks for everyone’s input and for Microsoft for getting to the bottom of it.
From Microsoft:
We have tested on your environment and here is the investigation result from our senior engineer:
================================================================
Basically the command fails due to invalid parameter, the invalid one is the ‘-‘. I think the one customer used is copied from the online document sample which translate to the unicode is 0x8211 means “en dash”, it
can’t be input by normal keyboard, so I pretty sure it is from web (mostly HTML document).
The one we check (compare) is ‘-‘ which has the code 0x45.
So it always failed to compare the parameter and ARRconfig.exe thought it is invalid parameter.
The solution is quite simple, just using keyboard to retype the command, using normal ‘-‘ and I have tried the password prompt shows
Best Regards,
Johnny Chen
Microsoft Partner Support Community Technical Support Engineer
Microsoft Global Partner Services"

How To Setup A Local Exchange Server Integrated With Office365 For A Single Mailbox

Hello,
We recently migrated to Office365 but had an issue since we need more than 16 simultaneous connections to a single mailbox. Because of this, we need to deploy a local Exchange Server that will be used to host a single mailbox that requires up to 500 simultaneous
connections for a Contact Center application. I'm looking for information on how to setup the local Exchange Server to basically create a local instance of a mailbox hosted on Office 365. So we can have our application open the numerous simultaneous connections
to our local server which will then connection to Office 365 to send/receive email through the mailbox hosted on Office365.
Please let me know if you have any information or resources you can direct me toward.
Thanks,
Chris

Hi,
To deploy local Exchange server integrated with Office 365, we can depend on Exchange Server Deployment Assistant:
http://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-AAAAAAAAQAAAAAEAAAAAAAA%7e
Please note that there may be 9646 error if there are many simultaneous connections at the same time.
Thanks,
Angela Shi
TechNet Community Support

Limitations of SharePoint 2013 integration with Exchange 2010?

Customer using SharePoint 2013 and looking at whether its possible to integrate this with Exchange 2010 and which features would be available / limitations. Looking for a matrix similar to those found in the Good, Better, Best documents available for previous
versions. Nothing available on Recently Published content for SharePoint 2013 yet http://technet.microsoft.com/en-us/library/cc262043.aspx

I haven't seen a specific list, but the three features I've run into that only work with Exchange 2013 are eDiscovery in Exchange, Automatic Task Synchronization with Outlook and the Site Mailbox feature. There is a Legacy Task Synchronization mode
available that will work with Exchange 2010 if you turn off the Farm level feature controlling Exchange 2013 task synchronization. It lets users manually sync specific task lists with Outlook. But there is no task aggregation. I found this
whitepaper helpful for exploring the new features and how to turn them off when using Exchange 2010.
http://www.microsoft.com/en-us/download/details.aspx?id=38799
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Can Exchange 2007 to be integrated with SharePoint 2013

Can Exchange 2007 to be integrated with SharePoint 2013?

In the sense of using Incoming and Outgoing email, absolutely. But not for other things, like Site Mailboxes, which require Exchange 2013.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Lync on premises with Exchange online UM SRV record

Hi,
We have Lync 2013 on premises and we have Hybrid exchange deployment, recently we have integrated Lync on premises with Exchange online UM, we have configured subscriber access and I have done all configuration, created hosted voice mail policy, created
Subscriber access UM contact.
Problem is that if a user dials from Lync client to voice mail (Exchange online UM Subscriber Access number) the call successfully establish, if the same user is outside the organization and wants to call the Exchange online UM Subscriber
Access number from his mobile or from his home phone number the call doesn't connect, this problem is not from the same user any one from outside the organization can not call to subscriber access number from his mobile or from his landline (outside the organization
numbers)
I have done some logging on Lync Edge server and found two things:
When a user calls from Lync client to O365 UM Subscriber access the call establish successfully and when I see the call logs I am seeing the
[email protected] and SRV record for the domain.com is verified
When a user calls from outside the organization (Landline or mobile) to O365 UM subscriber access the call doesn't establish and when I see the call logs I am seeing
[email protected] and subscriber access number as
[email protected] and the error says Unable to resolve DNS SRV record for domain it.domain.com.
Please note our internal domain is it.domain.com and our external or smtp domain is domain.com
In Lync 2013 the default sip domain is also it.domain.com and additional sip domain is domain.com
Pleasae help me to resolve the issue.
If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync

The issue is that your default domain is it.domain.com. I suspect that even if your Edge server is able to route this call back to Exchange online, that tenant will reject this call as it will not be able to find it.domain.com or federation SRV record associated
with it.
You will need to change your default SIP domain to your public SIP domain. If you decide to do this, please note that you will also need to review any impact on the simple URLs (and certificates if applicable).
It is also recommended to perform an export-csconfiguration command to backup the topology before making these changes.
Hope this helps.
SinghP80

Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

Here is the scenario:
Legacy Host: Windows 2008 R2
Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster). (copy VM files to new 2012 R2host) Everything works fine.
Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
Services upgrade.
Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
upgrade.
Thanks
Gerhard Waterkamp ACSLA Inc.

Hi,
Could you try use the following method to fix this issue first?
1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
http://support.microsoft.com/kb/947821/en-us
2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
%SYSTEMROOT%\Logs\CBS\
3. Please paste the checksur.log here for analysis.
If there is no error found, please try the following step.
==================================
2. Use Fix it tool to reset the Windows Update components.
1. Open the following link.
http://support.microsoft.com/kb/971058/en-nz
2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
3. Click “Run Now” to reset the Windows Update components.
Note: We can reset the Windows Updates manually by following the steps in the KB above.
3. Use the System File Checker tool to repair missing or corrupted system files
1. Open the command promote with Administrators.
2. At the command prompt, type the following command, and then press ENTER:
sfc /scannow
Any errors are found in the steps above, please let me know.
Hope this helpful.
Best Regards,
Jason Zeng
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Error while running SSRS 2012 report integrated with SharePoint 2013

Hi,
Our reporting services environment has SSRS 2012 integrated with SharePoint 2013. The SharePoint 2013 farm has 2 web front ends, 1 app server and a separate server for reporting services i.e SSRS 2012 .
We have created a https web application in SharePoint 2013 and all the SSRS 2012 reports are deployed into a "Report Library" residing in its root site collection.
The simple reports are running well. But there is a report where we have 3 multi-value parameters. On running this report in IE or Chrome, we get the error "Sys.WebForms.PageRequestManagerParserErrorException: The message received from the
server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled. Details: Error parsing near ' <!DOCTYPE html PUB'."
Some of the forums suggested to add the below entry in the web config of the SharePoint web app where the SSRS reports are deployed. We did that too, still the error is appearing. Please can anyone help .
<appSettings>
<add key="aspnet:MaxHttpCollectionKeys" value="100000" />
</appSettings>
Thanks

Hi Surendra,
I have tested on my local environment and the issue can be caused by the session time out ,the time out of the report precessing, database timeout,DataSet query execution timeout and so on.
I would like to confirm that the refresh you have mentioned is the page refresh or the report reloading?
Please reference to the setting below to don't limit the timeout values if you got the report reloading:
Point to a report in the library.
Click the down arrow, and select Manage processing options.
In Processing Time-out, select Do not time out report processing or
Limit report processing in seconds if you want to override that value with no time-out or different time-out values.
If you got the session timeout that refresh the page, please reference to the setting in below article:
http://msdn.microsoft.com/en-us/library/gg492284.aspx#bkmk_session_settings_section
Details information in the article below about the timeout setting for your reference:
Set Processing Options (Reporting Services in SharePoint Integrated Mode)
If you still have any problem, please feel free to ask.
Regards
Vicky Liu
If you have any feedback on our support, please click
here.
Vicky Liu
TechNet Community Support

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Cannot write email body in OWA with Exchange 2013 SP1 CU6

Hi,
I have a problem with Exchange 2013 SP1 with CU6.
All of OWA user cannot write in the body of email. They can write the Object and the recipient but they cannot select body and write the body message. We have try with multiple Web brother and desactivate all Add-on but the problem still there...
The only way that works is to respond to an email, and in that case, it's working, we can write normally in the body of email.
Have you an idea ?
Thanks in advance!
Sebastien

Hi,
After contacting Microsoft support, we have found the solution.
The problem appear after we have recently install the patch described in this KB 2997209:
https://support.microsoft.com/kb/2997209?wa=wsignin1.0
But on 2013 Mailbox Server, Echange is not installed in the default path C:\ but on D:\
So we have to manually copy the content of folder D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\prem\15.0.995.29 in the folder 15.0.995.31 (MAKE a BACKUP of FOLDER BEFORE!)
No need to reboot, or restart IIS, it's working after that!
@+
Sébastien

Creating a New Email address policy for users in another Domain with Exchange 2013 powershell?

Hi
Everyone
Is it possible to create a new-emailaddress policy with Exchange
2013 Powershell, for users within OU´s located on another different
domain/forest than where Exchange 2013 is installed?
There
is a Transitive, two way trust between the domain/forest where the users are
located - and the Exchange 2013, multi tenant domain.
Further
more, and if possible, I need to create linked mailboxes to all these users as
well.
Í have been struckling with this issue for weeks, so please anyone -
advice - and comment.
Best
Regards
Peter
A-ONE Solutions

Hi Siddharth
I want to create a new e-mailaaddress policy - and after that create linked mailboxes/users in my account domain with powershell.
Can you help me achieve that ?
I have a powershell CMDlet, but i doesn´t work. (Cannot fint user OU in my account domain)
CMDlet is as follows:
New-EmailAddressPolicy -Name $CustomerName -RecipientContainer "OU=$CustomerName, OU=kunder, DC=Domain, DC=local" -IncludedRecipients 'AllRecipients' -ConditionalCustomAttribute1 $CustomerName -Priority '1' -EnabledEmailAddressTemplates SMTP:%2g%1s@$AcceptedEmailDomain
Where $Customername = test.dk
and Account domain is = OU=kunder, DC=Domain, DC=local
But the command fails with:
New-EmailAddressPolicy : Couldn't find organizational unit "OU=Test.dk, OU=kunder, DC=Domain, DC=local". Make sure you have typed the name correctly.
At line:52 char:1
+ New-EmailAddressPolicy -Name $CustomerName -RecipientContainer "OU=$CustomerNa
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-EmailAddressPolicy], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : [Server=HE-MBX03,RequestId=2cbe1b51-4af2-4c04-9f7e-e440000975e6,TimeStamp=24-03-2014 12:58:19] 2D00FD2A,Mi
crosoft.Exchange.Management.SystemConfigurationTasks.NewEmailAddressPolicy
So, I cannot find the OU on the Account forest/Domain, even though the OU do exists in the Account domain.
Verifying with this:
Get-ADOrganizationalUnit -Identity "OU=$CustomerName,OU=kunder,DC=Domain,DC=local" –Server ‘DC01.domain.local’| FL
This works fine, Can you please help/assist?
Peter

Lync Server Integration with Exchange 2013

Similar Messages

Maybe you are looking for