Exchange 2007 OWA with S/MIME installed Context Menu Disspear

Hi Guys,
We are experiencing the following issue with Exchange 2007 SP3 OWA when S/MIME control is installed:
Context Menu and Email Format are grey out
Does anyone know if this behavior is by design??
Best Regards
Federico Giampietri
Federico Giampietri Latamsupport IT Infrastructure Services

Hi,
I tested in my lab, Exchange 2007 SP3. The result is the same with you.
Without the S/MIME
control, Cut, Copy, and Paste from the Context Menu worked as expected and I could change email format . When I installed the
S/MIME
Control, the behavior with the Context Menu was reproducible, and email format is greyed out, but I could use Ctrl +X/C/V to cut, copy and paste.
I searched through internal channel and found this behavior is by design. However, as a workaround for choosing Cut, Copy, or Paste from the Context Menu, we can use Ctrl +X/C/V to cut, copy and paste.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Similar Messages

Exchange 2007 EXCDO 8206 error in Exchange 2007 SP2 with Rollup 4

Dear sir,
    We have a problem on Exchange 2007 Server. When user use OWA to access web mail calendar, server event log will show EXCDO error 8206:
Calendaring agent failed with error code 0x8000ffff while saving appointment
Type: Error
Event ID: 8207
Category: General.
     Moreover server becomes working in very slow web mail response during any user click web mail calendar.   Server performance return back after error message appeared in event log.
It doesn't has problem if using Outlook to access mailbox calendar.
Any suggestion to fix it ?
Joe

Hi Joe,
We are also finding the same issue with getting that EXCDO error. The problem stemmed when users noticed some previously accepted appointments disappeared (As I suspect you discovered with your users).
The workaround has been to get the user to accept the appointment again by going into deleted items, this seems to add the appointment as it should have the first time.
We have done the following but it didn't fix the problem:
Disabled extra SEP features on the clients - No Change
Disabled non-essential Outlook add-ons - No Change
Removed BES Express and CDO MAPI From Exchange server - No Change
Disabled MS Defender on Exchange - No Change
Fixed any Public folder errors - No Change
Disable Window services WSS and UNC sharing feature in Active Sync - No Change
Also ensured Autoupdate and auto process was enabled for affected users - No Change
I'm going to try the reg change mentioned in this thread but other than the built in MS Defender we don't have anti-virus on our mail server.
At first we thought it was Active Sync as it only seem to impact those with a A/S device, but now it's intermittent for other users using Outlook.  We are currently using Exchange 2007 SP3 with RU13. We are looking at trying an update
to RU14 but I am doubtful it will fix the problem. Did you have any luck finding a solution?
Thank you in Advance.

How to get current user in Exchange 2007 OWA customization page?

Hi,all
I customize an ASPX page(smsconfig.aspx) in Exchange 2007 OWA( this file in ..\Exchange\ClientAccess\OWA\smsconfig.aspx, I don't modify registry.xml & web.config).
My Exchange 2007 OWA has been configurated with Forms-Based Auth.
https://mail.myexchange.com/owa/smsconfig.aspx The page works fine, but it cannot get current logon user with HttpContext.Current.User.Identity or
UserContext.MailboxIdentity or UserContext.LogonIdentity
<%@ Page language="c#" AutoEventWireup="false" Inherits="Microsoft.Exchange.Clients.Owa.Core.OwaPage" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<%@ Import namespace="Microsoft.Exchange.Clients"%>
<%@ Import namespace="Microsoft.Exchange.Clients.Owa.Core"%>
<%@ Import namespace="Microsoft.Exchange.Clients.Owa.Premium"%>
<%@ Import Namespace="System" %>
<%@ Import Namespace="System.Data" %>
<%@ Import Namespace="System.Data.SqlClient" %>
<%@ Import Namespace="System.Xml" %>
<%@ Import Namespace="System.Collections.Generic" %>
<%@ Import Namespace="System.Text" %>
<script runat="server">
。。。(my codes in here)
</script>
thanks for your help.
Your Passion.My Potential.

Microsoft.Exchange.Clients.Owa.Core.OwaContext.Current.UserContext.LogonIdentity.PrimarySmtpAddress
Высказанное мною здесь - мои личные взгляды, а не позиции корпорации Microsoft. Вся информация предоставляется "как есть" без каких-либо гарантий.

Exchange 2007 Environment with BlackBerry Enterprise Server 5

Hi,
I am planning to migrate Exchange 2007 to 2013 DAG with BlackBerry Enterprise Server 5. For BlackBerry Users, How can I configure to work with Exchange 2013? Because Exchange 2007 works with MAPI for BES but 2013 with RPC/HTTPS.
Do I need to set up new BlackBerry Server? Please advise
Regards,
Zaw Tun Naing
ZAW

Have a look in the Blackberry
KB33413.
As stated in this blog this seems to be an "all or nothing for BB mailboxes". So if you plan to migrate slowly it would be the best to install
another BB Server.

Unable to insert hyperlinks in Exchange 2007 OWA messages

Hi, we have recently moved to Exchange 2007 OWA and users are unable to insert links to shared files on the network. I was wondering if there might be something in our Windows 7 GPO that is preventing this from happening?

do you mean they cannot see the network path or that they are not able to type
\\networkshare\share ?
If first one,please check Outlook Web app policy and enable/customize Direct file Access.
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

How to configure Exchange 2013 OWA with Single Sign On

Hi All ,
How to configure Exchange 2013 OWA with Single Sign On ?
Thanks .

Hi,
From your description, I am not quite sure what you really want to achieve. Could you explain it furthermore? If you need to set up Exchange 2013 OWA single sign on with Exchange 2010, here is a helpful thread for your reference.
Exchange 2013 OWA Single Sign on with Exchange 2010
https://social.technet.microsoft.com/Forums/en-US/2899ebfc-8622-4cdc-8d77-d76b607618f7/exchange-2013-owa-single-sign-on-with-exchange-2010?forum=exchangesvrdeploy
If that is not your case, please feel free to tell me.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange 2007 OWA Error after installing Service Pack 3 (MSExchange OWA event 65)

Hi everyone, I have multiple servers in Exchange 2007 SP1, Windows Server 2003 SP2 64bit.
I installed SP3 and RU15 a CAS / HUB server and now I access OWA, showing the below error:
Outlook Web Access did not initialize. There has been an event for the system administrator can resolve the problem. Contact the support of the organization.
Object reference not set to an instance of an object.
Request
URL: https: // mailserver01: 443 / owa / auth / error.aspx url = https: // mailserver01 / owa / & reason = 0
Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: Object reference not set to an instance of an object.
Call stack
in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager () in Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication () in Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart (Object sender,
EventArgs e)
Inner Exception
Exception type: System.NullReferenceException
Exception message: Object reference not set to an instance of an object.
Call stack
in Microsoft.Exchange.Clients.Owa.Core.Configuration.CheckPublicFolders (ADSystemConfigurationSession session, ADObjectID [] pfdbIds, Boolean & allLegacy, Boolean & allLater) in Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor (ADSystemConfigurationSession
session, String virtualDirectory , String WebSiteName, ADObjectID distinguishedName, Boolean isPhoneticSupportEnabled) in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration () in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager
In server events next event is logged
Event Type: Error
Event Source: MSExchange OWA
Event Category: ADNotifications
Event ID:. 65
Date: 12/27/2014
Time: 7:20:54
User: Not available
Team: mailserver01
Description:
There was an error loading the configuration parameters of Outlook Web Access. Virtual directory "owa". Website: "Default Web Site".
Error message:
"Object reference not set to an instance of an object."
HOW CAN I SOLVE THIS?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hello
everyone,
thank you
for
answering,
finally
opened
with
Microsoft
support
case
and
showed
me
that
delete
servers
from
ADSEDIT.
I deleted
the
servers
that
should
not
be
and
immediately
everything
started
to
work
properly
Many
thanks to
all
for
the
help
Microsoft Certified IT Professional Server Administrator

Cannot connect to OWA after Exchange 2007 SP3 and Rollup 13 install.

Hi,
Our OWA website isn't accessible after we installed SP3 and rollup update 13 for Exchange 2007. When we attempt to visit the OWA URL, all we receive is HTTP 403.4 SSL is required to view this resource. Doug

Hi,
I recommend you follow the steps below for troubleshooting:
1. Open IIS Manager, click Default Web Site -> Authentication, make sure that Anonymous Authentication and Windows Authentication are enabled.
2. Click Default Web Site -> SSL Settings, check "Require SSL" and click Ignore.
3. Click Default Web Site -> HTTP Redirect, check Redirect (enter your
https://URL), check "Only redirect" box and Status code Found 302.
4. Expand Server Configuration -> Client Access ->double click owa ->Authentication tab. Check the Basic Authentication and check the Use forms-based authentication button Logon Format: Domain\user name.
What's more, here is a thread for your reference.
Exchange 2007 SP3 Rollup 2 installed - OWA stopped working
http://social.technet.microsoft.com/Forums/en-US/8481eb3d-a6ab-42fc-b7ea-fa9a9a625e48/exchange-2007-sp3-rollup-2-installed-owa-stopped-working?forum=exchangesvrdeploylegacy
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

OWA functionality in Exchange 2007 coexistance with 2013

I have conexistance environment with Exchange 2007 and Exchange 2013. Out of about 1200 users we have 25 test users in the 2013 environment. The problem we are seeing is when a 2013 mailbox has "Full Access" to a 2007 mailbox and tries to connect
to that mailbox through OWA 2013 the connection always fail. I can attach the mailbox in Outlook with no problems but cannot open that mailbox through OWA 2013. Any thought?

See if this helps. It's not an exact match for your versions, but I think it's what you need to look at.
http://support.microsoft.com/kb/981541
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2007 SP1 with GoDaddy Cert - iPhone cannot verify cert

Hi Everyone,
My school has just moved to Exchange 2007 and I'm trying to connect my iPhone to it. We haven't changed any settings on the Exchange server really that relates to ActiveSync (at least as far as I can tell). We're using a GoDaddy wilcard SSL cert with the site for OWA and (I hope) ActiveSync.
From what I can see, Apple has included all of the GoDaddy Intermediate and Root certs in OS 3. I have manually installed these certs again on my iPhone (the one I'm testing with) by emailing them to myself. This hasn't helped with the issue...
When trying to add the Exchange account on the iPhone I'm getting an "Unable to Verify Certificate" error. The error makes no mention of autodiscovery (which it should be using), so I'm not sure if it has anything to do with that. I'm really not sure what to do at this point since we're all new to Exchange, and I only have used my iPhone through Exchange with Google in the past.
Thanks,
-MRCUR

Ever hear anything back on this? I too have an iPhone (3G) and would like to connect it to a GoDaddy Exchange server. No luck so far.

Exchange 2007 OWA sends attachments Outlook connector clients cannot send attachments.

Exchange Server 2007 SP1 + Rollup ***Problem with sending email attachments from Outlook 2007***
* Inbound mail arrives in OWA and Outlook normally with and without attachments.
* OWA email to external email account with attachment goes thru successfully.
* Outlook 2007 sends to an external email address with attachments the message does not arrive at the external mailbox. The messages leave Outbox but are never delivered. The messages appear in Sent Items also.
* Outlook sends non attachment emails to external addresses successfully.
* Outlook sends email attachments to local domain accounts fine.
#1 Exchange Server on Server 2013 fully patched problem commences. Exchange Server on version less than first RTM release of Exchange 2007.
#2 Outlook profiles were changed to see if that is the problem.
#3 Upgraded Exchange to SP1 and Rollup 10(Rollup was autodownloaded by MSUpdate)
#4 Ran EXBPA nothing of any interest in the report.
--Unified Messaging not configed (Done nothing)
--SenderID (Re-enabled) I had shut all of the antispam to eliminate these.
-- Junk Store threshold not configed (No change)
Any suggestions to get Outlook clients capable of sending attachments configured.
Thx,
-Scot

Hi Scot,
Providing some information on Poison Queue:
The poison message queue is a special queue that's used to isolate messages that are determined to be harmful to the Exchange system after a transport server or service failure.
The messages may be genuinely harmful in their content and format.
Alternatively, they may be the results of a poorly written agent that has caused the Exchange server to fail when it processed the supposedly bad messages.
The poison message queue is typically empty. If the poison message queue contains no messages it doesn't appear in Queue Viewer or
Get-Queue results. The messages in the poison message queue are never automatically resumed or expired. Messages remain in the poison message queue until they're manually resumed or removed by an administrator.
According to the description above, I suspect Outlook 2007 changed the email's format when send email with attachment. The reason as below:
If the original email's (with attachment) content or format is harmful to the Exchange 2007 server, it will go to the Poison Queue when sending via OWA. However it didn't, sending via OWA is perfect. So I suspect it is an issue on the Outlook 2007
client side.
Please using Pipeline Tracing to verify whether there is something changed during transmission.
More details in the following article:
Using Pipeline Tracing to Diagnose Transport Agent Problems
http://technet.microsoft.com/en-us/library/bb125198(v=exchg.80).aspx
If it is convenient, I suggest doing following tests to narrow down this issue:
Note: Same content, same attachment, same format.
1. Please using Outlook 2010/2013 or others' Outlook clients for testing.
2. Please change to another format for testing. More details in the following article:
Change the message format to HTML, Rich Text, or plain text
http://office.microsoft.com/en-001/outlook-help/change-the-message-format-to-html-rich-text-or-plain-text-HP001232996.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Need help on Cross Forest Exchange 2007 - 2013 with Linked Mailboxes

Hey all,
So I'm in a bit of a pickle with my Exchange design and am trying to figure out if there's a way to migrate mailboxes across forests where Linked mailboxes are being used. I've done a bit of reading and have noted stuff like preparing the move request in
AD, etc. But I'm wondering if someone can break it down for me.
http://1drv.ms/1lWjLqG
The above is a OneNote diagram of how we have moved over time. Please forgive my sloppy handwriting but I hope it gets the point across. I will text it out here as well:
Original Design
The original design of the domains when I joined the company were fabrikam and contoso. Contoso is a domain that sits entirely in the "DMZ". Fabrikam was the internal AD forest where most services and users authenticated to. In Contoso, there
are 2 domain controllers, the "Front End" Exchange Server (Edge Transport), and the "Back End" server, which is CAS/Mailbox.
There is a forest trust between contoso and fabrikam where "Linked Mailboxes" are created in Contoso, and then the LinkedMasterAccount is set to Fabrikam.
Migration/Hybrid Design
Due to the fact that these two domains were configured massively inappropriately, riddled with security holes as well as strange permissions configurations, the decision was made to create a new internal AD domain. In my OneNote, I've labeled this 'specialbank.com'.
A long while ago we migrated users from Fabrikam to SpecialBank via trusts. To facilitate access to Exchange, a new trust was created between Contoso and SpecialBank to allow us to update the LinkedMasterAccount parameter to the new Specialbank domain.
We have most of our users authenticating to their mailboxes via SpecialBank, while the mailboxes still reside in Contoso.
Migration from Exchange 2007 to Exchange 2013
I am attempting to now figure out the best way to migrate the mailboxes from Contoso to a new set of Mailbox servers in SpecialBank. This will also be an upgrade from Exchange 2007 (Current) to an Exchange 2013 installation.
The latest Service Packs and CUs are installed in both.
What would be the best procedure to move these mailboxes? To my knowledge, the current best practice/recommended way is to perform a user/SID migration from Contoso to SpecialBank. But I already have accounts in
SpecialBank that users are actively using.
I'm not opposed to doing a simple PST export from Contoso to SpecialBank, but we're looking at around 120 mailboxes. So I'm trying to make my life a little easier instead of spending a weekend here.
If I try to do it in batches, I need to figure out how to handle autodiscover and CAS. Since I'm creating an entirely new Exchange environment, I'm trying to limit what I place in the existing configuration. But I'm not opposed to setting up something temporarily
if I need to in order to make the migration transparent to users.
Can anyone help?

Hi ,
From you description i came to know contoso is the resource forest and special bank is the account forest .
You just wanted to migrate the linked mailboxes from resource forest to account forest and also you would want the migrated mailboxes to get merged to the respective user accounts in the account forest to become as a normal user mailbox.Am i right ?
Please correct me if i am wrong . I have found some blogs in internet please have a look in to that especially the first one.
http://www.outlookforums.com/threads/60210-cross-forest-mailbox-move-and-linked-mailbox/
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27974905.html
Regards
S.Nithyanandham
Thanks S.Nithyanandham

How to export an exchange 2007 owa certificate from production to lab environment

I'm setting up an Exchange 2007 Lab but I have a trouble regarding exchange's certificate
Note: My lab environment is not conected to internet
I've followed the next link but it doesn't work
https://www.digicert.com/ssl-support/pfx-import-export-exchange-2007.htm
Once I finished all the steps if I run the next powershell command get-excahangecertificate I see that my exchange certificate has the status as unknown
I'm not sure if the problem is related with the server is not conected to internet, so exchange is not be able to check the status of the certificate.
I've tried to turn off the Check for publisher’s certificate revocation option on the server
To do this, follow these steps.
Start Internet Explorer.
On the Tools menu, click Internet Options.
Click the Advanced tab, and then locate the Security section.
Click to clear the Check for publisher’s certificate revocation check box, and then click OK.
After the update rollup installation is complete, turn on the Check for publisher’s certificate revocation option.
But it still not working
Could anyone help me?
Thanks in advance

Hi Pardo,
According to your description, I understand that the exchange certificate cannot work and display unknown status after import it.
If I misunderstand your concern, please do not hesitate to let me know.
Depending on the results of “Get-ExchangeCertificate | FL”, please pay attention to following points:
1. RootCAType: Registry
“An internal, private PKI root CA that has been manually installed in the certificate store.”
2. Status: Unknown
“This status generally indicates that the status of the certificate cannot be verified because the certificate revocation list (CRL) is unavailable or this server cannot connect to it.”
The reason why it failed is that internal Exchange server cannot connect to CRL. As you mentioned, exchange can’t be able to check the status of the certificate.
More information about Certificate Use in Exchange Server 2007, please refer to
Certificate Fields and Configuring Access to the Certificate Revocation List
section in below link:
http://technet.microsoft.com/en-us/library/bb851505(v=exchg.80).aspx
However, we can renew a certicate from local CA:
http://technet.microsoft.com/en-us/library/bb310781(v=exchg.80).aspx
Best Regards,
Allen Wang

Upgraded to Exchange 2007 - Problems with opening attachments in e-mail Treo700wx

We upgraded our server at work to Exchange 2007. Ever since then, there have been multiple problems, on of which I am not able to open pdf files, excel or word files on my handheld 700wx. Anyone else have this problem. Talked with Verizon, they suggested downloading a new version of the pdf viewer. That didn't work. Looking for any suggestions.
Post relates to: Treo 700w (Verizon)

Hello!
Since your company is now using 2007, good chance you will need a Windows Mobile 6 and up phone. Please install this update to get your phone to windows mobile 6.0:
http://kb.palm.com/wps/portal/kb/common/article/10133_en.html
Be sure to follow the instructions on the page.

Exchange 2007 - Outlook Anywhere problems after installing new SSL cert

*** Original thread posted on wrong forum ***
Hi all,
Exchange 2007 environment (2x CAS, ISA2006). Not much familiar with Exchange.
Problem: 20-odd machines off the domain use Outlook Anywhere (XP with Outlook 2010). AUthentication pop-up and not able to connect.
Company has recently changed its name and we have to renewed the SSL cert. Previous SSL cert. was issued to: webmail.oldcompname.co.uk (several SANs on that cert., including internal server names).
Applied for a new UCC SSL cert issued to: newcompanyname.com (also includes webmail.newcompanyname.com ; autodiscover.newcompanyname.com + old SANs).
The setting on those machines point the proxy to the following:
Https://webmail.oldcompname.co.uk (which is fine since it is in the cert and can be accessed)
Only connect to proxy servers that have this principal name in their cert.:
msstd:webmail.oldcompname.co.uk (I believe this is the problem since the new UCC SSL cert. was issued to newcompanyname.com).
Browsing technet + internet it seems that I need to look into OutlookProvider EXPR.
When I run Get-OutlookProvider everything is blank (I believe I should be concerned to EXPR only for Outlook Anywhere).
I am thinking of running: Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:newcomanyname.com
My only concern is whether this might break something else in the Exchange environment, especially as we have 100+ users on smartphones connecting via SSL on webmail.oldcompname.co.uk
Is it save to run this command? Do I need to re-start IIS? Do I need to look into any settings on ISA2006?
Comments/help are much appreciated.
Regards

Hi,
According to the description, I found that we re-new a SSL certificate.
"I am thinking of running: Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:newcomanyname.com"
Just do it. Then remove the old certificate on ISA server and install a new one.
Found a similar thread for your reference:
Renewal of SSL certificate in exchange 2007 with ISA 2006
http://social.technet.microsoft.com/Forums/exchange/en-US/25770038-8491-470a-92fa-8ae50674b7a6/renewal-of-ssl-certificate-in-exchange-2007-with-isa-2006
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2007 OWA with S/MIME installed Context Menu Disspear

Similar Messages

Maybe you are looking for