Quantcast
Channel: Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients forum
Viewing all 10580 articles
Browse latest View live

Migrating from Exchange 2010 to Exchange 2013 while coexisting

$
0
0

Hellow everyone.

I would like some knowledge insight in my preparation for a migration of exchange 2010 to exchange 2013 with DAG in our DR Site.

First of all, what i would like to achieve. 

  1. after moving users mailbox to exh2013, i would prefer not to have any manual intervention in the users outlook profile
  2. iPhones/Android using active sync ( if possible, be reconfigure automatically )

What i have done so far.

  1. exchange 2010 upgrade to sp3 (current owa.pro.mydomain.com, it has an old cert that will expire next year owa.pro.mydomain.com )
  2. Exchange 2013 installed in Prod ( PROD2013 current webmail.mydomain.com )
  3. and DR (DR2013 current drwebmail.mydomain.com )
  4. wildcard certificate installed in both exch ( *.mydomain.com )
  5. my internal domain is mydomain.local, so i created split DNS in my DNS servers
  6. configure DAG ( 2013DAG.mydomain.local ) and give its IP - Tested and working
  7. changed its Virtual Directory to use the same address for internal and external, including autodiscover
  8. created the A records to DNS to point to its respective servers

Now the issues i am facing.

  1. When move a test user to new PROD2013, the user can use the OWA successfully, but i cant successfully use outlook 2013 or 2010, it get error The action cannot be completed. the connection to microsoft exchange is unavailable. outlook must be online or connected to complete this action.
  2. I can complete it manually, but everytime i open the outlook i get prompt for username and password

it led me to believe that is   authentication issue, here is my autodiscover details, which in my point of view it is correct.

C:\>Get-OutlookAnywhere -server PROD2013

RunspaceId                         : 6512e9c9-4e21-43eb-bc03-7a45185ae23d
ServerName                         : PROD2013
SSLOffloading                      : False
ExternalHostname                   : webmail.mydomain.com
InternalHostname                   : webmail.mydomain.com
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://PROD2013.mydomain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 913.22)
Server                             : PROD2013
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web
                                     Site),CN=HTTP,CN=Protocols,CN=PROD2013,CN=Servers,CN=Exchange Administrative
                                     Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=mydomain,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=local
Identity                           : PROD2013\Rpc (Default Web Site)
Guid                               : 22368d46-0985-498d-83c3-aabf395ece3c
ObjectCategory                     : mydomain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 17/06/2014 14:48:00
WhenCreated                        : 02/06/2014 12:18:00
WhenChangedUTC                     : 17/06/2014 13:48:00
WhenCreatedUTC                     : 02/06/2014 11:18:00
OrganizationId                     :
OriginatingServer                  : PRO-ADC02.mydomain.local
IsValid                            : True
ObjectState                        : Changed

If someone could give some help it will be very appreciated.

Cheers


Exchange Auto Mapping

$
0
0

We run Exchange 2010 SP3 on prem (with Outlook 2010 and 2013), we have started experiencing auto mapping problems since we applied Rollup 6. It is affecting an increasing number of clients as well.

The main issue is that some users who had previous access to Shared Mailboxes working just fine have now "lost" access to the shared account folders. Outlook simply displays the client's personal folder structure instead of the folders belonging to the Shared mailbox. Properties of the Shared account Inbox actually point to the person's email address, not the shared mailbox one.

All attempts at remedying the situation failed, including recreating the profile, setting up on a new computer, cache vs non-cache mode. Even giving access to the Sahred mailbox to a new user will result with the same problem. The auto mapping attributes (msExchDelegateListLink and msExchDelegateListBL) check out fine as well. At a loss with this one. Note that the shared accounts are fine, accessing them via OWA for instance works just fine.

Finally, I noticed that auto mapping for our Outlook 2013 clients has stopped working altogether. Can this be related?

Help!


Windows Store App with Exchange Web Services (EWS) - Password change troubles

$
0
0

Hello All,

I'm working on a Windows Store App (Target: Windows 8 & 8.1; Dev Environment: VS 2012, Windows 8.1) that communicates with an Exchange Server (office365) using EWS. I've got most of it figured out but I am facing an issue and am not sure how to go about fixing it.

Here's how the problem is created:

  1. Log in to exchange with user account XYZ through the App
  2. Change the password for user XYZ through OWA
  3. Fetch data from the exchange server through the App

The problem is that at 3, I am able to fetch data through the App even though the password has changed. I have verified that the password has, in fact, changed, by logging in through OWA (the old password does not work but the new one does).

I have tried

  1. restarting the app
  2. uninstalling the app before running it again
  3. restarting the dev machine before running the app again
  4. wait 15 minutes (It's now been 4 hours since I changed the password) before trying again

but I'm still able to fetch data from Exchange without specifying the new password. My guess is, the session is saved somewhere on the local machine and it does not get invalidated even when the password has changed. But I haven't been able to figure out where.

What's weird is that I see the same behavior in Outlook. Outlook is able to sync with the Exchange server without requiring me to enter the new password.

I'm trying to figure out how to get the App to stop communicating with the server when the password is changed. The solution does not have to be programmatic.

Any help will be greatly appreciated. Thanks in advance.

Outlook Web Access will only log in as Light Version

$
0
0
My office has been using Microsoft Exchange Outlook Web Access for longer than a year at least. We have been using the full version.  We have a desktop operating Windows 7 with the most updated IE browser, and my computer a Windows 8 laptop with the most updated IE browser. My lap top is where the problem is. As of about two days ago the OWA is only logging in as the Light version. There is an option on the log in screen that says "Use Outlook Web Access Light" and the box is checked and grayed out so that I can not uncheck it. I did not check this myself it just happened. Also the setting for blind and vision impaired users is not checked off in the accessibility tab under options. I have checked the Windows 7 desktop and it is functioning normally.  It allows the user to check or uncheck the "use outlook web access light" at will and does not get stuck in Light version.  Also please note that this is the same email address for both computers not multiple users where one works and one doesn't.  I am charged to monitor the email in our office and do it from the laptop but there is access to it on the desktop if the other employee needs access.  I have also seen forums where they say to change the server to say OWAPremiumClientEnabled. I do not know how to do this.  If this is a possible solution please give me steps on how to access the server which i don't even know if i am connected to.

Cannot access Exchange Admin Centre (ECP) on Exchange 2013 server. Got HTTP 500 Internal Server Error

$
0
0

I just installed Exchange 2013 Standard SP1 on a server running Windows 2008 Server R2 SP1.  I didn't encounter any issue when installing Exchange 2013 SP1.  It passed prerequisite check and went though all 15 steps smoothly without any issue. However when I tried access Exchange Admin Centre (ECP) at https:\\servername\ecp I got HTTP 500 Internal Server Error saying  "This website cannot display the page.  Most likely causes: 1. The website is under maintenance. 2. The website has a programming error."   I tried access ECP at https://localhost/ecp and I got the same problem.  Under either cases I was able to see the logon page of  ECP and I was able to enter my credential (e.g. domain\user name, password).  However I got HTTP 500 Internal Server Error at the next page.  I tried entering wrong password and ECP returned "The user name or password you entered isn't correct.  Try entering it again".  This indicates ECP does check my logon credential. 

I checked the event viewer of the exchange server.  There is nothing Except for a couple of entries of Schannel eventID 36888 every hour.  I did some reached on this.  As per the link below, there is nothing to worry about.

http://social.technet.microsoft.com/Forums/forefront/en-US/92c63737-c2a3-41f7-8878-3b0cf5ee95ff/new-install-event-log-schannel-event-id-36888

My research showed that HTTP 500 error messages are generally attributed to either certificate misconfiguration or authentication misconfiguration of OWA and ECP, but I don't know why I get this error right after a fresh new installation.

One thing I want to mention is that there was a previous attempt of Exchange 2013 installation by a former IT person.  I ran "get-ExchangeServer" command in Exchange Management Shell and it returned two servers both running Mailbox and Client Access role.  The first server in the list does not exist anymore as I confirmed the server hardware has been wiped and rejoined to the domain not as an exchange server.  The second server is the one I installed recently.  

Any idea what caused the problem?  Your help is much appreciated. 

Two companies, one Exchange Server

$
0
0

We are an organisation with a single Exchange 2010 server.

All our addresses are currently @aaa.co.uk.

We have now acquired another company (bbb.co.,uk) and would like some of our users to have the ability top receive email from both domains and to be able to send from either @aaa.co.uk or @bbb.co.uk.

It would be advantageous to have the emails kept separate which may suggest these users having a mailbox for each company.

We have all our mail coming in via an ISP, who host our MX records, so I assume we just get them to host the MX records for bbb.co.uk also.

We do not have an Edge Transport server role.

Where do I go from there?

Am I right in thinking we need to create an Accepted Domain for bbb.co.uk then create separate mailboxes?

Well explained guidance would be much appreciated.

Regards,

Shared Mailbox 'Send As' Error

$
0
0

I have created a shared mailbox with three recipients and this works fine.  I have added two 'Send As' delegates and this has worked but when I try and add another 'send as' I get the following error:-

warning
The appropriate access control entry is already present on the object "CN=Office,OU=**************.onmicrosoft.com,OU=Microsoft Exchange Hosted Organizations,DC=EURPR07A002,DC=prod,DC=outlook,DC=com" for account "EURPR07A002\kate50282152621639".

If I try and delete one of the 'send as' delegates I also get a very similar message.  I have checked as many settings as I can and cannot see a reason for this?

The attachment size exceeds the allowable limit

$
0
0

I am using Exchange 2013 on Windows 2010 and all my clients are Outlook 2010. 

We cannot attach more than 10MB's of attachments. I get the two below errors in Outlook:

I have increased both the send and received connectors in ECP to 100MB and restarted the transport service. No luck. All users are effected by this.

Any ideas?

Thansk


Dave


How to search users in Outlook Using Last Name and First Name

$
0
0

During recent times we change the naming convention in AD, FirstName , LastName

We can search users using More Columns but I would like to know alternate method to search users. The search result should sort results by last name as query


Regards Chen V [MCTS SharePoint 2010]

Imap folders open with multiple threads in read/write mode - getting denied

$
0
0

Cannot Open Imap folder with Multiple threads in read/write mode - getting denied.  It only allows one thread. 

This article is expressing my same issue and refers to Exchange Throttling:

http://stackoverflow.com/questions/24189171/javamail-multiple-threads-opening-a-folder-in-read-write-mode-is-blocked

However, I have increased all throttling in a new throttlingpolicy I created just for this user to unlimited.  I have set Imap eventlogging to high for both imap and imap BE.  I'm still not seeing any indication why Exchange could be blocking another thread to open that same folder in read/write mode.

How can I further debug this or fix this?!

Exchange 2013 OWA, Active Sync etc...

$
0
0
We are in the process of replacing our 2007 Exchange environment with a 2013 messaging environment with a hosted Edge Transport service.  My question is,  are the Active Sync and OWA interfaces exposed via the Mbox and CAS roles or are they now connected via the NEW Edge Tranpsort services.

Exchange 2013 SP1 OWA the page can't be displayed issue

$
0
0

OWA the page can't be displayed

Hi,  i've Exchange topology (upgraded from 2007 one server)

2 CAS servers NLB with VIP 172.16.0.98

2 MBX Servers DAG with DAG

using Cisco ASA NAT public IP for example 9.9.9.9 ....> 172.16.0.98

i've created split DNS zone for public domain in internal DNS to unify URLs internal and external Mail.Domain.Com

i've created internal zone called Mail.Domain.Com and Autodiscover.domain.com point to VIP 172.16.0.98

Everything is OK but sometimes users report when they access OWA from inside or outside when user submit user/ pass faced error  the page can't be displayed?

i tried this this user from different browsers and different computer the same issue 

if i tried another user from the same computer it works fine

the strangest point after 30-60 minutes it backs to live and everything going fine

i checked event viewer there is nothing related to this issue.

in sometimes if i tried to access manual to CAS1.Domain.Local / IP address/ owa it works fine.

 URL changes to https://Mail.Domain.Com/owa/auth.owa

i red some about putting my public domain as remote domain but it's not clear !

any ideas please?


Delivery has failed to these recipients or groups:

$
0
0


I get this error message: #550 5.7.1 RESOLVER.RST.AuthRequired; authentication required ##

I have this mailbox that I setup with a forwarding rule that when a message arrives to inbox form anyone it should redirect the message to a distribution group. But in the inbox all I see are error messages. I checked that the distribution group doesn't have any restrictions on either. I also went and set "Send-as" permission on the distribution for this email address. But I still get this NDR:


Microsoft OutlookReplyReply AllForwardActions
To:
 mailbox@domain.com
 Wednesday, September 18, 2013 12:28 PM
Delivery has failed to these recipients or groups:
distributiongroup@domain.com
Your message can't be delivered because delivery to this address is restricted. 

Outlook 2013 Profile Error

$
0
0

Every time I open Outlook 365 I get the following error:

"Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. Your profile is not configured."

Click "OK" and the box closes. 

If I remove my profile and re-add it I can get into my mailbox, however it immediately acts up. I can receive mail but can not send it. If I close Outlook I get the same error again and have to remove my account all over again. I have tried deleting the profile and all outlook files under my Windows profile, have removed my profile uninstalled office and re-installed. I have tried running 'outlook.exe /resetnavpane' in the command prompt as well as running scanpst.exe. All other office products as well as Outlook 365 Online work.

Exchange Email account, only 1 account. outlook is not in compatibility mode.

I am open to any suggestions at this point.

Multiple OWA sites, one using Windows Auth, one using FBA and still able to use single namespace?

$
0
0

I have Exchange 2010 SP3 now.  Owa uses Windows Auth only now.

I have Exchange 2013 SP1 installed but with no mailboxes.  I would like to setup this environment so that OWA users on the inside use Windows Auth and external users use FBA.

I've read that to do this I would setup the default website OWA site for Windows Auth, and then setup a second website (with a second IP) with a second OWA virtual directory and set it to FBA.  I would do this with ECP too.  I understand this, but then would I still be able to use the single namespace of mail.doman.com?  Or would I need to set it so that external had mail.domain.com and internal had servername.domain.com?


Exchange 2013 RPC URL shows Error 404 Page Not Found

$
0
0

Hi,

I have been told by Barracuda Support to verify my Exchange 2013 RPC url is working correctly using the following address in a Web Browser: 

https://RoH server address/rpc

When I hit this URL I input my credentials and get a Error 404 - Page Not Found. 

I dont have any issues with Outlook Anywhere and clients are working fine. The tests come from this article and I am wondering if they are still valid for Exchange 2013 so need some help:

https://techlib.barracuda.com/BMA/EnableRoH

Does anyone else get the 404 error when they try the RPC virtual directory? If I got rpc/rpcproxy.dll that works fine and no issues. 

We have Outlook Anywhere configured for NTLM authentication so maybe this is an issue and should be Basic?

Calendar Conditional Formatting disappears randomly

$
0
0

I have an exchange calendar that has been shared via SharePoint / Comcast

All of the conditional formatting was set up on each individual computer. It is not necessary to have everyone see the same conditional formatting. 

Everyone looks at the calendar in preview mode, so that the body of the events can always be seen .

If the calendar is closed, and re-opened,  sometimes - randomly, it will re-open in calendar view but w/o preview. When they change the view back to preview, the conditional formatting has disappeared. If you open the conditional formatting window, all of the settings have disappeared. If I re-enter all the cond formatting settings, they will stay until who knows when...

What am I missing to make these settings "stick"?

This has happened at different PCs

Windows 8.1 Pro - Office 2013 H&B

Windows 7 Pro - Office 2007 and Office 2010

Unable to open OWA cross site between 2013 and 2010 Exchange Server

$
0
0
Hello,
First of all allow me to describe the scenario as this always helps and is often omitted from many questions.
 
SITEA – 1 x 2010 Exchange Server (All roles except UM and Edge), Domain controllers etc available
SITEB- 1 x Newly installed 2013 Exchange Server (Mailbox and CAS roles), GC Domain controllers etc. avaliable

Sites and Services are correctly configured between the sites and we have a high speed WAN connection between the data centres all ports and communication between servers at both sites are open as the connection is secure. 

After installing Exchange 2013 in SITEB, whenever I try to login to either the ECP or OWA of the 2013 with a user whose mailbox is in SITEA we immediately receive the sad smiley face with the something went wrong message. Clicking more details displays the following message:
X-FEServer: <OUR_EX_2013_SERVER>

I was expecting Exchange to proxy the request to the 2010 server and get the 2010 OWA experience. If I create a new mailbox on the 2013 then it is of course fine. 

Is someone able to suggest any troubleshooting steps? I have of course fully followed the Exchange 2013 deployment assistant from Microsoft and ensured all pre-requisites were carried out. 

The Exchange 2013 server is SP1 and is running on Windows 2012 R2

Autodiscover for Exchange 2013 migration

$
0
0
Hi,

I am after a bit of advice for autodiscover in an Exchange 2010 to 2013 migration. 

Just to set the scenario:

Site A - 1 x Exchange 2010 server 192.168.0.10
Site B - 1 x Exchange 2013 server (new/proposed) 172.16.0.10

1 forest and domain = company.local
External Name= company.co.uk (configured for split DNS)

The sites are correctly configured in AD sites and services and there is a very fast (100Mb) and secure WAN connectivity between the two sites. 

We want to migrate all the mailboxes to the new 2013 server in Site B. 

My question relates to autodiscover. Currently on the 2010 server when I run the following command to get the autodiscover information I receive the following:

Get-ClientAccessServer | Select Name,AutodiscoverServiceInternalURI,AutodiscoverSiteScope | Fl

Name                                          :EX2010
AutoDiscoverServiceInternalUri: https://ex2010.company.com/autodiscover/autodiscover.xml
AutoDiscoverSiteScope              : Site A


When we install the 2013 server (CAS & MBX) I am unsure as to what to configure the AutoDiscoverInternalUri to? 
Do I set it to be the same as the Exchange 2010 server above? The issue I am concerned with is the company is looking to change the namespace to a new domain name - so want to use mail.newcompany.com for everything including autodiscover (which will be autodiscover.newcompany.com)

I hope this question makes sense! All I am looking for is a way to test that when a mailbox is moved to the new Exchange 2013 site the user will still be able to discover and connect to their mailbox with no popups or warnings 

This question assumes that we will be purchasing a SAN SSL certificate and will have configured all the OWA/EWS etc to use the same names internally and externally in a split DNS method. 

Thanks!

http 400 - bad request

$
0
0

The setup is as follows

Windows Server 2012 R2 running Exchange 2013 CU5 - CAS Role
Windows Server 2012 R2 Running Exchange 2013 CU5 - Mailbox Role
Published via Web Application Proxy, using ADFS on Server 2012 R2


The problem

Browse to https://webmail.contoso.com/owa - log into OWA as myself this works fine - try and open another users mailbox that i have full access to, i get HTTP 400 bad request

If i browse to https://servername and perform the same procedure it works.   This leave me to the conclusion that the Web Application Proxy server / ADFS server is at fault

this KB article is not relevant in this instance, as I can resolve the names correctly;http://support.microsoft.com/kb/2770796/en-au

Any suggestions

Thank you.


Viewing all 10580 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>