Office Software Thread, urgent...need to uninstall office 2010 silently and deploy office 2013 in Technical; Hi there
I want the steps that are needed to deploy office 2013 and uninstall office 2010, since what I ...
urgent...need to uninstall office 2010 silently and deploy office 2013
I want the steps that are needed to deploy office 2013 and uninstall office 2010, since what I need to do is to put a link on the website and allow the staff in my college to just click on it to uninstall the office 2010 " old version" and install new version office 2013. I did the OCT step and save the msd file in the update folder , then I have updated the config.xml file to do the silent uninstall of office 2010 and silent install of office 2013 with the following content:
I need a batch file to do the following:
1. amount the office 2013 setup on the client PC when he click on the website link.
2. uninstall office 2010 silently.
3. install office 2013 silently.
and I want to ask if I have the msd, xml and bat file, what is the next step to deploy office 2013 so I can put it as a website link.Is there a certain configuration tool to do that.
and I'd like to know if I can use SCCM 2012 to deploy office 2013. If the answer is yes, then how can I use the set of my files (msd file, xml file and bat files) with in SCCM 2012. Is there any usefull link to show me the steps of deploying office 2013.
Last edited by engineer_z; 8th August 2013 at 11:30 AM.
As long as the workstations can see the network share, and the users have permissions to install software it would then run. It should be deployable via SCCM as the instructions here were the first hit I found for it.
1. Is this batch file responsible to do just the install for office 2013 and do I have to change on some variables name.
2. For SCCM, Can I run it on my home edition PC or it should be installed on A server.
3. Would you please illustrate the steps in detail for doing a setup application for office 2013 installation. Since, how can I use the msp, xml and bat files . I mean do I have to insert them in a folder and the batch file will run to do the office installation.
4. Is there a certain tool can be used to combile between msp, xml and bat files to deploy office 2013.
1, 3 & 4) First we did an admin install of Office 2013, so it decompressed the setup files into the central package deployment folder on our network under a subfolder called "office_2013" (I know very imaginative!)
Then we ran the OCT to define what components of Office 2013 we wanted to be installed by default, and the fact that all previous office version were to be uninstalled. We then saved it in office_2013\configs (file called basic.msp)
We editied the proplus.ww\config.xml file, setting the display level, username, company name and reboot value
The batch file we then run on the local machines connects in to the network share (replace ServerName with yours!) and uses the generated MSP file and automatically picks up the proplus.ww\config.xml during the install. As far as the users is concerned during the install nothing is happening other than the hard drive light flashes away.
2) We don't actually run SCCM so can't help you much there, we went for the free WPKG for package deployment since we didn't have the funds for server license for SCCM or the hardware to run it on at the time.
1- For the content of batch file you put it ("\\ServerName\applications$\Office_2013\setup. exe" /adminfile "\\ServerName\applications$\Office_2013\configs\ba sic.msp" "C:\Windows\System32\cscript.exe" "%PROGRAMFILES%\Microsoft Office\Office15\OSPP.VBS" /act).
Do I have just to insert it in txt file and save it as filename.bat. Furthermore, how can I update the bat file so when the user want to install
office 2013, the office setup will abe amounted on the client Pc as local driver then install office 2013 then disconnect the local hardware.
And how do I have to run the batch file.
2. Do you have some useful link to show how (free WPKG for package deployment) can be used to deploy office 2013 and
should WPKG for package deployment installed on a server machine or client machine.
3. In summary, What I got it the process on my server is as the following :
3.1 After updating the files, I have to put all the files (basic.msp, config.xml and file.bat) into office_2013 folder.
3.2 Ran the batch file.
3.3 Use WPKG for package deployment.
3.4 Use the software package in step 3.3 as a link on my website so the employees in my college just click on the link and install it.
3.5 Do I have to do the steps of process on a server or home edition PC (normal PC) and if I can do it on normal PC, Do I have to change the server name in bat file to My PC name.
Last edited by engineer_z; 8th August 2013 at 08:19 PM.
Reason: edit part
Assuming your wanting your staff to update their laptops/computers via your college network, then there is no need to mount the office setup files onto the computer first. As long as they can access the network share where you put the Office 2013 admin install, then the command line I used above would work... (In my case all our software is stored on a central server in a share called Applications$)
If you only have 1 MSP file, then you can store it in the updates folder. If you have multiple different installation types (which we do) then you need to use a custom folder, hence I reference office_2013\configs\basic.msp in the adminfile path.
Full guides for the command line installation can be found from Microsoft TechNet, article cc178956 and dd630736
The cscript.exe line is only needed if your using KMS activation. If you are using MAK, then you can ignore it since you would have entered the product key during the xml or OCT phase
You can then pop the batch file on your intranet, and your staff can then click to download and then run it.... if they are outside of your network (ie at home) then it will not function, and to be honest I'd be ensuring deployment was only on internal devices anyway for license implications. if you have Home use rights, then deployment for that is a completely different kettle of fish.
If you already have SCCM (which I inferred from your original post that you might have) then WPKG is not something to look into as SCCM already handles software deployment as this blog which I referred to earlier has the complete steps you need to take to get it to work.
@engineer_z. Follow the SCCM guide that Boredguy linked to in post #6 (assuming you already have it up-and-running on your network). I deployed Office 2013 pretty much same way and it worked perfectly. The only difference being that the software was deployed to a device collection rather than a user collection.
If on the other hand, you don't have SCCM, you are really going to struggle setting it up since it is not simple.
To install Office 2013, users can run Setup from the network installation point, or you can use the network installation point as a starting place to distribute Office 2013 by using a software deployment tool, such as Microsoft System Center 2012 Configuration Manager, or to create a hard-disk image or a custom DVD.
As they wrote create hard disk image, this Why I said I need a batch file to mount the office setup files onto the computer as a deployment tool.
Create a network installation point
The first step in a typical corporate deployment is to create, replicate, and secure a network installation point. To do this, copy all source files from the Office 2013 installation DVD to a shared location on the network. Also copy any language packs that you want to deploy from the source media to the network installation point. Users can run Setup from the network installation point.
As you have been running OCT, you should already have completed this step, as this contains the location for your updates folder, and the proplus.ww.
You do not need to create a mount point or virtual image as long as your users can access this network deployment.
I have found the following bat file to amount setup file :
net use x: "C:\Users\DELL\Desktop\Microsoft Office Professional Plus 2013\SW_DVD5_Office_Professional_Plus_2013_W32_Eng lish_MLF_X18-55138"
START "Office 32-bit" x: "setup.exe"
net use x: /delete
1.For the first line, is the path realted to the root folfer that contains office 2013 with 32 bit?
2. Do I have to put echo off in the beggining?