Snap Deploy and PXE

Hi,
I am experimenting the Snap Deploy to install multiple PC's. I managed to install the server software, and to have the PXE server working.
At least, it sends a package to my target PC, it boots the Acronis client and after selecting the Deploy option it waits for a time, before powering off again.

I noticed in the logging pane of the management deply section some activity and a valid IP address for my network. But when the machine is waiting for the image to be delivered it shows an IP address from the APIPA range (169.x.x.x) and nothing happened, since this address range is outside our scope.

I tried this with bootable CD, created with my server PC, but with the same result.

Can somebody tell me what to do about this ?

I use the the build 1.277 - trial edition (for now).
TIA

 

Hello Twixbe,

Thank you for your interest in Acronis Complete System Deployment Software.

Could you please do the following?

- When the client side of Acronis Snap Deploy is starting up, wait for boot menu to appear and press F11. As you get the "Linux kernel settings" prompt, remove the "quiet" parameter and press OK;
- After you get the command prompt enter:

product /mode:demon /log-level:verbose /log:../tmp/problem.log

and press Enter key;
- Reproduce the deployment problem from the Management Console;
- After you get the command prompt again (if it doesn't appear please press the Ctrl+Alt+F2 combination) insert a diskette into the floppy drive and issue these commands:

mkdir /mnt/t
mount -t vfat /devfs/floppy/0 /mnt/t
cp /tmp/problem.log /mnt/t
umount mnt/t

- Send the 'problem.log' file from the diskette to our Support Team.

Thank you for the cooperation.

--
Andrew Berezovsky

 

Thanks for your reply.But I do not have a floppy drive on my system. I do have an external USB floppy drive, but the commands given do not work with that.

And now, as I was executing your instructions, it did work. I did not change anything to the server/clients of Acronis. Nothing changed to my DHCP server. Maybe I should call Ghostbusters?

But my network appeared to be overloaded while using this. My users started to complain that it took them forever to get to some network resources. I used to have Symantec Ghost and I never noticed this when doing multicast deployments.

Any ideas ? Thanks