Upload of Office 2010 package fails at 25%
I am trying to upload our customized Office 2010 package without success.
The system uploads about 25%, then fails with the error “Upload file cannot be blank.â€Â
The zip package is 0.98 GB (1,058,979,840 bytes) on disk.
I have tried creating different zip files, uploading from other PCs, and even rebooted the K2000.
Other files created as a test upload just fine, but they are not as large as the Office 2010 package.
I found the following post, but would rather not have to hack this as the file is well under the 1.5 Gb upload limit on the K2000. http://itninja.com/question/mst-creation423
I looked at http://www.kace.com/support/kb/index.php?action=artikel&cat=6&id=1063&artlang=en as well.
Is there anything else I should be loooking at with this?
Thanks!
John
The system uploads about 25%, then fails with the error “Upload file cannot be blank.â€Â
The zip package is 0.98 GB (1,058,979,840 bytes) on disk.
I have tried creating different zip files, uploading from other PCs, and even rebooted the K2000.
Other files created as a test upload just fine, but they are not as large as the Office 2010 package.
I found the following post, but would rather not have to hack this as the file is well under the 1.5 Gb upload limit on the K2000. http://itninja.com/question/mst-creation423
I looked at http://www.kace.com/support/kb/index.php?action=artikel&cat=6&id=1063&artlang=en as well.
Is there anything else I should be loooking at with this?
Thanks!
John
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
jgeorge
12 years ago
While waiting for a response, I decided to give the procedure found at the following link a try.
http://www.kace.com/support/kb/index.php?action=artikel&cat=6&id=1063&artlang=en
That works very well for my purposes as the organization I work for has a software repository already set up.
I mapped the top level software folder, and then CD to the appropriate directory.
Here is the script I used:
net use n: \\Servername\Software /user:domain\username password /persistent:no
n:
cd "Full Applications\Office14"
start/wait setup.exe /adminfile "custom.MSP"
http://www.kace.com/support/kb/index.php?action=artikel&cat=6&id=1063&artlang=en
That works very well for my purposes as the organization I work for has a software repository already set up.
I mapped the top level software folder, and then CD to the appropriate directory.
Here is the script I used:
net use n: \\Servername\Software /user:domain\username password /persistent:no
n:
cd "Full Applications\Office14"
start/wait setup.exe /adminfile "custom.MSP"
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.