Config_Mgr_noob Posted May 2, 2016 Report post Posted May 2, 2016 Hi every, I was wondering if someone can assist me or provide some info regarding the deployment of Office 2016 via SCCM 2012. I created a package in SCCM to deploy office 2016 and I am successful in installing the package but the taskbar icons do not populate with the default shortcuts MS creates when installing the software. However, when I manually install the set.exe with the .xml configuration, it creates the task bar icons as the set.exe feature provides this.I was wondering if there is something SCCM is doing in the background that is suppressing the setup.exe from creating these icons? Here is my .xml configuration: <Configuration> <Add SourcePath="\\server\software$\Microsoft\O365_2016\Setup" OfficeClientEdition="32" Branch="Business"> <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> <ExcludeApp ID="Groove" /> </Product> </Add> <Updates Enabled="TRUE" Branch="Business" /> <Display Level="Full" AcceptEULA="TRUE" /> <Property Name="AUTOACTIVATE" Value="1" /> </Configuration> Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted May 5, 2016 Report post Posted May 5, 2016 Keep in mind that ConfigMgr will perform the installation with the SYSTEM account. Quote Share this post Link to post Share on other sites More sharing options...
Config_Mgr_noob Posted May 10, 2016 Report post Posted May 10, 2016 Meaning that some of the customization, such as taskbar icons, will not appear? What about deploying it using the User rights instead? Will that over right using the SYSTEM account? Quote Share this post Link to post Share on other sites More sharing options...
ZeZe Posted May 11, 2016 Report post Posted May 11, 2016 Meaning that the system account needs permission in the share folder where the sources are Quote Share this post Link to post Share on other sites More sharing options...
Config_Mgr_noob Posted May 11, 2016 Report post Posted May 11, 2016 The SYSTEM account already has FULL control over the source folder. Quote Share this post Link to post Share on other sites More sharing options...
Config_Mgr_noob Posted May 11, 2016 Report post Posted May 11, 2016 Figured it out. Tried running the program using the User rights instead of Administrator. Thanks! 1 Quote Share this post Link to post Share on other sites More sharing options...