Hello, 

I'm try to configure Office Customization Tool such that when a domain user logs into any workstation, their outlook profile is automatically configured and the shared department email account is added as the secondary mailbox but it hasn't worked for me. I looked up for the settings on the internet where I found a few server settings but none of them worked for me. We have Office365; I added outlook.office365.com, and the settings that starts with chprod.. that didn't work either. I also sent a test email, and looked up the server settings from messageheaderanalyzer in office365 OWA and added the settings in the OCT, that couldn't pull up the email either. How can I make it to work? 

Just to be clear, this is what I want. 

When a user logs in to the workstation and starts outlook, it should find the users email and configure it automatically. Then it should also add department mailbox as their secondary mailbox if they have permission. 

Thanks

Hi,

I recently switched over to office 2013, and bought enough copies to upgrade our entire office to Office 2013 (80+) But on the few test machines I've installed on everyone is having a problem with outlook not displaying the unread message count.

Let's say I receive 5 new messages, my inbox on the left pane will show that there are no new messages but if I click on my inbox I see the messages listed. If I restart outlook it will then display Inbox 5 and Unread: 5 on the bottom bar. If I open all 5 messages, this number doesn't change again until I restart outlook again.

We are using Communigate as a mail server, using the Mapi Connector for Outlook.

I need to find an answer to this before I begin this roll out, or people will be missing e-mails all day because they rely on the unread count.

Thanks, 

Josh

Hi!

We are running Exchange 2013 together with Outlook 2013.

After installing Exchange SP1, the following messages appears on all clients:

"The Exchange admin has made a change that requires you to restart Oulook"

This appears when starting Outlook, and also at random intervals when Outlook is running. I have tested to recreate a profile on the client, but this doesn't help. And the message did not apear before Exchange 2013 SP1.

What can I to to make this disapear?

Regards,

Lennart

Hi All

Exchange Server - 2013 CU2 (Windows 2012 Standard)
AD Server - 2003 R2 SP2
exchange-svr01.domain.com - internal name
mail.company.net - external name

When users opened Outlook 2010, they will encountered

"There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site exchange-svr01.domain.com.

Outlook is unable to connect to the proxy server.(Error Code 10)"

I also used the Microsoft Remote Connectivity Analyzer to test RPC/HTTP connectivity.

    Validating the certificate name.
     Certificate name validation failed.
     Host name company.net doesn't match any name found on the server certificate CN=AMAZONA-U59HG9G.

Testing SSL mutual authentication with the RPC proxy server.
     The test passed with some warnings encountered.
     
The certificate common name company.net doesn't match the mutual authentication string provided mail.company.net; however, a match was found in the subject alternative name extension.

 please help.

Hi Everyone,

I just migrate from Exchange 2007 to exchange 2013. Last night I migrated the Public Folder and this morning it keeps popping in outlook the following message. I closed and reset outlook twice but it keeps coming back.

"Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook"

Please for assistance.

Raphael

Hello,

We are in the process of attempting to migrate to Exchange 2013, but during the migration time, we need to coexist with the two versions.  Our outlook clients are a mix of Office 2007, 2010, and 2013.  When a user is migrated from 2010 to 2013, they start getting prompted for their password in Outlook every few minutes.  They can click cancel and continue working, but they continue to get prompts for their password.  If they click the update folder button in outlook, it updates fine, and the password prompt goes away for awhile. 

Most topics on this state that this is caused by a certificate issue.  We have an internally deployed CA, with the Root certificate trusted by all clients.  The exchange 2013 server has a certificate that was created by this CA.

I believe that this is caused by OAB (address book) still being hosted on the Exchange 2010 server (with a self signed cert), that is causing the connection to fail.  Is there anyway to test this without breaking outlook connections for the users that are on Exchange 2010?  Or is there any other reason that this would occur?

Thanks for any assistance.

Hi!

I have a multitenant exchange 2007 at a single server setup and I’m trying to do migration to exchange 2013. I’m testing this in my lab environment before I go the production. I’m quite far and for example the owa redirection to exchange 2007 works. Also I can connect with outlook anywhere the exchange 2013 server when the mailbox is transferred.

Problem is that the exchange 2013 proxy redirection to 2007 server isn’t working. My Outlook 2010 just keeps asking username and password. Outlooks are configured to connect with basic authentication.

I have done a lot of googling about the issue and there is a lot of discussion about it. I have tried a lot of things and I’m quite lost now.

I have tried to configure the externalclientauthenticationmethod, internalauthenticationmethod and IISauthenticationmethods with different kind of setups but can’t get it to work. Also tried to change the internal and external hostnames.

My outlook anywhere setup at 2007 server is:

RunspaceId                        : 714f0d1a-c0f0-4694-aefe-8cf6218521ea

ServerName                        : EXCHANGE07

SSLOffloading                     : False

ExternalHostname                  : exchange07.xxx.fi

InternalHostname                  : legacy.xxx.fi

ExternalClientAuthenticationMethod : Basic

InternalClientAuthenticationMethod : Ntlm

IISAuthenticationMethods          : {Basic, Ntlm}

XropUrl                           :

ExternalClientsRequireSsl         : True

InternalClientsRequireSsl         : True

MetabasePath                      : IIS://wcn-exchange07.welcomnet.fi/W3SVC/1/ROOT/Rpc

Path                              : C:\WINDOWS\System32\RpcProxy

ExtendedProtectionTokenChecking   : None

ExtendedProtectionFlags           : {}

ExtendedProtectionSPNList         : {}

AdminDisplayVersion               : Version 8.3 (Build 83.6)

Server                            : WCN-EXCHANGE07

AdminDisplayName                  :

ExchangeVersion                   : 0.1 (8.0.535.0)

Name                              : Rpc (Default Web Site)

ObjectClass                       : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}

WhenChanged                       : 14.5.2014 20:56:18

WhenCreated                       : 14.10.2008 12:33:07

WhenChangedUTC                    : 14.5.2014 17:56:18

WhenCreatedUTC                    : 14.10.2008 9:33:07

Exchange 2013 outook anywhere setup:

RunspaceId                        : 714f0d1a-c0f0-4694-aefe-8cf6218521ea

ServerName                        : EXCHANGE13

SSLOffloading                     : False

ExternalHostname                  : exchange07.xxx.fi

InternalHostname                  : exchange07.xxx.fi

ExternalClientAuthenticationMethod : Basic

InternalClientAuthenticationMethod : Ntlm

IISAuthenticationMethods          : {Basic, Ntlm}

XropUrl                           :

ExternalClientsRequireSsl         : True

InternalClientsRequireSsl         : True

MetabasePath                      : IIS://exchange13.xxx.fi/W3SVC/1/ROOT/Rpc

Path                              : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc

ExtendedProtectionTokenChecking   : None

ExtendedProtectionFlags           : {}

ExtendedProtectionSPNList         : {}

AdminDisplayVersion               : Version 15.0 (Build 847.32)

Server                            : WCN-EXCHANGE13

AdminDisplayName                  :

ExchangeVersion                   : 0.20 (15.0.0.0)

Name                              : Rpc (Default Web Site)

ObjectClass                       : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}

WhenChanged                       : 14.5.2014 20:55:56

WhenCreated                       : 2.4.2014 0:57:19

WhenChangedUTC                    : 14.5.2014 17:55:56

WhenCreatedUTC                    : 1.4.2014 21:57:19

Any help would be appreciated.

Vincent Sprague

trying to figure out why POP3 won't connect.  We want to use SSL.

Results of tests and the settings are shown below.  I have tried Logintype 1,2 and 3 in the pop-settings and all give same result.

Test-PopConnectivity <cas-server> |fl
RunspaceId                  : 3eeb6ac7-f1db-41d6-bf18-65e12a853b51
LocalSite                   : Default-First-Site-Name
SecureAccess                : False
VirtualDirectoryName        :
Url                         :
UrlType                     : Unknown
Port                        : 995
ConnectionType              : Ssl
ClientAccessServerShortName : <cas-server>
LocalSiteShortName          : Default-First-Site-Name
ClientAccessServer          : <Cas-Server>.company.local
Scenario                    : Test POP3 Connectivity
ScenarioDescription         : Connect to server using POP3 protocol, search for the test message, and delete it along
                              with any messages that are older than 24 hours.
PerformanceCounterName      : POPConnectivity-Latency
Result                      : Failure
Error                       : POP Error: -ERR Logon failure: unknown user name or bad password.

UserName                    : extest_e32d2d1d14c04
StartTime                   : 4/22/2014 11:27:22 AM
Latency                     : 00:00:00.4090460
EventType                   : Error
LatencyInMillisecondsString :
Identity                    :
IsValid                     : True
ObjectState                 : New
********************************************************************************************************
POP-Log
"R=""-ERR Logon failure: unknown user name or bad password."";Msg=NoUserInAD"
*******************************************************************************************************
Get-PopSettings |fl

RunspaceId                        : 3eeb6ac7-f1db-41d6-bf18-65e12a853b51
Name                              : 1
ProtocolName                      : POP3
MaxCommandSize                    : 512
MessageRetrievalSortOrder         : Ascending
UnencryptedOrTLSBindings          : {[::]:110, 0.0.0.0:110}
SSLBindings                       : {[::]:995, 0.0.0.0:995}
InternalConnectionSettings        : {<Cas-Server>.company.local:995:SSL, <Cas-Server>.company.local:110:TLS}
ExternalConnectionSettings        : {}
X509CertificateName               : mail.company.com
Banner                            : The Microsoft Exchange POP3 service is ready.
LoginType                         : SecureLogin
AuthenticatedConnectionTimeout    : 00:30:00
PreAuthenticatedConnectionTimeout : 00:01:00
MaxConnections                    : 2147483647
MaxConnectionFromSingleIP         : 2147483647
MaxConnectionsPerUser             : 16
MessageRetrievalMimeFormat        : BestBodyFormat
ProxyTargetPort                   : 9955
CalendarItemRetrievalOption       : iCalendar
OwaServerUrl                      :
EnableExactRFC822Size             : False
LiveIdBasicAuthReplacement        : False
SuppressReadReceipt               : False
ProtocolLogEnabled                : True
EnforceCertificateErrors          : False
LogFileLocation                   : C:\Program Files\Microsoft\Exchange Server\V15\Logging\Pop3
LogFileRollOverSettings           : Daily
LogPerFileSizeQuota               : 0 B (0 bytes)
ExtendedProtectionPolicy          : None
EnableGSSAPIAndNTLMAuth           : True
Server                            : <Cas-Server>
AdminDisplayName                  :
ExchangeVersion                   : 0.10 (14.0.100.0)
DistinguishedName                 : CN=1,CN=POP3,CN=Protocols,CN=<Cas-server>,CN=Servers,CN=Exchange Administrative Group
                                    (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft
                                    Exchange,CN=Services,CN=Configuration,DC=<company>,DC=local
Identity                          : <Cas-server>\1
Guid                              : 25123301-9ed4-4989-83e7-85dcb9d5a90a
ObjectCategory                    : <company>.local/Configuration/Schema/ms-Exch-Protocol-Cfg-POP-Server
ObjectClass                       : {top, protocolCfg, protocolCfgPOP, protocolCfgPOPServer}
WhenChanged                       : 4/22/2014 11:24:28 AM
WhenCreated                       : 11/26/2013 8:22:55 AM
WhenChangedUTC                    : 4/22/2014 6:24:28 PM
WhenCreatedUTC                    : 11/26/2013 4:22:55 PM
OrganizationId                    :
OriginatingServer                 : DC1.<company>.local
IsValid                           : True
ObjectState                       : Unchanged

Any ideas?

We couldn't make Outlook 2013 (latest updates) to connect to our Exchange 2013-SP1 through the Internet.

Any PC inside the LAN (on the domain or outside the domain) can connect normally.

Any PC outside the LAN (WAN) cannot connect, it keep showing this error:

"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."

OWA is working fine from the WAN, smartphones (Android & Apple) are also working fine from the WAN.

Port 443 is open on the firewall.

So what we are missing!

Exchange 2013 SP1. Since last week we have the issue that some users are getting an HTTP 500 Internal Server error when they access OWA from the internet after logging on. For other users it works fine. When the users who are having problems access OWA from internally they can logon fine. OWA authentication is set to Windows Integrated.

For external access OWA is published using TMG. No errors are reported in the eventlog of TMG or the Exchange server. Any idea what might cause this? Is there a way to get some more detailed information about the HTTP error 500?

I've checked the issue with inheritance on the AD user object, but the userobjects have inheritance enabled. Also, since it's Exchange 2013 it doesn't have the Form based authentication service which also might cause this error.

Any idea?

Frank.

I am going to try to be as concise as possible with this issue.

I have an Exchange 2013 organization that is in Domain A (A is the Forest Root).  A new child domain was added recently, domain B.

DNS seems to be resolving correctly and /preparedomain:B.domain.com was ran to prepare the new child domain.

New mailboxes in domain B can log into OWA just fine, but Outlook does not auth (Login prompt appears repeatedly).

Using the Test Autodiscovery in the Outlook client, it seems to retrieve the server information fine, but if I go to the autodiscover URL and use one of my domain B user accounts, the login is rejected. A user account from domain A is accepted though.

Is there something with this new child domain that I am missing to allow Exchange to accept the login from the new child?

(this message was moved from Office forum to Exchange forum)

http://answers.microsoft.com/en-us/office/forum/office_2010-outlook/outlook-2010-send-delay-rules-1-min-but-email/a8a2a00d-4d48-4ac8-bd6b-ec0bb6f482b0

chanwingkai

Hello all!

I am using Outlook 2013 with both Exchange Online (Office 365) and with an IMAP server.  The accounts are configured to use two completely separate profiles as Outlook isn't able to handle multiple S/MIME certificates (ahem! FEATURE REQUEST!!! ahem!). LOL

I have actually been having this problem for a long time and none of the KB articles, blog posts, or 3rd party websites seem to address the issue I am experiencing.

My requirement is to send and receive encrypted e-mail from a group of external recipients.  I have valid certificates from each of the recipients and have gone through the painful process of creating individual Contacts for each recipient, then associating the certificates with the respective contacts.

For whatever reason, I am able to send encrypted e-mails to some of my Contacts without issue, but with others I am not. The results are very inconsistent despite the fact that I have all of the Contacts configured in an identical fashion.

The message I receive is probably familiar with most:

Encryption Problems

Microsoft Outlook had problems encrypting this message because the following recipients had missing or invalid certificates, or conflicting or unsupported encryption capabilities:

Username 1, Username 2, etc.

Continue will encrypt and send the message but the listed recipients may not be able to read it.

"Send Unencrypted""Continue" (ALWAYS GREYED OUT)"Cancel"

I have deleted the Contacts and re-created them, I have deleted the Auto-Complete address list for inline auto-complete, I have even tried deleting the profile and re-creating it from scratch.  I have also gone into the Certificates MMC snap-in and tried adding the certificates for the users there.  Still I receive the same error.

This happens regardless of whether the mail server is Exchange (and Publish to GAL is enabled along with custom Mail Contacts), or it is IMAP/POP3/Gmail/etc.

What is the best way to debug this issue?  There doesn't seem to be any sort of advanced logging, that I am aware of, which would allow me to see what the exact issue is.  It's very frustrating because other e-mail clients, such as Mozilla Thunderbird, work just fine with the same recipients.  But I hate Thunderbird and don't want to use it if I can avoid it.

Even Outlook 2011 for Mac OS X works just fine, but Outlook for Windows (2010 and 2013) do not.

I'm about to open a support case with Microsoft Support, but wanted to ask the Microsoft "wizards" here if there are any other options I can try to enlist to resolve the issue on my own.

Hi,

We cannot seem to set automatic reply's within outlook 2010 & 2013.  We have an exchange server 2010.  We can setup automatic reply through OWA absolutely fine.   The error that we receive is 'Your automatic reply settings cannot be displayed because the server is currently unavailable.  Try again later.

However we can setup out of office on any other office version below 2010 fine.   Any help would be appreciated thanks.  

Thanks

Tom

I have a single user that cannot send email from the Mac after migrating to Exchange 2013 on-prem. I myself am on the same Exchange server and am using a Mac with Office 2011 and am able to send/receive emails without any issues.

When the user sends an email it goes to the sent mail folder and syncs with the server and can be seen on a windows machine running any other version of Office (same in OWA). I've logged the user in on my Mac and blown away my profile and seeing the same issue. Not sure if this narrows my issue down to the Exchange server receiving the send request from a Mac or if it's some setting in Outlook on the Mac?

I do not see anything in the logs on the server and have not seen any error son the Mac.

Any thoughts as to where my issues is? 

We are seeing this error when connecting to OWA (Exchange 2013 SP1 with Claims Based Auth enabled) through Windows Server 2012 WAP configured for ADFS (v3.) Now I have seen this discussion on WAP (Here) articles and they seem to lay the blame the OWA server, which is why I am posting here.

The user sees this error: "This method or property is not supported after HttpRequest.Form, Files, InputStream, or BinaryRead has been invoked." which goes away after the browser is refreshed. This is an intermittent issue.

WAP reports this error:

Anthony Sheehy - MCP, MCITP

I have a user with Outlook 2013 connected to an 2010 Exchange Server. I have a user that is unable to edit any existing contact, getting an error: Your changes cannot be saved because you don't have permission to modify some or all of the items in this folder. Do you want to save a copy of this item in the default folder for the item?

I have checked the permissions on the mailbox folder as well as the Contacts folder. The user has "Owner" permission to these folders.

No other users report the problem, and loading the users account on another computer demonstrates the same problem.

Any ideas what I am missing?

Running Outlook 2010 & 2013 with Exchange 2013 (on premise).  The behaviour I'm trying to achieve is

1. for a user to have access to a shared mailbox,
2. have sent items go to the sent items folder of the shared mailbox, and
3. have new/reply messages from the shared mailbox show personA on behalf of sharedX.

No 1 easy enough - full access granted.  Shows up automatically or loaded as extra account in Outlook client.

No 2 not so easy/intuitive, but loading it as an extra account in Outlook seems to do the trick. Simply responding from an auto mapped mailbox puts the sent message in your personal sent items and not the shared mailbox sent items folder. If there is a smarter/more intuitive/sensible way of doing this at scale please let me know!

No 3 is where I'm getting stuck. If I remove full access and grant SendOnBehalf using EMS (http://technet.microsoft.com/en-US/library/jj150498(v=exchg.150)) I get #3 to function as required, but not with full access still granted which in turn breaks requirement #1 & #2.

Am I missing something obvious or is this a very real limitation/shortfall in the Exchange/Outlook ecosystem?  The fact that the EAC does not even cater for Send On Behalf on a shared mailbox gives me little hope that this is/was a thought through scenario for the Exchange team.

As an aside - It would be very useful if MS had a definitive guide on how to configure these 'common' scenarios - perhaps the topic for a series of blogs by the Office/Exchange server teams?

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?