Adding "Author" permission via OWA on Exchange 2013

Hello,
We're having issues with our Apple users: whenever they add access to a calender using Apple Calendar, it seems the account gets added to
ResourceDelegates, even if you want to give them read-only access (thanks Apple...). This causes problems as the delegated users get invites and get confused as to why this is.
So we want to recommend they only set calender sharing permissions using Outlook Web App... but the problem is, the
Author permission isn't available in the drop down menu, only
Reviewer or Editor are.
My question is, how can I add this option to the OWA drop down list?
Thanks for your assistance.

Hi,
Author permission is available under calendar
folder permission, not calendar sharing permission.
When we
share calendar via Outlook, it should be like this.
No Author permission, just like
what you experienced in OWA. By default, these three permissions are available and we cannot add permission to this drop down menu based on my knowledge.
Author permission is available under permission tab when you right-click calendar folder to properties in Outlook. And we can’t set calendar folder permission from OWA until now.
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Similar Messages

How can i publish owa on exchange 2013 without ssl?

hi
i need connect to owa on exchange 2013 without ssl.
but when i change config from https to http. my iis return internal error.
can anybody tell me switch from https to https step by step on exchange 2013?
regards

Check out http://technet.microsoft.com/en-us/library/dn635115(v=exchg.150).aspx#OWA
Bharat Suneja
Exchangepedia.com | bsuneja
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup purposes only.

Users with mailboxes on exchange 2010 cant proxy to OWA on exchange 2013

We are in the process of migrating from 2010 to 2013. Users with mailboxes on exchange 2010 can't proxy to the owa on Exchange 2013 - there is no error - just receiving a message "Still working on it"
alex serdyukov

Hi Alex,
As the above suggestion mentioned, you can try to upgrade the Exchange 2013 to CU8 and check if any helps:
Cumulative Update 8 for Exchange Server 2013
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

ECP redirects to OWA in Exchange 2013

When logging into ECP 2013, the Exchange Admin Center login does not come up. A Windows Security login window comes up instead and it takes me into Outlook Web
App.
What am I missing?
July 2, 2014 Update. This has been resolved via reinstall. Thank you everyone to assist with this issue.

Have a look here:
http://technet.microsoft.com/en-us/library/jj150562.aspx
"If you’re in a coexistence scenario, where you’re running Exchange 2010 and Exchange 2013 in the same organization, and your mailbox is still housed on the Exchange 2010 Mailbox server, the browser will default to the Exchange 2010 ECP. You can access
the EAC by adding the Exchange version to the URL. For example, to access the EAC whose virtual directory is hosted on the Client Access server CAS15-NA, use the following URL:
https://CAS15-NA/ecp?ExchClientVer=15. Conversely, if you want to access the Exchange 2010 ECP and your mailbox resides on an Exchange 2013 Mailbox server, use the following URL:
https://CAS14-NA/ecp?ExchClientVer=14."
Try the URL modification:
https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15
It will show up as OWA authentication but after you provide credentials it will redirect back to EAC.
Flame to MS guys: this modification does not harm the scenario when you do not have the exchange 2010 or 2007 coexistance. Why could not you set the param by default when accessing Exchange 2013 CAS ECP application? Why make all those who attempt
to migrate from older exchange versions (2007 and 2010) stumble upon this problem? Shame on you.
Regards,
Eugene
I added the user to groups and that didnt work. But https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15
as suggested in above posted worked for me. (make sure you log out 1st and then try it)

Error while adding member to the dag in exchange 2013 sp1

I have Windows Server 2012 Std Edition with Exchange 2013 SP1 and get the following error while adding member to the dag either i do it using EAC or the powershell
Senior Technical Consultant, MDS Computers

When running set-databaseavailabilitygroup Exchange-dag without parameters, it crashes again:
[PS] C:\Windows\system32>Set-DatabaseAvailabilityGroup exchange-dag
WARNING: An unexpected error has occurred and a Watson dump is being generated: Some or all identity references could not be translated. Some or all identity references could not be translated.
+ CategoryInfo : NotSpecified: (:) [Set-DatabaseAvailabilityGroup], IdentityNotMappedException
+ FullyQualifiedErrorId : System.Security.Principal.IdentityNotMappedException,Microsoft.Exchange.Management.Syste
mConfigurationTasks.SetDatabaseAvailabilityGroup
+ PSComputerName : <server>
Also, this is logged in the eventlog:
Watson report about to be sent for process id: 7424, with parameters: E12, c-RTL-AMD64, 15.00.0847.032, w3wp#MSExchangePowerShellAppPool, M.Exchange.Management, M.E.M.C.FileShareWitness.Create, S.S.Principal.IdentityNotMappedException, 3e5c, 15.00.0847.031.
ErrorReportingEnabled: True
Definitely looks like a problem creating the filewitness share.
Frank.

Cannot write email body in OWA with Exchange 2013 SP1 CU6

Hi,
I have a problem with Exchange 2013 SP1 with CU6.
All of OWA user cannot write in the body of email. They can write the Object and the recipient but they cannot select body and write the body message. We have try with multiple Web brother and desactivate all Add-on but the problem still there...
The only way that works is to respond to an email, and in that case, it's working, we can write normally in the body of email.
Have you an idea ?
Thanks in advance!
Sebastien

Hi,
After contacting Microsoft support, we have found the solution.
The problem appear after we have recently install the patch described in this KB 2997209:
https://support.microsoft.com/kb/2997209?wa=wsignin1.0
But on 2013 Mailbox Server, Echange is not installed in the default path C:\ but on D:\
So we have to manually copy the content of folder D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\prem\15.0.995.29 in the folder 15.0.995.31 (MAKE a BACKUP of FOLDER BEFORE!)
No need to reboot, or restart IIS, it's working after that!
@+
Sébastien

OWA problem Exchange 2013 coexistence with 2010

Hi all,
I am in the midst of a migration from a single Exchange 2010 server to a two-server Exchange 2013 environment (both servers are CAS and MBX with DAG). Everything seems to work fine. I can access OWA on 2013 for mailboxes already moved to 2013, I use ActiveSync
successfully but I cannot for the life of me figure out how to enable OWA 2010 proxying through 2013. I have checked many websites, forums etc. for it, I changed Authentication Methods back and forth and did everything I can think of but still... when trying
to access OWA with a mailbox that is still on 2010 it fails with the following error:
something went wrong
A problem occurred while you were trying to use your mailbox.
X-OWA-Error: Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
X-OWA-Version: 15.0.913.21
X-FEServer: <name of 2013 server>
X-BEServer: <name of 2013 server>
Maybe I should add that the new 2013 servers are installed in a completely different AD site which is connected through VPN to the 2010 site. In the new site I also have a loadbalancer in front of the 2013 servers.
Actually I am still not sure if I need a different address in Exchange 2013 for OA, OWA and so on then in Exchange 2010. If I understood correctly there is no need for a legacy namespace anymore so I used the same URL for OA, OWA ... in both environments.
This seems to be in conflict with the requirement that the OA URL in Exchange 2010 should point to the 2013 URL?!?
Any help is greatly appreciated!
Best regards
Daniel

Hi,
How do you configure your Exchange virtual directories in Exchange 2010 and Exchange 2013? Please run the following command to provide detailed information about it:
Get-OwaVirtualDirectory | Select Identity,name,Internalurl,ExternalUrl,*auth*
According to your description, I noticed that it is set the same URL for OWA using. If the ExternalUrl
for OWA 2010 is configured in your coexistence environment, please remove it. Then when external Users access OWA 2010, they can use OWA 2013 URL and be automatically proxy to Exchange 2010 and access their mailboxes.
Regards,
Winnie Liang
TechNet Community Support

How to enable S/MIME in OWA MS Exchange 2013?

Hello,
I can't find in ECP for MS Exchange 2013 function to enable S/MIME for OWA. Can somebody help me? I found only registry update for MS Exchange 2010 SP1 or download S/MIME function for IE7+ for MS Exchange 2010, but I am not sure if I can use it for 2013.
Thank you,
Pavel Hula

As Martina has pointed out, no S/MIME support in 2013 yet!
Rajith Enchiparambil |
http://www.howexchangeworks.com |

Не работает OWA на Exchange 2013

Установил обновление exchange 2013 SP1 после этого не могу попасть на OWA, при вводе логина и пароля получаю белый экран и в адресной строке: https://cas2.ru/owa/auth.owa, так же перестал цеплятся outlook пишет что не удается войти в систему,
хотя с данными все в порядке.
И на ECP не смог зайти как обычно только через: https://cas2.ru/ecp/?ExchClientVer=15
Что может быть? куда копать? Настройки виртуальных директорий проверил все в порядке

Hi,
I suggest we firstly run the UpdateCas.ps1 script.
http://social.technet.microsoft.com/Forums/windows/en-US/d2cd5268-1319-48e3-be09-bb9ee2771fff/owa-problem
If it still does not work, check all the BE server and see if a valid certificate is enabled for the IIS service.
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 Public Folder Calendars in OWA

Hello,
I have a Public Folder calendar that I need to publish via OWA in Exchange 2013. I understand that you cannot view any public folder that is not mail enabled in OWA. If I make this specific calendar mail enabled will I be able to view the calendar
in OWA? I think I still have to convert this to a shared mailbox. If that is the case, what are the best steps to perform that?

Hi,
Yes I agree with Ed Crowley. In Exchange 2013 Cumulative Update 1, Microsoft have allowed to display public folders. However, two major restrictions exist. First, OWA can only display modern public folders. In other words, you have to complete your
migration to Exchange 2013 and then execute a public folder migration before OWA can be used. No access is possible to legacy public folders. Second, OWA can only display “mail public folders”, or public folders that contain “mail and post items” (as they
are referred to by Outlook). Other folders (calendars, contacts, tasks, notes, InfoPath, and journal items) are unsupported.
Regards,
Santhosh,
www.jijitechnologies.com

Exchange 2013 OWA is not auto formatting hyperlinks when forwarding a message

I have 2 sales managers in a company that receive sales leads via email from our website. The email is formatted in HTML with a table containing the name and email address of the customer and the url of the product they're interested in from our website.
The managers then forward this email to the next available sales associate to contact the potential customer.
The first sales manager uses Outlook and receives the sales lead email with active hyperlinks intact for the email address of the customer and url of the product. When you inspect the email, there is no href code in the source, so outlook is recognizing
the types 'email address' and 'url' to make the text active. He then forwards the email to sales with active hyperlinks in the source. (they prefer this)
The second sales manager uses OWA. when he receives the email, the email address and url are plain text (which is how its coded) so when he forwards the email to sales there are no hyperlinks.
Is it possible to set OWA (for exchange 2013) to auto format (recognize then format) email addresses and url's from an email when forwarding it that didn't have the href code in the source to begin with? ...like Outlook does?

Hi,
Does this issue happen on all the OWA users or on specific user?
Does this issue happen when sending emails by HTML format?
Thanks,
Simon Wu
TechNet Community Support

Migration to Exchange 2013 from 2010 - Client side issues

Hi Everyone,
I've been having issues with clients connecting to an existing Exchange server (Getting login prompt- but not usual reason).
We currently run Exchange 2010 with approx 200 mailboxes on the server. Last night I renewed the certificate on the 2010 server (go daddy SAN cert, all ok) and added the cert to my new Exchange 2013 server. I tested it with my account, and a
test account approx 12 times, and had not login prompt when launching Outlook. All seemed ok, until this morning.....
This morning, most (not all) users are getting the login prompt. We are able to get by this by inputting domain\username and Outlook opens fine and is able to connect. No users are on the Exchange 2013 server yet (only 1 test account)
I've been googling all morning and I'm not seeing anything directly relating to my issue. I've read about the Anon vs Negotiate issues (KB2834139) - But - the strange thing is all clients are set to negotiate network security (And encrypt data) This
is opposite of what the MS article says. CLients are all Outlook 2010
Here are my outlook anywhere settings:
ServerName : exchange2010
IISAuthenticationMethods : {Basic}
ServerName : exchange2013A
IISAuthenticationMethods : {Basic, Ntlm}
ServerName : exchange2013B
IISAuthenticationMethods : {Basic, Ntlm}
Identity ClientAuthenticationMethod IISAuthenticationMethods
exchange2010\Rpc (Default Web Site) Basic {Basic}
exchange2013a\Rpc (Default Web Site) Ntlm {Basic, Ntlm}
exchange2013b\Rpc (Default Web Site) Ntlm {Basic, Ntlm}
If I change the Exchange 2010 server to NTLM, will this resolve what I'm seeing? And do I need to restart RPC Client Access and Transport Service to make changes take effect? Or reboot the whole server?
If you need more info or logs please let me know
Thank you for any help!
-Jeff

Hi,
Please confirm if the Login prompt issue occurs when users open the Outlook client at first time after renewing Exchange certificate or happens when opening the Outlook every time.
I noticed that the user can connect to Exchange server after inputting domain\username. Please confirm if the issue happens to external users who use Outlook Anywhere. For Outlook Anywhere coexistence,
please choose NTLM for IIS authentication.
Set-OutlookAnywhere -Identity "exchange2010\Rpc (Default Web Site)" -IISAuthenticationMethods Basic,Ntlm
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 migration and Lync server

hi guys,
i wanna upgrade my exchange 2010 to 2013 in our company.
but i faced with a question
will exchange migration has effect on Lync server an should i reinstall it again in our caompany or not?
plz help me
thanks guys

Hi,
you will need to config IM in OWA for Exchange 2013 server.As i can remember voice and everything else should be fine.
Here is a guide for enabling IM in OWA:
http://www.expta.com/2010/09/how-to-integrate-lync-server-2010-with.html
Just remember to point DNS to the New Exchange 2013 server and it should be fine.
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. Thank you! Off2work

Exchange 2013 - OWA "Something Went Wrong", Out of office in Outlook "Server unavailable"

Hi,
We have a new deployment of Exchange 2013 CU2 V2 running on a Windows 2012 server. Everything has been running without issues and then without any real clue to why, we are now getting an issue where OWA says "Something Went Wrong" after processing
your login, (it appears to process the login as if I type in incorrect details it tells me the password/username is wrong).
At the same time we have also lost the ability to run the Out Of Office in Outlook which comes back saying the server is not available and we can't seem to share calendars correctly either. (Can set Out Of Office via the Management Shell without issues).
When running a Get-Serverhealth on the OWA.Protocol it tells me the OWASelfTestMonitor is unhealthy.
I've tried re-creating the OWA, EWS Virtual Directorys and also the autodiscover but with no effect. I've also restarted the server.
Outlook 2013 and mobile phones are working fine on the server and the Exchange Admin Centre is also working without issues.
I am getting tempted to apply CU2 again to see if this sorts it but don't really like doing this on a server with 50 live users on it...
In the eventlog I can see lots of the 2 errors listed below which seems to line up. (System Log and Application Log seem to be clear of other errors or warnings.)
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 04/11/2013 11:25:00
Event time (UTC): 04/11/2013 11:25:00
Event ID: 2fcdb9112c794b63a9ea9577a23e4603
Event sequence: 2
Event occurrence: 1
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/2/ROOT/owa-411-130280378905273269
    Trust level: Full
    Application Virtual Path: /owa
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
    Machine name: SERVERNAME (I altered this for post)
Process information:
    Process ID: 9648
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
Exception information:
    Exception type: HttpException
    Exception message: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
Lots more code.......
AND
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 04/11/2013 11:24:24
Event time (UTC): 04/11/2013 11:24:24
Event ID: 2586a044b2d74b97a1095aec478bf4ae
Event sequence: 2
Event occurrence: 1
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/2/ROOT/EWS-668-130280378564324526
    Trust level: Full
    Application Virtual Path: /EWS
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\exchweb\EWS\
    Machine name: SERVERNAME (I have changed this for post)
Process information:
    Process ID: 9840
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
Exception information:
    Exception type: HttpException
Exception message: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
lots more data...

Hi Angela,
I can't see any re-directions on the website and have certainly not set any intentionally. I did try installing the Remote Web Gateway on the server and then found that it doesn't work on an exchange box and removed it but the server was working after
this.
The HTTP Redirect in Default Web Site is not showing anything set and the same for the Back End.
The bindings on the default site all look normal with;
http     80   127.0.0.1
https   443 127.0.0.1
http     80    *
http    443   *
The same is mirrored in the Exchange Back End site but with ports 81 and 444.
Running the Outlook auto configure just using Autodiscover all looks good with the URLs listed all pointing to (http)://mail.mydomain.co.uk/whatever... and the log says Autodiscover to (https)://mail.mydomain.co.uk/Autodiscover/Autodiscover.xml Suceeded
(0x00000000)
But, if I type in the OOF address of (https)://mail.mydomain.co.uk/EWS/exchange.asmx I get a login prompt but once user details are entered I then get;
'.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
   System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) +163
   System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() +7572550
   System.Xml.XmlTextReaderImpl.ParseDocumentContent() +62
   System.Xml.XmlReader.ReadToFollowing(String name) +112
   Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.ReadKillBitXmlContent(XmlReader reader, Int32& refreshRate) +185
   Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.TryReadKillBitFile(Int32& refreshRate, DateTime& lastModifiedTime) +710
   Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitTimer.Start() +202
   Microsoft.Exchange.Services.Global.Application_Start(Object sender, EventArgs e) +975
[HttpException (0x80004005): '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
   System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +12864205
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +175
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475
[HttpException (0x80004005): '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12880948
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12722137
Really wishing I had installed Exchange 2010 at this point!! Just can't see why its not working :(

Cannot access another users mailbox via OWA 2013

Hello
I have just migrated a few users from Exchange 2010 to Exchange 2013.
If I try and access their mailboxes via OWA 2013 using "open another users mailbox" I receive the following error:
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
X-OWA-Error: SDServerErr;Microsoft.Exchange.Data.Storage.AccessDeniedException
X-OWA-Version: 15.0.995.28
X-FEServer: EX2013
X-BEServer: EX2013.company.local
Date: 07/11/2014 11:23:46I can still access any mailbox on a 2010 server via the same method.
Can anyone assist in resolving this issue please?
Matt

Hi Amy,
Yes Inheritance is enabled.
Just to clarify this is affecting ALL mailboxes once moved to Exchange 2013, not specific users.
There are multiple 2013 databases all with mailboxes on. Each databases is displaying the same behaviour.
Here are the permissions I have checked so far:
ADSI Edit: CN=Databases,CN=Exchange Administrative Group (<>),CN=Administrative Groups,CN=Company
,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=localnet
The AD group has inherited Full Control on all of the database objects.
EAC: The AD group has full control on every migrated mailbox
EMS: The AD group has the following permissions on all mailbox databases:
Identity User IsInherited Deny AccessRights
MDB01 Company\AD Group True False {GenericAll}
I have removed permissions for the group and re-added them, this has made no difference.
The only way I can access any of the migrated mailboxes is to explicitly grant my account "Full Access" via the Add-MailboxPermission command.
Regards
Matt

Adding "Author" permission via OWA on Exchange 2013

Similar Messages

Maybe you are looking for