App-V Office 2013/Office 365?

Hi,
In order to App-v Office 2013, apparently you need Office 365 ProPlus? How to get it, we do have Office 2013 ProPlus but that's not sufficient? Don't get what the difference is actually.
Note: we don't want to use  Office 2013 click-n-run.
J.
Jan Hoedt
Note: the click-n-run doesn't give the option to mention you Exchange server, the junk folder used in Outlook etc., that's what we really need (just as the setup.exe /admin option in Office.

The difference between Office 365 ProPlus and Office Professional Plus 2013 is licensing only as the text you've quoted shows and as Rory has provided details on as well.
This is separate from how you deploy Office. With either Office 365 or Office 2013 you can choose to use a standard installation or the Office Deployment Tool (App-V). Office 365 also provides the Click-to-Run version which you download from the Office 365
site.
If you have licensed Office 365, but want to use the Volume License media, you may have to purchase the media separately (which is really a download from the Volume License site). You may be required to purchase the minimum of 5 VL licenses to get access
to the media, but check with a Microsoft licensing expert for clarification. 
The only supported method of deploying Office 2013 / Office 365 with App-V is via the Office Deployment Tool. This means that you can't use the VL media (SETUP /ADMIN) to create a configuration and capture that with the Sequencer.
See these articles for more info:
https://support.microsoft.com/kb/2772509 (Rory has already posted this one)
http://support.microsoft.com/kb/2915745
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

  • "Cannot start Microsoft Outlook. Cannot open the Outlook window. The information store could not be opened." [Office 2013/Office 365]

    So here is the error in Outook 2013
    "Cannot start Microsoft Outlook. Cannot open the Outlook window.
    The information store could not be opened."
    Very Very frustrating having spent three hours today reading forums, installing, reinstalling etc.
    HELP?
    1) I have completely un-installed and reinstalled Outlook 2013 (And also all of Office 2013)
    2) Have blown away all profiles and created new ones.
    3) Have blown away all Outook data files and starting from scratch
    4) Have run /resetnavpane............in an attempt to rebuild the navigation pane
    5) Have gone into Registry and deleted all remnants of previous Outlook installs, HKey_Local, System Current
    config......Office etc.
    6) I have spent hours reading online fixes/technet forums etc..............to no avail.
    Please give more suggestions.
    Thanks
    Phil H   Charlotte, NC

    Hi,
    Basically you have tried a lot but the issue still exists, now one more suggestion I can provide is to make sure Outlook is not configured to run in Compatibility Mode:
    Take Windows 7 for example, in Start -> Type "Outlook" in the search box -> Right click on the "Outlook 2013" shortcut -> Click Properties -> Under Compatibility tab -> Make sure "Run this program in compatibility
    mode for" is clear.
    This method has resolved the issue for some users in this thread below:
    http://answers.microsoft.com/en-us/office/forum/office_2007-office_install/cannot-start-microsoft-office-outlook-error-cannot/e75265b4-044f-4d92-a078-1acbf9ae34d6
    I hope the information is helpful.
    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.

  • Right protected Microsoft Office 2013 office documents can not open

    Hello,
    I am facing a problem with opening right protected Office 2013 documents. I can right protect Office 2013 documents with Windows 2008R2 ADRMS servers but when i email it to another user who is having Office 2013, document will not open and "configuring
    your computer for information rights management" dialog box appear for long time without any change.  I have attached the screen shot aswell.
    Kindly help me to rectify this issue ASAP
    Dilshan

    I have seen something similar when your RMS pipeline URL is using SSL but the client opening the document does not have internet access.
    What happens is the client tries to get a CRL from crl.Microsoft.com and eventually times out.
    Does disabling CRL checking in IE change the behavior?

  • WSUS updates not applying to Office 2013 Home and Business OEM version

    Hi
    For some reason I cannot get WSUS updates to automatically install on clients running Office 2013 Home and Business OEM version.
    For example
    If user opens any of the office 2013 apps e.g. Outlook , word etc, it prompts a message at the top under the ribbon toolbar; UPDATE NOW.
    All other updates for OS are downloading and installing just fine from our WSUS server.
    What could this be?
    I dont have this issue with clients running office 2003

    First thing you need to do is be absolutely certain which edition of Office you have installed.
    There are five editions of "Office 365" and these days, almost anything that is "OEM" is almost certainly Office 365:
    Office 365 Home
    Office 365 Personal
    Office 365 Small Business
    Office 365 Small Business Premium
    Office 365 Midsize Business
    Office 365 ships with an activation code for an online management account, and authorizes the installation of the software on up to five devices. Office 365 is updated via the WEB .. ONLY.
    In addition there are three editions of Office 2013:
    Office Home & Student
    Office Home & Business
    Office Professional
    If you have one of these three editions, you should also have a DVD and a Product Activation Code for the SINGLE-PC installation which is licensed for these editions provided by the vendor of your computers. Office 2013 can be updated using WSUS.
    Since you're getting a prompt IN THE APPLICATION to "Update Now", I believe you're looking at instances of Office 365, not Office 2013. Office 2013 (desktop) does not provide in-product prompts for updates/upgrades.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • 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 Service Pack 1 installation causes shim error in Windows 8.1 Enterprise

    On a clean install of Windows 8.1 Enterprise and Office 2013 I installed RSAT and everything works fine initially.  When I install the Office 2013 Server Pack 1 update (categorized as an "Important" update) I then get the following
    errors when attempting to open Server Manager:
    (I attempted to include an image of the error and a link to the KB article but it wouldn't allow that saying my account must be verified although there appears to be no way to actually verify my account.  The "Verify Your Account 13" thread
    doesn't help by the way.)
    ServerManager.exe - This application could not be started.  Do you want to view information about the issue?
    Which if I click Yes it takes me to the page for this KB article:
    KB2715633
    The KB page refers to three different SHIM errors.  The second two don’t apply to this scenario but the first seems to.  Unfortunately the info on this one is:
    “The app is not configured in a way that makes it possible to determine the appropriate version of the .NET Framework runtime.
    You can't fix the configuration problem yourself. Contact the app vendor to resolve the issue.”
    I've re-installed Windows twice and have been able to replicate the problem each time (Clean Win 8.1 install, Office 2013 install, RSAT, everything works, install Office 2013 SP1).
    It says in the KB to "Contact the app vendor".  In this case that would be Microsoft. 

    1. What is you install W 8.1 ENT + all important updates -> Office 2013 > Office 2013 SP1 > RSAT ?
    2. Make sure that .NET 3.51 and 4.51 are installed.
    3. Make sure that there is no coincidence with issues
    http://support.microsoft.com/kb/2817430
    4. Try to sesolve problem with Process Explorer and Process Monitor
    HTH
    Milos

  • Office 2013 products manage version function never responds

    This all started a few weeks ago and had previously been working.
    scenario ...
    Open any office document from any internal SharePoint 2010 site
    Go to Info->Manage Versions, we receive a trying to retrieve server versions message and the refresh server version list is greyed out.
    Thus in the office app you cannot checkout a document. If you check out the document in SharePoint first, and then open it you cannot checkin an updated version from inside the office app, for the same reason. This only occurs on clients running office
    2013, office 2010 clients continue to work. There are multiple separate SharePoint farms involved, so I don't think it is a server side issue. I can save the document changes and then go back to SharePoint and explicitly checkin the changes. It affects
    multiple users on multiple client machines.

    Hello,
    Thank you for your question.
    I am trying to involve someone familiar with this topic to further look at this issue.
    Thanks
    George Zhao
    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 "[email protected]"

  • Re-installing windows, will i have to re buy office 2013

    I am going to re install windows on my laptop,I was wondering if I would have to buy office again if I wiped my hard drive and re install windows.

    Hi,
    You can reinstall Office and activate it with your original product key. As long as your hardware is not substantially different, Office product key will still works.
    If you have made changes to the hardware, then it will be considered as a new computer. You may choose the phone activation and activate the Office. You might check this link to see how to do a phone activation:
    https://support.office.com/en-US/Article/Activate-Office-2013-Office-365-Home-or-Office-365-Personal-1144e0de-e849-496e-8e33-ed6fb1b34202
    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.

  • SharePoint 2013 - Office 365 Custom Rating(0-5) Sharepoint Hosted App SetRating Reputation Class using Javascript and CSOM

    I have created the list and enabled the rating feature. I want to display the List items and rate individual items from an App.  I can able to create and bind the rating control through CSOM associated with the Rating Value.  But I unable to rating
    when I click rating star button. I am using the below code for clicking through JavaScript
    function SetRating(webUrl, listId, itemId, ratingElementId) {
    hostWebContext = new SP.AppContextSite(context, hostWebUrl);
    var listPrograms = hostWebContext.get_web().get_lists().getByTitle("MyList");
    context.load(listPrograms);
    var RatingValue = 5;
    EnsureScriptFunc('reputation.js', 'Microsoft.Office.Server.ReputationModel.Reputation',
    function () {
    var rating = Microsoft.Office.Server.ReputationModel.Reputation.setRating(hostWebContext, listId, itemId, RatingValue);
    context.executeQueryAsync(Function.createDelegate(this, this.RatingSuccess), Function.createDelegate(this, this.RatingFailure));
    While executing this script I got error like get 0x800a01b6 - JavaScript runtime error: Object doesn't support property or method 'addQuery'
    * Which Context we have to use for this case? AppWeb / HostedWeb
    * Is there any way to update the rating control value at runtime?
    Please help us to find out the solution.
    Thanks.

    Hi Elie,
    Since this forum is discussing about Developing Apps for Office 2013, and your issue is more related about Exchange development. I will move this thread to the more related forum.
    Reference:
    https://social.msdn.microsoft.com/Forums/en-US/home?forum=exchangesvrdevelopment
    Thanks for your understanding.
    Best Regards,
    Edward
    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.

  • Office 2013 VL and app-v 5 SP2 on RDS server - package add fails with script error

    We have used the MS Office Depolyment Tool for click-to-run to download the latest Office 365 version, and flatten it into an app-v 5 package - not a problem.
    When we try to add the package to our client machine (Server 2008R2 running the app-v 5 SP2 client software), it fails with an message that a script has failed and not returned a 0 code.  We have not added any scripting to this automatically created
    package, so it seems that the app-v client does not like the "official" package.  Any hints and tips gratefully accepted, thanks
    App-v client has scripting enabled.
    The powershell command line we are using is:
    PS C:\windows\system32> Set-ExecutionPolicy Unrestricted
    PS C:\windows\system32> Add-AppvClientPackage -path file://hostname/app-v/o365-noaccess/ProPlusVolume_en-us_zh-cn_x86.appv -DynamicDeploymentConfiguration \
    \hostname\app-v\O365-NoAccess\ProPlusVolume_en-us_zh-cn_x86_DeploymentConfig.xml
    with a result of:
    Add-AppvClientPackage : Embedded Script process exited with an error code indicating failure (return code other than 0). Please ensure that Embedded
    Script process can complete successfully and exits with 0.
    Operation attempted: Configure AppV Package.
    AppV Error Code: 100000000C.
    Please consult AppV Client Event Log for more details.
    At line:1 char:1
    + Add-AppvClientPackage -path
    file://hostname/app-v/o365-noaccess/ProPlusVolum ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~
        + CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException
        + FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage
    and these are the error messages we see in the debug app-v client logs:
    Script Launcher successfully waited for script with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe" /I /Msi /License /AppV PackageGUID=D24C3BDD-8FAD-44d3-998C-933F8F053682
    PackageRoot="C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
    PRIDName=ProPlusVolume'.
    and...
    Package {d24c3bdd-8fad-44d3-998c-933f8f053682} version {cd9725ce-4503-4932-863b-4fcda3f9551d} failed configuration in folder 'C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D' with error 0x79100E10-0xC.
    and...
    machine script for event AddPackage with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe"'
    exited with failure error code: The extended attributes are inconsistent.. Because Rollback is set to true in the script definition, the current AppV Client operation was rolled back.
    We believe this last error message is the kicker, but can't debug any further.

    Just to validate the problem, I started again.
    I have just downloaded the latest ODT from MS, and then downloaded the latest Office 2013 packaged - volume license.  Then created the app-v package - all went perfectly, no error messages.  Uploaded the package to the app-v 5 server and published
    it.  I have made NO changes to any of the files.
    I have just built a brand new Windows Server 2008R2 Datacentre VM, patched it to the hilt, and installed the RDS role, powershell 3 and appv 5.0 SP2 client for RDS.
    I then use powershell as above:
              scripting unrestricted
              app v client scripting enabled
             app v server added
              global and user update enabled
             add-appvclient package  "url of office package.appv"
                 and received exactly the same error message.  
    It is not complaining that scripting is not allowed, it is complaining that the script is invalid.
    Help!!!!

  • Problems with Lync integration in App-V Package for Office 365 ProPlus

    We have problems with setting Lync 2013 to automatic start after Windows start with Office 365 ProPlus App-V Package made by Office Deployment Tool. We use latest version for both (ODT and download package) at Windows 7 Enterprise 64 bit.
    We have done this for Lync 2010 and also for Lync 2013 (MSI installations) and it works correctly.
    User can choose to start Lync automatically, but this settings is ignored and in virtual registry is set wrong. We look for possible ways to set this by GPO (in ADMX is not this option available) by inserting in virtual registry with Package ID and user
    SID in registry path.

    Usually setting apps to auto start sets a registry key under HKCU\Software\Microsoft\Windows\CurrentVersion\Run, but since this registry key is inside the virtual environment, Windows does not read it at logon.
    The workaround is to either set this key in the native registry (perhaps by an App-V script), or easier still, just copy the shortcut to the Start Menu\Programs\Startup folder. Since you can't really modify Office 2013 packages with the sequencer, you'd
    have to add this shortcut by modifying the deployment config file.
    Dan Gough - UK App-V MVP
    Blog: packageology.com
    Twitter: @packageologist
    LinkedIn

  • App-V 5 SP2 and Office 2013 - How to control user access?

    What is the best way to control access to the Office 2013 application shortcuts?
    Because it must be published globally, how can we only allow certain users to access Office 2013 on RDS servers when the default action would mean all users can access it?
    Can removing the shortcuts using the DeploymentConfig file (see
    here) followed by setting up something using the UserConfig file linked to an AD group work?
    If so how would this be done?

    See these threads:
    http://social.technet.microsoft.com/Forums/en-US/a455d7e2-e0e6-4843-b07b-42afc18623e2/office-365-proplus-appv-50-package-installs-lync-outlook-infopath-and-onenote-even-though-they?forum=mdopappv#6fbcf59b-351c-48d1-8e63-539550a88b56
    http://social.technet.microsoft.com/Forums/en-US/f4b47f1e-e494-4477-97e9-6942c4f8ec2d/office-2013-vl-appv-5-packages?forum=mdopappv#7f63bea4-57c3-40a7-bdf4-6f25320e5b68
    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

  • Office 2013 (local) vs. Office 365 (cloud)

    For the moment we are primarily interested in using the main Office 2103 apps from the user Desktops. (We do not want users to even store documents on the cloud)
    1. Is there a URL indicating the feature differences between local and cloud Office 2013?
    2. If we install the suite locally and Microsoft updates the cloud based version, I presume our local verisons will
    not be updated automatically. Is that correct?
    TIA,
    edm2

    FWIW, Office 365 desktop applications are Office 2013  and are installed locally, on your desktop, just like every other previous version. Storing documents in the cloud is optional with all versions of office, either subscription or the perpetual license
    version.
    1. Which office suite are you looking at? The subscription is office pro plus. See http://products.office.com/en-us/buy/compare-microsoft-office-products for the non-subscription offers.   Also, the perpetual license doesn't get a license for ipad/android
    tablets. 
    2. You'll be able to install updates as you do now using windows updates, but the updates may not be available for days or weeks after the click to run versions. (So far this isn't happening, but it could in the future.) 
    Diane Poremsky [MVP - Outlook]
    Outlook & Exchange Solutions Center
    Outlook Tips
    Subscribe to Exchange Messaging Outlook weekly newsletter

  • How to Get user profile properties in provider -cloud hosted app in sharepoint online - office 365 using REST API?

    How to Get user profile properties in provider -cloud hosted app in sharepoint online - office 365 using REST API?
    any idea?

    Hi,
    From your description, my understanding is that you want to get user profile properties in provider-hosted app in SharePoint online using REST API.
    Here is sample code for getting user profile properties:
    http://www.vrdmn.com/2013/07/sharepoint-2013-get-userprofile.html
    Here is a blog below about accessing data from the provider-host apps:
    http://dannyjessee.com/blog/index.php/2014/07/accessing-sharepoint-data-from-provider-hosted-apps-use-the-right-context/
    Best Regards,
    Vincent Han
    TechNet Community Support
    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]

  • Stream 7 - Reinstall local Office 2013 from Office 365 subscription

    Ok, I signed up for my free year of 365 3-4 weeks ago.  Doing so resulted in downloading the desktop Office 2013 for a local install.
    Takes up a lot of valulable space, and there are a few Office apps I rarely use (Access, etc.)  Mostly Word, Excel and PP.
    So, I'd like to remove the apps I don't use, but in the case I want to use them later - how do I reinstall them?  The download occurred "automagically" as a result of the Office 365 subscription/signup process - I have no D/L to reinstall.  Nor, do I believe, do I have a key to take an existing install and install and activate.
    So - how can I D/L and install later?  And possibly determine just what my key is for that day?

    Due to limited storage, the installation folder/files is not downloaded into the device. The only way you can reinstall the MS Office is by doing recovery but will wipe out your data. After recovery you need to use the same account you used the fisrt time you registered your Office.
    Hope this helps.

Maybe you are looking for