Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Deploy image job is not rebooting correctly

Created: 02 Apr 2014 • Updated: 10 Apr 2014 | 17 comments
This issue has been solved. See solution.

We  upgraded from SMP 7.1 SP2 to 7.5. I am using jobs/tasks for deploying images. Everything worked well under 7.1, but now with 7.5 the Reboot to pxe task is not behaving like it used to. I use my existing jobs/tasks for image deployments. With the Reboot to task that is set to reboot to pxe; the computer reboots into pxe and receives the initial deployment menu instead of the imaging job that I scheduled for this particular client. The job status says 'queued' and 'start pending'. I removed all my jobs/tasks and re-created them thinking maybe something going from 7.1 to 7.5 messed up my jobs/tasks. But the behavior stays the same.

On 7.1 I can schedule an image deployment job to a particular client, it will reboot to the preboot env. through pxe, it will receive the winpe env. and get the image I setup within that job. Now it reboots to pxe and somehow bypasses the job and gets initial deployment menu. Since this client is managed and I set initial deployment for only un-managed computers for now. PXE errors and boots to the hdd. If I remove the client computer from the console (un-managed) PXE will work, but go to initial deployment instead of running the job I scheduled. Any ideas in this change of behavior?

I also noticed that the job never fails and stops on its own, the job keeps recycling until the client fullfills it's job.

Operating Systems:

Comments 17 CommentsJump to latest comment

Igor Perevozchikov's picture

Hi,

Did you make sure that NBS settings are correct on your SMP Server?

NBS_Settings.jpg

Thanks,

IP.

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread
MJammer's picture

Tried this, I unchecked the setting 'Respond to Unknown Computers'. Nothing worked, it booted to the nic card, failed, then booted to hdd. Next I unchecked 'Apply NBS Settings Immediately'.

MJammer's picture

Forgot to mention same results after unchecking 'Apply NBS Settings Immediately'. Boots to nic > fails again > boots to hdd.

Thomas Baird's picture

There are two issues being looked at here and they are completely separate.  How PXE responds is totally different than if you get an Initial Deployment menu or not, and I'm concerned we're going to get mixed up.

 

How PXE responds is dependent now on a direct connection with the NS at the time of boot, and of course recognition of the system.  If it's deleted, then PXE will respond as if it's a new computer and of course you'll get initial deploynent when in automation.

 

The OTHER question is once in Automation (regardless of how you got there), why are you getting an initial deployment menu?  Well, if it's deleted, then yeah, you'll get that.  If it's NOT deleted, then we need to troubleshoot a bit.  The logs can show you what's happening - SMP log, PECTAgent.log, and DSTasks.log.

For instance, if in the ... SMP log I think, I''m confused now between that and PECTAgent, since the naming convention changed in 7.5.  Anyway, one of those will show the agent checking in and reporting up several hardware keys.  Most of them don't matter, but the lines after that where we say if you're managed or not DOES matter.  If it's not finding you, then we need to know why.  Why can be discovered by watching the process in Profiler, or looking at the data sent up, or...

Anyway, if you're not being found, THAT will cause the Initial Deployment menu to come up, and may be why you're not seeing these jobs ever completed, because to the SMP, the computer never re-connected to get the job, but this weird unknown one did...

 

Something to consider.  In the new world, we have systems being plugged into docking stations for re-imaging.  That generates a new MAC address not associated with the system.  If that's the case, it may be a bit ... interesting to find out how we can fix this.  The NS tracks Name.Domain, FQDN, and MAC on a system, and if the MAC is being changed...  FQDN and Name.Domain IS being changed because it's in PE.  <sigh>

 

Let us know.  If you can't do it yourself, zip/post the entire Logs folder from under x:\program files\symantec\deployment and we'll take a peek.

 

GL!

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

MJammer's picture

Tried it again this morning with no success again. Here are the details:

The client computer I am running the job with is managed in the console, it is NOT deleted. The NBS General settings are setup the way Igor P. informed me to do in the above screenshot.

The client receives the reboot to pxe task (1st task in the imaging job), reboots to the nic card. Then I receive the pxe error: "PXE-M0F: Exiting Broadcom PXE ROM". I guess this means I am a managed client and since NBS Settings are not setup for managed computers I am out of luck obtaining a preboot environment? So it looks like I am trying to get the preboot environment and initial deployment menu. Although I am in the middle running a job.

Why am I going to initial deployment instead of running my imaging job?

Also, the reboot to pxe task in this job recyles until I stop > delete the job and/or delete the client from the console. I am used to 7.1 where reboot to pxe fails > job automatically stops.

Thomas Baird's picture

Respond to managed computers MUST be selected in the NBS settings or this wont work.  Period.  When you pxe boot the client, the PXE server service asks the NS what to do with the client.  If the NS says "Hey, the admin told you not to respond to known computers and this is a known computer" then it'll tell the system to go away (PXE-M0F) and boot to production.

And yes, it will then cycle over and over until the task expires.

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

Thomas Baird's picture

By the way, go ahead and have it respond to all forms of computers - predefined AND unknown as well.  That's not the settings we're really troubleshooting at this time anyway.  We need to know what's happening in Automation.

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

SOLUTION
MJammer's picture

Tried it with managed computers checked off. I left pre-defined off because we are not using that option. It finally pulled the image; it is focusing on the job instead of acting like a new computer waiting for initial deployment menu. That worked!! In 7.1 I could run a job like this anytime I wanted, with unknown computers checked. The job would run all the time. What is the relation to having Managed Computers checked off with 7.5?

Below is the results after the job completed. Does not give me a completed 100%. Guess it thinks the job never started and finished.

MJammer's picture

Guess my screenshot did not get added. But you understand that the status of the job is still saying queued and start pending.

Igor Perevozchikov's picture

Don't know does it will make sense, bud did you try to:

  1. Another client computer with same Job execution? Any difference of behavior?
  2. What about to create "Client Job", which will include 3 different "Run Script" tasks (Not DS tasks)? What status will has this Job? 100% Complete or same as for DS Job?
  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread
MJammer's picture

Did not try another client, but I am running a job with three tasks:

Reboot to: PXE

Deploy image

Reboot to: Production

MJammer's picture

After the image job is done, I receive Symantec Agent 7.1 and all 7.1 plug-ins we use. Any reason why I am not getting all the 7.5 agent ad pluins?

Igor Perevozchikov's picture

Seems like you have an image which was created in 7.1, including 7.1 plug-in version.

If you want to update 7.1 plug-ins to 7.5 version, you need to enable all required Plug-in upgrade rollout policies on SMP Server.

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread
MJammer's picture

That makes sense, did not think of that. I did build a test image prior to our upgrade to 7.5. Wasn't sure if the server deployed updated agent/plugins or not. Thanks

Igor Perevozchikov's picture

What about your main problem, that DS tasks weren't complete correctly? You've solved this problem?
Also, you've tried to perform a DS jobs, using Task Servers 7.5 version for 7.1 clients?

Symantec Management Agent on client computers and Task Server should have latest version of installed release/hotfix on SMP server, because if SMA or Task Server will has difference in versions of release/hotfix, then tasks won't work.

Otherwise, if you have latest version of Task Server and SMA on client computer and you will see that something doesn't work, then it will be easier to investigate for Tech Support and there will be no additional verifications/questions, in case if TS or SMA has different versions.

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread
Thomas Baird's picture

OK - the puzzle pieces all come together now.  :D

 

1) you MUST upgrade your image to have the new agent in it.  Otherwise, things go nuts post imaging.

2) if the OLD agent is in the image, then it can not send up the job status as complete when it reboots.

3) The job does not show complete in the console until AFTER the image has rebooted into production and the NEW DS 7.5 agent gets a chance to report up completed.  THIS is why you are getting the job showing incomplete in the SMP even though it ran.

 

This is commonly overlooked by customers.  The images, unforatunately, NEED to have an updated agent in them.  This is a major release of the product, not a minor release, and that means agents everywhere NEED to be udated - on site servers, on clients, and IN images.  There's no shortcut for this.

 

And the good news now for you is that you now understand how it all works.  Remember, how things worked in 7.1 was... kludgy at best.  People became accustomed to it because they had to, not because it was logical.  7.5 attempted to fix that and make things logical.  So far, what I'm hearing is that it's working as designed.

 

Good luck!!

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.