Ghost Solution Suite

I am trying to create a boot disk using gss 3.1,but I keep getting an error saying the file does not exist c:\program files (x86)\altiris\express\deployment server\bootwiz\platforms\winpe 4\x86\templates\startnet.cmd.  I have tried reinstalling the ADKs. I've tried usings WinPE 4.0, 5.x, and 10.0.  I get the same message everytime after getting to 80% of Copying files to the production area.  I was able to create a bootable usb when we first implemented GSS3.1 but now even those configurations will not allow me to create a boot disk.  My bootable usb still works, so I can still create and deploy images, but I need to be able to create a disk for an older pc that is not able to boot from USB.

Does that file exist?   I included the one from my server if you would like to try it out.   I renamed it startnet.cmd.txt so that it can upload remove the .txt

I would recomend making a new configureation if you haven't already.    From the boot disk creator select configureaion and then right click and select new configureation.   I would recomend that you use windows PE 10 build 1511 as versions newer than this have been known to have issues with the client in WinPE.

With the new configureation that is using pe 10 it shouldn't care then that there is a file missing in the pe4 folder and should move on with a new boot disk I would think. 

Hope that is helpful.

Attachment(s)

startnet.cmd_.txt   13 KB 1 version

I tried creating a winPE10 configuration and still got the same message.  after I replaced the startnet.cmd i got another message that was looking for the startutl.  I was able to find a file in that folder that had .backup attached to it.  so I made a copy of that and renamed it.  I tried to run it again and then got the same error message looking for the setenv.bat file.  That one I cannot find.

Ferrus,

I am not sure why you are receiving this error. The below documentation will help to recreate the environment.

Installation:

1. Install Windows ADK 

https://msdn.microsoft.com/en-us/windows/hardware/dn913721(v=vs8.5).aspx#winADK

2. Import WinPE into Ghost:

How To Import Preboot Operating Systems Into Ghost Solution Suite 3.1(Standard Tools Installation)
http://www.symantec.com/docs/HOWTO124712

3. Create a boot disk:

Creating Boot Media For Legacy Ghostcasting With Ghost Solution Suite 3.1
https://support.symantec.com/en_US/article.HOWTO124429.html

Hello Ferrusq14

The mentioned files Setenv.bat & Startnet.cmd are files that belong to bootwiz itself. In the Templates folder we have more than 10 files that are used in bootwiz when creating configurations.

Seeing that you already was missing 1 file and after replacing it you found another file missing I fear that the current installation is corrupted (Missing files, and god knows what else you might be missing).

Thus I would go ahead and re-install the product, as it should re-generate those missing files. While re-installing you can still specify same DB and choose not to overwrite it, that way you will not use any Information stored in DB, nor will you lose your previously built configurations.

Best regards, Indrek

As a side note since there are more than just the one file missing is the boot disk configureation a new one or one from before the upgrade? 

If it is a reused configuration I would recomend trying to create a new configureation if you hadn't already.    In the end it sounds like It will likely be a reinstall to cover all the missing files.