OSD - Reimaging an existing system

Usage and Config
1

(imported topic written by vincent.h)

Hi,

I’m trying to reimage a system using Bare metal imaging on a system that I’ve already imaged successfully in the past. Here’s the scenario:

  1. Image target using image#1

  2. Reboot or shut down the target, boot to network to attempt to reimage using same image again

  3. Target PXE boots into rembo, sits there with msg
    "“no tasks to execute; staying idle” and then boots to the OS.

Why is this happening? I figure its due to the fact that the target has been register into TEM and TPMfOSD and as such, as a cautionary measure (in case a user tries to reimage again) doesn’t allow the system to be reimaged again?

How do I override this behaviour so that I can perform another deployment to an existing system?

Thanks!

2

(imported comment written by avt85)

what’s the target status of that machine on your tpm gui?

In my cases, when a target is not identified as 100% complete from a previous image, this would occur.

Resetting the target state for that machine in the tpm gui does the trick.

3

(imported comment written by vincent.h)

Thanks for the response avt85. I noticed the status after posting the original question. It was stuck at 77%. Not sure why though. There was nothing unusual in the logs and the previous imaging task seemed to have completed fine. The OS image was deployed, the agent was up and running and I didn’t notice anything wrong with the running system.

I was able to reimage that system again after deleting the target from TPMfOSD but its quite the hassle if I have to do that (or reset the status) everytime that I find the deployment menu doesn’t show.

4

(imported comment written by sergio.tarchi)

Hello,

the binding menu in this case has not been displayed because there was a pending task (not completed) on the target machine. Deleting the entry of the computer deleted also the pending task for that computer, so the “new computer” had not pending task and binding menu has been displayed.

This is one of the reasons when the binding menu is not displayed (in any case this problem does not occur often) but not the only one. When the problem occurs the server logs (located in \logs directory, where is the one provided at bare metal server installation time, default is C:\TPMfOS files) could help.

Thanks.

Sergio Tarchi

IEMfOSd application level 3 customer support

5

(imported comment written by avt85)

Hi Sergio,

the problem that Vincent is having whereby targets are stuck at 77% happens all the time in my environment as well.

Even though the imaging process has already completed and joined the domain, started processing TEM tasks the target still sites at 77% completion.

The one thing I did notice was that, it seem to site at 77% if not all the drivers have successfully installed on the machine (in my case, there were 2 devices that the system could not find a driver for). Manually installing the drivers have set this progress from 77 to 100%.