Office 365 (2016) SCCM install, unable to disable first things first screen
I'm trying to deploy Office 365 (version 2016) and I'm unable to get it to accept the license agreement and disable the first things first screen when deploying this through SCCM. If I install it outside of SCCM everything installs and works perfectly, it's only inside SCCM where the first things first screen keeps popping up and users have to accept the EULA.
I followed the instructions here https://technet.microsoft.com/en-us/library/dn708063.aspx?f=255&MSPPError=-2147217396 and it doesn't work properly. Installing this through SCCM it seems to pick up everything from the .xml file except for the EULA.
This is my configuration.xml:
<Configuration>
<Add OfficeClientEdition="32">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Updates Enabled="FALSE" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
Anyone have any success deploying Office 365 (2016) 32-bit through SCCM?
TIA
I followed the instructions here https://technet.microsoft.com/en-us/library/dn708063.aspx?f=255&MSPPError=-2147217396 and it doesn't work properly. Installing this through SCCM it seems to pick up everything from the .xml file except for the EULA.
This is my configuration.xml:
<Configuration>
<Add OfficeClientEdition="32">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Updates Enabled="FALSE" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
Anyone have any success deploying Office 365 (2016) 32-bit through SCCM?
TIA
0 Comments
[ + ] Show comments
Answers (3)
Answer Summary:
Please log in to answer
Posted by:
EricD
7 years ago
Top Answer
Microsoft provided me the following registry keys to change which resolved our issue:
[HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Common\General]
"OptInDisable"=dword:00000001
[HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Registration]
"AcceptAllEulas"=dword:00000001
We're currently deploying those via GPO. We may change those to a compliance setting.
[HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Common\General]
"OptInDisable"=dword:00000001
[HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Office\16.0\Registration]
"AcceptAllEulas"=dword:00000001
We're currently deploying those via GPO. We may change those to a compliance setting.
Comments:
-
`OptInDisable` helped me to supress the dialog. Thank you. - asteinbr 7 years ago
Posted by:
rileyz
7 years ago
Copy and paste us your XML, we need to check it.
Your actual xml, not from the web page.
Your actual xml, not from the web page.
Sometimes you can have bung quotes which can cause issues. Check it in Notepad++ or something, they should be straight, not angled.
Also screen shot the pops up you are getting.
Comments:
-
<Configuration>
<Add OfficeClientEdition="32">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Updates Enabled="FALSE" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration> - EricD 7 years ago -
Not sure how to post a screen shot, but if the user has normal rights it opens a "activate office" screen and prompts them for an email address. If they have admin rights it opens a "first things first" screen and asks them to accept the EULA - EricD 7 years ago
Posted by:
apptopack
7 years ago
To suppress First thing first you need to capture the registry change that has been done when you accept the prompt and add it to the package and make it install via a script or batch file. You can check in this registry location for the fix.
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Registration\Machine Name\{90xx0000-xxxx-xxxx-0000xxxxxx}\O365ProPlusRetail\EULA]
"16"="PLEASE NOTE: Your use of the subscription service and software is subject to the terms and conditions of the agreement you agreed to when you signed up for the subscription and by which you acquired a license for the software.
Since it is a user registry, it will not be installed via SCCM as it runs in system context. Better use GPO or logon script.