Need a clear cut detailed explanation of how to get network boot to work
This is my second pass at Snap Deploy. The first attempt was with version 3 that I was never able to get to work so I went with Norton Ghost which never gave me any configuration problems. But my version of Ghost is pretty old so I decided I'd give Snap Deploy another chance. I'm using a trial version to determine if I want to buy it.
- I have a Dell R320 server that's an Active Directory Domain Controller that I want to use to deploy an image to 25 computers in a student lab.
- I installed Snap Deploy using the "typical" option on the server and I am trying to deploy an image to a Dell Optiplex 3010 that has the built-in NIC and on the same subnet. The 3010 is part of the AD domain and its Windows Firewall has been disabled.
- I installed the Snap Deploy Agent remotely to the target computer and created an image that is saved on the server.
- I am trying to use the PXE server option to deploy the image.
- When I use the CD to boot the target, I can see it is in a "Ready" state in the console.
- How do I go about getting the target to use the PXE server to receive the image so I don't have to use the CD?
- The BIOS on the 3010 is configured to use PXE as the first boot option.
- Do I install PXE server in the target also? I did that by installing that component remotely to the target computer and the service is running. How do I force it to "Ready"? There is nothing in the User Guide that describes how to make it reboot from Windows to the Acronis environment.
- I uploaded the Snap Deploy Agent to the PXE server but what is supposed to happen after that?
- I created a test deployment task but but the target never goes to "ready" so the deployment can start.
- When creating groups and adding a few machines in the console using the MAC address is easy but are we expected to add large groups of machines by hand by entering MAC addresses? This hardly seems practical for anything more than just 4 or 5 computers. I would need to record the MAC addresses on 25 units, make sure they are correct then manually enter them. That takes too much time. With Ghost Corporate, all that's required is to remotely install the client. After that, they just show up in the console. That seems significantly more intuitive.
Since this is a trial version, I don't have a lot of time to troubleshoot. I've combed the forums for solutions but whenever I found something similar, no one offered a definitive answer that worked. The knowledge base articles didn't provide a solution either nor did the User Guide.
Thanks for your time and your help.

- Log in to post comments

Update 2:
After doing a Live Chat, I was given a link to download build 584 supposedly because it had an updated PXE server. So uninstalled build 540 and installed this one. I uploaded the Agent and Master Image Creator to the PXE server. But when I go to actually create the image, the console doesn't connect to the target. As stated on the original post, the target has the firewall turned off. Clicking the 'Browse' button to search for the target only shows the server Snap Deploy is installed on. Why doesn't the target computer appear when I attempt to browse for it. But the target and the server are on the same Active Directory domain they have the same WINS settings. When I browse the network I can see the target, but Snap Deploy can't see it.
I have a little over a week to figure this software out before the trial runs out. It shouldn't be this hard.
- Log in to post comments

Update 3:
I was able to successfully complete the first trial stage.
- PXE (network) boot is not an option. We do not have a DHCP server that will answer requests from a PXE computer.
- Apparently I was given a Snap Deploy Server license and not a Workstation license. The trial download does not specify which one you should get. I assumed (bad move on my part) that since the deployment was being done from a server, that a server license was needed. As a result I kept getting a failure during the deployment task that there were no workstation licenses.
- Although I'd prefer to network boot, I have to use a bootable CD. That will take more time since I have to boot each target individually.
- The next task is to figure out how to deploy an image to 25 target and have them retain their original computer names.
Anyone encounter this and figured out to do it?
Thanks for your time.
- Log in to post comments