Ladybug Version 6 the imaging disk

 To all;

 

 I have updated Ladybug once more, it now has several new improvements and additional .bat files to make your imaging even easier. Please Changes below.

 

 

FITZ

Version 6.1

 

 

 

Totally automated flash drive “FlashBug” or USB HDD imaging-

Oh this was a fun one , but I got. What I did was to figure out a small search command line that looked for specific folder names and then added that to the mapping of “V” drive. So it does not make any difference if you use a CD to boot or a flash drive, it will search all drive letters looking for the image folders and start process on them. Total time to image a laptop with a flash device and a 16 GB 64bit image is now at 9 minutes.

 

Renesas USB 3.0 USB drivers for HP equipment

Both driver sets loaded without issue and work with mouse and any USB device  I have plugged in. Imaging total time decreased when using 3.0 USB HDD device.

 

I know it is a hair large for PXE, but on a GB network it loads fine for your WDS server. It is WinPE 3.0 at its heart.

 

Fully automated imaging to your network share-

 You have to create a a “read only” share account, then embed it within Ladybug. Yes, you just click “start_here” and choose either 32bit or 64bit, it pops up a little “echo” telling you its finished. This works great!

 

DOD wipe even Encrypted drives

 I had some issues with encrypted drives using this the first time around and realized all I had to do was add the quick format command and encryption goes away allowing the HDD to be DOD wiped. Now all drives get wiped with this bat.

 

What do you,  as a tech have to do to make this auto imaging happen?

Edit “imagethiswin7workstation.bat” and the other bat files the same way.

Not hard to figure out if you look here; 

 

@echo off

diskpart /s "X:\Program files\BATS\cleanandformatwin7.txt"

cls

echo Where is the image? Enter path. (Example \\servername\sharename\wim\7HAI32 folder)

set /p drive=

cls

echo Enter username for access. Example "domain\username" or "workstation\username" on wkgrp

set /p usern=

cls

echo Enter Password

set /p password=

cls

echo CONNECTING .........

net use V: "%drive%" /User:"%usern%" "%password%" /PERSISTENT:NO

Imagex /apply V:\win732s.wim 1 S:

Imagex /apply V:\win732w.wim 1 W:

echo Ladybug imaging has completed, click "START"\Shutdown\Reboot and check the box to eject CDROM.               Have a nice day: FITZ

pause

Exit

 

 

 

And you follow the same editing with the other bat files to match.

So if you edit this bat file (Remove this part) and set path, set username and password, guess what happens when you start the batch file? It will tell you when it is done. If you still want to enter path, username and password manually, then do so, use LadyBugv6 straight out of the box. Or ISO.

 

 

The Qualifiers to make all of this work?

This is based on a 2 partition system with windows 7, one “S” or system drive and one “W” or Windows drive. That’s what the Sysprep process looks for as it is running on a first boot. With XP it looks for and uses one “C” drive.

 

So, if you have more than 2 partitions on your designed system in Windows 7, then you will need to edit all the batch files to make it work, but it will work as I have created one that did 3 partition's so I could create a self-imaging system with a grub boot loader.

 

Yes, I copy both the “S” and “W” drives off my “Master” machine when capturing a Sysprep image. I find that it just works very well to do so and I have had no issues with images or processing of them.

 

 

What Ladybug 5.5 or 6 will not do?

 

Neither will make multiple copies of a “NON-SYSPREPPED” image that you can apply to many machines, does not work that way and it fails every time because of the GUID within windows 7.

 

 

You have options Version 5.5 or 6/6.1

The instructions for building version 5.5 or 6 are the same from a base WinPE 3.0 image, so depending on what you are looking for it’s your choice.

 

 

Screen shots of new LadyBug v6.1

Below

My list of programs in boot.wim\Programs folder.