kiplaws
February 22nd, 2006, 05:01 PM
Playing around with Snap Deploy to see if it will work for our purposes. I have loaded everything onto one central machine (license server, pxe server, deployment management console, the whole works). Everything is working just great, but I'm running into this last little problem. Here's the scenario:
I'm PXE booting a "master" machine up to the Deployment Server, no problems there. I pick which physical HDD that I want to image first (there are two physical drives in this chassis, one IDE drive [primary] and one SCSI drive [golden]) and start that image creation process. The Primary drive imaging process completes with no problems and is stored on a network share on the deployment server. I then PXE boot the "master" machine back up to the deployment server once again, to image the Golden drive (SCSI) and store it on the deployment server as well. That goes perfectly, saving the golden image right next to the primary image. Needless to say, the "master imaging" process is working perfectly (as far as I can tell). I then take a look at the location that is storing both of the images, and I see them both, one "Primary" image and one "Golden" image. They are both showing to be the sizes that I would expect them to be; not identical, of course, but expected.
When I turn around to deploy those images back to a bare machine (same exact hardware as the "master" machine), I'm having an issue there.
On the deployment server, I have created two templates; one for the Primary image, and one for the Golden image. When I edit those templates, it indeed shows that the Primary image is physical disk #1 and the Golden image is physical disk #2. No problem, right?
When I go to deploy the Primary image, and look at the summary screen right before the deployment begins, it shows that it's going to write it to physical disk #1. When I go to deploy the Golden image, and look at the summary screen, it still shows that it's going to write the image to disk #1, even though the template itself shows that it should be deploying to physical disk #2.
Why is this? Why can't I get the Golden image template to put the image on the correct physical drive? I've even tried ignoring this and going ahead with the deployment, but it writes the darn thing to physical disk #1 every time. It's like the deployment process can't see that there are two physical drives in the bare machine. It just sees the IDE drive and that's it.
Do I need to load in any SCSI drivers into the deployment console (somehow) so that it will see that second physical disk?
See the attached screenshots of the templates, showing that the images are evidently aware of where they originally came from (disk 1 and 2).
Thanks in advance for any hints on why this may be happening. That's the only thing that is left to do before we fully implement this solution.
-kiplaws
I'm PXE booting a "master" machine up to the Deployment Server, no problems there. I pick which physical HDD that I want to image first (there are two physical drives in this chassis, one IDE drive [primary] and one SCSI drive [golden]) and start that image creation process. The Primary drive imaging process completes with no problems and is stored on a network share on the deployment server. I then PXE boot the "master" machine back up to the deployment server once again, to image the Golden drive (SCSI) and store it on the deployment server as well. That goes perfectly, saving the golden image right next to the primary image. Needless to say, the "master imaging" process is working perfectly (as far as I can tell). I then take a look at the location that is storing both of the images, and I see them both, one "Primary" image and one "Golden" image. They are both showing to be the sizes that I would expect them to be; not identical, of course, but expected.
When I turn around to deploy those images back to a bare machine (same exact hardware as the "master" machine), I'm having an issue there.
On the deployment server, I have created two templates; one for the Primary image, and one for the Golden image. When I edit those templates, it indeed shows that the Primary image is physical disk #1 and the Golden image is physical disk #2. No problem, right?
When I go to deploy the Primary image, and look at the summary screen right before the deployment begins, it shows that it's going to write it to physical disk #1. When I go to deploy the Golden image, and look at the summary screen, it still shows that it's going to write the image to disk #1, even though the template itself shows that it should be deploying to physical disk #2.
Why is this? Why can't I get the Golden image template to put the image on the correct physical drive? I've even tried ignoring this and going ahead with the deployment, but it writes the darn thing to physical disk #1 every time. It's like the deployment process can't see that there are two physical drives in the bare machine. It just sees the IDE drive and that's it.
Do I need to load in any SCSI drivers into the deployment console (somehow) so that it will see that second physical disk?
See the attached screenshots of the templates, showing that the images are evidently aware of where they originally came from (disk 1 and 2).
Thanks in advance for any hints on why this may be happening. That's the only thing that is left to do before we fully implement this solution.
-kiplaws