/build/static/layout/Breadcrumb_cap_w.png

K2000 doesn't see extra vhd drive deploying wim

We have physical K2000 3.7.  I have a case ticket in but, still looking for answers.
I cant seem to get the k2 to see 2 attached vhdx when trying to deploy win to a VM.  The second vhdx is for temp wim during delpoyments.  I was under the impression that kace would see all available disk for required space.
The second vhdx is formatted and recognized in disk part as i have diskpart script that assigns correct drive letter.
Any suggestions other than making single vhdx larger?

3 Comments   [ + ] Show comments
  • May you post here the logs of the failed deployment please?
    Regards,
    Marco - StockTrader - StockTrader 9 years ago
  • It might take me a bit but I will let you know, thanks for the response. - wessdf 9 years ago
  • I have successfully added a second VHDX to VM as SCSI disk and can now deploy wim image to the desired VM with a minimal size. With SCSI disk on VM also allows be to add and remove it from a live VM, even in diskpart running KBE environment.
    I have also had to create Mid-Level task to run bcdboot d:\windows /s c: and modify diskpart preinstall task to accommodate the hdd config of the vm's and whether they were captured from c, d, e etc no biggie.
    Much to learn here lol, thank you for responding. - wessdf 9 years ago
    • Scrap all that lol. I have figured it out thanks to IT Ninja and Kace Tech Support and good ol trial and error. - wessdf 9 years ago

Answers (1)

Posted by: wessdf 9 years ago
Purple Belt
0
Attaching an extra drive as SCSI, KBE see's second drive. Deployment setup in general:

Deploy Image to VM with K2000 with Secondary SCSI VHDX

Create New Disk on VM 30 – 40 GB to “as needed”, DynamicDisk.

                Maybelarger if needed.

Attach Temp Disk to VM - 80 GB SCSI (allows for temp wimfile created before moving to K2000)

                SCSIVHDX drives can be added and removed while VM is running, including in PE environment.

DVD Drive Connected.

There should be 2 Partitions C:, D:

Pre-Install Task should be:

                VM –Create 2 Partitions, Fix DVD, Fix Temp VHDX

                Windows7 & 8 Format 2 Partitions

Install Vista / 2008  / 7 / 8 / 2012 MBR

Mid-Level Task should be:

                Script –Remove DPInst Reboot

Boot to PE.

Select Deploy.

Select Image.

Select Restart.

When deploy is complete, verify and remove SCSIVHDX drive.

Capture Image of VM with Kace with SCSI VHDX

Create New Disk on VM 30 – 40 GB to “as needed”, DynamicDisk.

                Maybelarger if needed.

Attach Temp Disk to VM - 80 GB SCSI (allows for temp wimfile created before moving to K2000)

                SCSI VHDX drives can be added and removed while VM isrunning, including in PE environment.

DVD Drive Connected.

Boot to PE.

Select Capture.

Name Image with date.

Select WindowsImaging Format (NOT Kimage)

If you don’t have three volumes shown as below, J: Temp is probablynot formatted or initialized yet and you will need to use diskpart to set it upand reboot into PE.

Or manually set up partitions as needed to look like belowimage.

 


 

This is how Diskpart will see the drives initially:

Diskpart cmd

Select disk 1 (should be 80 GB)

clean

Create partition primary

Format fs=ntfs label=”Temp” quick

Assign letter=j

Select vol 0

Assign letter=z

Select vol 2

Assign letter d:

List vol (to check that the 80 GB partition shows up)

Exit

Now we are ready to capture. The letters will be reordered by kace, but our ultimate goal is to capturethe OS / Windows partition as D: and System partition as C: This will work forVMs deployments.

When capture is complete, remove SCSI VHDXdrive.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ