Exchange 2013 - Client Access - Wrong Servername
Hi,
i have 4 exchange servers running, 2x Client Access, 2x MAilbox with DAG.
i configured the external URL on all virtual directories and outlook anywhere to cas.contoso.com
the internal url is cas01.contoso.com and cas02.contoso.com.
All Clients connect from outside the company, so the internal url doesn't matter.
When i client connects from outside, it's very slow. I saw on the firewall, that outlook is trying to connect to cas01 or cas02.contoso.com and then gives up and go to cas.contoso.com which is right.
how can i check, why outlook is trying to access the servers instead of the alias cas.contoso.com ?
cas.contoso.com points to KEMP Load balancers which distribute the load to the two Client access servers.
hi,
we have no internal traffic, all clients connects from external sources.
anyway, i changed all URL's to the external URL now, for OWA, ECP, EWS and Outlook Anywhere.
I created a new outlook profile and it still tries the internal URL first.
BTW: the internal URL is also a public IP address but firewalled POrt 443, only the cas.contoso.com IP is open on 443.
So the internal Hostnames are DNS resolvable on the internet? If so, that is not what you want to do. Make only the external Host name resolvable.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.
Well, the hole system is resolvable on the Internet, i can switch them to https://localhost/...
but in my case, i switched everything from cas01 or cas02 to cas and outlook still shows up with
cas01.contoso.com connecting....
cas.contoso.com conneted...
where does this client get cas01.contoso.com from ?!
Similar Messages
-
Exchange 2013 - Client Access Servers - Disk Space C:\ Running Low Space
Currently having an issue with both of our client access servers with exchange 2013.
The issue is that the C:\ drive will run low on disk space on one of the cas server and the other one will be fine. We have cleaned up all the logs etc to free space on the cas server that is running low on space but its not sufficient enough
as it keeps on running low on space, then what we do the free up the space is to reboot the cas server that runs low on space, and it free the space up after it has been restarted, then the other cas server starts running low on space.
has anyone seen this before?Hi,
If it is possible, I suggest re-installing Exchange Server on another path instead of C:\.
Thanks
Mavis
Mavis Huang
TechNet Community Support -
No new mail notification in Outlook - CAS Exchange RPC Client Access problem
Hi, we're facing this problem:
Users start complaining they suddenly don’t receive new mail notifications in Outlook (2010/2013) anymore
Inbox does not show the new mail either
When the user changes folders in outlook, the new mail does show in the Inbox folder
Restarting Outlook shows the new mail as well.
The same new e-mail arrives instantly (with notifications) in Owa and on mobile devices
Sometimes the new mail notification pops up after a longer period of time (from 30 seconds to 10 minutes). But more often not at all.
This issue seems to occur at random. We’ve been problem free for a week, and sometimes it comes back three times a day.
Clients running Outlook 2010, 2013 cached or online, on site and off site. So it seems server related, not client.
It was seen first around January 8th. We did not make any changes around that time that we can link to this problem.
Only one CAS server (EXCH1-RTD) shows this issue. CAS servers on other sites are ok
EXCH1-RTD has CAS and HUB transport roles. The same site has two mailbox only servers. EXCH2-RTD (mailbox server for normal mailboxes). And EXCH3-RTD (mailbox server for archive mailboxes)
No entries in the event logs that seems to be related
As the problem only occurs with Outlook clients, I suspected RPC issues. We cannot gracefully stop the “Microsoft Exchange RPC Client Access” service on EXCH1-RTD while the issue occurs. We
can only kill the process and restart the service, solving the issue instantly.
What we’ve tried until now:
Updated all Exchange servers from Exchange 2010 SP3 RU6 to RU8-v2 (server OS=W2K8R2)
Updated all Exchange servers to latest critical Windows updates
Recalculated requirements using MS Sizing tool. Upgraded EXCH1-RTD VM from 8GB and 2 vCPU (1 core/cpu) to 16GB
and 4vCPU (1 core/cpu)
Ran various perfmon counters and compared them with other Exchange servers, not finding any obvious anomalies.
Any ideas would be greatly appreciated!
RonHi Ron,
From your description, OWA works well, the issue is related to Outlook side. In your case, I recommend you use Outlook safe mode to determine whether the issue is related to add-ins. If the issue persists, you can create a new profile to check the result.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support -
Microsoft Exchange RPC Client Access will not start.
A few days ago all my outlook clients were disconnected. Looking into it and the Microsoft Exchange RPC Client Access service had died. Tried several restarts of the system but the service will not go into a running state. It always says
Starting. But it is actually terminating and restarting. In the system log get Event 7031 - "The Microsoft Exchange RPC Client Access service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be
taken in 5000 milliseconds: Restart the service." I can't find anything else on the error in any log file. Some other info not sure if this related or not. The contentIndex are corrupt and will not rebuild. Get a state of "Failed"
with an error message of "The database has been dismounted." Also at time the system is very sluggish. Mostly right after a reboot for an hour or two. Details about the system are; Running Exchange 2013 SP1 on server 2012 R2. All
roles on one machine. About 20 mailboxes. Database is about 40gig. No VM, just a normal server. plenty of diskspace, memory and CPU. The system has been running fine for about a year. Also, mobile devices and OWA work fine. Mail flow
is fine. Outlook just can't connect.
Tried restoring the databases and logs from before the problem started but that did not help.
Not sure what to try from here.
ThanksHi,
Please check whether an unavailable Public Folder database is pointed to in your Exchange 2013 mailbox database as the default public folder database setting.
If there is no legacy public folder database and you are working in a pure Exchange 2013 environment, please remove the default public folder database setting on each Exchange 2013 Mailbox database that points to the deleted public folder database object
in ADSI Edit:
1. Open ADSIEdit, Connect to the Configuration container.
2. Expand Configuration, expand CN=Configuration,DC=Domain,DC=com.
3. Expand CN=Services -> CN=Microsoft Exchange -> CN=Domain -> CN=Administrative Groups -> CN=Exchange Administrative Group -> CN=Databases.
4. In the right hand pane you will see a list of databases. Right-click the listed database object -> Properties.
5. Check whether the msExchHomePublicMDB value is set to an unavailable value. If you see reference to the old database, please clear the value.
6. Click OK.
7. Check the rest of the databases to make sure that they are not populated in the same way.
For more information about this, please refer to:
http://support2.microsoft.com/kb/2962915/en-us
Regards,
Winnie Liang
TechNet Community Support -
Exchange 2007 Client Access and Receive Connector options not available (EMC)
We have a SBS2008 server with Exchange 2007
When I open the EMC and go to Server Configuration --> Client Access, none off the options are available (greyed out). OAW, OWA, ActiveSync are working without any problems. Outlook anywhere enabled shows False,when I try to reanable it I get the following
error message:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:01
SERVERNAME
Failed
Error:
The Active Directory object for virtual directory 'IIS://SERVERNAME.domainname.local/W3SVC/3/ROOT/Rpc' on 'SERVERNAME' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create
it.
Unexpected Error
Warning:
Outlook Anywhere will be enabled on your Client Access server after a configuration period of approximately fifteen minutes. To verify that Outlook Anywhere has been enabled, check the application event log on server SERVERNAME.
Exchange Management Shell command attempted:
enable-OutlookAnywhere -Server 'SERVERNAME' -ExternalHostname 'mail.domainname.net' -DefaultAuthenticationMethod 'Basic' -SSLOffloading $false
Elapsed Time: 00:00:01
Also the receive connectors are not visible from EMC, it's just blank under receive connectors, but mails are received without any problems.
Does someone know a way to resolve this?That worked!
I created a new account and placed it into the Exchange Organization Administrators role, now I'm able to see all the options normally.
I also re-added the original account to the EOA role but I still don't see the options there. When I go to Organization Configuration I also get the following error message:
You do not have permissions to read the security descriptors on CN=servername,CN=Server......DC=domainname, DC=local. It was running command 'get-ExchangeAdministrator'
So it must be a permissions issue. The strange thing is that under Exchange Administrators I can see my account and it has the role Exchange Organization Administrators. -
Exchange 2013, clients prompting for password
Exchange 2013 SP1 on Server 2012 R2 both fully patched. Exchange 2013 is a single server will all roles installed. There is also an Exchange 2007 (fully pathed) as we are in the process of migrating the users.
Setup legay.company.com points to Exchange 2007 and mail.company.com point to Exchange 2013
Security on Exchange 2013 set to NTLM for External and Internal.
Mobile access works for user on Exchange 2013 and Exchange 2007
Client with Mailbox's on Exchange 2013 using Outlook 2010 - 2013 internally and externally getting prompted for username and password.
Clients with Mailbox's on Exchange 2007 ok.
Checked IIS, autodiscover, EWS and Kernal mode is set.
Nothing showing in the Event Logs.Hi Skynite,
I have met this issue before, I recommend you try the following method and check the result:
In this situation, you must set LmCompatibilityLevel on the client to a value of 2. To do this, follow these steps.
Click Start, click Run, type
regedit in the Open box, and then press ENTER.<u5:p></u5:p>
Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\
In the pane on the right side, double-click lmcompatibilitylevel.<u5:p></u5:p>
In the Value data box, type a value of 2 and then click
OK.<u5:p></u5:p>
Exit Registry Editor.<u5:p></u5:p>
Restart your computer.<u5:p></u5:p>
More details about this Key, please refer to the following link:
http://technet.microsoft.com/en-us/library/cc960646.aspx
Best regards,
Niko Cheng
TechNet Community Support -
EXCHANGE SERVER 2013 CLIENT ACCESS ROLE BASED QUESTION
In my environment,i have to install two CAS in two different host machines and mailbox server on a different host machine.can it be possible?if possible then please tell me the procedure how can these communicate with each other?and is this a cas array?please
help me,i am confused.
traineeYes you can always go ahead and do this . Having 2 cas and one mailbox is not going to harm in anyways but one cas can handle all the connections as far as you have less number of users and you can have equal number of mailbox servers as well so that
you can manage the DB's btw 2 mbx servers by setting up DAG.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That
will encourage me - and others - to take time out to help you.
Regards,
Sathish -
OWA Exchange 2013: Something went wrong error
Getting this error on event log for owa. when we log in to owa, error shows :"something went wrong" 500
tried to recreated owa virtua directories and webconfig file but same issue, please help.
Event code: 3008
Event message: A configuration error has occurred.
Event time: 15/9/2014 11:05:36 PM
Event time (UTC): 15/9/2014 3:05:36 PM
Event ID: ec79c7b2c1ef4b95adbb445c80939fc4
Event sequence: 1
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2/ROOT/owa-45-130552671349946251
Trust level: Full
Application Virtual Path: /owa
Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\
Machine name: LBVSMX01
Process information:
Process ID: 17484
Process name: w3wp.exe
Account name: NT AUTHORITY\SYSTEM
Exception information:
Exception type: ConfigurationErrorsException
Exception message: Could not load file or assembly 'Microsoft.Exchange.Flighting, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\Program Files\Microsoft\Exchange
Server\V15\ClientAccess\Owa\web.config line 117)
at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
at System.Web.Configuration.AssemblyInfo.get_AssemblyInternal()
at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)
at System.Web.Compilation.BuildManager.ExecutePreAppStart()
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
Could not load file or assembly 'Microsoft.Exchange.Flighting, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection,
Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection,
Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
Request information:
Request URL: https://localhost:444/owa/exhealth.check
Request path: /owa/exhealth.check
User host address: ::1
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\SYSTEM
Thread information:
Thread ID: 42
Thread account name: NT AUTHORITY\SYSTEM
Is impersonating: False
Stack trace: at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
at System.Web.Configuration.AssemblyInfo.get_AssemblyInternal()
at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)
at System.Web.Compilation.BuildManager.ExecutePreAppStart()
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
Custom event details:
no they are not shared mailboxes.
here are the logs.
Not sure if this will make any difference, but there are 2 domains on exchange one is mail.domain1.com and another is webmail.domain.com
we have added another owa virtual directory for the second domain when we were having issues but i think since we are having a problem on the first domain owa, the second one will have the same.
just wondering why ecp can still work when owa doesnt. outlook clients can connect and so are phones.
#Software: Microsoft Internet Information Services 8.5
#Version: 1.0
#Date: 2014-09-15 10:10:56
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
2014-09-15 10:10:56 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 1531
2014-09-15 10:10:56 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:11:02 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.70 Microsoft+BITS/7.5 - 404 0 2 249
2014-09-15 10:11:15 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 62
2014-09-15 10:11:15 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
2014-09-15 10:11:15 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
2014-09-15 10:11:15 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 0
2014-09-15 10:11:26 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 14
2014-09-15 10:11:26 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
2014-09-15 10:11:26 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
2014-09-15 10:11:26 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 0
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.70 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.70 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.70 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.70 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
2014-09-15 10:11:51 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:11:51 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.80 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.80 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.80 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.80 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:53 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.84 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:53 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.84 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:53 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.84 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:53 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.84 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:12:31 192.168.1.44 GET /owa &ActID=d0e541bb-2726-473a-9891-74afd643bd53&CorrelationID=<empty> 443 - 192.168.1.17 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+rv:30.0)+Gecko/20100101+Firefox/30.0 - 401 2 5 22905
2014-09-15 10:13:08 192.168.1.44 GET /ecp/ - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 400 0 0 10240
2014-09-15 10:13:28 192.168.1.44 POST /Microsoft-Server-ActiveSync User=andrew.solis2&DeviceId=ApplC38LTUR3FRC5&DeviceType=iPhone&Cmd=Ping 443 - 172.16.0.33 Apple-iPhone6C2/1102.55400001 - 404 0 2 0
2014-09-15 10:13:31 192.168.1.44 GET /ecp/ - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 400 0 0 15
2014-09-15 10:13:38 192.168.1.44 GET /ecp/ - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 400 0 0 15
2014-09-15 10:13:40 192.168.1.44 GET /ecp/ - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 400 0 0 15
2014-09-15 10:13:40 192.168.1.44 GET /ecp/15.0.995.28/themes/default/clear1x1.gif - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https://webmail.domain.com.sg/ecp/ 400 0 0 78
2014-09-15 10:13:40 192.168.1.44 GET /ecp/15.0.995.28/themes/default/main_default.css - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https://webmail.domain.com.sg/ecp/ 400 0 0 109
2014-09-15 10:15:51 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.76 Microsoft+BITS/7.5 - 404 0 2 218
2014-09-15 10:15:55 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:15:55 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:15:55 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:15:55 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
2014-09-15 10:16:26 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.70 Microsoft+BITS/7.5 - 404 0 2 203
2014-09-15 10:16:44 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.70 Microsoft+BITS/7.5 - 404 0 2 218
2014-09-15 10:16:56 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:16:56 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:17:07 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.70 Microsoft+BITS/7.5 - 404 0 2 218
2014-09-15 10:17:38 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.97 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6425;+Pro) - 404 0 2 0
2014-09-15 10:17:38 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.97 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6425;+Pro) - 404 0 2 0
2014-09-15 10:18:48 192.168.1.44 GET /owa &ActID=5c208db7-3a44-43d0-b5d8-24f107542a81&CorrelationID=<empty> 443 - 192.168.1.44 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 401 2 5 0
2014-09-15 10:20:51 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:20:51 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:20:52 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 31
2014-09-15 10:20:52 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
2014-09-15 10:20:52 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
2014-09-15 10:20:52 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 0
2014-09-15 10:21:19 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.107 Microsoft+BITS/7.5 - 404 0 2 218
2014-09-15 10:25:04 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.190 Microsoft+BITS/7.5 - 404 0 2 218
2014-09-15 10:25:22 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.190 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:25:22 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.190 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:25:22 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.190 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
2014-09-15 10:25:22 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.190 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:25:40 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.190 Microsoft+BITS/7.5 - 404 0 2 203
2014-09-15 10:25:54 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 0
2014-09-15 10:25:54 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:27:16 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.65 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6213;+Pro) - 404 0 2 15
2014-09-15 10:27:22 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.65 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6213;+Pro) - 404 0 2 15
2014-09-15 10:27:25 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.65 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6213;+Pro) - 404 0 2 15
2014-09-15 10:28:22 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.81 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.6023;+Pro) - 404 0 2 15
2014-09-15 10:28:41 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.81 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.6023;+Pro) - 404 0 2 15
2014-09-15 10:29:20 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.107 Microsoft+BITS/7.5 - 404 0 2 203
2014-09-15 10:29:45 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.107 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:29:45 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.107 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:29:45 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.107 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:29:45 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.107 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
2014-09-15 10:31:40 192.168.1.44 GET /owa/ &ActID=cdc5aa77-7e17-4a56-83ed-2e7047c12c5b&CorrelationID=<empty> 443 - 172.17.0.198 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/37.0.2062.120+Safari/537.36
https://webmail.domain.com.sg/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fwebmail.domain.com.sg%2fowa 401 2 5 16
2014-09-15 10:32:00 192.168.1.44 GET / - 80 - 172.17.0.198 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/37.0.2062.120+Safari/537.36 - 200 0 0 31
2014-09-15 10:32:00 192.168.1.44 GET /iis-85.png - 80 - 172.17.0.198 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/37.0.2062.120+Safari/537.36 http://webmail.domain.com/ 200 0 0 265 -
Exchange 2013 - ECP shows wrong public folder permissions
Hi everybody,
I just migrated from Exchange 2007 to 2013 SP1 CU7 and we have an issue with the public folder permissions in ECP. ECP doest not show the correct permissions, here an example:
Get-PublicFolder "\Folder" | Get-PublicFolderClientPermission | ft
FolderName User AccessRights
Folder Default {Author}
Folder Anonymous {None}
Folder Administrator {Owner}
Thank you very much and best regards,
SebastianHi,
Based on your description, the public folder permissions you get using command aren't the same with that you view from EAC.
Please check if you can change the wrong permissions to right in EAC.
If you have multiple public folder mailbox, please move affected public folders to another public folder mailbox and move back to check result.
And if you have multiple DCs, please make sure there is no replication issue between DCs or you can force DC replication and then to check result.
Best regards,
Belinda Ma
TechNet Community Support -
Exchange 2013 DAG / client access
Hello
I'm in the planning of a new Exchange 2013 infrastructure. The infrastructure will be located in a datacenter and should host about 1000 mailboxes. I have read many whitepapers and tutorials, but some things are still unclear to me.
- Microsoft suggests multi-role servers for this amount of users because client access is no more than a reverse proxy in EX2013. Is this correct? I've read that one users with 200 mails/day needs 8.5 MCycles with only DB and 10.63 MCycles with DB and CAS
on the same server. So I plan to start with 2 multi-role servers in a DAG. What's your oppinion on this?
- Client connections: I assume the clients connect to the cluster IP of the DAG. How do they get directed to the server on which their database is online? Does each server need to have the cluster IP and a public IP to which the clients connect?
- SMTP: As I understand the documentation, mails are sent from the server which the user is active on. (Which makes sense for high availability.) What is best practice regarding the protocol logs? Do the support employees need to search in the files on 2
servers?
Thank you very much for your input!Hi
I would use the firewall for load balancing unless there is a technical reason why this is not possible. NLB is not recommended as it is not service aware - you cannot configure a probe to test OWA is working for example - so if you already have something
better that would be my choice.
In the choice between IIS ARR and NLB or CAS and NLB I would go for IIS ARR as this reduces you license costs, but neither of these is better than the appliance/firewall option.
I've never used NLB for load balancing other than on TMGs so I cannot say what the performance is like behind a firewall, in theory your assumption would be correct.
The load balancer doesn't make this decision it just spreads the load between the active servers, the CAS role connects the use session to the correct mailbox server:
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Steve -
Exchange 2013 - Prevent Outlook Clients From Connecting To A CAS Server In A Different AD Site
Hi all,
I could really do with your help!
We have 3 physical sites, A, B & C, with sites A & B having a really fast low latency links between them, so from an AD point of view they are 1 site. Site C has links to both sites A & B, but the link is a lot slower.
We have an exchange design with 3 servers (one located at each physical site) that will form a DAG spread over the 3 physical sites. Ideally we will separate the CAS and mailbox server roles out and have them controlled by a hardware load balancer,
however we can have both roles on the same server if required.
What we want, is to prevent is a situation where an outlook client in site C connects to a CAS server in site A/B with the mail being hosted on a mailbox server in site C therefore traversing the network twice to get its mail.
From doing the Microsoft training course, my understanding is that in Exchange 2013, the CAS server only proxy's the request on to the mailbox server and does not redirect the request to the CAS server in the site where the mailbox server resides.
I have seen information online stating that a single namespace is the way to go as long as your site links/network bandwidth is good, but nothing to help with our scenario.
Has anyone else come across this situation and how did you get round it?
Thanks in advance :)Hi Johnson,
Based on my knowledge, Outlook Client will connect to the CAS server which in local first.
Please check whether the CAS server that in site C is healthy.
If the CAS server in site C is healthy, please disable the CAS Load Balance for testing.
Also found a useful blog for your reference:
Exchange 2013 Client Access Server Role
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support -
Exchange 2013 user cann't access exchange 2013 public folder
Hi, during the coexistence exchange 2007 and exchange 2013, outlook is unable to access public folder of exchange 2007 from exchange 2013, I've install CU2 for exchange 2013 and also set authentication to Ntlm, but also failed. please help to look into this
problem, thanks.
belows are information about outlook anywhere in our exchange.
exchange 2007：(primary site)shmail04,shmail05,shmail06; (DR site)drpmail05,drpmail06
exchange 2013：(primary site)shcas01,shcas02; (DR site)wxcas01
Identity : SHCAS01\Rpc (Default Web Site)
InternalHostname : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : True
ExternalHostname : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : SHCAS02\Rpc (Default Web Site)
InternalHostname : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : True
ExternalHostname : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : WXCAS01\Rpc (Default Web Site)
InternalHostname : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : True
ExternalHostname : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : SHMAIL04\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : SHMAIL05\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : SHMAIL06\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : DRPMAIL05\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : DRPMAIL06\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}Hi,
I have found an article said that we need to set the external host name the same. See more details in the following link:
http://blogs.technet.com/b/mspfe/archive/2013/10/21/upgrading-to-on-premises-exchange-server-2013.aspx
To allow your Exchange 2013 Client Access server to redirect connections to your Exchange 2007 servers, you must enable and configure
Outlook Anywhere on all of the Exchange 2007 servers in your organization. If some Exchange 2007 servers in your organization are already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange 2013.
The following configuration is set on each Exchange 2007 server:
The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
Sent By
Silver -
Exchange 2007 migrate to Exchange 2013
Dear MS Support,
I did migrate Exchange 2007 to Exchange 2013
The install complete, the exchange 2007 and 2013 can work together successful
DAG has created and work fine
Below is capture on exchange group after migrate
The exchange 2007 work fine with outlook anywhere, all the users can connected and send and receive mail in 5 year
The cerificate enroll with
Alternative Names: mail.biendongpoc.vn
The autodiscover on exchange 2007:
[PS] C:\Windows\system32>Get-ClientAccessServer | ft Identity,*uri* -AutoSize
Creating a new session for implicit remoting of "Get-ClientAccessServer" command...
Identity AutoDiscoverServiceInternalUri
BDPOC-SERVER1 https://mail.biendongpoc.vn/Autodiscover/Autodiscover.xml
I have created new certificate for Two exchange 2013
The certificate enroll with
Alternative Names: cas.biendongpoc.vn
I have create cname cas point to dag on DNS server
I have create A record autodiscover.biendongpoc.vn point to IP of dag.biendongpoc.vn
I did migrate mailbox from exchange 2007 to exchange 2013, the migrate successful , the outlook can
connected to Exchange 2013 and working perfectly
Our problem, the account exchange 2007 work not stable ,
sometime it connect to mail.abc.com, sometime it connect to cas.abc.com
If the outlook connect to cas.biendongpoc.vn, the request put password and i can't connect to exchange 2007, if outlook connect to mail.biendongpoc.vn i can connect
It is not stable for current exchange 2007
Anyone who can help me ?
ThanksHi
huynhtrongnhatminh,
I suggest you please go through this article.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Please check this for step by step guide.
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Please point your autodiscover and commonname to Exchange2013 CAS
Please configure your URLs. There is no CAS array in Exchange2013 but the concept of single name space remains.
You need to have an A record (e.g. legacy.domain.com) in yout external DNS and add that name (legacy.domain.com) in your certificate for exchange 2007 users to have access externally.
Configure your commonname URLs in Exchange2013. Point commonname and autodiscover to exchange2013 in both external and internal DNS servers
Configure URLshttp://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
No CASARRAY in 2013http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Please configure splitdns or pinpoint DNS in your internal DNS server if not configured
http://exchange.sembee.mobi/network/split-dns.asp
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. -
Exchange 2013 user cannot mail 2010 user
Hello All, I am migrating from 2010 to 2013. The Exchange Server Deployment Assistant is proving very helpful thus far. I created a mailbox in 2013 and attempted to email a 2010 user. No luck - the email gets stuck in the queue "Last Error: 400 4.4.7
Message delayed". I can see that it is attempting to send the email to the correct database in 2010 but that is the extent of my troubleshooting knowledge.
I have yet to complete the step "Enable and Configure Outlook Anywhere" which states: "To allow your Exchange 2013 Client Access server to proxy connections to your Exchange 2010 servers, you must enable and configure Outlook Anywhere
on all of the Exchange 2010 servers in your organization." - I haven't yet done this because I didn't want anything destructive to happen to the current 2010 server, but perhaps to enable a 2013 user to send to a 2010 user this step needs to be completed
- thoughts? Btw, 2010 can successfully email a 2013 user. Is it a particular receive connector that I need to modify?
Cheers, db.Hi Dennis,
if you go to your Ex 2010 Server, please install Telnet-Client ; you can do this from Powershell using "install-windows-Feature telnet-client".
1. run a Powershell or CMD
2. telnet exchange2013server 25
Does it connect using the Exchange 2013 CAS / Transport Server Name?
If no, please check
1. is there any anti Virus / Firewall Software blocking the Connection?
2. is there any Firewall on the Network blocking the SMTP Connection?
3. does your receive connector include the subnet of your Exchange 2013 CAS server?
If you cannot connect verify please the remote IP range includes your new servers , check it running
Get-ReceiveConnector | fl name,binding,remoteipranges
from Powershell. If required, use set-receiveconnector to Change it.
http://technet.microsoft.com/de-de/library/bb125140(v=exchg.150).aspx
Regards,
Martin -
Unable to connect to local Exchange 2013 server when opening Exchange Management shell
Hi Everyone
Yesterday evenything was working fine, and then this morning, I`m unable to establish a connection with the Exchange shell. I receive the following errors. Any help is appreciated.
Welcome to the Exchange Management Shell!
Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help *<string>*
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Show quick reference guide: QuickRef
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List
Tip of the day #55:
Want to view the mounted status of all mailbox databases? Type:
Get-MailboxDatabase -Status | Format-Table Name, Server, Mounted
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH01.BLCLAB.CA.
New-PSSession : [c-exch01.blclab.ca] Connecting to remote server c-exch01.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH01.BLCLAB.CA.
New-PSSession : [c-exch01.blclab.ca] Connecting to remote server c-exch01.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
VERBOSE: Connecting to .
New-PSSession : Cannot bind parameter 'ConnectionUri'. Cannot convert value
"http:///powershell?serializationLevel=Full;ExchClientVer=15.0.516.32;clientApplication=ManagementShell;TargetServer="
to type "System.Uri". Error: "Invalid URI: The hostname could not be parsed."
At line:1 char:30
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [New-PSSession], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.NewPSSessionCommand
[PS] C:\Windows\system32>
Ernie Prescott
Updated information.
I can succussfully connect to the exchange powershell from a remote computer, using this method.
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri
http://<FQDN of Exchange 2013 Client Access server>/PowerShell/ -Authentication Kerberos
Import-PSSession $Session
So the problem is localised on the server.
RegardsHi
Try the steps for Error 1 on this link
http://www.petenetlive.com/KB/Article/0000477.htm
Hope it will help
Cheers
If you have any feedback on our support, please click
here
Zi Feng
TechNet Community Support
Maybe you are looking for
-
Not a computer person but I'm wanting to get photoshop for my Chromebook and need to know what to buy?
-
Compatible USB enclosure for hard disk from a 15-inch Aluminum Powerbook
My old Powerbook finally bit the dust, so I dismantled it and removed the hard disk. I want to get an enclosure to use it as a USB drive, but do not know what size or type of enclosure to purchase. I tried to guess, and ended up buying: Connectland C
-
<p>Maybe this is more simple than I am making it, but I am tryingto load a level 0 file into my ASO app. I get to messagesonce the data load happens. The first is:</p><p> </p><p>SourceTYPE SourceFile Opera
-
My MacPro has been behaving strangely... 1) on start up it gives me the blank grey screen (before the grey screen with the apple logo) for some 30-60 seconds... normally this stage of start up would only take 5-10 secs. 2) I've been re-experiencing t
-
Why doesn't firefox use Active X Controls
I need to have Active X Control to access my banking process. I have this on IE but prefer to use Firefox, how can I make Active X Control work on Firefox