All previous users must register again, since we have changed the format of our forum with the current website update.

Good question.  Normally CDS uses a single ISO image for all OS deployments - scripted or disk imaging.  Since all deployments are initiated the same way, we focus on changing the "worker"  scripts not the ISO itself.  When WinPE starts, it executes the startnet.cmd script which in turn executes the startnet2.cmd script.  The startnet2.cmd script uses tftp download the worker script (deploy.cmd or ghost.cmd) from the server then execute said worker script as shown below.

----startnet2.cmd----

x:tftp %script% %serverip% %localip%
if errorlevel 1 goto error
x:getconfiginfo %script%
if errorlevel 1 goto error
%script%

:error
echo There was an error.

------------------------------

In the case of  WinPE 2.0, we use the same method.    A single .wim image but multiple worker scripts.  You can create as many worker scripts as you need.  Just change the Script value in the clients.xml file as needed.  In the example below, you will notice that the Vista configurations all use the same image, pxeboot.n12, but different scripts.  The startnet2.cmd within the .wim image is responsible for downloading the script assigned to each Configuration.  I created a menu called default.mnu that lists all the Configurations. The T154 variable stores the name of the unattended.xml file to use for each Vista configuration.


<CDS>
<Clients> 
  <Client Name="pcsales1" Address="00164154E78D" Image="default.ldr" />
  <Client Name="pcsales2" Address="000C29B48BEA" Image=" default.ldr" />
  <Client Name="lamktg8" Address="0015582E7BDC" Image="default.ldr" />
  <Client Name="lamktg11" Address="0013D4D46F67" Image=" default.mnu" />
  <Client Name="default" Address="????????????" Image="default.mnu" />
</Clients>
<Deployment Options="T140='\\fs1\deploy':T141='argon\deployer InstallM3'">   
  <Config Name="Join GhostCast Session" Image="winpe.iso" Script="ghost.cmd" Options="T150='Join GhostCast Session':T160='\ghost\':T161='GhostCast':T162='deploy'" />
  <Config Name="Ghost - Dump 2 FS1" Image="winpe.iso" Script="ghost.cmd" Options="T150='Ghost - Dump 2 FS1':T160='\ghost\':T161='Create':T162='glenda.gho '" />
  <Config Name="Install Windows Vista-Sales" Image="pxeboot.n12" Script="sales-vista.cmd" Options="T150='Windows Vista for Sales':T153='\vista':T151='size=60000':T152='NTFS':T154='scripts\sales.xml'" />
  <Config Name="Install Windows Vista-Marketing" Image="pxeboot.n12" Script="marketing.cmd" Options="T150='Vista for Marketing Group':T153='\vista':T151='size=60000':T152='NTFS':T154='scripts\mktg.xml'" />
  <Config Name="Install Windows Vista-Default" Image="pxeboot.n12" Script="vista.cmd" Options="T150='Install Windows Vista':T153='\vista':T151='size=40000':T152='NTFS':T154='scripts\vista.xml'" />
</Deployment>
</CDS>

Hi all,

I was wondering if this issue regarding the manual removal of the client from its assignment has been resolved on the server side?

We've been base testing this and have also noted that it is an extra step to have to go into the console to manually delete each entry once its been completed.

Also, has anyone had any success using WINPE 2.0 with CDS?


Any assistance on this would greatly be appreciated.[em01]

I have to agree Jonathan. We here are going to wait for Argon to upgrade CDS instead doing all of these work arounds for something that should already be incorporated into it. We're looking for WinPE 2.0 out of box functionality, the removal of the client from the database automatically (even if client fails before it has a chance to remove itself). There are just too many modifications that need to be made right now. We understand from Argon that an upgrade is in the works and should be released within the next month or so. However, we don't know what this actual upgrade will include, enhance or even fix. Lets cross our fingers.

RB  [em04]