Task Deploy does not starts

[zingaro]

Hi,
I created a deploy task with web-interface but the client ( unregged ) does not starts.
The image was created with another identical PC :
capture and deploy from web interface works fine;
deploy from client boot menu works fine.
with another identical PC works only deploy process from boot client menù.

I noted the options "ignored mac client and imaging " and check it, but the client unregged does not start the deploy process created whit the new task.

the questions is : It’s necessary record a new client into web server page before starts the same task more times with more pc ?

Regards

[Sebastian Roth]

@zingaro How do you start a task for an unregistered client from the web interface?

[zingaro]

@Sebastian-Roth said in Task Deploy does not starts:

How do you start a task for an unregistered client from the web interface?
my step was :

1. add a client to fog
2. create image definition , assign to client regged
3. capture image
4. deploy image on same captured pc ( to test restore operation )

5.test a: change with another identical pc and restore ( deploy ) from boot client menu without regs step. ( work )

5.test b: change with another identical pc and select the original ( first client ) machine and deploy task image.
starts another identical pc ( deploy on client does not starts )

[Sebastian Roth]

@zingaro said in Task Deploy does not starts:

5.test b: change with another identical pc and select the original ( first client ) machine and deploy task image. starts another identical pc ( deploy on client does not starts )

Sure, every “identical” client has a different MAC address on its network adapter. So to FOG all those “identical” clients are different. Creating a task for the original (first client) will only run on this client!

Test A is working because the deploy from boot menu is different to creating a task in the web GUI. Starting a deploy from the boot menu (called ‘Quick Image’) is possible for unregistered clients. But as I said, this is different to scheduling a task for a registered client.

So from my point of view FOG is behaving as expected in your case.

[zingaro]

@Sebastian-Roth
Ok Correct,
But i see the options “flag”( ignored mac client … ) and I was thinking that this selection can be used for skip the control to the target.

[Sebastian Roth]

@zingaro I think you misinterpret the option. To quote Tom (see here

What ignore for imaging does is make sure that nic does not get used as the method for checkin and progress.

This option is for clients that actually have more than one MAC address. In this case things can fail if the client uses the wrong MAC/adapter in the imaging process. Checking the option will make this particular client to use the other (unchecked) MAC/adapter for imaging.

So back to the initial question: Imaging an unregistered client is only possible in the boot menu AFAIK.

[Tom Elliott]

The “image ignore” and “client ignore” flags are meant to IGNORE the mac address in use for the respective item. For example:

Image Ignore makes it so the MAC Address being loaded is NOT going to be able to be used for Imaging. But this is only regards to the system it’s registered with. (Seeing as identity is verified/validated by the MAC Address this should be expected).

So, an unregistered machine, using a NIC that is registered to another machine, will appear to be that “registered” machine. Why would Image Ignore be a useful option? I don’t know, but I know the client ignore option IS useful (for example a shared USB nic on multiple machines so you can have the client work without thinking the system is another host.)