Kaseya Community

Upgrading Office 2010 to 2016

  • Hey All, 

    I am curious. We were just asked to upgrade an organization's Office from 2010 to 2016 (about 2000 systems).  I am curious what issues any of you have come across when doing this upgrade?  We have done very small projects with no issue, but nothing ever this big and we are just trying to make sure we are prepared for every scenario.   Thanks for your input. 

  • "It depends". Start by figuring out how office 2010 was deployed (MSI, OEM, retail, GPO etc), hence how you can best remove it. Installing 2016 won't remove 2010 by default.

    If is really Office 2016, or is it really Office 365?

    Outlook 2016 uses a different mechanism to talk to Exchange - ensure this works, I've seen many upgrades where word, excel are OK but Outlook breaks, prompting users for passwords which it never accepts.

    How are you licencing 2016 - VLK, 365? If 365, have you got SSO set up and working first, so users aren't prompted to log into '365 constantly?

  • Hey Craig,

    It is Office 2016. We will be using Volume Licensing for it.  It was orginally deployed via setup.exe with the OCT.

  • Hello.  We have a kaseya procedure to automate Office deployments using the MS Open Licensing.

    1. We customize the office package with an admin file.   Run setup.exe /admin and configure the site settings

    2. We stage the Office sourcefiles on the client site and put the admin file in sourcefiles

    3. We have a batch file we run with the kaseya procedure that determines if Office is already, is either 32bit or 64 bit and then installs the new office overwriting and replacing the the with the new office.

    4. The install keeps the old users Outlook profile so after the reboot, the user just uses the office apps.

    5. All of the annoying prompts, registration, key codes and Outlook settings are pre-set in the office admin file.

    THat is how we deploy MS office since Office 2007 using Kaseya procedures.


  • batch file (installOffice.cmd)


    REM *********************************************************************

    REM Environment customization begins here. Modify variables below.

    REM *********************************************************************

    REM Get ProductName from the Office product's core Setup.xml file, and then add "office14." as a prefix.

    set ProductName=Office14.ProPlus

    REM Set DeployServer to a network-accessible location containing the Office source files.

    set DeployServer=\\sses-ad01\Setup\MS Office\Office 2016 Plus\X64

    REM Set ConfigFile to the configuration file to be used for deployment (required)

    set ConfigFile=\\sses-ad01\Setup\MS Office\Office 2016 Plus\X64\Updates\SSES2016.MSP

    REM Set LogLocation to a central directory to collect log files.

    set LogLocation="\\sses-ad01\Setup\MS Office\Office 2016 Plus\X64\logs

    REM *********************************************************************

    REM Deployment code begins here. Do not modify anything below this line.

    REM *********************************************************************

    IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)

    REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key


    reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%

    if NOT %errorlevel%==1 (goto End)

    REM Check for 32 and 64 bit versions of Office 2010 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS)


    reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%

    if %errorlevel%==1 (goto DeployOffice) else (goto End)

    REM If 1 returned, the product was not found. Run setup here.


    "%DeployServer%\setup.exe" /adminfile "%ConfigFile%"

    echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt

    REM If 0 or other was returned, the product was found or another error occurred. Do nothing.