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

exchange server 2013 change to web access url

$
0
0
I have install & configure exchange server 2013 in my local pc. my ip address http://192.168.0.30/ecp but not access http://mail.test.com/ecp. and till i have purchased one mail so till i wants to my mail server access (send and received mail all mail id public and private) please send configuration url. 

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!


XLSM files blocked through OWA even though allowed in virtual directory setting

$
0
0

I checked the virtual directory settings through powershell and xlsm files are in the allowed file types list.  We don't do the public/private setting so everyone connects through the public option.  I've tried adding the OWA URL to intranet and trusted websites.

The xlsm attachment icon is greyed out and I get the "Access to this attachment is blocked" message when clicking on the icon. What am I missing?

Exchange 2007 - Outlook 2013 - IMAP - no items downloaded

$
0
0

Hello,

I am facing a weird issue.

I use outlook 2013 and I am trying to get IMAP working from Exchange 2007. Authentication looks right and when receiving mail, outlook takes i little while when "synchronizing". But no mail is ever loaded in any directory. In OWA it looks ok and mails are visible.

I have tried - download all mails in IMAP config, recreating account in client, view only subscribed folders/not, I don't have problematic KBs that were mentioned on few discussions.

Thanks for any advice.

Exchange 2010 - Offline Address Book and Global Address List Issue!

$
0
0
I don't think I'm going crazy but cant find out why this is happening?

When I search the Address book in cached mode (OAB) in outlook for "Jackie W"I get a number of users which include "Jackie W***"but some are "Jackie K***" or "Jackie B***"but their Office is set to "Westminster"

But this is the strange part when I search on the address book with Cached mode disabled (GAL) I only get users with Surnames begging with"W" so only "Jackie W***" show up and if I just type in "Westminster" I get users form that location! but not a mix like on the OAB! Also when using the OAB if I type"Jackie West" it brings up the Jackie from Westminster but this dose not happen when using the GAL because there is no"Jackie West" in the Address book?

To my knowledge the OAB is just a Copy of the GAL that updates every 24 hours, and should be the same (give or take a few starters and leavers in the last 24 hours) and should pull up the same information when searching is this correct or am I going crazy! :D

Technical Beta Tester || Matthew John Earley BSc (hons) || www.o0MattE0o.myby.co.uk

Problem with Office 365 Home - Setting up mail account

$
0
0

Would like to use Office 365 Home with SBS 2003 ? Will this work ?

Receive an error "The resource that you are trying to use is located on an unsupported version of Microsoft Exchange. Contact your e-mail administrator for assistance"

Thanks

Can't Access OutlookAnywhere or ECP - Certificate Problem

$
0
0

I have a client with a new Exchange 2013 server that was migrated from Exchange 2007.  Everything was working fine. They still co exist.  Windows Essentials Experience was installed on the new exchange server.  I have uninstalled the Windows Essentials Experience and users can get email but there are a few lingering problems.  Primarily, there is no access to OutlookAnywhere or ECP.

Get-OutlookAnywhere returns the following:

[PS] C:\Windows\system32>get-outlookanywhere
WARNING: Warning: "Rpc (Default Web Site)" was not found. Please ensure that the RPC over HTTP Proxy feature has been added to server "A08".

RunspaceId                        : 07081ab0-858b-4574-b823-7a23f0938781
ServerName                         :A08
SSLOffloading                      : False
ExternalHostname                   : remote.associatedengineers.com
InternalHostname                   : remote.associatedengineers.com
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods          : {Basic, Ntlm, Negotiate}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       :IIS://A08.aei.local/W3SVC/1/ROOT/Rpc
Path                               :
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags              : {}
ExtendedProtectionSPNList            : {}
AdminDisplayVersion                  : Version 8.3 (Build 83.6)
Server                              : A08
AdminDisplayName                     :
ExchangeVersion                      : 0.1 (8.0.535.0)
Name                                : Rpc (Default Web Site)
DistinguishedName                    : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=A08,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=AEI,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=aei,DC=local
Identity                          : A08\Rpc (Default Web Site)
Guid                                : e240f899-98b1-4aed-bff0-d9e0c1f92538
ObjectCategory                     : aei.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 9/4/2014 2:15:23 PM
WhenCreated                        : 12/2/2008 7:13:37 AM
WhenChangedUTC                    : 9/4/2014 7:15:23 PM
WhenCreatedUTC                    : 12/2/2008 1:13:37 PM
OrganizationId                    :
OriginatingServer                  : A14.aei.local
IsValid                            : True
ObjectState                        : Changed

RunspaceId                        : 07081ab0-858b-4574-b823-7a23f0938781
ServerName                        : A14
SSLOffloading                      : True
ExternalHostname                   : remote.associatedengineers.com
InternalHostname                   : remote.associatedengineers.com
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                      : IIS://A14.aei.local/W3SVC/1/ROOT/Rpc
Path                              : D:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 847.32)
Server                            : A14
AdminDisplayName                   :
ExchangeVersion                  : 0.20 (15.0.0.0)
Name                            : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=A14,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=AEI,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=aei,DC=local
Identity                          : A14\Rpc (Default Web Site)
Guid                              : cb886cd7-dd5c-4976-83e2-790c263193c7
ObjectCategory                    : aei.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 9/4/2014 2:15:38 PM
WhenCreated                        : 8/30/2014 10:04:48 AM
WhenChangedUTC                    : 9/4/2014 7:15:38 PM
WhenCreatedUTC                    : 8/30/2014 3:04:48 PM
OrganizationId                    :
OriginatingServer                  : A14.aei.local
IsValid                            : True
ObjectState                        : Changed

When a user tries to login remotely to outlook anywhere they are presented with a certificate that is not the correct certificate.

The certificate information says

Issued to: e89a2f3098a5a0d0

Issued byL Token Signing Public Key

Get-ExchangeCertificate returns the following:


[PS] C:\Windows\system32>Get-ExchangeCertificate |fl


AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {remote.associatedengineers.com, www.remote.associatedengineers.com, associatedengineers.com,
                     webmail.associatedengineers.com, autodiscover.webmail.associatedengineers.com,
                     autodiscover.associatedengineers.com}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/,
                     O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US
NotAfter           : 8/31/2017 11:10:45 AM
NotBefore          : 8/31/2014 11:10:45 AM
PublicKeySize      : 2048
RootCAType         : ThirdParty
SerialNumber       : 27DE8143691709
Services           : IMAP, POP, IIS, SMTP
Status             : Valid
Subject            : CN=remote.associatedengineers.com, OU=Domain Control Validated
Thumbprint         : 0AC739F727C1BE8A1A7D4E7F210EDD6263F97121

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {A14}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=aei-A14-CA
NotAfter           : 8/29/2019 5:19:49 PM
NotBefore          : 8/30/2014 5:19:49 PM
PublicKeySize      : 2048
RootCAType         : Registry
SerialNumber       : 3F00000003A9D7CC948AF550E9000000000003
Services           : SMTP
Status             : Valid
Subject            : CN=A14
Thumbprint         : F6FF6B35A7DBFD1457C41F47485943073F278648

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=Microsoft Exchange Server Auth Certificate
NotAfter           : 8/4/2019 9:51:13 AM
NotBefore          : 8/30/2014 9:51:13 AM
PublicKeySize      : 2048
RootCAType         : None
SerialNumber       : 27232CBCD18185B546FBE5793AEF5645
Services           : SMTP
Status             : Valid
Subject            : CN=Microsoft Exchange Server Auth Certificate
Thumbprint         : 0A36707585CC0BC4C8662E58E986F8F05DEE81B7

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {WMSvc-A14}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=WMSvc-A14
NotAfter           : 8/27/2024 8:56:34 AM
NotBefore          : 8/30/2014 8:56:34 AM
PublicKeySize      : 2048
RootCAType         : Registry
SerialNumber       : 514EAEBED77CD5BF483F9C7077036B83
Services           : None
Status             : Valid
Subject            : CN=WMSvc-A14
Thumbprint         : 39940C9EF9AB475A7D144C83EFEF17C7B2053157

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {aei-A14-CA}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=aei-A14-CA
NotAfter           : 8/21/2054 12:19:40 PM
NotBefore          : 8/29/2014 12:19:40 PM
PublicKeySize      : 2048
RootCAType         : Registry
SerialNumber       : 7C5FD94CFED4EDA244B701291565C4F8
Services           : None
Status             : Valid
Subject            : CN=aei-A14-CA
Thumbprint         : 11D09686FEBED4ED4908497E6E71AA15DF5DEC23

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {A14.aei.local}
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=aei-A08-CA
NotAfter           : 8/27/2015 2:58:04 PM
NotBefore          : 8/27/2014 2:58:04 PM
PublicKeySize      : 2048
RootCAType         : Enterprise
SerialNumber       : 1B529423000100000036
Services           : IIS, SMTP
Status             : Valid
Subject            : CN=A14.aei.local
Thumbprint         : 7E1073385BE7C716A3E0410AA7335DA6F05B5DEB

Can anyone help me fix this?

Thanks

MAPI LOGON FAILED (MAPI_E_LOGON_FAILED) 0X80040111

$
0
0

Hello,

I’m running a test environment with Windows Server 2012 R2 / Exchange 2013 SP1 / Client Outlook 2013

- This is all running on one server

- Exchange is running in a VM  (HyperV)

I have installed Outlook on this machine (thus replacing Exchange MAPI with Outlook MAPI) all works fine.  After I uninstall Outlook and try to run any Mapi application I am not able to connect to my Exchange Server. I have tried using MFCMapi, and even installed CodeTwo’s ExchangeSync which uses Mapi and it also failed.

I do have Mapi HTTP enabled

I checked Outlooks Connection status and it shows HTTPS to the Server.

Any ideas what could be blocking the Mapi connections?




slow online mode "browsing"

$
0
0

Hi there,

Currently my configuration is exchange 2013 CU3 with windows 2012 server (fully patched and up to date)

my issue is with internal network slow outlook clients working with online mode (long delays when going from one message to another)

OWA mail browse is very fast though with no delays what so ever (IE8/9/10/11/Chrome)

I know that Microsoft recommend working with cache mode, but sometimes cache mode is not applicable like Terminal servers environment.

is there any way to improve online mode speeds? (exchange 2010/7 has not delays with outlook internal clients)

any ideas??

Thanks Ahead


User Password change fails in OWA 2013

$
0
0

User Password change fails in OWA with this error: Your password couldn't be changed. Make sure the old password you typed is correct and that the new password meets the minimum security requirements.

We are migrating from Exchange 2007 to Exchange 2013.  Have mailboxes in both environments.  OWA 2007 password changes succeed (user mailbox is still in Exchange 2007).  When the user mailbox is moved to Exchange 2013, password changes fail with the above error.

We have the Exch 2013 servers are on Windows 2012 and we are running Exch 2013 CU3.   We have made changes to the Default Role Assignment Policy to prevent users from changing Contact information and setting user photos, etc.  We are not exactly sure when user password changes stopped working, or even if they ever did work, although we recently installed our Prod Exch 2013 servers alongside our 2007 servers without any RBAC delegation implemented and a quick test of a user password change was successful.

I reversed all the changes to the Default Role Assignment Policy but the password change still fails.

Exchange 2013 not returning OAB URL Issue

$
0
0

We have implemented our Exch2013 servers 2 server 1 dag w/ 2 databases. We are using split DNS.

We have only moved over 2 users to the 2013 environment and ran into an issue with Address book not updating. Everything else checks out fine.

What I have found so far is the Autodiscover is not returning an OAB URL.

Test-outlookwebservice gives me this with a verbose:

"VERBOSE: [22:01:59.504 GMT] Test-OutlookWebServices : Autodiscover response:Microsoft.Exchange.Management.Tasks.ServiceValidatorException: The Autodiscover response did not return a URL forOffline Address Book. Response details:"

Get-clientaccessserver shows the autodiscover urls correctly.

Get-offlineaddressbook shows external/internal URls correctly and Webdistriution is enabled.

I have tried removing and rebuilding the autodiscover virtual directory based on some other troubleshooting I have found, but it is still not working.

Any ideas?

Which version of Outlook can be used to access the In-Place Archive mailbox in Exchange 2013?

$
0
0
Apparently, some versions of Outlook can view the In-Place Mailbox in Exchange 2013 and others cannot. What to tell the customer regarding which versions of Outlook they can use in case they need to purchase a special version of Outlook. They already have several versions Outlook 2007, Outlook 2010, Outlook 2013 that came with their computers as part of Microsoft Office Home and Business.

john11

Exchange Server version details needed for Office 365

$
0
0

The moderators on the Microsoft Office 365 forum have asked me to repost the following question to this site instead:

I am setting up a cloud-based Customer Relationship Management (CRM) solution for my users who do not have a client version of Outlook i.e. we all use OWA for emails and calendar etc. The CRM provider needs to know the version of Exchange Server being used in Office 365 so that they can set up integration but I can’t find this information anywhere. The instructions for ‘Connecting Office 365 to your Outlook desktop application’ aren’t any help in this instance as Outlook won’t be calling for the data.

Can anyone advise please – I don’t want to take a guess!

Many thanks
Peter

Creating archive rule on the clients by script

$
0
0

Is it possible to create archives rule by script (powershel,vbs) or something else? I want to create archives rule on all of the client in organisation… with out manuals, I cant use GPO.
Thank you for your answer.

We use outlook 2010 and Excahge 2013

Outlook Connection to Exchange Issue

$
0
0

Hello,

After I assigned my IIS,IMAP,SMTP,PoP3 services to my public certificate, I cant' configure my outlook clients to connect to exchange. Outlook outdiscover finds the exchange server, but when logging it gives my security alert and freezes. Could you please assist me with this? Thanks a lot.


Pooriya Aghaalitari


unable to access OWA on iPad / iPhone

$
0
0

New Exchange Server with Certificate installed.
webmail.domain.com & autodiscover.domain.com setup on the Certificate 

I'm able to access OWA & ECP on a PC with https://webmail.domain.com/owa (or ECP)

However on mobile devices such as Andriod I get a SSL error!

on the Andriod phones I can setup Activesync but owa gives SSL error

on iPhone/iPad neither activesync or owa will work - even tried chrome on iPad

 


ChrisS

Remove misconfigured e-mail

$
0
0

Hi, I have a problem with removing Microsoft Exchange Server in Outlook 2013. The server is not recognizable and outlook does not work. I tried to follow the instructions given in order to remove the misconfigured e-mail on a wrong server :

1) Go to Control Panel and type mail to search for theMail item, and then open it. If there are two Mail items, choose the one that is labeled Microsoft Outlook 2013 or Microsoft Outlook 15.
2) Now click on Email Accounts and select the misconfigured Exchange server email account and click onRemove and Close.
3) Now try starting Outlook and verify the result.

The problem when following the instructions is that Microsoft Outlook 2013 cannot be open when I search it from the Control Panel. I have 64-bit operating system and the Microsoft Outlook 2013 appear as Mail Microsoft Office 2013 (32-bit).

If you could help me with configuring Outlook 2013 so I could run it on my computer.

Thank you!

I am looking forward to hearing from you!

Outlook Anywhere not working for some users

$
0
0

Hi All,

I am having a strange issue today with a customer - Outlook Anywhere has been enabled on their Exchange 2010 environment, but it doesn't work for some users.

Using the ExRCA I have been able to identify the following error on the users who are unable to connect:

"Testing the MAPI Mail Store endpoint on the Exchange server."

"Attempting to log on to the mailbox"

Mailbox logon returned ecLoginPerm 1010. You don't have the correct permissions to log in to the mailbox.
EMSMDB Status: ecLoginPerm 1010
Elapsed Time: 225 ms.

On users that are able to connect it goes through the ExRCA without any issues.

Any help would be much appreciated.

Cheers,

Jack

Testing the MAPI Mail Store endpoint on the Exchange server.
 An error occurred while testing the Mail Store.
 
Additional Details
 Elapsed Time: 333 ms.
 
Test Steps
 
Attempting to ping the MAPI Mail Store endpoint with identity: outlook.mg.com:6001.
 The endpoint was pinged successfully.
 
Additional Details
Attempting to log on to the Mailbox.
 An error occurred while logging on to the Mailbox.
 
Additional Details
 
Mailbox logon returned ecLoginPerm 1010. You don't have the correct permissions to log in to the mailbox.
EMSMDB Status: ecLoginPerm 1010
Elapsed Time: 225 ms.


While in Exchange 2003-2010 Coexistence, Proxy/Redirection Points to Internal 2010 Server URL

$
0
0

Swing migration from Exchange 2003 to 2010 behind TMG 2010 SP1.

After configuring the two servers for coexistence, OWA and ActiveSync work just fine as long as the mailbox resides on the Exchange 2003 Server. If the mailbox resides on the Exchange 2010 Server, the page cannot be displayed because the URL in the address box is pointing to the INTERNAL address of 2010 server.

Internally this works just fine. But as the address is not available from the Internet, user simply receive an error.

Everything else appears to be working just fine. Mail flow. Public folder access. We're not looking at a critical situation here. But, I can't proceed with the migration until I can solve this.

I've searched high and low for articles that address my situation, but I have not been successful in finding a solution matching my situation.

I would appreciate any insight.


Bob Esquenazi

Decomissioning and old Exchange 2013 server : OWA unavailable

$
0
0

Hello group, we are trying to decomission an old Exchange 2013 mailbox server.

Arbitration mailboxes are moved successfully.

However, when we offline the old Exchange Server prior to decommission in order to test for negative impact, we lose the access to ecp and owa, even with a working frontend CAS Exchange 2013 server and backend mailbox server remaining in production.

PS : We updated the virtual directories to Exchange 2013 version, if that information can be of any help.

[PS] C:\Windows\system32>Get-OwaVirtualDirectory -ShowBackEndVirtualDirectories

Name                                    Server                                  OwaVersion

----                                    ------                                  ----------

owa (Exchange Back End)                 NEWMAILBOXSRV                            Exchange2013

owa (Default Web Site)                  NEWCASSRV                                 Exchange2013

owa (Exchange Back End)                 OLDMAILBOXSRV                            Exchange2013

 

When OLDMAILMBOXSRV is offline, the requests fulfill authentication (auth.owa) page and stall here

We are going to check the IIS Logs for protocol status and win32 status and give you more information when we’ll try again to offline the server.

Any obvious thing we need to check in the meantime?

 

Viewing all 10580 articles
Browse latest View live


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