Deployment Solution

 View Only
  • 1.  Scripted OS install - DOS automation

    Posted Apr 06, 2009 06:35 AM
    Hi

    I am doing a scripted OS install of windows xp with sp 3, using the Scripted OS task in deployment server 6.8 sp2

    I am using pxe environment and DOS automation.

    Issue: I am copying folders and files to the production machine using $1 & $$, the folders and files copy to the production machine but the copy process has an 8.3 file limitation. I need to know if this because I am using DOS automation or is it because I am using the dos.img as part of the process. I have set my unattend process to convert fat32 to ntfs and this appears to be working.

    I have VB scripts that run at first boot to install software etc that are in these folders but are failing due to the short filenames. I know I could copy the folders from the network at first boot but then it makes $1 & $$ an obsolete process.

    Also I am importing an unattend.txt file I have created, but the Scripted OS install also has unattend settings in it that are not part of my unattend.txt file, I would like to know where these settings are saved so I can later edit it manually.

    Thanks in advance
    Cat



  • 2.  RE: Scripted OS install - DOS automation

    Posted Apr 06, 2009 08:16 AM
    I'm pretty sure the 8.3 issue is related to DOS.  The only recommendation that I have to ensure that is the case is to always surround the long file name in quotes (i.e.:  "c:\program files\folder one\folder two\long file name.txt").  If you don't do this, some commands (especially copy, del, rd, etc.) will stop at the first space and assume the file or foldername ended there. 


  • 3.  RE: Scripted OS install - DOS automation

    Posted Apr 06, 2009 08:42 AM
    I have not been able to get $1 to work since I started using the Scripted OS Install (SOI) job with xp sp3 (or even with a SOI I made).  I have had to even stop using the SOI job and replace it with my own so I can copy files down between the imaging and the executing of winnt.exe.  I think this is better anyways because it allows me to copy drivers easily so the computer can continue after the SOI.  As for the unattend.txt (correct my if I am wrong) but I believe it copies this file from the express share\deploy (\\server\express\deploy).  This is also where it keeps the i386 folders that are used during the SOI job.