App-V 5.0 MAK activation in Office 2013

Hi,
I created a App-V package for Visio and Project 2013 Standard Edition using ClicktoRun Office Deployment Kit. Now i have the Keys. How can i implement the MAK activation in the App-V package. Is there any thing that i can do in the configuration file. Please
help me.
Thanks,
Prem

Are you also virtualizing Office 2013?
Are they in separate packages from Office 2013? I think the packages are only supported if they're in a single package.
Test by creating an Office 2013 package with Project and Visio and see whether that activates successfully.
Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or 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.
This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.
Twitter:
@stealthpuppy | Blog:
stealthpuppy.com |
The Definitive Guide to Delivering Microsoft Office with App-V

Similar Messages

PDF Maker Icon on Office 2013 Ribbon

XI Pro installed. Windows 7 64 bit. Trying to get PDF Maker Icon on Office 2013 ribbon. In Add-ins, PDFMaker is an active ofifce Com add-in.

Hi Ric1944,
Please update Acrobat to v11.0.7 and check.
The pdfmaker plugin does not get enabled with the base version 11.0
Regards,
Rave

Activating Microsoft Office 2013 Pro Plus? Volume licensing needed?

Hello,
I have unique scenario in my company where we need to install office 2013 pro plus on 10 hard drives. Each hard drive has its own windows 7 operating system. Due to security reasons, the setup consists of one computer tower (with no primary hard drive) that
has a slot in tray for one hard drive. These hard drives are accessed one at a time. There are not set up on a network and do not have internet access. What would be the best method of installing office? Of course we could install 10 copies of office on the
10 hard drives, but this would be expensive. I keep hearing about KMS (Key management service) and MAK (multiple activation key) which I believe would require volume licensing. Is this a possible cheaper alternative? Would we need to set up a server to manage
the keys?
Any feedback is appreciated.
Thank you

Hi,
A volume licensing aggreement is the best plan for your case, I think.
Multiple Activation Key (MAK) activation is used for one-time activation through Microsoft hosted activation services, either via the Internet or by telephone. Each MAK has a predetermined number of allowed activations, this number is based on volume licensing
agreements.
KMS is a client-server model in which the client requests activation from a computer serving as the KMS host. KMS activation requires TCP/IP connectivity between the clients and the KMS host. By default, KMS host uses DNS to publish the KMS service. It works
best with more than 50 computers.
So I think the best choice for your scenario is MAK as your setup is not on a network and only need 10 copies of Office. Also, with MAK, you don't need a server to "manage the keys" as the MAK key need to be added at installation time.
Here is the reference you'll need:
http://technet.microsoft.com/en-us/library/ee624358(v=office.15).aspx
http://technet.microsoft.com/en-us/library/dn385359(v=office.15).aspx
http://technet.microsoft.com/en-us/library/ee624357(v=office.15).aspx
Regards,
Ethan Hua
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.

Missing Acrobat PDF Maker Tab within Office 2013

Acrobat PDF Maker Tab is missing from all apps within Office 2013 suite. I have already installed the latest MS hotfixes. I am using Adobe Acrobat 9 Standard with Office 2013 [x32 bit]. Please help!

Hi,
In the situation, you may select the higher version of Acrobat PDFMaker office COM Addin to install:
The following table provides the currently available compatibility list for the Adobe PDFMaker add-in and Office programs.
Office version
Supported PDFMaker add-in versions
(check PDFMOfficeAddin.dll version)
2010 (32-bit)
10.x and higher
2013 (32-bit)
10.x and higher
2010 (64-bit)
10.1 and higher
2013 (64-bit)
10.1 and higher
Please see the information on the following Web page for the latest compatibility information between the PDFMaker add-in and Office programs.
Acrobat Help / Compatible web browsers and PDFMaker applications | Acrobat, Reader
http://helpx.adobe.com/acrobat/kb/compatible-web-browsers-pdfmaker-applications.html
More detail:
http://support.microsoft.com/kb/2800094
Best regards,
Rex Zhang
TechNet Community Support

Activating MS Office 2013 ProPlus via KMS running on the same server

Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc)
Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered).
Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run.
There are no entries in KMS event log related to this failure.
Everything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).
Output of slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD:
Windows Script Host
Software licensing service version: 6.1.7601.17946
Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 2e28138a-847f-42bc-9752-61b03fff33cd
Application ID: 0ff1ce15-a989-xxxx-xxxx-xxxxxxxxxxxx
Extended PID: 55041-00206-234-486666-03-xxxx-xxxx.xxxx-xxxxxxx
Installation ID: 01683679734050124078134659xxxxxxxxxxxxxxxxxxxxxxxxxxx
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: xxxxx
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 2/05/2015 10:00:12 AM
Key Management Service is enabled on this machine
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 0
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 0
Requests with License Status Initial grace period: 0
Requests with License Status License expired or Hardware out of tolerance: 0
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 0
OK
Output of cscript ospp.vbs /dstatus
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS: ---OOB_GRACE---
ERROR CODE: 0x4004f00c
ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x4004f00c
Last 5 characters of installed product key: GVGXT
DNS auto-discovery: KMS name not available
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
---Exiting-----------------------------

Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc)
Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered).
Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run.
There are no entries in KMS event log related to this failure.
Everything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).
Output of slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD:
Windows Script Host
Software licensing service version: 6.1.7601.17946
Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 2e28138a-847f-42bc-9752-61b03fff33cd
Application ID: 0ff1ce15-a989-xxxx-xxxx-xxxxxxxxxxxx
Extended PID: 55041-00206-234-486666-03-xxxx-xxxx.xxxx-xxxxxxx
Installation ID: 01683679734050124078134659xxxxxxxxxxxxxxxxxxxxxxxxxxx
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: xxxxx
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 2/05/2015 10:00:12 AM
Key Management Service is enabled on this machine
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 0
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 0
Requests with License Status Initial grace period: 0
Requests with License Status License expired or Hardware out of tolerance: 0
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 0
OK
Output of cscript ospp.vbs /dstatus
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS: ---OOB_GRACE---
ERROR CODE: 0x4004f00c
ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x4004f00c
Last 5 characters of installed product key: GVGXT
DNS auto-discovery: KMS name not available
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
---Exiting-----------------------------

Installed Office 2013 home and Business and its prompting activation for Office 2013 standard

Dear Friends,
Previously i got a trial version of Office 2013 stadard version on my PC and later on i purchased Office home and business version, i uninstalled standard version restarted the PC and installed Office 2013 home and Business OEM pack and activated the prduct.
Now while i am opening any office product like Excel or Word while checking for activation information there its showing me both the versions of office, Office 2013 standard (activation required) and office 2013 Home and business activated. Now my question
is why that office standard 2013 is still showing in my activation page where as the same version was unable to find in my control panel programs and features. please help me out to get rid of this issue.
Thanks in Advance

Hi,
Maybe you didn't remove the the Standard version completely, I suggest you uninstall Office using the Fix it tool:
Click this Fix it.
Or we can uninstall Office 2013 manually, the steps are long and depend on your installation method, please refer to this article below:
Manually uninstall Office 2013 or Office 365
Note Before you start, you need to know removing Office manually is a long, complex process and might require that you reinstall the operating system if certain steps are done incorrectly.
After the uninstall, install the version you need to check the result.
Regards,
Melon Chen
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]

Product activation failed office 2013 at windows 8.1

when i update my windows 8 laptop to windows 8.1 i was shocked when i open my office 2013 and it says product activation failed though it was activated, when my laptop is running windows 8, through kmsnano
what should i do in order to reactivated it

Hi,
Which Office version did you use? Office 2013 RT ,home or other? Please follow the link to activate Office 2013:
http://office.microsoft.com/en-in/support/activate-office-2013-programs-HA102819770.aspx
Regards,
George Zhao
TechNet Community Support

How do I activate Office 2013 that I have deployed using ODT and App-V onto a Remote Desktop Server?

I am setting up a demo Server 2012 R2 environment (1 DC server, 2 RDSH servers, 1 App-V server).
I have created an Office 2013 volume license App-V package using the latest Office Deployment Toolkit. I have deployed the App-V package to an RDS server and it all works fine. However, I am unable to activate Office 2013 using the MSDN Office 2013 retail
key because it tells me the product key is invalid for this version of Office. I've looked at the alternative of using the App-V Sequencer to create the Office 2013 package, but from what I've read this is not a Microsoft supported method.
Is there any way that I can activate Office 2013 (volume license on RDS) using the method I've outlined above, or is there any way of using the Office2013 download from MSDN such that it can be packaged by the ODT (or App-V Sequencer) for successful deployment
using App-V and activation using the retail Office 2013 product key on MSDN?

True, VL channel media can't be activated with MSDN Retail pkeys (that's what I was trying to get you to understand, I figured you would be attempting that, as so many people do :(
I've not attempted your scenario myself.
It sounds like you aren't following the supported scenarios as (poorly) described by MS;
The way I read their guide, for an RDS scenario, you must use a VL key [either MAK or KMS] (since a subscription product+key can't be used on RDS):
i.e.: <Product ID="ProPlusVolume">
http://support.microsoft.com/kb/2772509
http://support.microsoft.com/kb/2915745
http://technet.microsoft.com/library/dn481351.aspxhttp://blogs.technet.com/b/office_resource_kit/archive/2013/12/02/announcing-app-v-5-0-sp2-support-for-office-2013-volume-licensing-editions.aspx
So, that all means that for RDS, you can't use anything other than VL "product" (in
the form of an ODT-generated output) with a VL pkey. So, for your RDS demo setup, you need to use real product and real pkeys.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Virtual Application: Activation Office 2013

Hello All,
We have created virtual office application as directed in Office Deployment method. In Config.xml we gave "ProPlusVolume" we got out final .appv file
We need to deploy this virtual application to all our clients. We are having a tough time in getting this done.
How do we activate this virtual application?
Some blogs say MAK and KMS cannot be used for Virtual application, it is supported only for Non-Virtual application
is this right? or using KMS we could achieve?
How activation for Office 2013 applications can be achieved using VLSC?
Any help would be greatly appreciated
Thanks!

Hello,
If you are using KMS / AD-based activation I would guess it would detect it automatically.
If using MAK - see the option to use ospp.vbs
http://technet.microsoft.com/en-us/library/dn385359(v=office.15).aspx
I haven't tried the above options, but it would be the most obvious chocies.
Nicke Källén | The Knack| Twitter:
@Znackattack

Office 2013 Volume licensing Activation using VAMT

Can we activate office 2013 pro plus volume license edition using VAMT 2.0

I found a confirmation on this link:
http://blogs.technet.com/b/office_resource_kit/archive/2013/01/30/volume-activation-of-office-2013-frequently-asked-questions.aspx
Why would I want to use Volume Activation Management Tool (VAMT) 3.0 rather than VAMT 2.0?
In addition to KMS and MAK activation, which VAMT 2.0 supports, VAMT 3.0 supports Active Directory-Based activation. For general information about VAMT, see
Manage Activations Using the VAMT. For more information about VAMT 3.0, see
Introduction to VAMT 3.0.
The quoted article doesn't confirm the question asked.
The quickest way to confirm if VAMT2 is suitable for Office2013 is to test it.
Even if it *does* work, it may not be "supported" by MSFT.
I've asked a MSFT contact this question, it may take a few days to get an answer. (and, the answer might be "it's not supported"..)
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Office 2013 converting to app-v gives xml error in manifest file

Hello,
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.
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 tryied creating a package for 32 and 64 bits, only office, office and visio, and office visio and project.
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).
So... what's happening?
Thanks in advance for any help.

Sounds like the same issue as this thread:
http://social.technet.microsoft.com/Forums/en-US/98e5508b-7898-4b2b-b24d-3fd0194bbbc7/office-2013-with-visio-and-project-error-package-manifest-is-invalid?forum=mdopappv
What I would suggest is try to add the package manually via powershell, and if you get the same error post in the above forum so its in the same place.

App-V Office 2013 x64 with local x86 version

Hi,
we have deployed Office 2013 x86 VL Version on all our machines locally (MSI Install). Since App-V 5 SP2 now supports virtualising Office 2013 VLs we would like to run a virtualised Version of Office 2013 x64 VL (especially Excel) alongside the locally installed
x86 Version. Is this possible?
Thanks!

There won't be any limitations for the virtualized Excel's core features, but interaction with other applications (native Office, OS, other apps) may be limited as, well, a virtualized application is sort-of isolated to a certain extent. Namely it
may happen that you loos the tight integration between Office apps based on OLE objects.
(Copy & Paste an Excel spreadsheet into Word/Powerpoint - Double-click on the Word-Embedded Excel and get all your Excel menus and options back).
'Simple' stuff (saving and loading files, copying simple data through clipboard) all will work. Users potentially won't be able to add new Excel Plugins and it might even be diffcult to do so for you.
If the use-cases allows that you could consider running Excel_x64 on remote machines (VDI, RemoteDesktopServer).
Falko
Twitter
@kirk_tn   |   Blog
kirxblog   |   Web
kirx.org   |   Fireside
appvbook.com

How to get user Office 2013 ProPlus activation information?

We have Office 365 E3 License. We have assign to a over 15,000 user with Office 2013
ProPlus license. Now we would like to find out which are user activated the
Office 2013 ProPlus product in Office 365. Is there a way to get this report via PowerShell?

We have Office 365 E3 License. We have assign to a over 15,000 user with Office 2013
ProPlus license. Now we would like to find out which are user activated the
Office 2013 ProPlus product in Office 365. Is there a way to get this report via PowerShell?
No. It is not possible for admin to get this data at all, in any way, from anywhere. Only the individual user can examine their activations/consumption.
http://blogs.technet.com/b/office_resource_kit/archive/2014/01/17/office-365-proplus-multiple-devices-and-de-activation.aspx
http://community.office365.com/en-us/f/148/t/274701.aspx
http://blogs.technet.com/b/office_resource_kit/archive/2012/11/28/managing-office-365-proplus-installations-activating-deactivating-and-reactivating.aspx
http://serverfault.com/questions/638619/office-365-how-to-get-a-report-of-office-installs-per-user
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Installing Office 2013 on several PCs in a small company

Rather than create individual Live IDs for each of the 7 PCs in a small company, in order to install Office 2013, can we install 7 copies of Office 2013 using a single Live ID? (each copy of Office 2013 is licenced individually, not bought through
VLSC).
Or, is there a better way to install several copies of Office 2013 in an organisation (that does not want to buy Volume Licencing, they just want to buy individual copies)?

Are you talking about the local install version Office 2013, or Office 365 (2013)?
Office 365 is "easier" if you are dealing with volume licenses. Office 365 "installs" very quickly, in a matter of minutes. So if you are talking about buying individual 365 business licensees, just document a short procedure telling users how to install
Office 365 (sorry, that may not work if they don't have admin rights on the PC).
If you bought Office 365 volume license, here is a procedure I pieced together:
How does a company install and control licenses - Business
Using Click to Run virtualization, the process of getting new users running has substantially changed. Because CTR installations are so fast, you no longer have to pre-install the software for users.
A business IT Admin controls use of corporate Office 365 licenses through the Office 365 Administration Center online.
Overview:
- In the Office 365 Administration Center the designated Office Administrator sets up the new USER ID
- Setup the associated email account(s)
- Setup Office licenses allowed to the userid
- the new User logs in to their new computer
- in Internet Explorer the user goes to the “Office 365 Portal” site to get their allowed Office 365 installation
- using the Click to Run installation process, Office 365 is installed and running on a new computer is a matter of minutes.
The following links will provide you with more detailed information of where to look and what to do. You may require some additional support from an “expert” .
Free MS training for Office 365 Administration Center / Portal
http://office365support.ca/does-microsoft-have-free-training-for-the-new-office-365/
Excellent resource to get you started administering your business Office 365 licenses.
The first video,
Exploring the Office 365 Administration Center (9:32), describes
how to create new userids, and to assign Office licenses to them. It also very quickly breezes by how to install Office.
The second vidow,
Office 365 Overview for IT Administrators (14:00), quickly walks you
through setting up new company and users.
On basic setup page, step 3 “Set up User Access” provides links to instructions on how to set up new users.
In Service Settings, Downloads, you can control what Office apps the user can download.
Creating Users for the NEW Office 365
http://office365support.ca/creating-cloud-users-for-the-new-office-365/
This page provides more detailed instructions for setting up the new userids and granting them Office 365 licenses
Configuring Desktops for the NEW Office 365
http://office365support.ca/configuring-desktops-for-the-new-office-365/
The following post will document how to setup a Windows 8 desktop for a cloud user for Office 365. I have already installed Windows 8 and created
the local account for my test user. I have logged into the Office 365 portal and had the user change his password. The password for Office 365 and the password for the desktop are the same.
Office 365 for enterprises: A tour for administrators
http://office.microsoft.com/en-us/videos/office-365-for-enterprises-a-tour-for-administrators-HA102654955.aspx
Office 365 for enterprises brings together the online services your business needs. To see how to set up and manage these services, watch these four short videos.
Where did My MSI go - Deployment Video
http://www.microsoft.com/resources/technet/en-us/office/media/video/video.html?cid=otc&from=mscomoffice&VideoID=670e3969-0509-4d3a-a8a6-ffbe526d3e6f&src=v5:endslate:related^play:related_0&from=shareembed-syndication
10 minute comparison of MSI and CTR
Touches on corporate provisioning in”User Based License Model Activation”. Users activate/deactivate, but IT still has control to deprovision the license (starting at about minute 8:15).
Then in this video / article :
http://blogs.technet.com/b/office_resource_kit/archive/2013/03/20/the-new-office-garage-series-identity-activation-data-access.aspx
They again say the companies can still allow userid activation while maintaining control of the licenses through Active Directory
<snip>
Jeremy: So we showed the installation experience for a domain-joined computer where single sign on is enabled and one that is not domain-joined, but installs via the Office 365 portal. In the direct from portal case when you kick off the
installation, you will see a file that looks something like this:
Setup.X86.en-us_O365ProPlusRetail_24*****-45a2-4eeb-b06f-b14****189c8_TX_PR_.exe
In a future episode we'll talk about all of the configurations needed to suppress completely sign-in, first run experiences and user prompts. IT admins have had to deal with these in past releases of Office, but now there are ways to
automatically sign users in to Office 365 installs picking up their domain credentials. I also showed the effects of deleting the user account from the Azure AD store and how it put Yoni's Office into Reduced Functionality Mode (RFM) -
even if Yoni installs Office on his personal devices using his organization's Office software assets, once Yoni leaves the org the IT department can deprovision his personal installs. That keeps software asset management cleaner and IT is in control.
Yoni: Don't forget we also had Mark Russinovich on the show and he explained the security model for online services with Azure AD - in your car. It sounds like they are taking the defense in depth approach to harden the service. And you
made him slum it in your car, Jeremy.
</snip>
Overview of ID, Authentication and Authorization in Office 2013
<snip http://blogs.technet.com/b/office_resource_kit/archive/2013/04/16/new-poster-and-content-roadmaps-about-office-identity-authentication-authorization-and-security.aspx
>
This page has links to 3 posters. The first poster “Identity and Authentication in the Cloud: Office 2013 and Office 365” describes at a high level how to control new user setup in a corporate / small business environment.
</snip>
<snip http://technet.microsoft.com/en-us/library/jj683102.aspx
>
This page also has a link to the same poster online (http://www.microsoft.com/en-us/download/details.aspx?id=38193 has PDF and Visio versions of the chart). As well, it goes into
more detail with information like the following:
… Because Office is a tool that is used by the same individual in two different roles, the new Office offers two identities with which users can log on to Office 2013:
A Microsoft account, which most people use for personal business
An organization ID that is assigned by Microsoft, which most people use when doing work for an organization, such as a business, charity, or school.
The credentials that are used to sign in are recognized as either personal or organizational. That sign-in identity becomes the user's “home realm” and determines which documents the user has access to on SharePoint, SkyDrive, or Office 365 Services for
a specific session. Each unique sign in identity is saved in a most-recently used list so that it is easy to switch between identities without leaving the Office experience.
a personal SkyDrive can be mounted to an organization identity so that personal documents can be accessed at work or school without ever switching identities. Also, when a user authenticates by using an identity, this authentication is valid for all Office
applications, not just the application he or she signed in to.
Two logon types are supported when users sign in to Office 2013, a Microsoft account or an organization ID that is assigned by Microsoft.
Microsoft account (the user’s individual account). This account, formerly known as Windows Live ID, is the credential that users use to authenticate with the Microsoft network and is frequently used for personal or non-business work, such
as volunteer work. To create a Microsoft account, a user provides a user name and password, certain demographic information, and “account proofs,” such as an alternative email address or phone number. For more information about the new Microsoft account, see
What is a Microsoft account?.
An organization ID that is assigned by Microsoft / Office 365 account ID that is assigned by Microsoft. This account is created for business use. An Office 365 account can be one of three types: a pure Office 365 ID, an Active Directory
ID, or an Active Directory Federation Services ID. These are described below:
Office 365 ID. This ID is created when an admin sets up an Office 365 domain and takes the form <user>@<org>.onmicrosoft.com, for example:
[email protected]
Organization ID that is assigned by Microsoft that is validated against a user's Active Directory ID. An organization ID that is assigned by Microsoft and validated against Active Directory as follows:
First, a person who has an [on-premise domain]\<user> account attempts to access organization resources.
Next, the resource requests authentication from the user.
Then, the user types in their organization user name and password.
Finally, that user name and password are validated against the organization AD database, the user is authenticated, and is given access to the requested resource.
An organization ID that is assigned by Microsoft that is validated against a user’s Active Directory Federation Services ID. An organization ID that is assigned by Microsoft and validated against Active Directory Federation Services (ADFS)
as follows:
First, one person who has an org.onmicrosoft.com attempts to access
partner organization resources.
Then, the resource requests authentication from the user.
Next, the user types in their organization user name and password.
Then, that user name and password are validated against the organization AD database.
Finally, that same user name and password are passed to the partner’s federated AD database, the user is authenticated, and is given access to the requested resource.
For on-premises resources, Office 2013 uses the domain\alias user name for authentication. For federated resources, Office 2013 uses the [email protected] user name for authentication.
</snip>
Office 365 Administration / Office 365 Administration Center / Office 365 Portal
http://technet.microsoft.com/en-us/library/jj819272.aspx
This page summarized methods of administering Office 365
User Account Management
http://technet.microsoft.com/en-us/library/jj819300.aspx
Sign-in for Small Business subscriptions
Users receive Windows Azure Active Directory cloud credentials—separate from other desktop or corporate credentials—for signing into Office 365 and other Microsoft cloud services.
Sign-in options for Enterprise, Midsize Business, Kiosk, Academic, and Government subscriptions
Office 365 for Enterprise, Midsize Business, Kiosk, Academic, and Government subscriptions has two systems that can be used for user identities:
Organizational account (cloud identity) Users receive Windows Azure Active Directory cloud credentials—separate from other desktop or corporate credentials—for signing into Office 365 and other Microsoft cloud
services. This is the default identity, and is recommended for small and midsize businesses in order to minimize deployment complexity. Passwords for organizational accounts use the Windows Azure Active Directory
password policy.
Federated account (federated identity) For all subscriptions other than Office 365 Small Business and Office 365 Small Business Premium, in organizations with on-premises Active Directory that use single sign-on
(SSO), users can sign into Office 365 services by using their Active Directory credentials. The corporate Active Directory stores and controls the password policy. For information about SSO, see
Single sign-on roadmap.
The type of identity affects the user experience and user account management options, as well as hardware and software requirements and other deployment considerations.
Custom domains and identity options
When you create a new user, the user’s sign-in name and email address are assigned to the default domain as set in the Office 365 admin center. By default, the Office 365 subscription uses the <company name>.onmicrosoft.com
domain that was created with the Office 365 account. You can add one or more custom domains to Office 365 rather than retaining the
onmicrosoft.com domain, and can assign users to sign in with any of the validated domains. Each user’s assigned domain is the email address that will appear on sent and received email messages.
You can host up to 600 registered Internet domains in Office 365, each represented by a different namespace.
For organizations using single sign-on, all users on a domain must use the same identity system: either cloud identity or federated identity. For example, you could have one group of users that only needs a cloud identity because they don’t access on-premises
systems, and another group of users who use Office 365 and on-premises systems. You would use add two domains to Office 365, such as
contractors.contoso.com and
staff.contoso.com, and only set up SSO for one of them. An entire domain can be converted from cloud identity to federated identity, or from federated identity to cloud identity.
For more information about domains in Office 365, see the
Domains service description.
Creating user accounts
Office 365 provides five ways to create user accounts, some of which are not available for Office 365 Small Business and Office 365 Small Business Premium: Add single User, Bulk upload using *.CSV files, Active Directory Synchronization, Azure Active Directory
Module for powershell, Exchange Simple Migration
Password management
The policies and procedures for password management depend on the identity system.
Cloud identity password management:
When using cloud identities, passwords are automatically generated when the account is created.
For cloud identity password strength requirements, see
Change your password.
To increase security, users must change their passwords when they first access Office 365 services. As a result, before users can access Office 365 services, they must sign into the Office 365 portal, where they are prompted to change their passwords.
Admins can set the password expiration policy. For more information for Enterprise and Midsize subscriptions, see
Set a user’s password expiration policy. For Small Business, see
Change how often passwords expire.
License management
A subscription to Office 365 is made up of a number of licenses to a set of services. An administrator assigns a license to each user for each service that user needs access to. For more information about managing licenses, see
Assign or remove a license in Office 365 Enterprise, or
Assign or remove a license in Office 365 Small Business.
Office 365 for Business FAQ
http://office.microsoft.com/en-us/business/microsoft-office-365-for-business-faq-FX103030232.aspx
Some general questions are answered
Deployment guide for Microsoft Office 2013
http://blogs.msdn.com/b/mssmallbiz/archive/2012/10/22/free-microsoft-ebook-deployment-guide-for-microsoft-office-2013.aspx
Free Download, 147 pg
Table of Contents
Getting help
Volume activation of Office 2013
Plan volume activation of Office 2013
Volume activation methods in Office 2013
Deploy volume activation of Office 2013
Use tools to configure client computers in Office 2013
Customize installations of Office 2013
Customize Setup before installing Office 2013
Configure a silent installation of Office 2013
Create custom configurations of Office 2013
Office Customization Tool (OCT) in Office 2013
Config.xml file in Office 2013
Setup command-line options for Office 2013
Setup properties in Office 2013
Setup architecture overview for Office 2013
Customize the Accessibility Checker for Office 2013
Outlook 2013
Planning overview for Outlook 2013
Choose between Cached Exchange Mode and Online Mode for Outlook 2013
Plan a Cached Exchange Mode deployment in Outlook 2013
Plan feature customizations in Outlook 2013
Choose security and protection settings for Outlook 2013
Configure multiple Exchange accounts for Outlook 2013
Configure Cached Exchange Mode in Outlook 2013
Configure Outlook Anywhere in Outlook 2013
Configure junk e-mail settings in Outlook 2013
Roll out Office 2013
Install Office 2013 from the local installation source
Deploy Office 2013 from a network installation point
Deploy Office 2013 by using Group Policy computer startup scripts
Language in Office 2013
Plan for multi-language deployment of Office 2013
Customize language setup and settings for Office 2013
Add or remove language packs after deployment of Office 2013
Mixed language versions of Office 2013
Companion proofing languages for Office 2013
Language identifiers and OptionState Id values in Office 2013
Security in Office 2013
Security overview for Office 2013
Authentication in Office 2013
Plan for Information Rights Management in Office 2013
Group Policy for Office 2013
Planning for Group Policy in Office 2013

Office 2013 Packager failed: Office (32-bit) not packaging because of Office (64-bit)

Hello,
I used ODT to download Office 2013 Pro 32-bit and now I am trying to create a package from those files. I use the command line:
Setup.exe /packager configuration.xml "E:\Office 2013 Pro App-v"
When I try to run this, I immidiatly get the following message:
"We found a problem! We're sorry, Office (32-bit) couldn't be installed because you have these 64-bit Office programs installed on your computer. Microsoft Office 2013. 32-bit and 64-bit versions of Office programs don't get along, so you can only have
one type installed at a time. Please try installing the 64-bit version of Office instead, or uninstall your other 64-bit Office programs and try this installation again."
I checked my installed programs on the server, but I don't have Office 2013 64-bit installed. I did in the past create packages for Office 2013 64-bit , but it's currently not in published/installed on the server. I checked with revo uninstaller to be sure.
Is there a registry setting, or something that is misleading App-V to believe I still have Office 2013 64-bit somewhere installed? I really need to stream MS Access 32-bit to users. But cannot solve this issue.
Thanks in advance,

Hello,
Thanks for replying. Your solution works, BUT I'm immidiatly running into a second problem. The .appv package that is created, cannot be published. The error I get is:
An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
I think this has to do with issues in the september releases of Office 2013. I'm gonna try downloading a previous versin using ODT. Changing the configuration.xml file to:
<Configuration>
<Add SourcePath="E:\DGI Applicaties\DGI Office 2013 Pro" OfficeClientEdition="32"
Version="15.0.4631.1002" >
    <Product ID="ProPlusVolume">
      <Language ID="nl-nl" />
<ExcludeApp ID="Excel" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="Infopath" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Outlook" />
<ExcludeApp ID="Powerpoint" />
<ExcludeApp ID="Project" />
<ExcludeApp ID="Publisher" />
<ExcludeApp ID="SharePointDesigner" />
<ExcludeApp ID="Visio" />
<ExcludeApp ID="Word" />
    </Product>
</Add>
    <Updates Enabled="False" />
    <Display Level="None" AcceptEULA="TRUE" />
<Logging Name="Office2013_package.txt" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

App-V 5.0 MAK activation in Office 2013

Similar Messages

Maybe you are looking for