Outlook Connectivity Problem on 2003 Term Server - Exchange 2013

I am working on deploying a new 2013 Exchange server. The Exchange is installed on a 2012 Server OS. I have three windows terminal servers (or remote desktop services) at three separate locations that have users working on them via thin-client - (RDP). The
users run Outlook 2010 from the three servers. Two of the terminal servers are Windows 2008 R2 and one is 2003 R2 Standard. I am able to get the Outlook clients to connect to Exchange from the two 2008 servers but the Outlook clients on the 2003 server are
so far unable to connect to the Exchange server.
When I try to add the mail profile from the control panel - signed on as each user - it auto detects the user profile and looks like it connects but then it prompts for a password. I can try to input the password but it will not accept it. Ultimately it
fails with a message indicating Outlook cannot log on etc., etc.
These three servers are at three different locations but connect back to the location where the Exchange server resides via MPLS. Connectivity between locations is solid.
Odd thing is I have an old 2003 server at the same location where the Exchange box is and I fired it up and tried to connect an Outlook client from it and it does not work either.
Does anyone know of any documented problems with connecting to 2013 Exchange from a 2003 server OS? Or, conversely, has anyone successfully deployed Exchange to Outlook clients on a 2003 server?

Hi there,
What version Outlook is install on the problematic Windows server 2003? Note that Outlook 2007 SP3 with July 2012 Cumulative Update or higher version can be supported; other earlier version is NOT supported.
Refer to:
http://blogs.technet.com/b/jribeiro/archive/2012/09/25/exchange-2013-preview-supported-outlook-clients.aspx
Besides, is the certificate installed on Exchange 2013 trusted by the problematic Windows 2003 server? Please test the proxy url from server 2003 and also run the online test from
https://www.testexchangeconnectivity.com/
Hope it is helpful.
Fiona Liao
TechNet Community Support

Similar Messages

Connectivity problem with MS BizTalk Server 2010

Hi colleagues,
I have a connectivity problem between MS BizTalk Server 2010 and SAP.
There are two virtual machines (VMs on VMWare), the first one is SAP ERP6 Ehp6 (IDES), and second one is MS BizTalk Server 2010 (BT). On BT side I have deployed a package which sends ORDERS05 document to SAP and has to receive a reverse call. The bottom line is that SAP can receive a call from BT but cannot send a reverse call. Gateway monotor shows the connection:
In the trace file I can't see anything suspicious:
trc file: "dev_rd", trc level: 1, release: "721"
Tue Apr 01 20:14:28 2014
***LOG S00=> GwInitReader, gateway started ( 5060) [gwxxrd.c     1759]
systemid   562 (PC with Windows NT)
relno      7210
patchlevel 0
patchno    136
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
pid        5060
gateway runs with dp version 138000(ext=120000) (@(#) DPLIB-INT-VERSION-138000-UC)
gateway (version=721.2013.09.02)
gw/reg_no_conn_info = 1
gw/local_addr : 0.0.0.0
gw/sim_mode : set to 0
***LOG S1I=> GwSetSimMode, Simulation Mode deactivated () [gwxxprf.c    4020]
* SWITCH TRC-RESOLUTION from 1 TO 1
CCMS: initialize CCMS Monitoring for ABAP instance with J2EE addin.
CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
Tue Apr 01 20:14:29 2014
Bind service sapgw00 (socket) to port 3300
GwIInitSecInfo: secinfo version = 2
GwIRegInitRegInfo: reginfo version = 2
Tue Apr 01 20:14:30 2014
GwPrintMyHostAddr: my host addresses are :
1 : [192.168.1.127] WIN2008R2 (HOSTNAME)
2 : [127.0.0.1] WIN2008R2 (LOCALHOST)
Full qualified hostname = WIN2008R2
DpSysAdmExtCreate: ABAP is active
DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
DpIPCInit2: read dp-profile-values from sys_adm_ext
DpShMCreate: sizeof(wp_adm) 42864 (2256)
DpShMCreate: sizeof(tm_adm) 5517056 (27448)
DpShMCreate: sizeof(wp_ca_adm) 64000 (64)
DpShMCreate: sizeof(appc_ca_adm) 64000 (64)
DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1384064/1384080
DpShMCreate: sizeof(comm_adm) 1384080 (2744)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (296)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (80)
DpShMCreate: sizeof(vmc_adm) 0 (2160)
DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: sizeof(j2ee_adm) 3952
DpShMCreate: SHM_DP_ADM_KEY (addr: 0000000011A40050, size: 7174832)
DpShMCreate: allocated sys_adm at 0000000011A40060
DpShMCreate: allocated wp_adm_list at 0000000011A430B0
DpShMCreate: allocated wp_adm at 0000000011A432A0
DpShMCreate: allocated tm_adm_list at 0000000011A4DA20
DpShMCreate: allocated tm_adm at 0000000011A4DA70
DpShMCreate: allocated appc_ca_adm at 0000000011FA0390
DpShMCreate: allocated comm_adm at 0000000011FAFDA0
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 0000000012101C40
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated gw_adm at 0000000012101CF0
DpShMCreate: allocated j2ee_adm at 0000000012101D30
DpShMCreate: allocated ca_info at 0000000012102CB0
DpCommAttachTable: attached comm table (header=0000000011FAFDA0/ft=0000000011FAFDB0)
MtxInit: -2 0 0
DpRqQInit: use protect_queue / slots_per_queue 0 / 2001 from sys_adm
Tue Apr 01 20:14:45 2014
GwDpInit: attached to gw_adm at 0000000012101CF0
Tue Apr 01 20:16:21 2014
Prxy Trace = 0

Hi Deepak,
Thanks for the answer, but this is not the case I'm afraid. I've received an error message for BizTalk instance:
"Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDP01006GRP   IDOCTYP: ORDERS05    Release: 620   CIMTYP: . Ensure that your message xml validates against the operation schema.
Don't really understood what does it want from me...

Edge Transport Server - Exchange 2013 coexistence Exchange 2007

Hi Exchange-Gurus,
We have one Exchange Org.
sub AD Domain1: A.domain.com (with Exchange 2007 SP3 R10)
sub AD Domain2: B.domain.com (with Exchange 2013 CU6); DMZ contains Exchange Transport Server - Exchange 2013
Is it possible to install within the DMZ of AD Domain1 a Edge Transport Server - Exchange 2013?
Thanks.
Guitarman

Hi Guitar,
Thank you for your question.
Is it possible to install within the DMZ of AD Domain1
an Edge Transport Server - Exchange 2013?
A: Yes, we could create an Exchange 2013 Edge server on the DMZ of AD domain1.
Notice: Before we create an EdgeSync Subscription between an Exchange 2007 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, we need to install Exchange 2007 SP3
Update Rollup 13 or later on the Exchange 2007 Hub Transport server.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Problem with Mavericks Mail and Exchange 2013

Hello,
I have just updated to Mavericks a few days ago. Now I have a strange problem.
The setup with Exchange 2013 works fine ... so I can send&receive mails.
The problem: I only get new mails. All (few thausand) mails stored on the Exchange account are not synced to mail?!
Maybe anyone has an idea how to solve this ...
Thanks,
Marc

Some problems with Exchange mail have been solved by disabling Autodiscovery. If that doesn't work, see below.
Back up all data. Delete the Exchange account from the Internet Accounts preference pane and add it back. If there's still no improvement, continue.
Quit Mail. Force quit if necessary.
Back up all data. That means you know you can restore the Mail database, no matter what happens.
Triple-click anywhere in the line below on this page to select it:
~/Library/Mail/V2/MailData
Copy the selected text to the Clipboard by pressing the key combination command-C. In the Finder, select
Go ▹ Go to Folder
from the menu bar. Paste into the box that opens (command-V), then press return.
A folder window will open. Inside it there should be files with names as follows:
Envelope Index
ExternalUpdates.storedata
Move those files to the Desktop, leaving the window open. Other files in the folder may have longer names that begin as above. Move those files, if any, to the Trash.
Log out and log back in. Relaunch Mail. It should prompt you to re-import your messages. You may get a warning that the index is damaged and that Mail has to quit. Click OK.
Test. If Mail now works as expected, you can delete the files you moved to the Desktop. Otherwise, post your results.

Exchange 2013 Office 365 Hybrid Cloud On-Premise Outlook Connection Problem

Hi Everyone,
We are required to migrate FROM the cloud TO an on-premise Exchange 2013 server. We set up a trial of Office365 and linked our test domain to that account. The test domain mimics our current domain, but ends in .net instead of .org.
We set up a test Exchange 2013 server with a few database servers. Internally, we can connect without issue (Outlook). We mapped our test CAS to face the Internet, and can access what we need without issue. We also set up the Hybrid
configuration on both the Exchange 2013 and Office365 servers. We have validated that DirSync works, and migration can occur up to the cloud and back down to the on-premise server.
Now, here is the issue:
We have our DNS records still pointing to Office365, so when we add an Office365 mailbox to Outlook (internal to the network or outside the network) we see absolutely no issues. We migrated a mailbox today to our on-premise server, but upon doing so,
can no longer connect to, or add, that mailbox to Outlook. When we put this integration in to effect for production, we want to be able to migrate mailboxes on-premise from the cloud, and we want to make sure users can still access their mailboxes. This
also goes for distribution groups, conference rooms, etc.
I see that most suggestions say to change your DNS record to point to the on-premise Exchange server, which is great, but after doing so Office365 accounts experience the same issue as above. We NEED to make sure that when we batch migrate, the users
DO NOT lose connectivity to their accounts. We need both Office365 accounts and Exchange on-premise accounts are accessible internally and externally. As an extra tid-bit, we HAVE configured Outlook Anywhere on Exchange 2013, but see no difference.
Any thoughts on this? Office365 and Exchange 2013 see eachother and recognize that the hybrid environment is set up good, but it appears we are missing some configurations. Currently, we have a CNAME record points our autodiscover to autodiscover.outlook.com.
Any help would be MUCH appreciated. Thanks!
Dan

Hi,
Here is an article on Move mailboxes between on-premises and Exchange Online organizations in 2013 hybrid deployments, for your reference:
http://technet.microsoft.com/en-us/library/jj906432(v=exchg.150).aspx
I want to make sure OWA works well with the moved mailbox.
To use CNAME based autodiscover method, we need to have all domain names present in a SAN certificate.
With Exchange 2013 CU1, we now have the option of adding multiple SMTP domains to Exchange Federation/Hybrid configuration and we can specify which of these domains should act the "autodiscover" domain.
To configure an SMTP domain as the autodiscover domain, you can run following command:
Set-HybridConfiguration -Domains "domain1.com, domain2.com, domain3.com", "autod:domain.com"
More details, please refer following blogs:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part11.html
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part12.html
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above links.
Thanks
Mavis Huang
TechNet Community Support

Outlook 2007-2013 doesn't connect in non-cached mode to Exchange 2013.

Hello!
I have organization Exchange 2010 + Exchange 2013 in one AD site (hybrid organization)
Mailboxes based on Exchange 2010 servers work fine. But after moving one of mailboxes to
Exchange 2013 database, Outlook doesn't connect to mailbox in
non-cached mode. If I turn on cached mode this mailbox is connecting perfectly (OAB, Folders, PublicFolders, Addresslists).
I cleaned parameter "PublicFolderDatabase" for Exchange 2013 database, but the problem didn't solve.
In CAS
RpcHttp
log:
2015-01-22T12:08:12.720Z,MBXDB13,RpcHttp,S:Stage=BeginRequest;S:AuthType=Negotiate;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?MBXDB13.DOMAIN.local:6001;S:RpcHttpUserName=DOMAIN\USER;S:ServerTarget=[email protected];S:RequestId=267b0bf2-4361-4efb-9865-7f8d664b6e00;S:ClientIp=10.10.10.111
2015-01-22T12:08:12.720Z,MBXDB13,RpcHttp,S:Stage=PostAuthorizeRequest;S:UserName=DOMAIN\MBXDB13.domain.local:6001;S:RpcHttpUserName=DOMAIN\USER;S:ServerTarget=[email protected];S:RequestId=267b0bf2-4361-4efb-9865-7f8d664b6e00;S:ClientIp=10.10.10.111
Exchange Server 2013 Cumulative Update 7 (CU7)
are installed.

Hi Allen!
Thank you for reply!
Outlook cannot connect to all mailboxes on Exchange 2013 server.
>Get-OutlookAnywhere | FL Name,*auth*,*host*Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2010.contoso.com
InternalHostname :
Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2010.contoso.com
InternalHostname :
Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2013.contoso.com
InternalHostname : cas1302.domain.local
Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2013.contoso.com
InternalHostname : cas1301.domain.local
Outlook error message:
"Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt log on to Microsoft Exchange has failed."
This error reproduced even in new profile. Repair does not help.

Server Exchange 2013 SP1 installation on Hyper-V server

Dear colleges, I seek your help with ExchangeServer 2013 installation on a Hyper-V server issue I've been having.
Getting below errors during prerequisites check of XCHG SVR installation. Installation is done on a Hyper-V server. This server is member of a domain. I have also promoted this server to a Active Directory Domain Controller. In other words there's 2 AD DC
- one is on the main server and the other on this one. The user the installation is run under has ALL required access rights. Please advise as this issue is getting on my nerves. I believe something is wrong setup on a AD DC part. Please suggest what to check
and post on the forum, so somebody can just point out what I am doing wrong.
Error:
The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container. See the Exchange setup log for more information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit:

Got the same errors when ran on the main AD DC server:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows\system32>setup /ps /iacceptexchangeserverlicenseterms
'setup' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>h:
H:\>setup /ps /iacceptexchangeserverlicenseterms
Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis FAILED
The Active Directory schema isn't up-to-date, and this user account isn't a
member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
Setup encountered a problem while validating the state of Active Directory:
Couldn't find the Enterprise Organization container. See the Exchange setup lo
g for more information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.AdInitErrorRule.aspx
The forest functional level of the current Active Directory forest is not W
indows Server 2003 native or later. To install Exchange Server 2013, the forest
functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.CannotAccessAD.aspx
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
H:\>

Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC

I wasn't prepared for this task, and it was thrown at me to do... Eyes are bleeding from planning reading and planning, would LOVE any input from you guys. First time posting, here and have heard great things about these forums. The Company
I work for obtained a new client and a network that is in a cluster at the moment, so I'm having to dig through everything and restructure..
Scenario:
Old Domain/Server: (To be decommissioned)
Server 2003 Standard SP2 (Domain: cosco.com; NETBIOS name: coscoex)
Exchange 2003 SP2 (6.5.7638.1)
Server is a domain controller and exchange server.
Migrating to:
Server 2012 R2 Datacenter (New Domain ad.cosco.com; NETBIOS name: cosco)
VM #1: Server 2012 R2 Domain Controller at 2012 R2 Functionality
VM #2: Server 2012 R2 with Exchange 2013 Standard (Not Yet Installed) Joined to ad.cosco.com domain
VM #3: Server 2012 R2 with Exchange 2010 (Not Yet Installed) joined to ad.cosco.com domain
These are probably not ideal conditions, but I have to work with what I'm given.
Host server (2012 R2) is in work group mode. Hyper V Installed with a VM of Server 2012 R2 and as a DC at a functionality level of Server 2012 R2. I had intended starting at a lower functionality level and raising
it later, but.... ya I forgot to change it. If needed I can spool up a new DC with a lower functional level.
DNS, AD and group policy is all jacked up on the 2003 DC so that doesn't matter, All user accounts are going to be created under the new domain. The concern is migrating the mailboxes from Exchange 2003 on the old domain to
Exchange 2013 on the new domain. The client is going to provide CSV of the AD accounts that are still valid (a lot of accounts are no longer used or are from people that no longer with the organization.)
I had some ideas, but I'm not sure if they will work. This is something I have never done before (Senior Engineer Quit).
My thoughts:
- Establish a two way trust relationship between the two domains.
- Create two VM's, one with Exchange 2010 and one with Exchange 2013 (They have a 2010 licence that was not used).
- Create the users on the new domain
- Use the double hop method from Exchange 2003 > Exchange 2010 > Exchange 2013
- Link Exchange accounts to the correct user accounts on the new DC.
Can this be done cleanly? Am I going about this the correct way? Any feedback would be GREATLY appreciated.
Note: We are forced to use ad.cosco.com (Obviously not the actual domain name)

Hi,
Base on my experience, your idea is feasible.
However, before getting started, you should note that Exchange 2010 (with any service pack or update rollups) is not (yet) supported to install on Windows 2012 R2. More details refer to the following link:
http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
After all the preparations complete, you can refer to the following articles to migration exchange 2003 to 2010, then to 2013:
Exchange 2003 to 2010 Cross-Forest Migration Step by Step Guide
Exchange 2010/2007 to 2013 Migration and Co-existence Guide
Best regards,
Niko Cheng
TechNet Community Support

Commigate server&exchange 2013

currently we have a communigate email server from a remote location.
we now have just installed a exchange 2013&server 2012.
I get a message about it not being a valid .ost file invalid outlook folders when installing to outlook 2010.
how can I install then both in outlook until we can move email over to exchange
I have tried creating different profiles and on different logins on different computers.
the commigate server had already been installed in outlook on pc in facility

Hello,
Do you mean the Communigate email profile coexistence with Exchange profile?
If so, I think the best place for this question is to ask here:
https://www.communigate.com/main/support/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety,
or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Does Outlook "Connection Status" Show Rollup Updates on Exchange 2010 SP3

Hi all,
I've looked for this answer everywhere, and can't seem to find it. When you CTRL right-click on the Outlook taskbar icon, and select "Connection Status", one of the pieces of information displayed is the Version number of the connected Exchange
server.
Does this build number include installed rollup updates, or does it show only the installed Service Pack. For example, if it's an Exchange 2010 SP3 server with RU6 installed, will I see 14.3.195.1
or just 14.3.123.4 (the SP3 build number)? I'm trying to use this information to troubleshoot
client issues, and it'd be helpful to quickly see if certain updates are installed on the Exchange server or not.
Thanks!

Hi,
Just as what mentioned above, connection status displays the Exchange version number.
Start Outlook and connect to the Exchange server if this isn’t done automatically already.
Hold CTRL while clicking on the Outlook icon in the Notification Area
(located in the right bottom area near the time; expand the Notification Area first if the Outlook icon does not show).
From the context menu that pops-up choose: Connection Status…
Scroll the horizontal scrollbar to the right to see the Version column.
(if the dialog is empty, then you are not connected to Exchange)
Here you’ll see a version number.
Best regards,
Belinda Ma
TechNet Community Support

Outlook connectivity and mail flow issue on Exchange 2010 3 node DAG

Hi,
I have 3 node DAG, 2 (NODE A, NODE B) in Production site and 1(NODE C) in DR site. but just 1 AD Site.
when I have the active databases on NODE B, everything works fine. no issues to report.
but when I move the databases on NODE A, outlook gets connected with trying to update folders. Furhter, emails will be in outbox and no new emails will be delivered to the users. After an hour or so emails get delivered from outbox.
Even after supplying the credentials OWA doesnt login. just tries to load.
No issues when I move the servcies on NODE C.
ANy idea what could be the issue?
Thanks,
Vinod

Hi Vinod,
According to your description, there is one-hour delay in the process of sending and receiving emails.
To check if it’s caused by Autodiscover service, we can use the tool Test Email AutoConfiguration：
1. Hold CTRL and Click the outlook Icon in the system tray and select “Test Email Auto Configuration”.
2. Deselect the “Use Guessmart” and “Secure Guessmart Authentication” and click Test.
3. Check SCP value returned
For more information, please refer to the following article:
http://blogs.technet.com/b/exchdxb/archive/2012/05/10/troublshooting-autodiscover-exchange-2007-2010.aspx
http://support.microsoft.com/kb/2663435
http://support.microsoft.com/kb/262052
If connectivity is well, the issue is mostly likely caused by the Exchange mail submission service.
We can check if the service work properly. And the issue may be not related to the Hardware Load Balancer. Because the emails are stuck in the client side.
Thanks,
Angela Shi
TechNet Community Support

Connection problems to Yahoo! Server

I'm trying to connect my iPhone mail app to my Yahoo! mail account. I've logged in through Safari, so I know I have the password correct. I am getting a "Yahoo! Server Unavailable" message when I try to authenticate using Settings > Mail. I've followed all the steps on the support pages, including rebooting my phone. Nothing works.

I have a recurring issue connecting to Yahoo mail on my I pad2.Yahoo mail is pushed to my iphone4 with no problem and my wife's yahoo account pushes to the iPad fine.
As far as I can tell the account settings are identical.
If it weren't for the hassel I'd just dump Yahoo.

Integration SAP CRM - MS Outlook, connection problem.

Hi guys!
I'd be really gratefull if you could help me.
I'm trying to integrate SAP CRM 7.0 with MS Outlook, I installed Desktop Connection for SAP CRM, PE and I made all steps from
Technical Configuration Guide but I've got an error every time when I try to log in: (I've tried a few times)
* When I installed version SP03:
* and for version SP02:
And also log screen:
Has anyone some ideas how to solve it?
Have a nice day!

hello Michael!
I was trying to re-install this application but it didn't help.
But now I`m having a different comunicate:
and of course I checked a log:
I installed this files:
I'll be very gratefull if you could help me.

Problems with cmdlets within the Exchange 2013 powershell

Hi,
i've following problem: I can't access all possible powershell cmdlets within the exchange powershell. For example following cmdlet is missing: "Get-Queue". Also we have trouble with some other cmdlets: Get-Mailbox only lists one of 30 mailboxes
and if we want to modify a mailbox identified by the logonname an error shows up that the user can't be found. Only the one listed user can be modified.
What can I do to solve this problem?
Yours
Achim

Hi Achim,
You need to be assigned appropriate permissions or roles before you can run all cmdlet. Although all parameters for this cmdlet are listed, you may not have access to some parameters if they're not included in the permissions assigned to you. For example
to run Get-Queue cmdlet - your user account must be assigned the "Organization Management" or at least "Server Management" role.
You can try this to view roles assigned to your account:
Get-ManagementRoleAssignment -RoleAssignee 'yourUserAcc' -Role "organization*" | fl role
Get-ManagementRoleAssignment -RoleAssignee 'yourUserAcc' -Role "*transport*" | fl role
Otherwise you can view and change role assignments with EAC:
In the EAC, navigate to Permissions > Admin Roles.
Select the role group you want to view the members of.
In the role group details pane, view the members in the role group details pane.
▲ Vote if Helpful / Mark if Answer
MCSE: Messaging 2013 Charter / Private Cloud / Server Infrastructure
MaximumExchange.ru

Excel Data Connection problem for posting Excel on SharePoint 2013

Hi there,
I tried to post an Excel file to a SharePoint 2013 site. The file has a column with VLOOKUP formula to look for data from another Excel file posted on the same site. However, once I open the file, it'll show the following message:
"We can't connect to '[link to file on onedrive/sharepoint]'. Please make sure you're using the correct
web address"
I don't recognize the website on this error message and there is no data linked to it. If I click OK, it'll show the following error message:
"Microsoft Excel cannot access the file '[link to file on onedrive/sharepoint]'. There are several possible reasons:
- The file name or path does not exist
- The file is being used by another program
- The workbook you are trying to save has the same name as a currently open workbook"
I tried to create another Library and post the file but it still shows me the same error message. I urgently need to fix this error as the file is viewed by several directors. Can someone help??? Thanks a lot!!

Currently, when a workbook that contains a Data Model is published to a library in Office 365, data refresh is unavailable.
However, you can use a PowerShell script to configure a workaround.
donwload this white paper for workaround:
http://technet.microsoft.com/en-us/library/jj992650.aspx
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Outlook Connectivity Problem on 2003 Term Server - Exchange 2013

Similar Messages

Maybe you are looking for