Office 2010 installation - bandwidth
I ran \\server\office14\setup.exe /admin and went through the customization tool to setup certain settings that I wanted. Then I used Deployment Solution to push the job by running a script that contained:
\\server\office14\setup.exe
It took an incredible time for the installation and sucked up all the bandwidth from my building to another building.
So I copied the office14 set of folders to a local computer. I changed the script to:
\\localcomputer\office14\setup.exe
and pushed it to a computer in that same building.
Same result. I had the network guy look at his monitoring tools and he said that there was a lot of activity between the main server and the client even though I was running the installation from \\localcomputer.
What can I do?
I also tried it on my KACE trial and used \\localserver for the alt. download location. I saw the same results doing this as well.
Thanks for your help.
Jane
\\server\office14\setup.exe
It took an incredible time for the installation and sucked up all the bandwidth from my building to another building.
So I copied the office14 set of folders to a local computer. I changed the script to:
\\localcomputer\office14\setup.exe
and pushed it to a computer in that same building.
Same result. I had the network guy look at his monitoring tools and he said that there was a lot of activity between the main server and the client even though I was running the installation from \\localcomputer.
What can I do?
I also tried it on my KACE trial and used \\localserver for the alt. download location. I saw the same results doing this as well.
Thanks for your help.
Jane
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
jfrasier
12 years ago
Someone on another thread posted this:
"Could be because setup.exe launches a huge number of separate msi files, which Kace may not detect."
Perhaps this is why when installing across the WAN it 'chatters' with the server so much. However, I don't think this explains why when installing from the a local computer, that the installation is still chattering with the original server.
"Could be because setup.exe launches a huge number of separate msi files, which Kace may not detect."
Perhaps this is why when installing across the WAN it 'chatters' with the server so much. However, I don't think this explains why when installing from the a local computer, that the installation is still chattering with the original server.
Posted by:
dchristian
12 years ago
The Kace alternate download is if you want to copy the install files from another source (other than the kbox).
After the file is copied everything SHOULD be run locally.
Where is your answer file?
Is it in the same folder as the office files?
After the file is copied everything SHOULD be run locally.
Where is your answer file?
Is it in the same folder as the office files?
Posted by:
jfrasier
12 years ago
I used the Office Customization tool to create the 'answers' and the resulting .msp file is in the updates folder as the instructions specify.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.