APP-V Office 2013 configuration.xml

Hi all, 
I'm trying to roll out Office 2013 with APP-V, whenever I change the config.xml to accept the EULA it still pops up with the EULA.
The documentation for APP-V differs from the normal ODT config.xml, what's the difference and am I missing out on something? 
See the document from Microsoft on the configuration.xml within app-v: 
https://technet.microsoft.com/en-us/library/jj219426.aspx
The XML file states to accept the EULA. The output in there is a configuration.xml like this: 
<Configuration>
  <Add SourcePath="C:\office2013" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="nl-nl" />
<Language ID="en-us" />
    </Product>
<Product ID="ProjectProRetail">
      <Language ID="nl-nl" />
<Language ID="en-us" />
    </Product>
 <Product ID="VisioProRetail" >
      <Language ID="nl-nl" />
<Language ID="en-us" />
    </Product>
  </Add>
<Display Level="None" AcceptEULA="TRUE" />
<Property Name="SharedComputerLicensing" Value="1" />
</Configuration>
Kind regards, 
Jacob van Rooijen

You can use two registry keys to disable it, push them using a GPO:
HKCU\Software\Policies\Microsoft\Office\15.0\Registration
Reg_DWORD = "AcceptAllEulas"= 1
HKCU\software\policies\microsoft\office\15.0\firstrun
Reg_DWORD = "bootedrtm" = 1
See this post

Similar Messages

  • 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

  • Office 2013 Silent XML setup works on 64-bit version but not on 32-bit

    Hello,
    I'm using a powershell script to silently install Lync 2013 (which is part of Office 2013) when domain computers initialize.
    The installation is using a XML file to get the configurations and installs only Lync (not Word, Excel, etc). The 64-bit Office version installation I tested several times and is working fine, it installs only Lync 2013, but the 32-bit installation is using
    an identical XML file, just changing the 64bit source to the 32bit source, and installs ALL the Office Products, everything. Anyone know whats wrong?
    This is the xml file:
    <Configuration Product="ProPlus">
    <OptionState Id="LyncCoreFiles" State="Local" Children="Force" />
    <Display Level="None" CompletionNotice="Yes" AcceptEula="Yes" />
    <Logging Type="verbose" Path="%temp%" Template="LyncSetupVerbose(*).log" />
    <Setting Id="REMOVEPREVIOUS" Value="" />
    <Setting Id="SETUP_REBOOT" Value="Never" />
    <DistributionPoint Location="\\grupouniasselvi.local\office\source\office2013_32bit" />
    </Configuration>
    And starting the setup like this: setup.exe /config configlync.xml

    Messing around with the XML file I found a workaround to the problem, explicit added the others products in the config.xml and set to "Absent", like this:
    <Configuration Product="ProPlus">
    <OptionState Id="LyncCoreFiles" State="Local" Children="Force" />
    <OptionState Id="ACCESSFiles" State="Absent" Children="Force" />
    <OptionState Id="EXCELFiles" State="Absent" Children="Force" />
    <OptionState Id="GrooveFiles" State="Absent" Children="Force" />
    <OptionState Id="OneNoteFiles" State="Absent" Children="Force" />
    <OptionState Id="OUTLOOKFiles" State="Absent" Children="Force" />
    <OptionState Id="PPTFiles" State="Absent" Children="Force" />
    <OptionState Id="PubPrimary" State="Absent" Children="Force" />
    <OptionState Id="VisualStudio_PreviewServer_SPD" State="Absent" Children="Force" />
    <OptionState Id="WORDFiles" State="Absent" Children="Force" />
    <OptionState Id="XDOCSFiles" State="Absent" Children="Force" />
    <OptionState Id="GrooveFiles2" State="Absent" Children="Force" />
    <OptionState Id="TOOLSFiles" State="Absent" Children="Force" />
    <Display Level="None" CompletionNotice="Yes" AcceptEula="Yes" />
    <Logging Type="verbose" Path="%temp%" Template="LyncSetupVerbose(*).log" />
    <Setting Id="REMOVEPREVIOUS" Value="" />
    <Setting Id="SETUP_REBOOT" Value="Never" />
    <DistributionPoint Location="\\grupouniasselvi.local\office\source\office2013_32bit" />
    </Configuration>
    It installed only Lync 2013 now, but its really odd that I needed to do this with the 32bit source and a single line did it with the 64bit source. Whats the difference? :(

  • App-V Office 2013 MLCFG32.cpl and Search indexing

    Hi there, 
    I used the ODT to make an app-v package of office 2013. However when I try to load the mlcfg32.cpl it displays the following error: 
    The operating system is not presently configured to run this application. 
    I start the cpl from the following location: 
    C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\764C2E31-0B14-4E44-818A-2836992E7EA6\Root\Office15
    Also the search indexing isn't working in Outlook 2013, whenever I try to load the indexing status it keeps on loading with no result. I wanted to remove the profile from Outlook 2013, but with no mlcfg32.cpl it's very hard. 
    I also tried a repair of the application with no result. 
    Why is there so little information on packaging office 2013 in combination with App-v from Microsoft? 

    Well the package should be published globally, in the policy the global refresh is enabled. However when I look at the settings of the application I see the following: 
    PackageId            : d24c3bdd-8fad-44d3-998c-933f8f053682
    VersionId            : 764c2e31-0b14-4e44-818a-2836992e7ea6
    Name                 : Microsoft Office 15 ProjectProRetail_O365ProPlusRetail_V
                           isioProRetail_nl-nl_en-us_x86
    Version              : 15.0.4701.1002
    Path                 : \\SRV-SDLP-001\Applications\AppV\Microsoft Office
                           2013,Visio,Project ProPlusRetail nl-nl,en-us\ProjectProR
                           etail_O365ProPlusRetail_VisioProRetail_nl-nl_en-us_x86.a
                           ppv
    IsPublishedToUser    : True
    UserPending          : False
    IsPublishedGlobally  : False
    GlobalPending        : False
    InUse                : False
    InUseByCurrentUser   : False
    PackageSize          : 2603951976
    PercentLoaded        : 100
    IsLoading            : False
    HasAssetIntelligence : True
    All of our applications state that they are published to the user... but our refreshing policy states the following:
    Id                        : 1
    SetByGroupPolicy          : True
    Name                      : appvserver
    URL                       : http://appvserver.ourdomain.com:889
    GlobalRefreshEnabled      : True
    GlobalRefreshOnLogon      : True
    GlobalRefreshInterval     : 1
    GlobalRefreshIntervalUnit : Hour
    UserRefreshEnabled        : True
    UserRefreshOnLogon        : True
    UserRefreshInterval       : 1
    UserRefreshIntervalUnit   : Hour
    We use the native App-V management server in combination with App-V publishing server... 

  • Office Open Xml (PPT Office 2013) - Drawing.xml looses the SmartArt Shapes Information

    I am facing a weird problem. When I open and edit a PPT presentation containing SmartArt and then save it, it looses all the SmarArt shapes information present inside the drawing.xml (OXML) inside the diagrams folder. This happens only when I edit any other
    slide (like changing title text) in the presentation not containing the SmartArt and then save it. The whole SmartArt shapes information just vanishes and somehow PPT is able to regenerate the presentation from this drawing.xml when i reopen the presentation
    and doesn't show it as corrupt. Initially I thought its an issue specific to my machine but I checked it on other machines and its replicable on them as well. Is it an issue with PPT in Office 2013?

    I called nViida thinking it might be an nVidia issue.  He told me to download the 335.70 beta which I did and installed.  Didn't help.
    I think called Microsoft and first guy took control of my PC and suggested I install Office Pro 2013 x86 (32-bit) and then transferred me to 3 people before I got disconnected; very frustrating having to explain my issue 3 times.
    I uninstalled Office Pro 2013 64 bit and installed x86 and my problems went away.  The Tech told me that the 32 bit version is more stable and they haven't had as many issues and told me that 3rd party apps integrate (like ACT! Contact management which
    I use) so I installed the x86 version and NOW WORD, EXCEL AND POWERPOINT ARE WORKING. 
    I need to get IE 11 x86 working but that isn't that important as I use Firefox as my main browser and Chrome secondarily.
    Not the greatest resolution but something didn't like the 64 bit version of Office when I did the 8.1 Update and Office updates yesterday.

  • 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

  • 0x87D01280 "Virtual application is currently in use" error when uninstall App-V Office 2013 in Software Center

    Getting the above error message when attempting to uninstall Office 2013 App-V version (downloaded using ODT) in Software Center. There are no office 2013 or App-V processes showing as running in Task Manager. Nothing in event viewer to show what is running
    either. Any idea on what could be running and holding the uninstall from completing?

    Hello,
    These issues are caused if the virtual package is used during the attempt to uninstall.
    SFTMIME is a legacy command-line interface for App-V 4.6, not supported for usage with App-V 5 (which is the only version that supports Office 2013).
    App-V 5.0 SP2 has introduced the ability to divert required actions to next logoff / reboot depending on publishing, if the package is in use.
    See these articles;
    http://www.applepie.se/app-v-5-0-sp2-and-pending-removal-update
    http://blogs.technet.com/b/virtualvibes/archive/2013/12/03/pending-tasks-in-app-v-5-0-sp2.aspx
    Nicke Källén | The Knack| Twitter:
    @Znackattack

  • Uninstall App-v office 2013 package sccm 2012

    Hi ,
    how do we add uninstall command to office 2013 appv appliation in sccm 2012, i see no option were we can give command lines unlike normal msi apps.
    please confirm
    Thanks

    Please take a look at this previous thread:
    https://social.technet.microsoft.com/Forums/en-US/6663cb6e-23c1-48e6-a62e-85c447b88f3d/appv-application-uninstall-with-sccm-2012-integration?forum=mdopappv
    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
    rorymon.com Twitter: @Rorymon

  • Office 2013 deployment tool Invalid product ID error

    Hi,
    Im in the process of virtualizing apps like Office 2013 with App-V. 
    Downloading the binaries with the Office Deployment tool and converting to app-v package is very easy, I've followed this kb
    http://support.microsoft.com/kb/2915745
    But now I want to sequence add-ins for Office 2013. So I need a local install of Office 2013 click to run.
    Im trying to use the command line option setup.exe /configure <path to config.xml> but everytime I try this I receive this error:
    Invalid product ProPlusVolume specified. Error configuring products
    I have tried several different ProductID's like ProPlusVolume and StandardVolume. None of the volume ID's seem to work. When I changed the ID to ProPlusRetail, the setup worked flawless. But I need to install the Volume version for my RDS server...
    I have found other people in the comment section in this blog: http://blogs.technet.com/b/office_resource_kit/archive/2013/12/03/3615124.aspx
    (read the comments in the bottom section) But no solution..?

    It's my understanding that  you don't use the "/configure" parameter when using the "Volume" options.
    Jeremy refers to this in the comments/responses.
    In the main blog article, he refers to "You can now use the Deployment Configuration file to configure...."
    This does not mean that you should use the "/configure" parameter - that is only used for C2R.
    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

  • How to force Office 2013 CTR update regularly

    We are using around 60 PKC licenses of Office 2013 which came in CTR format (we don't have any Office 365 subscription, these licenses came with the new computers). CTR can't be managed via WSUS and it usually updates itself once or two per month (ideally).
    But we have noticed that many clients are not updating regularly. Actually some are stuck on January builds. When you go to such PC it shows that Update is ready. Why it doesn't update automatically? Is the PC has to be idle for some time? Then it is a bad
    design as our employees usually do not slack around half a day and work with Office all the time. How can i force CTR versions to update? Other than going to every machine and pressing Update now or asking users to do so.
    Digging about this i have stumbled upon a blog post about Office Deployment Tool which came out recently (version 1, 2014.05.06). http://blogs.technet.com/b/odsupport/archive/2013/06/19/using-the-office-deployment-tool.aspx Can it provide a way to force
    updates or is it just a way to keep updates on a local share to save the bandwidth? Will the scheduled task behave the same in this scenario and wait for months to update?
    Also, it looks like ODT download page is broken, nothing happens http://www.microsoft.com/en-us/download/details.aspx?id=36778&751be11f-ede8-5a0c-058c-2ee190a24fa6=True

    Hi,
    The Click-to-Run for Office 365 Configuration.xml file is used to specify Click-to-Run installation and update options.
    You can specifies attributes for configuring updates in the xml file, If
    Enabled is set to TRUE, the Click-to-Run update system will check for updates automatically.
    If UpdatePath is set to empty (""), updates are obtained from the Microsoft Click-to-Run source, CDN. Not from a local server:
    <Updates
    Enabled=TRUE | FALSE
    UpdatePath=UNC | local | http path
    TargetVersion=X.Y.Z.W
    Deadline=MM/DD/YYYY HH:MM
    />
    More reference about the configuration.xml file and ODT tool:
    http://technet.microsoft.com/en-us/library/jj219426(v=office.15).aspx#BKMK_UpdatesElement
    http://technet.microsoft.com/en-us/library/jj219422(v=office.15).aspx#BKMK_ConfigxmlForConfigure
    Download link for ODT:
    http://www.microsoft.com/en-us/download/details.aspx?id=36778 It works for me, please have a try.
    Thanks,

  • Deploy Office 2013 - Uninstall Office 2010

    Hello,
    I am planing to deploy Office 2013 and created a MSP File (Setup /admin) for the silent Installation - everything works fine - except the uninstallation of Office 2010. In the OCT I´ve selected the Option to remove previous Versions of Office. I can
    remeber that this works perfect in Office 2010 to remove Office 2007 too.
    But in Office 2013 this doesn´t work anymore, the installed applications wizard (appwiz.cpl) Shows both Version of Office are installed. What is the best way to remove the old Version silently and install Office 2013? I would like to have all in one
    "Application" deployed via SCCM 2012 SP1. 

    Have you looked at this document, or it's online equivalents:
    http://blogs.msdn.com/b/mssmallbiz/archive/2012/10/22/free-microsoft-ebook-deployment-guide-for-microsoft-office-2013.aspx
    In the section "Setup command-line options for Office 2013", they say:
    /uninstall [ProductID]
    Runs Setup to remove the specified product from the user’s
    computer. Look up the value of [ProductID] in the Setup.xml
    file for the product that you want to modify.
    Example
    \\server\share\Office15\setup.exe /uninstall ProPlus
    where:
    Office15 is the root of the network installation point.
    ProPlus is the
    [ProductID] ([ProductID]
    is equal to the ID attribute of the
    Setup element listed in
    \\server\share\Office15\ProPlus.WW\setup.xml), where
    ProPlus.WW is the location of the Office Professional Plus 2013 installation files.
    You can customize the
    /uninstall option by using it with
    /config and a modified Config.xml file. This is necessary if you want to run a
    “silent”
    uninstall. In enterprise deployments, we recommend that you run a silent uninstall to prevent prompting users to enter information, and to prevent the installation from waiting for user interactions, even when files are being used.
    To run a silent uninstall
    Using a text editor, edit the following element attributes in the
    \\server\share\Office15\ProPlus.WW\SilentUninstallConfig.xml file:
    <Configuration Product="ProPlus">
    <Display Level="none"
    CompletionNotice="no" SuppressModal="yes"
    AcceptEula="yes" /> </Configuration>
    At the command line, use the following syntax:
    \\server\share\Office15\setup.exe /uninstall ProPlus /config \\server\share\Office15\ProPlus.WW\SilentUninstallConfig.xml
    Note:
    In Office 2013, just as in Office 2010 and Office 2007, you cannot use the Setup.exe command line to set Windows Installer properties, such as
    PIDKEY or DISPLAY. Setup does not pass these properties to Windows Installer. Instead, you make these customizations by using the Office Customization Tool or Config.xml. For a complete list of Setup properties, including blocked
    and unsupported properties, see Setup properties in Office 2010.
    The information also applies to Office 2013.
    Office Customization Tool (OCT) in Office 2013
    Config.xml file in Office 2013

  • Office 2013: 10 Best Features You Should Know About

    The new Office 2013 has some key updates that, while aren’t quite as dramatic as theWindows 8 from Windows 7change, still have some pretty cool features for mobile and desktop.  Office 2013, will ship sometime next year at prices that have not been announced
    yet.  Check out the top 10 features:
    Going Mobile. Microsoft has geared the new software towards a more mobile-friendly audience, allowing users to interact more
    efficiently on mobile and tablets including finger and stylus controls that may help to spur Office’s migration to mobile devices. Another decidedly mobile move is Office Home and Student 2013 RT, which includes Word, Excel, PowerPoint, and OneNote, will come
    with ARM-based Windows 8 devices including Microsoft Surface .
    In The Cloud. Microsoft’s SkyDrive cloud service is being positioned to play a key role in Office users’ daily computing
    lives. Office 2013 will save your documents to SkyDrive by default, enabling you to access files from multiple devices, including a smartphone and tablet. When you sign into Office from another device, your personalized settings and recently used files
    are already there for you. The new Office is available as a cloud-based subscription too. Office 365 is now also available for home-based users as well as businesses. Subscribers will get automatic upgrades, additional SkyDrive storage, multiple installs for
    several users, and added perks such as international calls via Skype.
    Finger and Stylus. Office 2013 embraces touch and pen input. The touch and stylus features are geared towards smartphones and
    tablets, as well as multi-touch laptops. The touch features are the same as users are accustomed to on their smartphones and tablets; swipe a finger across the screen to turn a page, pinch and zoom to read documents, and write with a finger or stylus.
    Metro Style. Office 2013 conforms to Microsoft’s “Metro” look that’s pervasive across the software developers latest mobile
    apps. The Office Ribbon in Word 2013 has a flatter look than its predecessor in Word 2010.
    PDF’s in Word. You can now edit PDF files in Word 2013 (yay!). Simply open a PDF as you would any other document. Word maintains
    the formatting of the file which is fully editable. You can insert pictures and videos from online sites such as YouTube and Facebook as well. And readers can watch video clips from inside your document.
    Excel. Excel offers some useful upgrades including new templates for budgets, calendars, forms, and reports. The new Quick
    Analysis Lens lets you convert data to a chart or table in a couple of steps. Flash Fill recognizes patters in your data and automatically fills cells accordingly. For example: if you want to separate first and last names into separate columns simply begin
    typing the first names in a new column, press Ctrl+E and Excel will copy the first names for you.
    PowerPoint Has Gained Power. PowerPoint 2013 now sports an updated Start screen with a variety of new themes and color schemes.
    The Presenter View now makes it easier to zoom in on a diagram, chart, or other detail that you want to emphasize to the audience. The Navigation Guide lets you switch slides, even move out of sequence, from a grid that you can see but your audience can’t.
    Presentations can be worked on from different PCs by colleagues to create a single presentation. Comments are allowed and presentations are saved online by default to SkyDrive.
    OneNote. OneNote automatically saves your notes to Skydrive, you don’t have to click “Save”, making your brainstorming sessions
    readily available across multiple devices. OneNote 2013 allows you to grab screens and add them to your notebooks.
    Skype Has Been Integrated. You can now integrate Skype contacts with Microsoft’s enterprise-oriented Lync communications platform
    for calling and instant messaging. Office subscribers get 60 minutes of Skype international calls each month.
    Going Social. Office now includes Yammer, a secure and private social network for businesses that Microsoft tentatively acquired.
    Yammer integrates with SharePoint and Microsoft Dynamics, the company’s line of CRM and enterprise resource planning apps. Office 2013′s People Card tool provides detailed information about your contacts, including their status updates from Facebook and LinkedIn.

    Awesome!
    Thanks for sharing the greate experience here. This is a good summary of Office 2013 cool features which is definitely useful for those who want to learn about the new Office.
    Thanks,
    Ethan Hua CHN
    TechNet Community Support

  • 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

  • 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.

Maybe you are looking for