janderson

Currently we're using the DOS deployment boot disc to image and restore machines. This is working out pretty well for us, but I'd like to get rid of the disc and just use PXE to get into the app. I'm running into a little trouble though.

I actually have the PXE server set up and responding, however when I try to launch it from the menu I get an error about licenses. I then went back into the PXE config and noticed the only option for type is automation, network is greyed out.

We usually use the network option to generate our ISOs, so I think this is part of the problem, but I have no idea why the option isn't available.

Is there something I'm missing here?

Thanks

bfusco1

I am having the same problem with WinPE, and no one seems to have an answer for this problem. I've resorted to putting a script that launches RDeploy in the startup batch file for the automation partition. This prevents it from restarting until after the imaging task is done.

jdan

The "network" boot option actually is available for PXE boot images, but you have to be a bit tricky to get to it.

When you create PXE boot images, they are "shared" by default. This means that the same PXE boot image is copied to all of the PXE servers to it is available everywhere. Because ti is available everywhere, then DS jobs can be assigned to that PXE boot image. That is the basic purpose of creating PXE boot images, is to use in DS jobs.

But in order to run a job, then the PXE boot image must be created as an "automation" boot images, which loads up the agent to contact the DS server and run the job. Since these PXE boot images can be assigned to jobs, then you cannot create these as "network" boot images, since they would not load the agent, and then they would not perform the jobs.

But, you can use the File menu in the PXE config utility to open a specific PXE server, and then you can create PXE boot images which are local to that one PXE server. Because these boot images are not shared and are only available on that one PXE server, then these PXE boot images cannot be assigned to jobs in DS.

Since these boot images are local to a PXE server and cannot have jobs assigned to them, then these PXE boot images can be created as "network" boot images, and not just as "automation" boot images.

So create one of these local PXE boot images as a "network" boot image, and when you PXE boot the client, then pick that specific local PXE boot image from the PXE boot menu.

It will boot, load and connect to the network, but the Altiris DS agents will not connect to the DS server.

A local user will be required to then do something on that system, and manually reboot that system, since this will not happen automatically.

andykn

What are you trying to launch, from what menu and when? What is the exact error message you get and exactly at what stage?

If you can get into PXE config, you should be able to create a PXE boot file. If your client is configured to Network (PXE) boot, once it is assigned a job in DS, the client should use PXE to boot to automation (DOS, Linux or WinPE) and run the job.

jdan

You are probably seeing the license issue because the PXE boot image is an "automation" boot image, which loads the Altiris agent, which attempts to connect to your DS server. If you already have too many clients connected to your DS server, then this client will not be able to connect to DS, because it will exceed your licensed client count.