Solution to automatically uninstall any version of Office In contrast, Office 2013 is installed and can’t easily be updated automatically.īelow, Office 365 can only be installed 5 times and it keeps a track of where it’s installed on the Microsoft Online Portal. Currently they are utilising the latest Office 2013 software, but that can change in the future all automatically, as Office 365 is streamed and not installed. As I mentioned before, Microsoft is now a devices and services company (read between the lines) my tip is that Office 365 is here to stay and is simply a brand name. Office 365 streams and updates in the background automatically, meaning that updates rollout to people automatically, including any new versions. In comparison, the ‘about’ screenshot on an Office 365 installation is slightly different, nowhere does it say Office 2013. See and read below carefully my ‘about’ screenshot. As for what it is? Well essentially at the moment, it’s Office 2013 (but it’s not called Office 2013).Īs an option, I don’t have to install Office 365, I can can still install Office 2013 only. So to simplify things, it’s all one single product called Office 365. See below, when I try to install Lync from the Microsoft Online Portal by itself, it clearly states that “ Lync 2013 is included in the latest version of Office” You can’t even install Lync or any other individual Office 365 component by itself. This includes all Office components including Lync. In saying this, the new product is called ‘Office 365’. Not too long ago Steve Ballmer the CEO announced that Microsoft would now be known as a devices and services company, here’s a link in case you didn’t see it Having two Office installations would be be confusing to the user and be very messy. As a result, when Office 365 is streamed to the computer, previous versions of Office are left installed, so you would effectively have two Office installations. With Office 365, it’s more like a stream rather than an install. Historically Office installations have been different where as they install fully inside of Windows. Do nothing.Companies moving to Office 365 will come across a hurdle. REM If 0 or other was returned, the product was found or another error occurred. Start /wait %DeployServer%\setup.exe /config %ConfigFile%Įcho %date% %time% Setup ended with error code %errorlevel%. Start /wait \\192.168.11.35\ClientApps \Office_20 13Pro\setu p.exe /uninstall ProPlus /config \\server\share\UninstallCo nfig.xml REM If 1 returned, the product was not found. If %errorlevel%=1 (goto DeployOffice) else (goto End) Reg query HKEY_LOCAL_MACHINE\SOFTWAR E\Microsof t\Windows\ CurrentVer sion\Unins tall\%Prod uctName% (Office 64bit would also appear here on a 64bit OS) REM Check for 32 and 64 bit versions of Office 2010. Reg query HKEY_LOCAL_MACHINE\SOFTWAR E\WOW6432N ODE\Micros oft\Window s\CurrentV ersion\Uni nstall\%Pr oductName% Check for 32 bit Office in emulated Wow6432 uninstall key IF NOT "%ProgramFiles(x86)%"="" (goto ARP64) else (goto ARP86) (the user doing the install needs write access) REM Set LogLocation to a central directory to collect log files. REM Set ConfigFile to the configuration file to be used for deployment (required) REM Set DeployServer to a network-accessible location containing the Office source files. REM Get ProductName from the Office product's core Setup.xml file, and then add "office14." as a prefix. REM Environment customization begins here. I used the script that was posted here and I modified it with the network share where the installation files are on. I want to do the uninstall completely silently. So this is the script I am using and running. However, before going ahead and doing that, I am trying to create the batch file and test it locally on the PC which has the Office 2013 installed to see whether it works or not before deploying.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |