Running 8.1 RU7. Recently most local clients are not registering after initial image lays down. Our initial image is very limited, basically just to OS. Our job is basically this: Deploy Image Boot to Production Update Configuration Rename Computer Send basic inventory Install a bunch of software (each an individual job). After the Deploy Image runs it reboots, but then does not register the client back in to the task server to run the rest of the tasks. If you log in with the local admin account the Agent will then register and then run all the tasks successfully. This has been an ongoing issue but recently has become almost 95% of imaging jobs run. Any solutions would be appreciated.

Deployment Solution

View Only

Clients not registering after imaging

Greg Thomas posted Jul 20, 2021 11:01 AM

Running 8.1 RU7. Recently most local clients are not registering after initial image lays down. Our initial image is very limited, basically just to OS. Our job is basically this:
Deploy Image
Boot to Production
Update Configuration
Rename Computer
Send basic inventory
Install a bunch of software (each an individual job).

After the Deploy Image runs it reboots, but then does not register the client back in to the task server to run the rest of the tasks. If you log in with the local admin account the Agent will then register and then run all the tasks successfully.

This has been an ongoing issue but recently has become almost 95% of imaging jobs run.

Any solutions would be appreciated.

Broadcom Employee Sergei Zjaikin posted Jul 21, 2021 03:55 AM

There were quite a few reasons for this. A lot of them have been fixed in 8.5 and 8.6 releases. You may want to upgrade to 8.5 at least or better 8.6

Greg Thomas posted Jul 21, 2021 09:24 AM

Thanks, we are working on a new 8.6 environment Was hoping there was some resolution in 8.1 until we get to 8.6.

deemacgee posted Oct 17, 2023 02:51 PM

Sorry to resurrect an older thread.

We're currently on 8.6 RU3 and still seeing this exact issue - it doesn't always happen, but when it does, it creates major complications. Although this has been tolerable for the last few years, we've seen a spike in this behaviour over the last week, with roughly 30% of builds stalling at Boot To Production. They do not correlate to site, operating system, or hardware.

The workaround for us is similar to Greg's description - we log in and hit the Reset Agent button in the Agent. The machine then resumes the deployment sequence without further difficulty. Whilst this works, it does defeat the purpose of automated deployments.

We run a dedicated Task Server alongside the primary Altiris server - I remember seeing discussion elsewhere, possibly in this Community (I've long since lost the link) about configuring IIS on the TS to use only HTTP connections, which we did during the initial diagnostic and mitigation a few years ago. This helped reduce the frequency somewhat but did not eradicate the problem entirely.

I am keen to hear from anyone who has either fully resolved this problem in their environments, or, is still seeing this issue on 8.6 RU3.

Thanks all

Broadcom Employee Sergei Zjaikin posted Oct 19, 2023 03:43 AM

deemacgee, could you please collect the logs from the agent before you reset it? thanks!