Hi guys
Our installation
2 Exchange 2010 CAS servers
2 Exchange 2010 Mailbox servers
2 Exchange 2013 CAS / Mailbox servers
Users will be migrated to 2013 soon.
Before that happens:
Is it possible to control which 2010 OWA server 2010 users accesses through the 2013 OWA?
Best regards
Klaus Ringe Nielsen
Best regards Klaus Ringe Nielsen
Hello ,
i have exchange 2010 and outlook 2010
i am facing problem ,all users received spam email in inbox not Junk mail
what to do to avoid this ?
I want when the user receives a spam I want to go to junk-email not inbox.
thanks
We have a new exchange server 2013 installed but also has exchange 2007 up.
MX records are now pointing to the new exchange server, all were working ok after DNS records were changed but after the weekend it Outlook clients and OWA keeps on disconnecting and reconnecting from exchange.
Exchange 2013 CU6
Anybody else experienced the same?
Error message I get is below:
Any one got the same issue?
It was working fine a few days ago,suddenly cannot move mailboxes.
-Tried to create another database in case it has a limit: same issue
-tried to move from GUI and shell same issue.
MigrationTransientException: The call to 'net.tcp://domain.local/Microsoft.Exchange.MailboxReplicationService.ProxyService domain.local (15.0.995.28 caps:017FFFFFCB07FFFF)' timed out.
Error details: This request operation sent to net.tcp://domain.local/Microsoft.Exchange.MailboxReplicationService.ProxyService did not receive a reply within the configured timeout (00:00:50).
The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message.
Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client. -->
The call to 'net.tcp://lnp-exch2013.loopartners.local/Microsoft.Exchange.MailboxReplicationService.ProxyService domain.local (15.0.995.28 caps:017FFFFFCB07FFFF)' timed out. Error details:
Hello,
I have an Exchange 2013 deployment and a LAN/WAN setup, we have many small remote WAN linked offices that can resolve to the Exchange Server's internal IP.
Outlook clients in remote WAN offices work fine as long as the link is UP since the Split Brain DNS for Exchange will resolve the internal clients to the internal IP of the Exchange server, Outlook connects up without issues.
However, in the event of loosing connection to our remote sites, they will no longer be able to resolve to the internal Exchange IP, but they still have a backup public internet that they can use. So should the inter-office connectivity fail we have it setup so clients in remote offices can still browse the internet, etc.
However, their Outlook fails to connect because it has a cached DNS record for our Split Brain Exchange DNS setup and tries to resolve it to its internal IP, instead of refreshing the cache and grabbing the public IP of the Exchange server since now they would be resolving it over the public internet.
Is there anything I can do with my existing configuration to allow the client to pick up the public IP of the Split DNS setup when our inter-office connection is down and the client is no longer able to use the internal IP they have cached for Exchange?
I guess I could lower the TTL on the DNS record to something like 1 minute so it does not cache the DNS record / IP for long? Is this the best approach?
After We migrated the Exchange from 2010 to 2013 any shared mailbox has been migrated is showing the inbox and all the subfolders from the user's mailbox in Outlook, instead of the shared mailbox content.
note: if we create new shared mailbox it works fine without any issue.
We have tried to removed full access permissions and re-added full access permissions, disabling AutoMapping and then added the shared mailbox manually in Outlook and that works fine but it is not a solution for us as we have 400+ shared mailbox and we cannot do it for every user have access on each shared mailbox.
any ideas.
Ayman Saleh
Would like to use Office 365 Home with SBS 2003 ? Will this work ?
Receive an error "The resource that you are trying to use is located on an unsupported version of Microsoft Exchange. Contact your e-mail administrator for assistance"
Thanks
hi Guys,
Need your expert advise.
-i can ping the servers vice versa
-i can run a command on the shell and both servers can see the mailboxes
-however, once i try to run a mailbox migration using shell, GUI or the endpoint migration it all fails.
This is the error i get from Exchange 2013
Error: MigrationTransientException: MapiExceptionRpcServerTooBusy: Unable to make connection to the server
I have tried to restart the Mailbox replication service from exch 2013, is there an equivalent in exch 2007?the mailbox migration was working a few days ago until yesterday when we had an ip conflict for one of the server..and now, i cant seem to do the mailbox move...
any help is apprceciated.
RunspaceId : 03e5b1a0-6c65-4d95-849e-f1c1848fa4ee
ServerName : EXCH2007
SSLOffloading : False
ExternalHostname : mail.domain.com.sg
InternalHostname :
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : False
MetabasePath : IIS://EXCH200.domain.local/W3SVC/1/ROOT/Rpc
Path : C:\Windows\System32\RpcProxy
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 8.3 (Build 83.6)
Server : EXCH2007
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web
Site),CN=HTTP,CN=Protocols,CN=EXCH2007,CN=Servers,CN=Exchange
Administrative
Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=First
Organization,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
Identity : EXCH2007\Rpc (Default Web Site)
Guid : 87be5b4b-5044-44ce-86ea-583538f13ca7
ObjectCategory : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 9/9/2014 6:31:53 AM
WhenCreated : 3/7/2011 4:02:48 AM
WhenChangedUTC : 8/9/2014 10:31:53 PM
WhenCreatedUTC : 2/7/2011 8:02:48 PM
OrganizationId :
OriginatingServer : AD.domain.local
IsValid : True
ObjectState : Changed
RunspaceId : 03e5b1a0-6c65-4d95-849e-f1c1848fa4ee
ServerName : EXCH2013
SSLOffloading : True
ExternalHostname : mail.domain.com
InternalHostname : exch2013.domain.local
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : True
MetabasePath : IIS://EXCH2013.domain.local/W3SVC/1/ROOT/Rpc
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 995.29)
Server : EXCH2013
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web
Site),CN=HTTP,CN=Protocols,CN=EXCH2013,CN=Servers,CN=Exchange
Administrative
Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=First
Organization,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
Identity : EXCH2013\Rpc (Default Web Site)
Guid : c8d04685-0f39-4985-9754-d6c5c4aa47b3
ObjectCategory : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 9/9/2014 6:32:00 AM
WhenCreated : 14/8/2014 4:10:08 PM
WhenChangedUTC : 8/9/2014 10:32:00 PM
WhenCreatedUTC : 14/8/2014 8:10:08 AM
OrganizationId :
OriginatingServer : domain.local
IsValid : True
ObjectState : Changed
[PS] C:\Windows\system32>
Can someone confirm that this has been broken in SP1 or do I have a misconfiguration on my servers?
Thank you
Daniel
Hi,
we are running a Server 2008 R2 as a Terminal Server with Outlook 2007 SP3 (incl Nov 2012 Update 12.0.6665.5000) which is known as fully supported with Exchange 2013.
With Exchange Server 2007 we did not have any issues. But after having successfully migrated to Exchange 2013 we cannot manage our public folders favorites from these clients anymore.
As we are running Outlook 2007 on a WTS we can not use Exchange Cache Mode and so we can also not download Public-Folders-Favorites as an option. Whenever we try to delete existing favorites or when we try to delete public folders with content or subfolders there will be an error msg that says that it cannot be deleted and that there may be no sufficient permissions. But this IS NOT the issue NOR the solution as I have full admin rights and am owner of the public folders.
On single fat clients with Outlook 2007 with Exchange Cache Mode enabled we can manage the favorites and the public folders without problem.
We need to be able to manage the favorites of all users (circa 50-60 users) from the WTS with Outlookm 2007. I have no more ideas right now. Does anyone know how to get this settled?
Thanks, Paula
Hi,
My outlook 2010 cannot able to download mails, but my mobile device is able to receive mails. I checked everything on outlook settings, bit nothing is changed, all settings are correct. I even recreated the profile, but of no use. I'm able to receive mail on iPhone/ActiveSync on my mobile device.
Any suggestion?
Thanks
Rajneesh Kumar MCITP - SA, MCSE, CNA
When setting up Outlook Profile on a NON domain joined computer the Setup Continuously Asks for Credentials!
found by trial and error that entering domain\username is accepted.
Side Note: If I change the 'A' record for mydomain.com to an account with a shared SSL
if I set it back to clients normal website which has NO ssl - not even a shared one it will only ask about 3-4 times
but again if I enter domain\username the setup completes fine !!
JK
Hello Folks,
I am having exchange sever 2007 SP3. currently facing issue with one shared mailbox. One of the user is not able to open that mailbox from outlook 2010.
I can able to add that mailbox in the outlook but while opening the outlook it is asking for password. Outlook is not accepting user password for that mailbox. I have removed that user from full access and added that user again.
Other shared mailbox is working fine with same outlook profile and other user can also able to access that problematic shared mailbox.
Can anyone tell how to troubleshoot..?
Thanks, Chinmay.
Hello,
I have been in the process of setting up our new exchange 2010 server and have found the following issue. I can log into the secure OWA site without issue and can send and receive emails fine. When i attempt to select any "option" such
as set automatic replies or see all options I receive the following error message -
"500 internal server error there is a problem with the resource you are looking for, and cannot be displayed".
I have verified that all required exchange servicesare running.
I am running exchange 2010 sp3 on server 2012.
I think it may an issue within IIS but i'm not sure
Any help would be appreciated.
Thanks
You can't send a message on behalf of this user unless you have permission to do so. Please make sure you're sending on behalf of the correct sender, or request the necessary permission. If the problem continues, please contact your helpdesk.
I have a user that continues to get the error above when she tries to send an email from a shared mailbox, where she has been granted send as + full mailbox rights. I have tried to resolve the issue by re-creating the .ost file. However this only works for about 2 weeks and the error comes back. I have also deleted the OAB & cleared cache, however this only works for about 2 weeks before the issue re-appears. Has anyone out there experienced this before? Can anyone think of a solution to my problem?
Thank you
TD
TD
Hello Folks,
I have this problem and is making me crazy if anyone have any idea please shed some light on this:-
1. Working Outlook 2010 and 2013 clients with webmail.xyz.com as Outlook Anywhere proxy address.
2. Installed new Exchange 2013 server (server02)with CAS and Mailbox role, Exchange install wizard finished and server is rebooted.
3. Server came up online started changing internal and external FQDN's of Virtual Directories and Outlook Anywhere to webmail.xyz.com
4. As soon as Fqdn's changed some outlook clients create support request that Outlook suddenly white's out and after reopening it is giving error cannot connect to exchange. upon checking Clients Exchange Proxy address is set to http://server02.xyz.com, even though OA/OWA/ECP/OAB/EWS/Autodiscover/ActiveSync FQDN's Point to webmail.xyz.com, on all servers if i create new outlook profile for same user it picks up correct settings through autodiscover and connects fine, this is happening to about 20% of outlook clients every time i am introducing new Exchange 2013 server in Organization. we have around 2000 users and planning on installing 4 exchange servers to distribute load and everytime changing outlook profile of close to 150-200 users is not possible.
Any help is greatly appreciated.
Thanks
Cool
Hi all!
Hope somebody can help me out. In my test lab, where I`m experimenting with Exchange 2013 SP1 and Outlook 2013 SP1 I came across very annoying thing.
Let me explain a little bit more about config that worked.
Outlook 2013 connected to Exchange 2013 via RPC over HTTPS is working great actually really great. I have created my own certs and imported ROOT CA cert to all of my machines and things are working peachy. As part of my plans for 2014 I have to test and deploy MAPI over HTTP sometime at the end of 2014 in our company (and migrate fromEX2007 but this is different story).
OK so I`ve enabled MAPI over HTTP on my test server and configured 5 virtual machines with different accounts to test things out. Started Outlooks, accepted "Your administrator has made change ....." prompts and here we go, I`m connected MAPI/HTTP and all works really great.
Except for one thing. When it does connect, things are super fast and it works as it should. But sometimes it does not connect right away and it is sluggish in performance. Also Outlook is missing "Quick steps" menu, see attached image:
I restarted all servers, clients, clean Outlook install nothing helps.
When RPC/HTTPS I could quit and start Outlook 10 times and it worked 10/10 without problems.
When MAPI/HTTP I restart outlook and it works 6/10, so 4 times I get messed up Outlook and very poor performance.
Any idea where to start troubleshooting? Maybe Outlook has a bug or 2 with this mode?
Server is correctly sized and backed up by enough of memory and CPU, mailboxes have 100-3500 items in them.
Again, RPC/HTTPS works every time without any problem.
MAPI/HTTP works lets say 6 times without any prolem at all and really works great but 4 times out of 10 it makes me want to throw it away :)
If someone knows best way to troubleshoot this one, please let me know.
Regards,
G