Ghost Solution Suite

We are using the Ghost Solution Suite console to deploy images to client machines. When the job is complete and we login to validate the build, the AClient is removed and we shut the client machine down.

So, the job is left in the console and grayed out. I have been moving the old jobs to a group "folder" with the days date, so that I can look at the job times for each task and build a time chart. I haven't done this yet, but have several days worth of builds.

We are having some issues where the client machines are not PXE booting because they do not pull an IP. When I email IT, they clear the leases and we are good again. But, today, one of the IT folks saw that I had the old jobs still in the console, and is trying to tell me that they will "hold on" to an IP until deleted.

This makes no sense to me at all. I would expect that the client PC simply reports the IP it has to the console via the AClient. Plus, I know that they have been trying to stand up a second server and have been making several network changes. I am pretty sure the subnet was split in half. I am looking for confirmation on whether I am correct or the IT folks, as I am no expect on GSS, but just know how things usually work and this sems very odd to me.

Thanks,

-Jeff

Jeff,

The jobs in the console do not hold onto i.p. address in a way that would effect your DHCP reservations. The computer information is saved in the job and the i.p. address may be in the job for configuration purposes but this does not warrant a dhcp reservation.

When imaging a machine the dhcp reservation comes when you boot the machine to PXE and the DHCP server hands that client an I.P. address. After imaging completes and the machine reboots that reservation (if not used in the production environment) should now be released and open to use on another client machine.

Let me know if you have further questions.