none
Office 2013 First Run and EULA RRS feed

  • Question

  • Hello,

    Is anyone succeeded in disable the First Run experience & First things First, and to accept the EULA automatically in Office 2013?

    Both EULA and the First Run wizards keeps bothering me after I disabled them using:

    • ODT’s Configuration.xml 
    <Display Level="None" AcceptEULA="TRUE" />
    • Local GPO (local for testing purposes)
    Disable First Run experience
    User Configuration\
     Microsoft Office 2013\
      First Run    Disable First Run Movie - Enabled
       Disable Office First Run on application boot – Enable
    Disable “First things First”
    User Configuration\
     Microsoft Office 2013\
      Privacy\
       Trust Center
        Disable Opt-in Wizard on first run – Enabled
        Enable Customer Experience Improvement Program – Disabled
        Allow including screenshot with Office Feedback - Disabled
        Send Office Feedback – Disabled
        Automatically receive small updates… - Disabled

    Both things doesn't disable First Run and accept the EULA for the user. Is anyone succeeded in disable these using Configuration.xml or GPO's?

    App-V 5.0 SP2
    Latest ODT version (2/25/2014) : http://www.microsoft.com/en-us/download/details.aspx?id=36778

    Wednesday, March 26, 2014 1:59 PM

Answers

All replies

  • I disabled the same two features in a deployment i did.  Try inserting these two registry keys.

    HKCU\Software\Policies\Microsoft\Office\15.0\Registration
    Reg_DWORD = "AcceptAllEulas"= 1

    HKCU\software\policies\microsoft\office\15.0\firstrun
    Reg_DWORD = "bootedrtm" = 1

    • Proposed as answer by ian rendall Wednesday, July 29, 2015 2:18 PM
    Wednesday, March 26, 2014 4:35 PM
  • Hello,

    My guess, since those reg-keys are in the key policies, is that it would be recommended to use GPO to push them out.


    Nicke Källén | The Knack| Twitter: @Znackattack

    Saturday, March 29, 2014 10:49 AM
  • Ben, did you ever get this figured out? Nicke's answer is not the correct answer as you were trying to push out the settings using GPO and I've also tried it.
    Monday, July 14, 2014 8:07 PM
  • Hello,

    One additional way (except for the GPOs), would be the as previously blogged;

    http://myitforum.com/myitforumwp/2013/12/18/using-app-v-to-deploy-office-2013/


    Nicke Källén | The Knack| Twitter: @Znackattack

    Monday, July 14, 2014 8:14 PM
  • Hi Nicke

    I actually tried that this morning before trying to go the GPO root but the keys aren't getting written to the registry. I suspect it's because we're streaming to the computer rather than doing a full install/running locally.

    Thanks
    Mike

    Monday, July 14, 2014 8:30 PM
  • Tried both (GPO and the "myitforum way"), but none works for me.

    Gave up on this a while ago.

    If anyone has suggestions for disabling the first run videos I'm happy to test them out.


    Tuesday, July 15, 2014 6:48 AM
  • Hello,

    I am sorry - can you define what the first run videos are?


    Nicke Källén | The Knack| Twitter: @Znackattack

    Tuesday, July 15, 2014 8:40 AM
  • I will recreate an Office 2013 package and upload a screenshot.
    Tuesday, July 15, 2014 8:52 AM
  • There's is no Welcome video, sorry Nicke!

    It is about the "First things first" (EULA) and "Welcome" screen.

    Office 2013 Accept EULA

    Office 2013 Welcome screen

    Tuesday, July 15, 2014 11:18 AM
  • Thanks for the update Ben.

    I've tried adding the keys to the ProPlusVolume_en-us_x86_UserConfig.xml as per http://ittechlog.wordpress.com/2014/04/23/how-to-modify-the-virtual-registry-using-app-v-deploymentconfig-and-userconfig/ with no luck (none of the settings are written to the registry). I don't know if it's because, in my case, we're trying to stream Office or not.

    Tuesday, July 15, 2014 3:08 PM
  • Hello,

    So, setting this as a local gpo (downloaded the 32-bit templates) works just great.


    Nicke Källén | The Knack| Twitter: @Znackattack

    Tuesday, July 15, 2014 4:37 PM
  • Nicke, I didn't try it as a local GPO (having to set a local gpo on hundreds of machines seems counter intuitive) but did try the settings on a domain GPO. I still got the First Run and Welcome screens (double checked that the gpo was applied). Did you install office as a local app or a streaming app?
    Tuesday, July 15, 2014 4:54 PM
  • Hello,

    I deployed it as an App-V package.

    Only reason I did it as local gpo - was because the initial poster tested this way. I don't see a difference in deployment method though


    Nicke Källén | The Knack| Twitter: @Znackattack

    Tuesday, July 15, 2014 6:00 PM
  • Thanks for testing Nicke!

    I have re-tested this, and I'm able to hide the Welcome screen. That's a step forward :)

    Probably I forgot to execute a gpupdate (or reboot). Mike, did you closed the local group policy editor and ran gpupdate /force to apply the new local policies?

    In my test environment these local policies are set:

    Microsoft Office 2013\First Run\Disable Office First Run on application boot : Enabled
    
    Microsoft Office 2013\Privacy\Trust Center\Disable Opt-in Wizard on first run: Enabled

    Nicke, what are the local policies you're setting exacly? I'm looking for the policy to accept/hide the EULA.


    Wednesday, July 16, 2014 1:43 PM
  • I'm in the same boat. I was showing a co-worker the same problem, reapplied the GPO, and verified that it had been applied. Sure enough only the First things First screen came up but no Welcome screen. So progress but not perfection. I even tried repackaging the ODT download because I hadn't put the AcceptEULA command in the config.xml.
    Wednesday, July 16, 2014 3:32 PM
  • Hello,

    I haven't gotten an EULA at any Point? Which is what the reference says?

    This is the tag from the XML

    <Display Level="None" AcceptEULA="TRUE" />

    http://technet.microsoft.com/en-us/library/jj219426(v=office.15).aspx


    Nicke Källén | The Knack| Twitter: @Znackattack

    Wednesday, July 16, 2014 6:55 PM
  • That's the one I used. I didn't used it during the download process so that might be making the difference for me. I'll give that a shot later today to see if it makes any difference.
    Wednesday, July 16, 2014 7:38 PM
  • Nicke, Mike,

    I'm using that exact same line (see below, copy/pasted form my Configuration XML). Unlike Mike, I'm using the same XML to download and create the package.

    <Display Level="None" AcceptEULA="TRUE" />

    With or without that line, the EULA must be accepted at the client (at first application launch).

    What Languages are you guys adding? Because I've seen weird things when adding multiple languages.

    My configuration XML:

    <Configuration>
    	<Add SourcePath="F:\_ODT_July2014" OfficeClientEdition="32">
    
    		<Product ID="ProPlusVolume" >
    			<Language ID="en-us" />
    			<Language ID="nl-nl" />
    			<Language ID="fr-fr" />
    			<!--Language ID="de-de" /-->
    			<ExcludeApp ID="Lync" />
    			<ExcludeApp ID="Outlook" />
    		</Product>
    
    		<Product ID="VisioStdVolume" >
    			<Language ID="en-us" />
    			<Language ID="nl-nl" />
    			<Language ID="fr-fr" />
    			<!--Language ID="de-de" /-->
    		</Product>
    		
    		<Product ID="VisioProVolume" >
    			<Language ID="en-us" />
    			<Language ID="nl-nl" />
    			<Language ID="fr-fr" />
    			<!--Language ID="de-de" /-->
    		</Product>
    		
    		<Product ID="ProjectStdVolume" >
    			<Language ID="en-us" />
    			<Language ID="nl-nl" />
    			<Language ID="fr-fr" />
    			<!--Language ID="de-de" /-->
    		</Product>
    		
    		<Product ID="ProjectProVolume" >
    			<Language ID="en-us" />
    			<Language ID="nl-nl" />
    			<Language ID="fr-fr" />
    			<!--Language ID="de-de" /-->
    		</Product>
       
    	</Add> 
    	<!--  <Updates Enabled="TRUE" UpdatePath="\\Server\Share\Office\" /> -->
    	<Display Level="None" AcceptEULA="TRUE" />
    	<Logging Name="AllOffice2013_Setup.txt" Path="%temp%" />
    	<Property Name="AUTOACTIVATE" Value="1" />
    </Configuration>
    
    
    

    Nicke, Whats your XML please?

    Friday, July 18, 2014 9:32 AM
  • Here ya go;

    <Configuration>
    
    <Add SourcePath="c:\media\" OfficeClientEdition="32" >
         <Product ID="O365ProPlusRetail">
           <Language ID="en-us" />
           <ExcludeApp ID="Access" />
          <ExcludeApp ID="InfoPath" />
           <ExcludeApp ID="Lync" />
         </Product>
       </Add>
     <Display Level="None" AcceptEULA="TRUE" />
     <Property Name="AUTOACTIVATE" Value="1" /> 
     </Configuration>
    Obviously, this is then deployed as a global package once it is generated.


    Nicke Källén | The Knack| Twitter: @Znackattack



    • Edited by znack Friday, July 18, 2014 10:11 AM
    Friday, July 18, 2014 10:02 AM
  • Thanks Nicke.

    That's basically what I'm using. You're doing Office 365, I'm using the Volume version. I will try Office 365 next week (when the licenses arrive).

    Btw I Think the "Accept EULA" in the configuration.xml is to accept the ODT's EULA. Not the Office EULA.

    Friday, July 18, 2014 10:14 AM
  • This https://blogs.technet.microsoft.com/deploymentguys/2011/05/31/deploying-custom-registry-settings-for-office-2010/

    along with this

    HKCU\Software\Policies\Microsoft\Office\15.0\Registration
    Reg_DWORD = "AcceptAllEulas"= 1

    Works like a charm, thank you gbillig !!

    Regards


    Tuesday, October 11, 2016 10:45 PM
  • Hi Jose,

    When you say this works like a charm, did you include these settings within the App-V package (Assuming you also had this issue due to App-V as Ben did) so that they would populate on first launch like in the linked article?

    The only way I was able to get this to work with no prompts was to create the following 3 registry keys  and applying them before installing the App-V package outside of the Virtual Environment.

    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Common\General]
    "ShownFirstRunOptin"=dword:00000001
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\FirstRun]
    "BootedRTM"=dword:00000001
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Registration]
    "AcceptAllEulas"=dword:00000001

    If you use SCCM you could apply the above as a Dependency Application that runs as the user.

    Ideally I would have liked to include them in the App-V package itself, however it seems even when adding the keys by editing the package with the sequencer (yes I know, unsupported), they are ignored as the package the ODT spits out already has Feature block 1 created.

    Warm Regards,

    Cristhian

    EDIT: Nevermind, I answered my own question by doing some testing, reply further above.

    Wednesday, October 19, 2016 1:06 AM
  • Hey Ben,

    Here is how I got it to work, with help from the registry provided by gbillig and the link provided by Jose, please note this approach requires you edit the .appv package which is unsupported by Microsoft:

    After you generate your App-V package using the ODT, Edit the package in the sequencer (at least 5.0 SP2) and create the following keys:

    Depending on your flavour of Office 2013 (x86 or x64):

    HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\15.0\User Settings

    or

    HKLM\SOFTWARE\Microsoft\Office\15.0\User Settings

    Under the above key create a key with any name, for the sake of following the link provided by Jose I called it FTPropagation. In that key, create a REG_DWORD called “Count” with a value of 1.

    Under the FTPropagation key create the following keys & values:

    \Create\Software\Microsoft\Office\15.0\Common\General
    
    "ShownFirstRunOptin" dword:00000001
    
    \Create\Software\Microsoft\Office\15.0\FirstRun
    
    "BootedRTM"=dword:00000001
    
    \Create\Software\Microsoft\Office\15.0\Registration
    
    "AcceptAllEulas"=dword:00000001


    for example :

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\15.0\User Settings\FTPropagation\Create\Software\Microsoft\Office\15.0\Registration]
    "AcceptAllEulas"=dword:00000001


    Save the package and deploy it to a machine to test. 

    You should be able to add any other customisations using this method provided you know the registry settings to apply.

    Warm Regards,

    Cristhian


    Wednesday, October 19, 2016 4:19 AM
  • Does anyone know how to do this for Visio 2013 and Project 2013 App-v packages?

    How do you view the app-v registry on a client (app-v 5.1). I'd like to compare pre and post to identify the keys but cannot seem to find a way to do this.

    How did you located the keys for Office?


    Monday, November 20, 2017 6:24 AM
  • Roaming User Registry COW data will go here:

    • HKCU\Software\Microsoft\AppV\Client\Packages\<GUID>\REGISTRY

    • HKCU\Software\Microsoft\AppV\Client\PackageGroups\<GUID>\REGISTRY

    Non Roaming User Registry and non-elevated Machine Registry COW data will go here:

    • HKCU\Software\Classes\AppV\Client\Packages\<GUID>\REGISTRY

    • HKCU\Software\Classes\AppV\Client\PackageGroups\<GUID>\REGISTRY

    For Machine registry data coming from elevated processes, the Registry COW data will go here:

    • HKLM\Software\Microsoft\AppV\Client\Packages\<GUID>

    • HKLM\Software\Microsoft\AppV\Client\PackageGroups\<GUID>

    Monday, November 20, 2017 6:33 AM
  • (free) AppV_Manage tool can show you the changes made for a virtual application on a test client.

    Tim Mangan MVP for App-V and Citrix CTP Author of AppV books: "PowerShell with App-V 5 (5.1 Edition)", "The Client Book (4.x)" and "OSD Reference Book" (http://www.tmurgent.com/Books )

    Saturday, November 25, 2017 3:25 PM
    Moderator
  • Thanks, this works like a charm!!
    Tuesday, March 5, 2019 5:20 PM