Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Dos Client Download

Updated: 22 May 2010 | 4 comments
mrguitar's picture
0 0 Votes
Login to vote

I'm getting a warning everytime I run a clone task from the console. This looks like an easy fix.


it says:
Details for Download DOS Client Upgrade:
Cannot open source file for transfer; check that file exsits and permissions are set correctly.


Where is the DOS client upgrade file and how can I check if it's intact?
Thanks.

discussion Filed Under:

Comments

David.P@TAMU's picture
03
May
2007
0 Votes 0
Login to vote

There are basically image file for msdos and im sure PCDOS to make the dos bootable partition for ghost tasks.  If you use MSDOS then I would suggest trying to re-aquire MSDOS through the boot wizard.
Nigel Bree's picture
03
May
2007
0 Votes 0
Login to vote

There's a little mini-updater for the DOS and Windows clients in case the console encounters an old version in the middle of a task (for instance, in a fixed Ghost Boot Partition). The file in the console install directory UPDATE.EXE is a self-extracting zipfile that contains just the minimum DOS and Windows client files.

If the console thinks that the clients are the wrong version, it sends this first (after this, for Windows it will then try sending the Client.MSI full installer) and runs it. For some reason it seems to be that the file has gone missing.

What version of GSS do you have installed on the server?

mrguitar's picture
03
May
2007
0 Votes 0
Login to vote

It was originally GSS1.1. I updated to 2.0 and then applied the 2.0.1 live update patch.

Updating the client failed on a large number of my clients, but it also worked on others. Could this be related?

Nigel Bree's picture
08
May
2007
0 Votes 0
Login to vote

To be honest I'm stumped on why this has happened for you. However, the main thing is to get you the UPDATE.EXE file back into its place. Probably the simplest way for you to do that is to use the 2.0.1 server installer on another machine to install a temporary copy of the code and grab the UPDATE.EXE file from that and move it into your server with the problem (or you could extract the file from the install CABs, but MSI tends to give files in the .CAB funky names so it's often just easier to install to find them).