ZTIUserExit.vbs

I am confused by what I have seen with testing the “ZTIUserExit.vbs”
described in the ZTI Deployment Feature Team Guide, and I am hoping someone
can help explain what I have observed.

I am testing using ZTIUserExit.vbs as a custom exit function for bare metal
builds (i.e. new computer scenarios). I am working with a lab system, so to
emulate a bare-metal install, I always clean the system’s hard drive to
remove all partitions, etc. before attempting a ZTI deployment. I have set
up the custom exit function as the ZTI guide explains, with the exception of
modifying the ztidiskpart.txt (see below).

I am trying to configure the system with a 15gb C partition, and leave the
rest of the disk alone so an installer can cut up the drive later as he/she
likes. When I set up ZTIUserExit.vbs to use the ztidiskpart options pasted
below, the set up does not work as I expected. Instead of creating a 15gb C
drive and installing the OS on that drive, OSD creates a C drive that uses
all available disk space (a full 60gb on my lab system).

ztidiskpart.txt:


select disk 0
clean
create partition primary size=15000
assign letter=c:
active
exit


I assume this has to do with OSD running diskpart.exe parsing the default
“diskpart.txt” on it’s own during the pre-install phase. I guess this must
happen after the custom action runs and overwrites the earlier configuration?

However, when I configure the ztidiskpart.txt with the settings below, the
disk is in fact configured with a 15gb C: drive and a 45gb D: drive.



select disk 0
clean
create partition primary size=15000
assign letter=c:
active
create partition primary
assign letter=d:
exit


Can someone explain why this occurs? If the default diskpart.exe command
runs during the pre-install phase AFTER the ztiuserexit.vbs, I would expect
it to clean the disk and delete both the C and the D drive? So both
scenarios mentioned above should leave me with a system that has a 60gb C
drive?

Just for background, pasted below is the default diskpart.txt stored in the
OSD directory

default diskpart.txt:



select disk=0

REM // The "clean" command is required to make sure that
REM // Diskpart writes out the MBR boot sector. Without this
REM // the machine may not boot into the new OS if the hard
REM // drive is new and did not already have a boot sector
clean

REM // Create a single partition that uses all available
REM // drive space and make it the C: drive.
create partition primary
select partition=1
assign letter=C

REM // Set the new partition as the boot partition
Active


Any assistance is appreciated.
.

Relevant Pages

  • OT: Computer maintenance (Was: Re: Whos out there?)
    ... -- Buy a software firewall. ... Use Windows' Disk Cleaning utility about once a week, ... A data/back up partition should be standard on every computer sold IMO. ... A lean and clean registry speeds up booting, especially on older machines with slower CPUs. ...
    (uk.rec.models.rail)
  • Re: How do I run an ??????????????????
    ... "Invalid node structure" after I tried to repair the disk with Disk ... Mac partition set up in HFS+ journaled. ... install (erasing the entire disk and reinstalling each OS clean), ...
    (comp.sys.mac.apps)
  • Re: diskpart
    ... REM This is an automated Disk Partition Script. ... REM change it's drive leter / Assign a drive letter to the selection ...
    (microsoft.public.scripting.vbscript)
  • XP Install Question
    ... I need to run a "clean" re-install of XP Professional on ... I ran the install from the cd and it seemed ... It just put XP onto the disk. ... partition so that a new one could be ...
    (microsoft.public.windowsxp.general)
  • Re: disk partition question
    ... want create one partition on that disk with logic letter c ... Personally, I use a similar system which instead of copying from an .sdi file - which is why the partition is 650MB, as that's the size of the image - I use xcopy to grab the image from a network drive. ...
    (microsoft.public.windowsxp.embedded)