Outlook 2013 SP1 S/MIME signature requires entering password twice

Since updating to Outlook 2013 SP1, every time I send an S/MIME signed email I'm prompted for the password twice. Prior to SP1, I was prompted once per email (I have PrivKeyCacheMaxItems=0, as I do want to be prompted for each email). Has anyone else
experienced this behavior? Is this a bug in SP1 or is there a configuration change to get the "once per email" behavior back?
Outlook 2013 (15.0.4569.1503) MSO (15.0.4569.1506) 64-bit.
Windows 7 Ultimate SP1 w/ all Microsoft Update patches.

As I remember, we don't need to type any password when we send an S/MIME signed email. Could you help to show the titile of pop-up windows? Better to capture a screenshot and post here.
By the way, does it happen in a new creating profile. And I've never heard the service pack 1 would be the root of this issue. Remove the SP1 to check if the issue would be gone in your machine if necessary. Thanks.
Tony Chen

Similar Messages

Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
Error look like - cannot find exchange server.
I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
Someone have the same problem with migrated mailbox? How to solve it?
Truly, Valery Tyurin

You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
Moreover, you can try this utility (
http://www.exchangemigrationtool.com/ ) to accomplish this task.

Links Don't Work in Contact Card (people view) Outlook 2013 SP1

I have Office Professional Plus 2013 SP1 x64 installed. When viewing contacts in "People" view, none of the links in blue work. For example, clicking on the "Schedule a meeting" blue link under Calendar or "Outlook (Contacts)"
blue link under View Source doesn't do anything.
I have uninstalled and re-installed. Also tried a new domain user (new profile) and same result. This is specific to this computer, as this works normal with the same user accounts on other PC's.
Any ideas on how to fix this? Or what mechanism is broken?
Thanks!

Hi,
Since you mentioned the issue persists when logging on the PC with a new account, I think there should be something wrong with the Office installation. I suggest you run Office Configuration Analyzer Tool to get a report of the installed Office Programs:
http://support.microsoft.com/kb/2812744/en-us
The report you can get includes many parameters about your Office program configuration. It also highlights known problems that are found when OffCAT scans your computer. For any problems that are listed in the report, you are provided a link to a public-facing
article (usually a Microsoft Knowledge Base article) about each problem so that you can read about possible fixes.
Let me know if there you can find any problems about Outlook.
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

After modifying an appointment with Outlook 2013 SP1 CU 10/14 or higher it cannot be read via WebDAV anymore

Hi,
we use WebDAV to read appointments from Exchange Server 2007 SP3 CU. When we modified an appointment with
Outlook 2013 CU 09/14 we experienced that we could not query it with the filter BillingInformation<>"" anymore.
With the Outlook 2013 CU 10/14 this temporarily fixed, but reocurred last week. It does not happen with Outlook 2010 SP2 (14.0.7113.500) or other versions of Outlook.
How can we tackle this?
Thanks for any advice
John
John

Hi,
we use WebDAV to read appointments from Exchange Server 2007 SP3 CU. When we modified an appointment with
Outlook 2013 CU 09/14 we experienced that we could not query it with the filter BillingInformation<>"" anymore.
With the Outlook 2013 CU 10/14 this temporarily fixed, but reocurred last week. It does not happen with Outlook 2010 SP2 (14.0.7113.500) or other versions of Outlook.
How can we tackle this?
Thanks for any advice
John
John

Need to enter password twice to login (when using lightdm)

Hi!
I need to enter my password twice before I can login (note that I need to enter it correctly both times). After the first time, the screen goes blank for a second and then returns to the login screen.
I'm using the latest versions lightdm 1:1.10.1-2 and lightdm-gtk2-greeter 1:1.8.4-2 (and I'm logging into an Xfce session).
The relevant part of /var/log/lightdm/lightdm.log is:
[+11.38s] DEBUG: Session pid=345: Started with service 'lightdm', username 'test'
[+14.95s] DEBUG: Session pid=313: User test authorized
[+15.03s] DEBUG: Session pid=345: Running command /etc/lightdm/Xsession startxfce4
[+15.04s] DEBUG: Session pid=345: Logging to .xsession-errors
[+15.29s] DEBUG: Session pid=345: Exited with return value 0
[+15.71s] DEBUG: Seat: Active display server stopped, starting greeter
[+15.71s] DEBUG: Seat: Creating greeter session
This shows that the sessions quits after .26 seconds after running and returns to the greeter. The second time I log in it appears to work fine.
I have already reported this bug to the lightdm development team (https://bugs.launchpad.net/ubuntu/+sour … ug/1333538), but I'm thinking that it might be an Arch-specific issue. My ~/.xsession-errors contains many lines stating that xfdesktop is trying to start, but it is already running:
xfdesktop[2276] is already running; assuming --reload
** (xfdesktop:2274): WARNING **: xfdesktop: already running, quitting.
xfdesktop[2277] is already running; assuming --reload
xfdesktop[2282] is already running; assuming --reload
xfdesktop[2285] is already running; assuming --reload
xfdesktop[2284] is already running; assuming --reload
xfdesktop[2275] is already running; assuming --reload
xfdesktop[2279] is already running; assuming --reload
xfdesktop[2280] is already running; assuming --reload
xfdesktop[2283] is already running; assuming --reload
xfdesktop[2278] is already running; assuming --reload
xfdesktop[2281] is already running; assuming --reload
xfdesktop[2286] is already running; assuming --reload
xfdesktop[2298] is already running; assuming --reload
xfdesktop[2297] is already running; assuming --reload
xfdesktop[2296] is already running; assuming --reload
xfdesktop[2303] is already running; assuming --reload
xfdesktop[2288] is already running; assuming --reload
xfdesktop[2290] is already running; assuming --reload
xfdesktop[2293] is already running; assuming --reload
xfdesktop[2307] is already running; assuming --reload
xfdesktop[2302] is already running; assuming --reload
xfdesktop[2292] is already running; assuming --reload
xfdesktop[2300] is already running; assuming --reload
xfdesktop[2304] is already running; assuming --reload
xfdesktop[2305] is already running; assuming --reload
xfdesktop[2306] is already running; assuming --reload
xfdesktop[2308] is already running; assuming --reload
xfdesktop[2314] is already running; assuming --reload
xfdesktop[2321] is already running; assuming --reload
xfdesktop[2309] is already running; assuming --reload
xfdesktop[2312] is already running; assuming --reload
xfdesktop[2335] is already running; assuming --reload
xfdesktop[2311] is already running; assuming --reload
xfdesktop[2339] is already running; assuming --reload
xfdesktop[2327] is already running; assuming --reload
xfdesktop[2338] is already running; assuming --reload
xfdesktop[2334] is already running; assuming --reload
xfdesktop[2337] is already running; assuming --reload
xfdesktop[2341] is already running; assuming --reload
xfdesktop[2346] is already running; assuming --reload
xfdesktop[2343] is already running; assuming --reload
xfdesktop[2350] is already running; assuming --reload
xfdesktop[2347] is already running; assuming --reload
xfdesktop[2349] is already running; assuming --reload
xfdesktop[2356] is already running; assuming --reload
xfdesktop[2351] is already running; assuming --reload
xfdesktop[2361] is already running; assuming --reload
xfdesktop[2359] is already running; assuming --reload
xfdesktop[2362] is already running; assuming --reload
xfdesktop[2363] is already running; assuming --reload
xfdesktop[2364] is already running; assuming --reload
xfdesktop[2369] is already running; assuming --reload
xfdesktop[2366] is already running; assuming --reload
xfdesktop[2371] is already running; assuming --reload
xfdesktop[2367] is already running; assuming --reload
xfdesktop[2376] is already running; assuming --reload
xfdesktop[2372] is already running; assuming --reload
xfdesktop[2375] is already running; assuming --reload
xfdesktop[2377] is already running; assuming --reload
xfdesktop[2379] is already running; assuming --reload
xfdesktop[2381] is already running; assuming --reload
xfdesktop[2378] is already running; assuming --reload
xfdesktop[2380] is already running; assuming --reload
xfdesktop[2382] is already running; assuming --reload
xfdesktop[2383] is already running; assuming --reload
xfdesktop[2384] is already running; assuming --reload
xfdesktop[2385] is already running; assuming --reload
xfdesktop[2386] is already running; assuming --reload
xfdesktop[2387] is already running; assuming --reload
xfdesktop[2390] is already running; assuming --reload
xfdesktop[2388] is already running; assuming --reload
xfdesktop[2389] is already running; assuming --reload
xfdesktop[2391] is already running; assuming --reload
xfdesktop[2393] is already running; assuming --reload
xfdesktop[2394] is already running; assuming --reload
xfdesktop[2392] is already running; assuming --reload
xfdesktop[2395] is already running; assuming --reload
The problem does not occur when using GDM instead of lightdm. I'm grateful for any hints that point me in the right direction to solve this issue - thanks!

cle1109 wrote:I have already reported this bug to the lightdm development team (https://bugs.launchpad.net/ubuntu/+sour … ug/1333538), but I'm thinking that it might be an Arch-specific issue.
This happens on all of my school's Ubuntu 12.04 computers and has for two years.

Have To Enter Password Twice to Log In to Snow Leopard on my iMac

*Why Do I Have To Enter My Password Twice to Log In to Snow Leopard on my iMac?*
It just started happening a couple of weeks ago but I have no idea what I changed at that point.
There's a normal login screen where you can choose a user and enter a password. Then it goes to a completely blank screen for a few seconds and the same login scree reappears and I have to choose the user and enter the password again. Then it logs in.
What is going on? HOw do I fix it?
(please note that I do not want automatic login to one of the user accounts - I want to use this as a protection against access to my computer should someone steal it etc...)
Thanks

What do you mean a "more fuller update" from software update? Do you mean the updates I automatically get from apple software update are not actually the latest snow leopard updates? I'm very confused.
No that is not what I was saying. Read all about the Snow Leopard combo update for yourself - http://support.apple.com/kb/DL1324
they're generally pretty useless and typically solve most problems by saying to reinstall everything.
That has never been my experience with Apple Care the few times I have used it.
This may be a user forum, but I'm pretty confident there are Apple staff helping people out on here.
Not the case here. Hate to bust your confident bubble. These forums are strictly user to user.
"Apple staff" do chime in from time to time in the Feedback forum area if you are having problems with the discussion website. Never for technical issues. Read the Terms Of Use.

Safari 3.2.1 and hotmail, I have to enter password twice, every time

The title says it all, this has been going on for months. I go to the hotmail login page entering everything correctly but hotmail will say password incorrect enter the same details again & I'm in.
Emptying the cache makes no difference.
Any ideas ?

Hi
This may be an issue due to your Internet Provider or corrupt cookies.
Let's try the Cookies side first. Open Safari. Safari Preferences>Security>Show Cookies. enter live.com in the spotlight panel. Remove the hotmail cookies that appear.
Close the panel and try logging on to Hotmail.
If no go, first go to the Hotmail log-in screen, Next in the Develop Menu (if one doesn't appear in your Menu Bar, go to Safari Preferences>Advanced panel and activate it at the bottom of the panel) go to the User Agent and change it to Firefox. Now log-in to your account.
Another alternative I've seen for working around this problem is to signing out first on http://mymsn.com (create a bookmarks bar entry for easy access to that page), then go to the HotMail page and log-in.
Hot Mail has historically been a bit of a flake in the web mail domain. Many have switched to G-Mail. consider doing the same.

Exchange 2013-SP1/Outlook 2013 connectivity issue.

We couldn't make Outlook 2013 (latest updates) to connect to our Exchange 2013-SP1 through the Internet.
Any PC inside the LAN (on the domain or outside the domain) can connect normally.
Any PC outside the LAN (WAN) cannot connect, it keep showing this error:
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
OWA is working fine from the WAN, smartphones (Android & Apple) are also working fine from the WAN.
Port 443 is open on the firewall.
So what we are missing!

Hi,
Firstly, I'd like to say, in Exchange 2013 SP1, Outlook 2013 SP1 clients may use MAPI over HTTP to connect to the server.
Before going further, let's confirm if they use MAPI over HTTP: Get-OrganizationConfig | FL MapiHttpEnabled
If the value of the above property is true, I recommend the following troubleshooting:
1. Check if your Exchange 2013 SP1 server is running on Windows Server 2012 R2.
2. Check MAPI virtual directory settings: get-MapiVirtualDirectory |fl
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Outlook 2013 client, not in domain, can't connect to the Exchange 2013 server.

Hello everyone,
A colleague and me are in the process of rebuilding our Hosted Exchange servers. Everything is working perfectly except for the local Outlook 2013 clients. They are not in the domain but in the same network (through VLANs) as our Exchange server, and still
they can't connect to Exchange without the use of Outlook anywhere. If we use Outlook Anywhere, it connects perfectly. If I ping the Exchange servers (1 CAS, 2 MBX servers) I get response with the right IP addresses.
We've tried to create a new profile, this goes without problems. We enter the FQDN (or IP address) of CAS server and the required usersname, and the FQDN gets resolved to the correct MBX server where the mailbox resides on. We complete the whole wizard and
then start Outlook. We then get the error that Outlook can't logon to the Exchange server.
Is this an authentication setting that is wrong or do we need to use Outlook Anywhere if the PC is not in the same domain as the Exchange server?
Thanks in advance!

Hi,
Agree with Martina, all Outlook clients use RPC over HTTP to connect to Exchange 2013. if the server version is Exchange 2013 SP1, only Outlook 2013 SP1 use MAPI over HTTP to connect to server after we enable the protocol MAPI over HTTP.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

MAPI over HTTP not working correctly, Outlook 2013 clients prompting for credentials during profile creation or opening depending on security of virtual directory

ENVIRONMENT
-1 Exchange 2013 SP1 CU7 server with all roles that is also a hybrid server with Office 365 tenant, mailboxes are all on premise only LYNC online is being utilized right now.
-Exchange 2013 public folders
-Mix of Outlook 2013 SP1 and Outlook 2010 SP3 clients all fully update to day as of Feb 2015
Outlook anywhere is working perfectly across all clients both internally and externally using autodiscover. Both Outlook 2013 and 2010 clients can open the program and create a profile automatically via autodiscover and no additional logon prompts
are seen.
We set the internal and external mapi virtual directory URLs to a valid URL that also matches the Exchange 2013 SSL certificate. We set the security to ntlm, negotiate on the mapi virtual directory. We reset IIS and enabled mapi over http in
the org config. We run in to problems here.
Outlook 2010 clients appear to be working fine. We can create a new profile and open and close Outlook without any logon prompts and verify that MAPIHTTP and Negotiate are used to connect to Exchange.
Outlook 2013 clients are having problems. As soon as we try to create a profile it says your administrator has made a change that requires you to restart outlook and then a windows logon prompt appears. If we authenticate Outlook will open and connect.
This logon prompt should not occur. We can confirm that it is connecting via MAPI HTTP and Negotiate.
If we set the mapi virtual directory to NTLM only then a logon prompt also appears during every open of Outlook 2013. We can confirm that it is trying to connect with MAPIHTTP via NTLM in the outlook connection test screen.
I do not understand this behavior by Outlook 2013 which was supposed to be designed with MAPI HTTP in mind. I would think the same issues would occur with Outlook 2010 but they do not. I am not sure how to resolve this and I am looking for help.

I have the same problem. Exchange and Outlook are both up to date. After creating a new profile Outlook prompts for username/password. A lot of users also get this prompt while
working - the profiles have been "migrated" from Exchange server 2010. <o:p></o:p>
Niko, as i can see in your screenshot you do not have Mapi over HTTP enabled. Why? You can change settings in the security tab – if you have Mapi over
HTTP enabled all options are grayed out (please correct me if I
am wrong):
This is a very annoying thing – does anybody else have the same problem?
Any suggestions on this?
Marc

Outlook 2013 sending email using template not working properly...

I've created several email templates by doing the following:
open new message
add some tekst in the body
save as > oft file
Now when I open such oft file I add some modifications in the body text and send the message. However, the send item does not contain the modifications I just made, only the text that was included in the template.
We're using Outlook 2013 SP1 (with all microsoft updates installed) with Exchange 2013 SP1 standalone server. Is this a Outlook or Exchange issue and how can I resolve this?
Thnx Remco

Hi Remco,
Please also try to start Outlook in safe mode and test again to check if this issue continues. To start Outlook in safe mode, press Windows key + R to open the Run command, type
outlook /safe and press Enter.
If problem continues in Outlook safe mode, please try creating a new mail profile and reconfigure your email account, then creating a .oft template to test this issue again. For your convenience:
http://office.microsoft.com/en-in/outlook-help/create-an-outlook-profile-HA102749460.aspx
Please let me know the result.
Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Exchange 2013 CU7 - Frequent Outlook 2013 Disconnections and Delays

We currently have the following environment:
Windows 2012 VM on Hyper-V with 24GB of RAM and 4 virtual procs (1 socket)
Cisco UCS, B200 M3 Blades
Exchange 2013 CU7
Exchange 2007 is in our environment, but public folders have been removed and only a few stale, unused accounts exist on it.
Two dual-role CAS/Mailbox servers
Mailbox servers are in a DAG
MAPI/HTTP is our connection protocol
.NET Framework 4.5.2
Clients are Outlook 2013 SP1 on Windows 7 and 8.1
(Currently round robin DNS, but we have a hardware load balancer we've temporarily taken out of the mix to solve this problem)
What we're seeing is frequent disconnections from Exchange, regardless of the CAS server. That is, both CAS servers will disconnect clients, but not at the same time. When we look at the Exchange boxes, we notice that the CPU is 99% - 100% each time the
disconnections occur. When we hunt down the IISWorker process causing the sudden CPU run, we see it comes back to the following app pools:
MSExchangeMAPIFrontEndAppPool
MSExchangeMAPIMailboxAppPool
(We were running RPC/HTTP, but switched to MAPI/HTTP to resolve the problem. We had the same issue with equivalent RPC app pools at the time.)
Eventually, within a minute or two, the CPU load will decrease and the clients connected via that CAS will regain connection. As you can imagine, the pain is felt more frequently by uncached clients--although everyone, regardless of caching, will see
the disconnections.
Basically, the problem sounds exactly as shown in this KB: http://support.microsoft.com/kb/2995145 Unfortunately, we already had .NET 4.5.2 installed, and have changed the environment variable and registry as shown in the article.
We're in contact with Microsoft Support, but thus far they're scratching their heads.
I'm clearing up all small errors to decrease the noise in the application error logs, but the most persistent one is Event ID 106 (MSExchange Common):
"Performance counter updating error. Counter name is Time in Resource per second, category name is MSExchange Activity Context Resources. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: Instance 'ad-powershell-defaultdomain'
already exists with a lifetime of Process. It cannot be recreated or reused until it has been removed or until the process using it has exited."
Loading/reloading and recreation of the performance counters does not fix the problem, by Microsoft Support or us. Of course, this error existed before we started having issues; I'd just like to clean it up just in case it's a contributing factor.
Has anyone seen anything similar?

We're using a Barracuda load balancer (641), but we've eliminated that as a source of the problem. The CPU spikes and disconnections happen whether or not the load balancer is in use.
This problem is still ongoing, and we're still working with Microsoft Support. Right now they're focused on our environment, but having combed through it numerous times, there's nothing that stands out. I suspect this is a bug in CU7 (yet I would
readily accept our environment being at fault if it means we can identify and resolve the problem), but that's not the road Support is going down.
We've looked at storage I/O on the VM hosts (disk responses are 10 MS or less), added double the CPUs to each mail server (for a total of 8, each), disabled TCP chimney offload, run numerous Experfwiz log collections, etc... Now
the tech is focused on a particular mailbox database being the culprit because it also takes up more CPU when the MAPI app pools are gunning pretty high. I suspect that it is a symptom and not the problem, but I have no choice but to follow his lead.
What is your environment like? Are you also CU7? And did the problem show itself after a cumulative update was applied?

Outlook 2013 IMAP account company issue. When i read an email and scroll to other email , previous email goes again to Unread.

Outlook 2013 Sp1 IMAP company account issue. When i read an email and scroll to other email in reading pane opens the 2nd message in the mean time 1st email again goes to Unread (format highlighted again as unread email) or sometimes it remain as
read message.

Here is my code and what is strange, there are incoming mails (I see them at upper corner and at inboxes) with zero recipients, giving me the message below. So I will give up and change ,at Outlook accounts configuration ",display names"
to the valid address names (ie Instead Manuel Costa I will put
[email protected]), so I can use the mail.To property!
private string GetSenderSMTPAddress(Outlook.MailItem mail)
               string smtpAddress = "";
               if (mail.Recipients.Count > 0)
                   string teste = OlMailRecipientType.olTo.ToString();
                   foreach (Outlook.Recipient recip in mail.Recipients)
                       Outlook.AddressEntry entry = recip.AddressEntry;
                       if (entry.Type == "EX")
                           smtpAddress = GetSMTPAddressViaOutlookObjectModel(entry);
                   return smtpAddress;
               else
                   MessageBox.Show("no recipients");
                   return "";
Thanks anyway Eugene

Exchange 2013 SP1 users randomly prompted with "The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook"

I got a call to check an issue with a Exchange Server 2013 SP1 environment recently. All server was upgraded from Exchange server 2013 CU2 to Exchange Server 2013 SP1. It was done successfully but many users were being randomly prompted with a popup in their outlook
client with the following message:-
“The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook”
Although there wasn’t any changes of late in the environment there were random popups like these for multiple users. As the behaviour was not consistent and effecting the entire upgration population
Please suggest us how to resolve the issue.
Regards, Md Ehteshamuddin Khan All the opinions expressed here is mine. This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

Hi,
Does the issue happen to all Outlook 2013 users? Please create a new Outlook profile to have a try.
If it fails, please check the msExchHomePublicMDB value in ADSI Edit:
1. In Adsiedit, expand Configuration-->CN=Services -> CN=Microsoft Exchange -> CN=domain -> CN=Administrative Groups -> CN=Exchange Administrative Group -> CN=Databases.
2. Right-click the listed database > Properties.
3. Check whether the msExchHomePublicMDB value is set to an available value. Please change the value to <not set>.
4. Click OK.
Then check whether the issue persists.
Thanks,
Winnie Liang
TechNet Community Support

Exclaimer manager signature does not update sent items for outlook 2013 clients when using cached mode

Hi
I have Signature Manager Exchange Edition 2.0.3.0 installed on the hub servers.
I have enabled Sent Items update.
some clients are not getting signature update in the sent items of outlook while using cached mode.
from OWA, and MS Outlook when connected online, the signature is updated in the sent items.
I have two CAS servers and two mailbox servers. all with Exchange 2013 SP1
I tested each CAS server for the URLs of Autodiscover and EWS, with no errors or warnings.
I also test Autodiscover through
https://testconnectivity.microsoft.com . I go successful result.
Outlook clients are updated to the latest version 15.0.4701.1000
for outlook clients; I deleted outlook profile, deleted outlook folder in the user profile, re-created the outlook profile, with no luck.
from Exclaimer event logs on the Hub servers. the sent items update is successfully updating clients. below is the screenshot of an event for one email message which is successfully updated from exclaimer but it did not update on the client outlook while
using cached mode.
Since the issue is with multiple users, I am searching for a centralized solution
Mashhour Faraj

Dear Mashhour
Here you go
Employees can see their email signatures and disclaimers
With Exchange 2013, a Microsoft Outlook user can’t see any added email signatures or disclaimers as they are added to an email when it passes through the Exchange server.
Signature Manager Exchange Edition lets email users see their email signature and corporate disclaimer within the Sent Items of their inbox, giving them visual confirmation of the processed email
Source -
http://blog.exclaimer.com/exclaimer-signature-manager-vs-microsoft-exchange-2013/
Updating to the latest version of signature manager exchange edition will help you to resolve this problem for sure
Or you need to contact them to find a solution on this .
I'm pretty much sure that this problem is related with some version mismatch on their s/w on exchange 2013 which is causing this issue.
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 Thanks Sathish
(MVP)

Outlook 2013 SP1 S/MIME signature requires entering password twice

Similar Messages

Maybe you are looking for