Digital signatures Office 2013 invalid in 2010

We have pc's with Office 2010, Office 2007 and Office 2013.
When we sign a document(with a certificate issued by a local CA server) in Office 2013, and open that file in Office 2010 or 2007, it says 'invalid signature'. When we open that same document on another pc with Office 2013, the certificate is valid.
What i already tried:
-Another document(it happens at every document signed by Office 2013)
-setting the 'Do not include XAdES reference object in the manifest'
to enabled/disabled in GPO(by adding the office 2010, 2007 and 2013 ADMX templates).
-Setting the 'Legacy format signatures'
to enabled in GPO
If we sign a document in 2010 or 2007, it is valid in all versions of Office.

-setting the 'Do not include XAdES reference object in the manifest'
to enabled/disabled in GPO(by adding the office 2010, 2007 and 2013 ADMX templates).
We need to set the 'Do not include XAdES reference object in the manifest' to
Enabled. After that, sign a new document in Office 2013 and then try to open it in previous version to check the result. The settings may not apply to existing signed documents, you will need to sign a new document to test the result.
For more information about digital signature settings for Office 2013, please refer:
http://technet.microsoft.com/en-us/library/cc545900(v=office.15).aspx
Regards,
Steve Fan
TechNet Community Support

Similar Messages

VBA: Valid digital signature is deemed invalid

I have a valid 3-year code-signing digital certificate recently issued by Symantec. The trouble I'm having is, when I sign my Word macro template (*.dot) with this cert, Word 2007 deems the signature to be invalid.
Word 2007's "Microsoft Office Security Options" dialog says "This digital signature is invalid and cannot be trusted", with no option to trust the publisher. This is not the case in Word 2010 and Word 2013
This is from the same *.dot macro template on all PCs.
Does anyone know of versioning issues regarding the signature validation between Word 2007 and later Word versions? Could it be related to the deprecation of SHA1?
I've already tried the hotfix available from https://support.microsoft.com/en-us/kb/967732, with no success. The version of Word 2007 in question is 12.0.6700.5000.
I would greatly appreciate any help.
Thanks
-cc

Hi Clint,
Thanks for posting on MSDN forum.
This forum is for developers discussing developing issue involve Word product. Since the issue is more relative to end-user, I would like to move it to
Technet forums - Word IT Pro Discussions - Microsoft to get more effective response.
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.
Thanks for your understanding.
Regards & Fei
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.
Click
HERE to participate the survey.

Problem with URL:s containing scandinavian characters (Office 2013 / Firefox / SP 2010)

We are encountering problems with document opening when URL contains scandinavian characters (ä,ö). This issue occurs only with Office 2013 when using Firefox. With IE it works just fine. And Office 2010 works nicely as well.
Error message: "We can't connect to 'https://intra.../Test powerpoint.pptx' Please make sure you're using the correct web address".
This issue only occurs when document or document set name contains scandinavian characters. If I rename it, document opens without any problems.
Any idea how I could fix this?

Hi Law, try changing the settings in the library to "open in client application." You should also read the following links for solutions:
http://sharepoint.stackexchange.com/questions/16938/why-is-word-document-created-from-template-saved-locally-instead-of-to-the-docu
http://social.technet.microsoft.com/Forums/sharepoint/en-US/ec048a1f-e6cc-481d-8f46-308823568b56/cannot-save-documents-to-sharepoint?forum=sharepointadminprevious
cameron rautmann

Office 2013 vs SharePoint 2010 - Unable to check out documents to SharePoint drafts folder

My company is foisting Office 2013 on us without upgrading SharePoint 2010 Enterprise. One of the issues I have discovered since receiving Office 2013 is that SharePoint no longer provides the option to save checked out documents to my local drafts folder.
This is despite having Office set to save checked-out files to the server drafts location and the Office Document Cache Handler enabled in IE9. Is there a registry setting or something I can change that will re-enable this feature?

Hi Nellie,
According to your description, my understanding is that you want to re-enable the add-on Office Document Cache Handler in IE9.
We can re-enable the add-on in IE9 using Group Policy:
Launch the Group Policy Editor.
Go to User Configuration > Administrative Templates > Windows Components > Internet Explorer > Security Features > Add-on Management >
Add-on List.
Set this policy to 'Enabled'.
In the Add-on List, add the CLSID of BHO (Browser Helper Object) (i.e.) {B4F3A835-0E21-4959-BA22-42B3008E02FF} as the ‘Value Name’ and 1 as the 'Value'.
Log out of the machine and log back in again for the setting to take effect.
More references:
http://support.microsoft.com/kb/2463597/en-us
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Debug office 2013 from VS 2010

I am trying to run in debug mode
an app in Office (Excel)2013, whereas I am developing in VS 2010.
I found this article, which is quite an alright solution. What I did is I opened the .vbproj file,
with a simple text editor, from the file system and edited OfficeVersion="14.0" to 15.0 (I
researched that Office 2013's version is 15). But when I run the solution, it still opens in Office 2010.

Hi,
Were you developing an
VSTO solution for Office?
If I understood correctly, to develop/debug an solution for Office 2013, we need to use Visual Studio 2012 or Visual Studio 2013.
You can get more detail about it from link below:
Running Solutions in Different Versions of Microsoft Office
Link below may be also helpful:
Configuring a Computer to Develop Office Solutions
Regards & Fei
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.
Click
HERE to participate the survey.

Digital signature valid or invalid depending on the signing Windows user

I have a very strange problem and was not able to determine how to resolve it because I quite don't undestand the mechanisms of signing, it seems.
I have a digital signature issued by a member of the "Adobe Approved Trust List". If I sign a document with Adobe Reader XI or Adobe Acrobat XI Standard logged in with one Windows user account the signature appears valid on any other Windows user account. If I use another Windows user account and sign the document with the same digital signature the signature is invalid in this Windows user account and any other.
I didn't change any settings in any of the Adobe products. I use the standard configuration as present just after a fresh install.
One thing I already checked, which nevertheless doesn't explain this strange behavior, is to enable Windows-Integration in the signature configuration of the Adobe products. If this is enabled both documents (the one signed with the "good" Windows user account and the other signed in a "bad" one) show the signature as valid on any Windows account.
So I am wondering if, besides the signature itself, anything else is integrated into a document while being signed that could explain that behavior and, if this is the case, where the setting, trigger, whatsoever, is, to set up Adobe correctly.
Please help.

What do you mean by "signature is invalid"? Is it a a red X or is it Unknown? A problem with trust results in the "Unknown" status, not "Invalid".
In any case, inspect the signature, first in the Signature panel. It will tell you some info about what's wrong with this signature. Then right-click on the signature and select "Show Signature Properties". You'll get a dialog with more info. In this dialog select "Show Signer's Certificate". Check the chain (in the left pane) and "Revocation" tab for each certificate in the chain.
Compare this info for signatures created on a "good" account and "bad". My guess is that the "bad" account is lacking some certificate-related component.and the "good account has it. The fact that if you turn on Windows integration signature becomes valid tells me that it is something related to account.
Another thing to try is this. Go to C:\Users\<username>\AppData\Roaming\Adobe\Acrobat\11.0\Security folder and see if it has CRLCache folder. If it has, delete it and try to sign again.
Also compare the preferences. Check the Edit->Preferences->Signatures->Verification->More->Verification Time preference. Is it the same on both accounts? Is it "Time when the signature was created"? Is the "Include signature's revocation status" check box in Edit->Preferences->Signatures->Verification->More->Creation and Appearances->More checked in both accounts?

Acrobat X Pro - PDFMAKER Office COM in Access 2010

Hi,
I have Office 2013 and Access 2010 installed on my computer. I cannot get the PDFMAKER plugin to work with Access 2010. I tried to manually register the DLL and enabling the plugin. Is this becuase I have MS Office 2013 installed alongside Access 2010. Any info would be great since we run reports in Access and need to ability to merge all the pages in the reports. This was working on another machine that only had office 2010.
Nick

Don't remember if it was AA X or AA XI when support for ACCESS ended. That may be the issue. The compatibility chart at Compatible web browsers and PDFMaker applications suggests that ACCESS does not work for OFFICE 2013 and PDF Maker, but does for ACCESS 2010 on AA X (only version of Acrobat that worked with ACCESS 2010. AA XI does not work with ACCESS. Since you mention both OFFICE 2013 and ACCESS 2010, there may be an issue with 2010 really being the application running (check the help file for About Access for the version). Of course, Acrobat may be confused too, so you may have to activate the addon for ACCESS 2010.

Office 2013 deployment

I'm in the process of building a package to deploy office 2013. Everything works as it should except uninstalling office 2010. OCT only does a partial uninstall of office 2010 but leaves evidence in Programs and features as well as the folder in Start
up. Does anyone have a solution for this?

Configure an application for Office 2010, configure Office 2013 to supersede 2010 and deploy, simple as that. What you need is uninstall command for 2010, install command for 2013 and detection method for both. There's no need for task sequence to accomplish
what you want, the trickiest part is probably getting the right detection method, you can use the product code of Office MSI package. For install/uninstall commands, follow the official documentation or try Google. Use script installation method and use the
setup.exe with .xml created with OCT.

Is it time yet for Microsoft to "Recall" Office 2013 and provide anyone who has a 2013 license a replacement Office 2010 license?

The interface is terrible and can't be changed. Every application in the suite locks up/crashes nearly constantly on any machine it is used on. The activation process is terrible and wastes hours of any support/IT dept's time. From a 'privacy
standpoint', the software is seemingly criminally intrusive. It is clearly a product that should never have been released and is so far from functional that it can't be repaired by any 'service pack', 'hotfix', or 'patch'. It needs to be completely
scrapped.
The only 'redeeming quality' of this software is that the guy who was in charge of creating it is gone from Microsoft. (Unfortunately, he is now President Obama's appointee for running the attempt at repairing the 'healthcare.gov' website...
out of the frying pan... )
When the software is installed using one profile (domain or machine account) and a different profile tries to use the software, it requires 're-activation' - which often fails because the software believes it has been installed multiple times. (This is particularly
frustrating because it has to be installed by an administrative user, but most of the time, the person who 'uses' the software is not the 'administrator' - so it is almost always being 'installed' using one profile and 'used' using another profile).
The necessary intrusion into privacy created by the requirement of a "Microsoft Account" to use the software is seemingly criminal.
The tracking of, and installation of licenses is absolutely ridiculous.
An example:
Many of my clients have many users and many computers (up to 75 or so).
I could create a "Microsoft User Account" for each 'user', but these machines get moved between users, and the software license is tied to the 'machine' and not to the 'user' so as soon as that happens, the licenses and the users are no longer
in line and become impossible to track.
I could create a "Microsoft User Account" for each 'computer'... and I can't even count the ways this would be a nightmare to try to track.
I actually did that up front for one client, and created Exchange email boxes for each computer so that "prove you are really you" emails from Microsoft could be received managed, and responded to, and passed out second usernames and passwords
to all of the users so they could "log-in" to their Office 2013 software, and created a database of the 'computer usernames and passwords' so I could track this... unfortunately, this confused the users (as it rightfully should) so they would change
the passwords for their computer's 'Microsoft User Account' thus locking me out and invalidating my database, ... and... CLUSTERF#%K!!!
As a 'best - worst case', I have had to create a single 'Microsoft User Account" for each of my clients' businesses so I can install and activate Office 2013 products. This is a whole new set of "Awesome Stupidity".
Now, I can put a new computer into a client's office and install their new license key for their oem Office 2013, and it shows up in the 'business's Microsoft User Account'. Then when I give the machine to the user, I get to 're-activate' the software
(hoping that it doesn't tell me to piss-off - which happens about 40% of the time. This is a process that can only be described as a "feat of engineering created by a group of monkeys whose former jobs included 'janitor at MAD magazine headquarters'
or 'beer-pong referee').
It starts with two hours of pressing phone buttons and ultimately talking to someone who tells me "yeah, nothin' I can do about that I'm just here for product activation" (which, incidentally, is done by machine until you pass through MS's ridiculous
labyrinth of repetitious keystroking until the machine is convinced you are just too stupid to punch in the right numbers and allows you to talk to a person... who then asks you for the exact same set of numbers and repeats back the exact same responding set
of numbers and acts dumbfounded when it still doesn't work - since it didn't work the first six times you punched or said it into the phone) followed by "I need to send you to the support group... but because it's 6:30 pm (in a process you started at
3:00pm) they are gone for the day and you'll have to call back on Monday morning"
At some point in the process, you get to log into the "Microsoft user account" and 'roll the roulette wheel of stupidity' by trying to activate the right software from a list of 40 different lines that all say "Microsoft Office 2013 Home and
Business oem", but none give any indicator or differentiating factor like for instance: license key, date installed, license key last 4 digits, mother's maiden name, phase of moon when software was first activated, color or type of blood of the user's
paperboy's dog's previous owner... NOTHING... RANDOM FREAKING STAB IN THE DARK - pick one, any one, hope its the license you are trying to install onto this machine, 'cause if not, you very well may kill the product on some other machine.
So through the process, the lucky support staff person gets' to waste roughly an hour and a half on average for every Microsoft Office 2013 installation. I have actually had to start telling my clients that they are going to likely have to pay an extra
$100 or so per machine in order to get their new Microsoft Office software which comes on their new computer activated - that number tends to work out roughly accurately - except that it is a terrible way of trying to 'please a client'.
Oh,... and did I mention... "THE SOFTWARE CONSISTANTLY FAILS"!?!
A client tries to open a document that they have been using for 8 years and Excel doesn't say "Hey, I don't know how to deal with some element of the file that you put in here using Excel 2003, or Office 2010 (both products, by the way, which worked
great) - no... instead,... it crashes. Doesn't really do any damage to the file it choked on, but the work you'd been doing on three other files which you also had open,... yeah,... that work is gone.
Yeah,.... over time, I have developed a pretty consistent spiel for client's needing new computers that goes over how absolutely terrible Office 2013 is, and explains that our options are further limited by Microsoft's yanking of all Office 2010 or previous
products from market availability, and explaining the merits of both LibreOffice and OpenOffice, as well as their drawbacks. I also have a strangely static response explaining how "larger companies are not burdened by these issues because they are
able to use MOPL which allows them to downgrade their productivity software to Office 2010 so they can continue to function happily, but this is really not a cost effective solution for smaller companies who primarily buy oem Office products with their replacement
computers".
Unfortunately, many clients still decide they want to go with Office 2013 because they apparently believe "it really can't be that bad". The value in my 'presale descriptions' are only really realized when they come back to me a week, two
weeks, or up to a month after the new machine is in place and say "wow,... you were right". The place I am left open for any further problems is when I don't impress upon them beforehand just HOW BAD OFFICE 2013 REALLY IS. In that case,
they still come back to me as though I have done something wrong foe selling them this piece of $#!% software and I have to remind them of our previous discussions.
Strangely, far too few heed the warnings and buy the software anyway - but the discussion has saved many clients the costs of Microsoft Project, because the discussion of LibreOffice and OpenOffice nearly always leads to at least a small philosophical conversation
about 'Open Source Software' in general, and my absolute favorite descriptive analogy in that discussion is to compare Microsoft Project at $600 v. ProjectLibre at $0 - and then further describe the costs of licensing and implementing the associated back-end
server solutions, etc.
This is a saving grace for me, because even though the client has been saddled with Office 2013, they have also saved substantially on Project and it is a rare (but granted, not absolutely absent) occasion that ProjectLibre is lacking some feature or function
that they actually need or want to use - and on those occasions, finding out has cost them absolutely nothing in software purchases.
Its not surprising, I suppose, that clients have grown to accept Office as a required 'cost', but still choke heavily on the price-tag of Project every time they have to buy it. The interesting thing to watch over the coming couple of years will be
'how many businesses stop accepting MS Office as a 'required cost' due to the failing of the software itself and the fact that most are being burned, at least once, by purchasing the software "against technical advice" and are learning, merely by
virtue of HOW BAD Office is, that there are other options out there that both cost less and work better... I mean,... LOTS BETTER.
How many businesses that are used to accepting the cost of Microsoft Office as a cost of doing business will be moved over to open source options and satisfied by them by the time Microsoft releases its next version - which will, presumably work - such that
they will no longer justify the cost of Microsoft's offering even if it is 'superior' to the open source offerings because the open source offerings are plenty sufficient and include a price tag of $0 and an installation/implementation time that is much, much
shorter than Microsoft's offering.
If Microsoft doesn't make some dramatic reparations, and do it soon, I expect their market share will be reduced in this area by a very significant margin.
I am suggesting either a 'Complete Recall' of Office 2013 including an 'uninstall 2013/install 2010' process driven by the automatic update engine, or at the very least, a free and easy downgrade rights offering for anybody who has already purchased 2013
and anyone who purchases it between now and the time the next "functional product" is released.

I understand the inconvenience you are experiencing when working with Office 2013.
If you have any feedback about Office 2013 product, click the and submit to Microsoft.
Microsoft will decide how to fix the problem for all customers.
For the activation mechanism, it intends to protect customers of their rights and interests.
For a retail version of Office, if it was purchased with a disk, Microsoft account is not necessary during the installation.
For volume license of Office, refer to the following link to deploy Office suites can be much efficient:
http://technet.microsoft.com/en-us/library/cc178982.aspx
For the problem Office 2013 keep crashing, check the following link to check:
http://support.microsoft.com/kb/2813143/en-us
http://support.microsoft.com/kb/2758592/en-us
Thanks,
Tyor Wang
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

Excel 2013 crash - related to digital signature?

This is a cross-posting of a thread originally started in Microsoft Answers (Office- Excel) forum, advised to post in this forum by MS support engineer Mohan Suryanarayan (link to other forum: here).
I have a VB macro in file A (which otherwise contains only several Excel Tables with named ranges). My digital signature (for signing code) is attached to file A.
As the macro executes, the Open file dialog is called up so that the User can select a secondary file to open (file B or C).
Files B and C contain several sheets with formulas and Excel Tables, and also their own extensive VB macros. My digital signature is also attached to files B & C.
The remainder of the macro in file A simply executes an update of the Excel Tables in the secondary file, before saving & closing it.
I have been finding that during execution of the file A macro, Excel crashes and closes all open Excel files.
If I remove the digital signature from the secondary files then the macro in file A executes with no problem.
The macro was written in Excel 2007 and on a different laptop, with different digital signature, and used to have no problem at all. When a new laptop was purchased a new digital signature was obtained and placed into all of the files.
Execution of file A is a critical process - I need help with stopping the crash, while maintaining a digital signature in the secondary files (so that their own macros can execute).
Event Viewer error shows the following:
Faulting application name: EXCEL.EXE, version: 15.0.4667.1000, time stamp: 0x543d366c
Faulting module name: mso.dll, version: 0.0.0.0, time stamp: 0x5447696f
Exception code: 0xc0000602
Fault offset: 0x011aafdd
Faulting process id: 0x2d58
Faulting application start time: 0x01d01e17eafcd0bb
Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\EXCEL.EXE
Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
JL Latham replied:
Tom, all I can give you is relatively non-information. I haven't experienced that type of behavior even in Excel 2013 with digitally signed macros in multiple workbooks. But my digital signature is a commercial one from DigiCert, not
self-cert. I'm not even sure what piece of Excel or Office processes the digital signature (that is, whether it is mso.dll or not). But your whole process has more moving parts than most of mine involving multiple workbooks do - I quite often turn
off .EnableEvents when doing things like that just so event driven macros in the other workbook(s) do not execute.
Do the macros in the 'B files' have to execute during all of this processing in file A? If not, have you tried turning interrupts off:
Application.EnableEvents = False
before starting to work with the B-files? Maybe something in them, such as a Worksheet_Change() or other event triggered process is messing things up?
If you do use Application.EnableEvents=False, remember that you MUST re-enable that later in the code with Application.EnableEvents=True to get responses to things like button clicks, changes in a worksheet or other event driven processes
to run 'normally' again.
Have you looked at this discussion:
http://answers.microsoft.com/en-us/office/forum/office_2013_release-excel/excel-2013-crashing-immediately-when-attempting-to/ea2ab100-5525-4a0d-a3cf-6977319f954f
Sounds very similar to yours - original signature created in 2007, and crashing in 2013. Some suggestions were made, but whether they fixed the issue or not is unknown: OP never came back and said "fixed it" or "didn't fix it".
I replied:
In answer, the secondary B files don't execute any part of their macros during the A file process, and I hadn't included an EnableEvents = False within the file A code. However, I have just tried it to check if it made any difference and unfortunately it didn't.
I had read the thread you gave a link to before posting, and also the sub threads given within that one, but didn't see anything I thought of immediate parallel other than an Excel 2013 crash.
The way I read the linked thread was that a User added a signature in Excel 2007 and when they tried to open the file Excel (2007?) crashes, although other people using Excel 2013 can open it (not clear whether it means others can open the one with
the 2007 signature or without it).
Anyway, the differences in my situation are that:
(1) my B-files were originally created in Excel 2007 on a different laptop to current and had their own signature attached. I maintain a 'stock' of B-file versions, some of which have the old signature and some the new. If I run the A-file macro
on one of the B-files with the old signature then it executes ok;
(2) I am able to open the B-files ok, no matter whether the signature in them derives from the old laptop with Excel 2007 or the new laptop with Excel 2013;
(3) the macros within the B-files execute ok (this includes any versions of the B-files which still have an old signature attached, by removing the old signature and replacing with the new and executing on the new laptop);
(4) the offending operation which triggers the crash (when the B-files have the new signature attached) is a Resize of the Excel Tables within the B-file. I understand that I may eventually have to find a workaround for this operation but initially
I want to sort out the signature issue (I'm reasonably sure the signature issue is not a red herring where the Resize is the 'real' problem).
Regards, Tom

Hi,
According to your description, this issue occurred with some particular files that stored in SharePoint site. Did the user download the file to local disk to print?
Based on the event log >>Faulting module name: EXCEL.EXE<<, it does not show the root Faulting module. Thus, please try to follow this KB to do general troubleshooting:
https://support.microsoft.com/en-us/kb/2758592
Then, if you have used "printer status application", please go to Device settings -> Installable options -> Printer Status notification and select disable.
If this issue still exists, we may need to collect the App crash dump file:
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
You can try to analyze dump by yourself if you would like to：
How to analyze app crash dump file:
http://blogs.technet.com/b/askperf/archive/2007/05/29/basic-debugging-of-an-application-crash.aspx
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
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]

Office 2013 with Visio and Project Error - Package manifest is invalid

In July I successfully created an App-V install of Office 2013 VL using the ODT. This week I decided to try just doing Visio as we don't install it or Project on all systems. I used my same customconfig.xml and just changed the ProPlusVolume to VisioProVolume
and changed the source path. Everything downloaded and packaged fine. I was able to import into SCCM just fine and create a deployment to my test collection. However when I run the install out of Software Center I get (as part of a much longer error) the message
in AppEnforce.log that the package manifest is invalid. Thinking that maybe I had to include Office as long with Visio I tried packaing all three items but still get the same error. Has anyone else seen this behavior and/or ideas how to fix it? Can I sequence
just Visio or just Project? I'm including my config.xml just in case I've got something wrong with it that I haven't caught. Thanks
<Configuration>
<Add SourcePath="<networkpath>\Microsoft\AppVOffice2013\Sept\" OfficeClientEdition="32" >
<Product ID="ProPlusVolume">
<Language ID="en-us" />
</Product>
<Product ID="VisioProVolume">
<Language ID="en-us" />
</Product>
<Product ID="ProjectProVolume">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

Hy. I'm having the same problema.
I'm trying to create na app-v package (v.5 SP2) of Office 2013.
I downloaded the Office Deployment Tool for Click-to-Run from here:
http://www.microsoft.com/en-us/download/details.aspx?id=36778
I installed it into C:\Office2013pck shared that folder as
\\APPVMANAGER\Office2013 and mapped as Z:\.
I changed the configuration.xml file to:
<Configuration>
<Add OfficeClientEdition="32" >
<Product ID="ProPlusVolume">
<Language ID="en-us" />
</Product>
<Product ID="VisioProVolume">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
Then I ran in na elevated cmd:
>Z:
>\\APPV-CL-WIN7DEF\Office2013\setup.exe /download
\\APPV-CL-WIN7DEF\Office2013\configuration.xml
and
>\\APPV-CL-WIN7DEF\Office2013\setup.exe /packager
\\APPV-CL-WIN7DEF\Office2013\configuration.xml
\\APPV-CL-WIN7DEF\Office2013\Appv
Everything seemed to work fine.
The creted folder had Office\Data\15.0.4649.1001 folder (I guessed this is a version number)
When I tried to add the package to App-V Server (in the Console) I get the following error:
An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
I tryied to publish it from powershell, getting the same error message agalluci image post shows.
From the Event Log I got this additional information:
There was a problem retrieving the requested package \\APPVMANAGER\AppVpck\Office\VisioProVolume_ProPlusVolume_en-us_x86.appv for import. Error message: Unspecified error
Element '{http://schemas.microsoft.com/appv/2010/manifest}UsedKnownFolders' is unexpected according to content model of parent element '{http://schemas.microsoft.com/appx/2010/manifest}Package'.
I haven't found any indication of which file is the manifest app-v file.
I also haven't found any .xml with the "UsedKnownFolders" tag (I changed the .appv package extension to .zip and explored some of the files).
I tryied creating a package for 32 and 64 bits, only office, office and visio, and office visio and project running Windos 7 and Windows 2012.
Thanks in advance for any help.

Excel 2010 - Multiple Digital Signatures?

How would you add multiple digital signatures to an Excel 2010 workbook?

Hi,
To add multiple digital signatures, we need to create the signatures first.
Then please refer to the following steps:
Click the File tab.
Click Info.
Under Permissions, click Protect Document,
Protect Workbook or Protect Presentation.
Click Add a Digital Signature.
Read the Word, Excel, or PowerPoint message, and then click OK.
In the Sign dialog box, in the Purpose for signing this document box, type the purpose.
Click Sign.
Check the following MS link for additional information.
http://office.microsoft.com/en-us/excel-help/add-or-remove-a-digital-signature-in-office-files-HA010354308.aspx
Regards,
George Zhao
TechNet Community Support

SharePoint 2010 Collect Signatures workflow - no digital signatures?

Hello, I configured a "Collect Signatures" workflow for the content type "Document", then uploaded a MS Word 2010 (.docx) document as content type "Document". This Word document as 2 empty Signature Line in it.
I then start the workflow, basically 2-stage with 2 person from my Active Directory. However, what I found is that when I go to my workflow task and click on the "This document requires your signature" link, it pops up a "Workflow Task" box in the
browser. There is a "Sign" button which I can click to sign but it does not sign on the signature lines inside my Word document.
What am I doing wrong here? Or does SharePoint 2010 Collect Signatures workflow no longer work with digital sigantures? Thanks.

Hello ,
We have chceked by setting up a repro at our end and its not possible to complete the workflow without opening the document . Also below are some additional findings that I have and would like to share :-
1) In Office 2007 (Word and Excel) you can click on the office button from the respective application while you have the concerned document open in it. This triggers the collect digital signature workflow and the users signs
it immediately as he can see the popup on the screen. Still he has to go to the task list to complete the task which I would say is a manual process following the workflow task is 100% completed.
2) In SPS2010 with Office 2010 we do not have an option to trigger the workflows from within the Office document. Instead you directly go to task list to open the task and click on sign button to complete the task. Here you
still need to open the document again and digitally sign it. The difference is workflow here is not triggered in Office document. Even here it is a kind of manual process except that you don’t see a popup to sign document immediately from Office document
due to the fact that workflow is triggered from SharePoint task list.
Thanks,
Manas
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."

Digital Signature and SharePoint 2013

Dear Expert,
My company has a plan to do digital signature and sharepoint 2013. Now, we focus for internal use that I know use AD CS. and in near future we use for external use. We plan to buy 3rd party certificate.
My question
1. How to implement this solution? Please suggest
2. If I implemented AD CS, can we use public certificate in near future.
3. Can we use public certificate with SharePoint 2013?
Thank you

Hi,
Based on your description, my understanding is that you want to use Digital Signature in SharePoint Server 2013.
You can use digital signatures in forms ,then use these forms in you SharePoint site.
In InfoPath form ,you can change the form to allow signature here: File>Info>Advanced form options >Digital Signatures .You can choose to sign the whole form or a field .
https://social.technet.microsoft.com/Forums/en-US/0ed54d57-d67d-41cd-bd1b-9e5a4be10d0c/use-of-digital-signature-in-sharepoint-2010?forum=sharepointcustomizationprevious
besides, here is a similar post, you can take a look at:
http://sharepoint.stackexchange.com/questions/78058/custom-digital-signatures-or-hash-on-list-items
For more information about implemented AD CS, refer to the following link:
http://technet.microsoft.com/en-us/library/hh831574.aspx
Best Regards,
Lisa Chen
Forum Support
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]
Lisa Chen
TechNet Community Support

How to use Digital Signature and PKI in SharePoint Server 2013

Dear Expert,
My company will plan to use Digital Signature and PKI document in SharEPoint Server 2013.
Can you guide me what's the concept and how to implement and develop?
Please suggestion.
BR,

Hi BR,
Based on your description, my understanding is that you want to use Digital Signature and PKI in SharePoint Server 2013.
You can use digital signatures in forms ,then use these forms in you SharePoint site.
In InfoPath form ,you can change the form to allow signature here: File>Info>Advanced form options >Digital Signatures .You can choose to sign the whole form or a field .
https://social.technet.microsoft.com/Forums/en-US/0ed54d57-d67d-41cd-bd1b-9e5a4be10d0c/use-of-digital-signature-in-sharepoint-2010?forum=sharepointcustomizationprevious
Or you can use any tools such as the ADSS Connector for SharePoint which allows enterprise users to "click and sign" on a document in SharePoint.
http://www.ascertia.com/
Thanks,
Victoria
Forum Support
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]
Victoria Xia
TechNet Community Support

Digital signatures Office 2013 invalid in 2010

Similar Messages

Maybe you are looking for