Exchange 2010: OWA Options menu

Hi all,
I am having a problem with OWA on a customer's Exchange 2010 server. With any account, including the Administrator account, when you click on "Options" after logging in, you get:
"Sorry Access denied
You don't have permission to open this page. If you're a new user or were recently assigned credentials, please wait 15 minutes and try again. If the problem persists, contact your administrator."
Screen shot of this here:
http://i51.tinypic.com/v6mc1c.jpg
URL points to this folder:
/ecp/?rfr=owa
I'm thinking this has something to do with IIS. Can someone point me in the right direction?
Thanks in advance :) .

Hi,
Please try to check the RoleAssignmentPolicy attribute for the users and see if the “Default Role Assignment Policy” is assigned to the users by
running the following command:
Get-Mailbox “user” | Select-Object RoleAssignmentPolicy
If no, please run the below mentioned commang to assign the default role assignment policy:
Get-Mailbox “user”| Set-Mailbox –RoleAssignmentPolicy “Default Role Assignment Policy”
Hope it helps.
Best regards,
Serena
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Thanks for this solution. I had the same problem!

Similar Messages

Exchange 2010 OWA [Change Number of items to display per page]

Hi Sir,
I have some problem and question ?
I has migrate from exchange 2007 to exchange 2010.
Exchange 2010 OWA cannot Change Number of items to display per page
Exchange 2007 can change number of items to display per page
Exchange 2010 OWA cannot Change Number of items to display per page
You can help me to solved problem and customization?
Thank you.
Boongerd

Hi,
This feature has been moved in Exchange 2010 OWA. However this feature is available in OWA light version. Here are steps to change the settings in OWA light version.
Log in to OWA, click the Use the light version of Outlook Web App
check box on the login page.
Select Options in the upper right hand corner of the screen.
Select Messaging from the left navigation panel.
In the section for "Message Options", change the "Number of items to display per page", select the desired number of messages.
Exchange 2010: OWA versus OWA light.
http://blogs.technet.com/b/ilvancri/archive/2010/04/07/exchange-2010-owa-versus-owa-light.aspx
New Features in Exchange 2010 OWA.
http://technet.microsoft.com/en-us/library/aa998629(v=exchg.141).aspx
Best Regards.

Exchange 2010 OWA usage in Exchange 2013

Hi,
I have Exchange 2010 with Sp3 Currently running in environment, Now we have plan to Migrate it to Exchange 2013.... Total number of mailbox is around 26000.
Before Migration we want below things to keep in mind...
1. We want to Use existing exchange 2010 OWA url ( mail.abc.com ), How to accompolish this as it will take couple of months to migrate all mailbox ?
2. Can i use my Existing Exchange certificate to get the above goal done ?
3. What will be the steps and pre-requsite to achieve the Goal ?
An Early reply would be appreciated !!
Amit

Hi Amit
First Change SCP of Exchange 2010 CAS VIP to Exchange 2013 CAS VIP.
Configure external DNS records accordingly.DNS entries should be pointed to Exchange 2013 CAS from Exchange 2010 CAS.
Ensure that you are having a seperate name for CAS array from external ews url
Outlook Anywhere should be enabled and Url should be external URL which points to Exchange 2013.
Authentication for OUtlook Anywhere should be - NTLM
for OWA exchange 2010 - FBA and windows
Point your new CAS server to the firewall or TMG . Now from exchange 2013 all request will be proxied to 2010 users
You cannot use the same certificate . YOu need to add seperate entries as the host name for new servers will vary
Apply a new certificate with all the required site names included in Exchange 2013 CAS.
Whats more you can refer my blog as well
http://exchangequery.com/2014/05/02/things-to-consider-before-configuring-autodiscover-in-exchange-20102013-coexistence-scenarios/
Cheers :)
Remember to 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 Check out my latest blog posts on http://exchangequery.com

Exchange 2010 OWA : TMG Error 12302 The server denied the specified Uniform Resource Locator (URL).

Hello All,
We are using TMG2010 (SP2, rollup4) for publishing Exchange 2010 OWA sites. The issue is that after every 10-24 hrs , the TMG server stops logging in OWA sites and start giving below error. Then we have to restart the server one two times or the problem
solves by itself.
I have also install a new server and it is also giving same behavior. On TMG server the exchange edge server and Forefront Protection for exchange is also installed.
Please help to solve this issue.
Denied Connection
-TMG05 5/21/2014 11:44:39 PM
Log type:
Web Proxy (Reverse)
Status: 12302 The server denied the specified Uniform Resource Locator (URL). Contact the server administrator.
Rule:
PRC-OWA
Source:
119.157.175.238:56971
Destination:
111.68.105.121:443
Request:
GET http://mail.parc.gov.pk/owa
Filter information:
Req ID: 0e947d98; Compression: client=Yes, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=yes, valid=yes, updated=no, logged off=no, client type=public, user activity=yes
Protocol:
https
User:
anonymous
Additional information
Client agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)
Object source: (No source information is available.)
Cache info: 0x0
Processing time: 125 MIME type:

Hi,
A similar thread:
http://social.technet.microsoft.com/Forums/forefront/en-US/e8fdc1bd-f023-4804-ad02-67899d8c7347/the-server-denied-the-specified-uniform-resource-locator-errors12302-ashttp-error-code-of-500?forum=Forefrontedgegeneral
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Exchange 2010 OWA login page customization does not work

Where can I post a question regarding Exchange 2010 OWA login page customization? The customization worked before running updates, now all users navigating to the OWA page see the default configuration.

Hello,
You should ask in the
Exchange Previous Versions - Administration, Monitoring, and Performance forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book: Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Securing publishing exchange 2010 OWA and ActiveSync with WAP 2012

Hello,
my client have the following environment:
Exchange 2010 sp3
AD 2003
we want to secure activesync and owa by using reverse proxy. TMG/UAG life ends 2015, then we study WAP 2012 and ADFS 3.0. the difficulties is there is not enough experience feedback, specially for this environnement.
Is there any incompatibility ?
do you know good articles and blogs which address this issue ?
Thanks in advance

Are any other options available since posting in June 2014? Specifically for securing ActiveSync connections from smartphones on the Internet. We are running Exchange 2010 in AD 2008
TMG has already transitioned from mainstream to extended support. Not only is there less support now, to my understanding there is still a licensing cost for this product. Paying for a product at EOL seems inadvisable.
Web Access Protocol (WAP) looked like the right choice, but to secure communications from domain users on unknown devices over the Internet requires Exchange 2013 which is "claims aware". Exchange 2010 is not and what we are left with is
configuring WAP in pass-thru mode, allowing unauthenticated Internet traffic into our internal network where the Exchange CAS server is.
Is there any Microsoft solution to authenticate the user before allowing the user's device to connect to our CAS server on our internal network.

Exchange 2010 OWA and ASA5510 - Wrong URL?

I'm in the final steps of migrating my customer's Exchange server from Exchange 2003 to Exchange 2010. I've got all the mailboxes moved and am testing the OWA access. Under Exchange 2003, the internal/external users were able to access OWA thru the following URL:
http://mail.mycustomer.org/exchange
It would pop up a login box, they'd put in their domain info and get connected to their mailbox.
After migrating to Exchange 2010, the user had to change the URL to httpS://mail.mycustomer.org/exchange or httpS://mail.mycustomer.org/owa, but it worked internally. When I test it externally, I get the following page:
https://mail.mycustomer.org/+CSCOE+/wrong_url.html
I have next to no experience with Cisco devices, management, and/or maintenance, but what I've found in my research points to an issue w/ our ASA5510 and the port 443 required by the SSL connection to the Exchange server. Any help to resolve this issue so that my external users will be able to access OWA would be greatly appreciated. Thanks.

Hi,
Can you check the output of the following commands
show run http
show run webvpn
These are basically the 2 services that utilize the port TCP/443 port on the ASA.
The first commands output will show some settings related to the ASDM which is the GUI for the ASA management. The second command output will show settings related to the SSL VPN.
Both of these services can be modified to use some other port than TCP/443 which would leave the port free for your server.
I assume that you only have one public IP address at your disposal which is configured on the ASA interface and you have no extra public IP address? Otherwise this should be no problem at all.
Naturally if you change the port on ASDM or SSL VPN it will cause some inconvinience for users of those services. Ofcourse you have the option to map the local TCP/443 port of the server to some other public port like TCP/444 but again this might cause inconvinience to the users also.
- Jouni

Use Exchange 2010 OWA Login Page with Exchange 2013

We are planning on upgrading our exchange server from 2010 to 2013. We want to keep 2010 OWA login page with this upgrade. Partly due to educating users to new OWA interface and no plan to upgrade to office 2013 anytime soon.
Questions:
1. Do you or do you not recommend?
2. Is it possible?
3. How to keep 2010 OWA login page during and after migration to 2013 (instructions)?
Thank you!

Hi, EthenLEC
I agree with Andy David.
For additional information, we can change OWA 2013 back to OWA 2010 interface to use light version by the following steps.
Log in to OWA 2013.
Once logged in, click on the settings gear in the upper right corner, choose
Display Settings.
From the Display settings menu, choose Outlook Web App version, then check the box to use the light version.
Sign out of OWA and sign back in. Now it has the OWA 2013 light version.
Best Regards.

Exchange 2010 - owa/auth.owa Bad Request

We just set up an Exchange 2010 server. When we try to use OWA and go to options > Set Automatic Replies, I get a logon prompt, however when I try to logon, it gives me a -
HTTP 404 Bad Request
The webpage cannot be found
and the page it's trying to go to is
http://ExchangeServer/owa/auth.owa. I looked through the OWA directory and I don't even see an auth.owa file.
Does anyone know how I can fix this?
Thanks,
Scott

Hi,
Does the problem happen to all mailbox users?
Try to check if you can access ECP virtual diectory: Open IE, type
https://yourdomain.com/owa/ecp
If the issue persists, please refer the following commands to create a new ECP virtual directory:
Remove-EcpVirtualDirectory -Identity "ServerCAS\ecp (default Web site)"
New-EcpVirtualDirectory -Identity "ServerCAS\ecp (default Web site)"
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

TMG 2010 publishing Exchange 2010 OWA cannot change password if user must change password at first logon is set

Hi,
I have an odd issue whereby if I set "user must change password" on an AD account, the end user cannot logon, they're simply taken back to the OWA login page as if their password is incorrect.
My setup is as follows:
outer TMG -- uses a listener for email.contoso.com and is configured for no authentication.This uses a publishing rule to publish the inner TMG server. This server is not a domain member.
inner TMG - uses a listener for email.contoso.com and is configured for NLTM\kerberos negotiation with forms authentication (Windows Active Directory). This server is a domain member and use a publishing rule to publish the internal CAS. Allow users to change
password is selected in the publishing rules.
Exchange 2010 SP1 - uses integrated windows and basic authentication. Has the appropriate registry key configured to allow users to change their AD password on first logon.
I've registered an snp for "http/email.contoso.com mailserver-dc1", all SSL certificates being used are valid and my configuration used to allow users to login and change their password with "user must change password on first login"
set in AD.
If I launch a web browser on an internal server and point it to email.contoso.com I'm immediately presented with a generic Windows authentication request (similar to what's seen in ADFS) rather than the standard OWA page. No matter what I do, I cannot login
and change my password using the correct URL. However if I point my browser at
http://192.168.4.10/owa I'm prompted to login and I can change my password using the sam credentials.
The only recent changes made are:
- Disabling SSL 3.0 and enabling TLS (http://www.isaserver.org/articles-tutorials/configuration-security/improving-ssl-security-forefront-threat-management-gateway-tmg-2010-published-web-sites.html)
- Replacing the TMG listener certificates so that they now use SHA2 rather than SHA2 (certificates are trusted on each TMG server)
Looking on the outer TMG and the DC logs I can see schannel errors which I believe are related to the problem. TMG monitoring also shows "Failed connection attempt: 1907 The user'spassword must be changed before logging on for the first time"
I've checked that my inner TMG and DC are using the same certificate for server authentication and gone through this guide:
http://blogs.technet.com/b/keithab/archive/2012/02/29/setting-up-and-troubleshooting-ldaps-authentication-in-forefront-tmg-2010.aspx
If I try to use ldp.exe on the inner TMG, I get the error in the pic below
Thanks
IT Support/Everything

Hi,
You could try to analyze the TMG tracing and try the troubleshoot steps in the blog below.
TMG 2010 – FBA, troubleshooting the change password feature
http://blogs.technet.com/b/isablog/archive/2012/05/07/tmg-2010-fba-troubleshooting-the-change-password-feature.aspx
Best Regards,
Joyce

Exchange 2010 OWA access on internal LAN login form not working as expected

hi
We have exchange 2010 sp3 installed and working. we have two sites
Site a
1 x CAS
2 X MBX
Site b
1 x cas
2x mbx
site A is the primary site we currently publish owa our through our TMG server located in the DMZ this is working as expected and carries out the forms authentication. our internal domain is company.local but our external domain is company.com
we have created split DNS so that we could use a wildcard cert and to deal with CA new rules. All URL's in Exchange are configured to use the external reference of company.com/
on the IIS server we have a redirection on the root of the site to redirect the requests through to OWA folder and we have basic Authentication enabled. on the OWA folder we have basic and windows authentication.
The problem we have is that when users try to access OWA internally we get username and password box appears once you login with this it then takes you through to the the normal login screen and you have tyo login again I'm thinking that this is the windows
authentication that is causing this but not sure?
also would be good to get an understanding as to what the Authentication, SSL and redirection setting should be set to on your CAS servers as looking at the ECP and autodiscover folder within IIS this currently has a redirect set to go to OWA surely that
cannot be right,
thanks
J

Hi
you are correct, the immediate concern is the double login to owa i do however want to also know what the settings/configuration for Authentication redirection and SSL should be set to on all virtual directories.
we do not have any additional OWA virtual directories just the default
These are the current live servers
Identity                      : ACAS01\owa (Default Web Site)
Url                           : {}
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   : https://email.Company.com.com/owa
ExternalUrl                   : https://email.Company.com/owa
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
ExternalAuthenticationMethods : {Fba}
Identity                      : BCAS01\owa (Default Web Site)
Url                           : {}
Exchange2003Url               : https://www.Companyt.co.uk/
FailbackUrl                   :
InternalUrl                   : https://webmail.Company.com/owa
ExternalUrl                   : https://webmail.Company.com/owa
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
ExternalAuthenticationMethods : {Fba}
These are the new servers which i have just installed
Identity                     : CAS05\owa (Default Web Site)
Url                           : {}
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   : https://webmail.Company.com/owa
ExternalUrl                   : https://webmail.Company.com/owa
InternalAuthenticationMethods : {Basic, Fba, Ntlm, WindowsIntegrated}
ExternalAuthenticationMethods : {Fba}
Identity                      : CAS06\owa (Default Web Site)
Url                           : {}
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   : https://webmail.Company.com/owa
ExternalUrl                   : https://webmail.Company.com/owa
InternalAuthenticationMethods : {Basic, Fba, Ntlm, WindowsIntegrated}
ExternalAuthenticationMethods : {Fba}
Identity                      : CAS04\owa (Default Web Site)
Url                           : {}
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   : https://webmail.Company.com/owa
ExternalUrl                   : https://webmail.Company.com/owa
InternalAuthenticationMethods : {Basic, Fba, Ntlm, WindowsIntegrated}
ExternalAuthenticationMethods : {Fba}
I have noticed that FBA is set on the new servers does this need turning off and if so is this on IIS or in Exchange?
the link that you have provided talks about creating new Vdir for TMG we are looking at removing TMG and replacing it with KEMP load balancers would we still need to have two Vdir to make FBA work internally and externally
to make a new vdir do you need a new IP address? and what are the steps required in Exchange and IIS to get this working.
thanks
Jason

Lync 2013\Exchange 2010 OWA Integration Problem

Hi there,
I've got a vexing issue that I haven't had much luck in researching. I am running Lync 2013 on Server 2008 R2 and Exchange 2010 SP3 on Server 2008 R2. I followed Jeff Schertz's instructions (http://blog.schertz.name/2010/11/lync-and-exchange-im-integration/)
and Lync\OWA integration is working--sort of.
We currently have a central pool (we'll call it lyncpool.contoso.com) and three pools housed on SBAs-- lyncsba-loc1, lyncsba-loc2,lyncsba-loc3. Users in our main location are housed on the central pool, whereas users in our remote locations are housed
on their respective SBA.
Following the instructions, I pointed my OWA virtual directories at lyncpool.contoso.com, and everything seemed fine at first. I could see presence in OWA, initiate an instant message...the works. However, when I asked a user homed on one of the SBAs,
he said that he could only see presence for other users in his pool\location. Everyone else had a white "unknown" presence chiclet. To verify, I temporarily moved my lync account to that branch pool, and sure enough--I saw the same thing. As
a troubleshooting measure, I re-ran the OWA configuration portion and instead of using the central pool as the instantmessagingserver value, I pointed it directly at that branch pool. At that point, he and I, being homed in that branch pool, could see
presence for EVERYONE. Problem solved, right? Well, no...because now, the central pool users could only see presence for other central pool users, and the other branches could still only see presence for their poolmates.
I've run Wireshark, CLS logging, you name it--I haven't seen anything fishy, and I'm starting to wonder if this perhaps a bug or an unsupported use-case(I hope not, since Microsoft otherwise endorses such a configuration). I've been beating my head
against this wall for almost two weeks with no change...someone, help! :)

This is the only thing that seems of interest in the CLS Log:
TL_WARN(TF_DIAG) [lyncpool01\VGTLYNCFE-01]1B70.4184::06/17/2014-20:47:03.028.00001F75 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(805))
[1781536493] $$begin_record
Severity: warning
Text: Cannot process Route headers from a non-trusted source, or with first Route field in the set not matching the connection on which the request arrived
Result-Code: 0xc3e93c5e SIPPROXY_E_ROUTING
SIP-Start-Line: SUBSCRIBE sip:LyncPool01.xxx.net:5061;transport=tls;ms-fe=VGTLYNCFE-01.xxx.net SIP/2.0
SIP-Call-ID: 45c62e9edaee4252908914b37ca5ef23
SIP-CSeq: 1895 SUBSCRIBE
Source: mail.xxx.net:47892
$$end_record
The "source" here is our OWA server. I have issued a certificate from our local CA(the same one that issued the Lync certs), making sure the CN of the certificate matches the OWA url. Any ideas?

Exchange OWA does not load OWA for Exchange 2010 users

I have recently installed Exchange 2013 SP1 CU4 in my existing Exchange 2010 SP3 environment but when I use Exchange 2013 OWA to login Exchange 2010 users (it should automatically take the user to Exchange 2010 OWA) but I get this error message "Forbidden
403- Access is denied". However exchange 2010 users can login to their /ecp directory from exchange 2013. Exchange 2010 users can use OWA using their exchange2010/owa URL without any problems. We do not have any http or https redirection enabled
on any of the server. Also I have tried to uncheck the "Required SSL" settings for default web site on both Exchange servers but error is still same. Any help will be highly appreciated.

Hi,
According to your description, your Exchange 2013 cannot proxy OWA request to Exchange 2010 server, but ECP　request　can work properly.
In this case, Ｉ'd like to confirm OWA and ECP settings on Exchange 2013 and 2010 servers before going further:
Get-OWAvituraldirectory |fl identify,*url,*authentication
Get-ECPvituraldirectory |fl identify,*url,*authentication
Thanks,
Angela Shi
TechNet Community Support

Exchange 2010/2013 coexistence: OWA proxy not working properly ":-( Something went wrong"

Hi
Exchange 2010 users are NOT able to connect to their mailboxes when they go through exchange 2013 OWA address. We get a message that says following ---> "Something went wrong"
Following is our URL. The address is pointing to 2013 CAS loadbalancer VIP. Outlook anywhere is working fine. What is going on?
Important: All my exchange 2010 / 2013 URIs are the same as suggested by Microsoft (Owa, ecp, activesync, ews, autodiscover): --> mail.domain.com/XXX

Hello Rawa,
Can you log on Exchange 2010 OWA using its localhost address?
Please make sure the intenralurl value is set to Exchange 2010’s local host name and set the Externalurl to Null.
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
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

Exchange 2010-2013 co-existence - need for OWA/ActiveSync legacy namespace?

Hi all
Straight to the point: how to I update units that were set up manually with Exchange ActiveSync (pointing to owa.domain.com) with a temporary legacy namespace owa-legacy.domain.com, and then back to owa.domain.com?
Background: I did a test run of migrating a single-server installation from Exchange 2010 to Exchange 2013. As expected, after moving a user's mailbox to the new Exchange 2013 CAS with owa.domain.com still pointing to Exchange 2010, the user
was unable to log in at the Exchange 2010 OWA, and the ActiveSync unit was unable to fetch mail.
So I created a legacy namespace (owa-legacy.domain.com) and set this as the URL on the Exchange 2010 server, and waited for it to populate, then switched owa.domain.com to Exchange 2013. But the URL on ActiveSync units was still pointing to the wrong URL.
What did I overlook or not understand, or am I making migration more complex than needed?
Thanks for reading and best regards
/Maurice
PS: here were some of my pre-post readings:
Exchange 2003-2013 co-existence, even better
Exchange 2003-2013 co-existence,
Exchange 2010-2013 co-existence slides,
Upgrading ActiveSync to Exchange 2010,

Hi
Is that because External URL on Internet facing CAS servers were set to Blank，and Users are not able to get Updated URL
Please try to Add the External URL and made sure that all the required configurations are set Appropriately.
Also I suggest posting on Exchange ActiveSync Forum as well
http://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Cheers
If you have any feedback on our support, please click
here
Zi Feng
TechNet Community Support

Exchange 2010: OWA Options menu

Similar Messages

Maybe you are looking for