My "team" calendar grouping has disappeared from my calendar view. I am on Exchange 2010 using Outlook 2010. This "Team" group was automatically created and automatically updated with those who share the same manager as myself.
I unfortunately suspect this is related to my team now including more than 100 members and Outlook not supporting this, as a colleague has the same problem.
Hi All,
Very very frustrating, am not sure where to hit my head on the servers or on the wall :(
We were in the process of transition from Exchange 2007 to Exchange 2013 and we have done the below:
Exchange 2007 upgraded to SP3 RU 10 during this time we have deleted public folders database as nothing was in the database, the process was to remove the database directly from ADSIEDIT and that's it
Exchange 2013 with CU1 was deployed 2 MBX servers and 2 CAS Servers, configured DAG and CAS Windows NLB
Changed all virtual directories of 2013 CAS with mail.domain.com where changed all Exchange 2007 cas virtual directory to legacy.domain.com as well as imported certificates on CAS servers of both Exchange servers, then changed port 443 from firewall to point to 2013 CAS NLB IP
Migrated 2000 mailboxes, 100 resource mailboxes, all clients are using mix of Outlook 2007, 2010 and 2013 where all outlooks are upgraded to the supported patch of Exchange 2013 compatibility
two days before I was receiving warnings that exchange 2007 databases are still pointing to Public Folders which I have deleted this pointer from adsiedit of each 2007 server I have double checked on 2013 databases attributes which was not pointing to any pf attribute
migrated exchange 2007 HUB connectors by creating new connectors in 2013 in this way we have migrated hub role to 2013
before demoting exchange 2007 we thought it is a good idea to shutdown all 2007 servers, we have shutdown 2007 servers at 12PM and after 2 to 3 hours users has complained that they are getting password prompts every and after some time.
Outlook any where settings in 2013 is NTLM for internal network and basic for external network, my internal and external url for OA is same which is mail.domain.com. client require ssl for internal and external is true as well as ssloffload is true where as I am not using any HLB, but ssloffload is true when I have deployed exchange 2013 for the first time.
I have tried to changed the OA authentication settings to different settings but nothing has worked out for users, this has not happened to few users but it happened to a lot of users but we did not get call from all users as well.
after this behavior we have tried to configured new outlook settings through autodiscover on outlook 2010, 2007 and 2013, if I am logged on to a computer joined to the domain and logged on with test1 user and try to configure the outlook with version 2013 and 2010 on the second step of searching and configuring outlook profile the pop up came to ask the password and it was mentioned on the pop up that connecting to mail application, if I will cancel this the profile created successfully
after configuring the profile when we open the outlook it asks for the password again if I click on cancel the outlook disconnects and on the bottom it says needs a password. at this time if I will click on outlook configuration by clicking ctrl + right click on the outlook in the task bar I don't see any thing related to Public folders or exchange 2007 url I only see GUIDs but it asks for the password I don't know why
if outlook 2007 is configured and if I restart the outlook at the first time it asks for the password how ever the user is logged on to the computer and it should not ask for the password, when the outlook 2007 asks for the password prompt, on the prompt it shows connecting to legacy.domain.com and If I click cancel again it says needs a password
if we turn on exchange 2007 servers, new profiles are created without any password prompts, restart of any outlook doesn't ask any passwords. I am not sure now that where to go what to do. please help me please.
If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync
All the info on OWA post CU1 says that OWA can access public folders. I can only see how to access PF of type Mail. Is it really possible to access PF contacts and Calendars from OWA?
Hi
In Exchange 2013 OWA the option to select Private or Public computer is not precent as Default.
Running the following powershell command will enable the checkbox on the logon page.
Set-OwaVirtualDirectory "ex1\owa*" -LogonPagePublicPrivateSelectionEnabled $True
After running that command, the checkbox is there, but how do I get the check box unchecked as default. As it is now the option "Private computer" is the default one, but I would like to have it unchecked as "Public computer" as default.
Is this possible to do? I've googled a lot on the case but not found anything how to change the default setting for the Private/Public OWA.
Best Regards
Lars
Hi,
I know this question has been asked a ton of times, but I haven't found any instance of this question asked for exchange 2013. Yes, I've seen Exchange 2010, Exchange 2007, but not Exchange 2013. The symptoms are all similar. Here is a description:
1 Exchange 2013 server, all roles installed.
External domain name: associates.com
Internal AD domain name: associates.local
Client installed a third party SSL certificate, but did not purchase a SAN or UC certificate, so there is one namespace on the SSL cert, and that represents the external OWA name: mail.associates.com
Now, when internal OUtlook 2010 clients start, they get the "The name of the security certificate is invalid or does not match the name of the site."
I'm just wondering if http://support.microsoft.com/kb/940726 still applies to Exchange 2013 to fix this issue. Does this article apply to Exchange 2013? If so, I will follow the above article. If not, please direct me to any articles for Exchange 2013 that addresses this.
the autodiscoverserviceuri points to: https://netbiosnameofmailserver.associates.local/Autodiscover/Autodiscover.xml
Thanks!
A
In our current setup we have a Hub Transport server and a seperate Client Access server. The HT server was using a self signed cert and the CA server was using a 3rd party signed cert that was going to expire and was tied to our direct outside name ex. owa.example.com.
I just purchased a wildcard ssl cert *.example.com and I was able to install it on the HT server for smtp and on the CA server for IIS but I get an error for POP and IMAP4 when I try to assign them to the new cert.
I've seen several posts regarding this issue and I think it'll work, but my main question is: What are the implications of changing the cert? Will my intranet outlook clients work with no problems? How about OWA or activesync? I want to make this transparent to the users, is that possible?
Vincent Sprague
Hello All
Facing a bit weird issue in environment and have been trying to fix it since few days now without any luck. We are running on Exchange 2010 SP2 UR3 (planning for SP3 UR 1) soon. Recently we observed following issues in environment:
Now as you must be suspecting by now, we have narrowed down the issue being packet loss in environment. After lot of diagnosis, we were able to determine that cause of packet drip is RX pause packets sent from servers to switch which indicates that destination box is unable to process as fast as they are being received, so it tells switch to slow down.
To fix above issue, switch guy tell us to enable flow control on switch which will buffer the packets. However we already have flow control on our esx 4.1 farm on which exchange is running along with dedicated NIC for mapi, replication and backup.
But the bigger issue is Outlook connections. In network capture we can see CAS requesting fast packet re transmit after intermittent packet drop.
Currently all users have more than 35 connections on an average. Exchange store limits have already been bumped up. The issue I believe is due to fact that exchange is not closing previously disconnected sessions and keep accumulating them over period of day. (tcp keep alive tome is default 2 hrs). Increased connections along with network packet drop is creating intermittent pop up on outlook side it seems.
So my question being:
Hopefully I covered most of background, please let me know if additional details required.
Thanks in advance !
AKL
I have a client who utilizes just one mail account for his whole staff. They've been doing this for years now, and haven't had many problems (besides the obvious mailbox size, etc.). We upgraded the Exchange Server to 2013. Now every 11th user or later who tries to open Outlook with that account cannot connect to the Exchange Server. It tries to make the connection, but ends up saying its disconnected. As soon as I have another user logoff, the user whose having the problem can connect.
At first I thought it was throttling, but I disabled it and the problem still occurred. Employees are using Outlook 2010, but I also tried 2013 with the same results. Running a test, while Outlook wouldn't connect, I set it up to a different user account and it connects fine, as soon as I went back to the original account it failed once again.
Does anyone know of a limitation like this? If so, how do I fix it?
Hi,
I am trying to publish Exchange 2010 OWA/EAS/Outlook Anywhere using TMG 2010.
Configuration detsils:
TMG 2010 has 2 NICs--Internal and External. External NIC has multiple IP asociated with it (used for multiple listener)
OWA/EAS will use basic auth and OA will use NTLM auth.
I have created 2 listerners--listener1 for OWA and EAS both and listener2 for OA. The relevant publishing rules have also been created.
The publishing rule for OA/EAS has autodiscover.contoso.com listed in the public website along with mail.contoso.com.
I have 2 public DNS records- mail.contoso.com and autodiscover.contoso.com.
mail.contoso.com will be used for OWA/EAS/OA and is pointing to the external IP of listerner1.
autodiscover.contoso.com is pointing to external IP of listerner2 which will make the OA work. Do I also need to point the autodiscover.contoso.com to the external IP address of listerner1 for EAS to work? Any help will be appreciated.
Regards,
Imrul Emon
Was working fine completely yesterday. Woken up this AM by customers complaining about not being able to access webmail. Double check all settings / auth and everything seems to check out.
After logging in a user will see "Loading..." in the name of the browser window with a blank white page.
I have searched extensively but none of the top fixes seem to be working for me, I have checked via Exchange Connectivity Tester
I am trying to dump the tester link but it is telling me I cannot post images.. I am only posted the copy/paste code.
Is there a way we can use a client distribution mailing lists?
We need the message to be sent TO employee_list(which is list of employees who are emailed) and CCed to manager_list(which is list of managers of those employees).
The recipients can expand the address, if they want, when they receive the message.
The public folders do not show up for users outside our domain, say for users setup with outlook at home use.
We have exchange 2013 cu1 installed. Outlook is 2010 in most cases.
The public folders/calendars show up fine in outlook for users logged in on our domain internally at work and we use domainmailserver as the internal url for all things like oab, etc. but use our external mail.ourdomain.com for connecting from outside our network, they can connect at home from their outlook to their account. We have http rpc enabled because we are behind a firewall and only through vpn can anyone even remote desktop so the internal and external urls are different in our exchange setup.
Any ideas as to why public folders show up only internally and not for those connecting from home or outside our network so to speak.
Also note that the public folders are used for sharing common calendars and they are all mail enabled, but even via OWA one cannot connect or open them, see the attached screenshot of error in owa.
Anyone know a resolution for this ?
Hi , I am unable to connect outlook on 365 and constantly get the message "unable to connect to the exchange. Outlook must be online".
I am connected to the internet and this is working correctly ,so there is an issue with my settings that I cant resolve.
Mark.
Hello,
In autodiscover.xml file, there is field "Server" (under protocol). Is it CAS server or mailbox server (assuming both roles are installed on different servers).
Thanks
IN WINDOWS 8 MY EMAILS ARE DELETED AFTER 2 WEEKS
Aloha all,
We have exchange 2010 and using office 2013. when trying to sent Messages from a shared mailbox.....message aren't saved to the Sent Items folder of the shared mailbox in Outlook 2013.
I really hope somebody has an answer to resolve this issue.
Mahalo!
Hi,
I have an issue where I have set up an auto response on a mailbox. If I CC in another recipient then no autoresponse is received
If I look at the rule properties then I can not see an option to reply if a recipient is cc'd in.
Any ideas
Hello
We are using Exchange 2007 SP3 and Windows 7 with Outlook 2010.
Myself and my colleague from time to time need to set and out of office message for an exec or someone who is on extended leave.
We can achieve this using Outlook 2003 without a problem, but for Outlook 2010, when we click on Automatic Replies, we receive the error
"Your automatic reply settings cannot be displayed because the server is currently unavailable. Try Again later"
From what I can tell, its that because I am logged in using my System Admin account (which has no mailbox), accessing another users mailbox, that Outlook cannot connect or authenticate to EWS to set the OOF.
We have no issues with users setting their own OOF messages.
Thanks.
This is an issue we are having with some but not all of our users..
It appears to be impacting about 60% of the accounts we have tested..
For some users the move is Successfull.. Outlook asks to restart, it does and they are good to go.
For others Outlook fails. They get the promot to restart outlook after the mailbox move is complete..
They restart and outlook stops with a Outlook cannot log on error.
THe profile looks correct with the Exchangeguid and email address.
They can log on VIA OWA without issue but not Outlook 2010.
I have run the Connectivity Analzser with on of the failed users credentials and it shows Autoconfigure passses
but it fails on Outlookanywhere.
If I gave a successfull 2013 user full control over a failed users mailbox and they can open the mailbox without any issues.
The issue also follows the user from PC to PC or thin clients. Successfull users work logged into a failed users PC. Failed users don't work logged into a successfull user's PC.
We thought it may be a Kerberos ticket size issue so we increased the HTTP parameters MaxFieldLength and MaxRequestBytes to 65534 on all the CAS servers.
THis did not help.
I ran Netmon while I had a user try to open outlook and noted for following
Network capture on CAS during attempts show
Http: Response, HTTP/1.1, Status: Unauthorized, URL: Using Multiple Authetication Methods, see frame details
StatusCode: 401, Unauthorized
And
Http: Response, HTTP/1.1, Status: Bad request, URL:
StatusCode: 400, Bad request
Outlook and the sever are current on all patching.
Certs on CAS are issued from our Enterprise CA.