Deployment Solution

 View Only

  • 1.  Depending on how the job is run either "This device is not capable of running this task" or "After scoping and filtering no computers are left assigned to this task"

    Posted May 22, 2012 03:31 PM

    Hey Fellas!

    Have another query to bother you fine folks with.

    I have been using deployment solution with a very good success rate in my environment.

    Mostly, new computers boot into PXE, are formatted into one single partition with no hidden partitions.

    After that, their names show up in the console as MiniNT-xxxxx.

    I then drag and drop an imaging job onto them that deploys an image that I have been using for a long time.

    Now, this is what happened yesterday.

    I tried to deploy an image to 3 brand new laptops yesterday using PXE. I booted them into PXE and selected a disk partition job from the initial deployment menu. After the partitioning was done, the computers simply would not get the imaging job. Every single time the error - Depending on how the job is run either - "This device is not capable of running this task" or "After scoping and filtering no computers are left assigned to this task".

    Recently the V3 rollup for the 7.1 SP2 version was installed on the platform.

    Now I'm not sure what the V3 rollup has changed but this is not the outcome I was hoping for.

    Any ideas what to do in this case?

    Thanks!

    n00b out!
     



  • 2.  RE: Depending on how the job is run either "This device is not capable of running this task" or "After scoping and filtering no computers are left assigned to this task"

    Posted May 23, 2012 10:09 AM

    Any ideas guys!! Where's mclemson when you need him lol...



  • 3.  RE: Depending on how the job is run either "This device is not capable of running this task" or "After scoping and filtering no computers are left assigned to this task"

    Posted May 23, 2012 02:42 PM

    Hey, I had a baby.  And work has been busy.  Why didn't I see more of you guys at the Intuitive booth at Vision Las Vegas?

    Jobs can fail in automation if a new computer has not yet been included as part of a Delta Resource Membership Update.  If this problem occurs again, and you run a Delta Resource Membership Update, is it resolved?



  • 4.  RE: Depending on how the job is run either "This device is not capable of running this task" or "After scoping and filtering no computers are left assigned to this task"

    Posted May 24, 2012 06:24 PM

    I too am having the same exact issue.  Running the NS.Delta Resource Membership Update task on the server didnt help.  I contacted Symantec support and they said it may be because I have tasks in my image job that the PXE envrionment cant run.  I do have some VBS scripts that run and have run for the past year.  I created a new job and removed all the script lines.  When I went to go run the job the error was gone.  My problem is I NEED those vbs scripts to run as they have had in past.

    I too ran the Hotfix v3 and wonder if that is what caused all the issues.  I will post back anything I find, and hope if you find an answer you will post it here as well.

     

    Thanks



  • 5.  RE: Depending on how the job is run either "This device is not capable of running this task" or "After scoping and filtering no computers are left assigned to this task"

    Posted May 28, 2012 11:29 AM

    Hey Mike! Many congratulations on the baby! Best wishes to you smiley. Hope everyone is doin okay?

    Sorry to bother you with all the queries, but you are one of the key resources on this forum. Plus, your solutions are always awesome laugh.

    Anyways, as resendesw has posted, even after running the Delta Resource Membership Update, the task fails to run. It's the same error everytime. I'm not using any scripting based tasks, only a simple imaging task.

    What I don't understand is, why is the job failing now when it ran fine previously! Have there been some changes with the new rollups related to PXE?

    I did not find any such documentation or information mentioned anywhere.

    Do reply when you get some time off taking care of the new onesmiley

    Take is easy...

    n00b out!



  • 6.  RE: Depending on how the job is run either "This device is not capable of running this task" or "After scoping and filtering no computers are left assigned to this task"

    Posted May 30, 2012 01:50 PM

    Symantec support suggested I install Rollup v4 and see if that corrects the issue.  I will post after the update and some testing. :)



  • 7.  RE: Depending on how the job is run either "This device is not capable of running this task" or "After scoping and filtering no computers are left assigned to this task"
    Best Answer

    Posted Jun 05, 2012 12:52 PM

    Looks like the Rollup V4 fixed the issues we were having.  Just be sure to backup your database and servers (if possible).  Since we run ours on VMware we just did a snapshot in case something went wrong.

    :)



  • 8.  RE: Depending on how the job is run either "This device is not capable of running this task" or "After scoping and filtering no computers are left assigned to this task"

    Posted Jun 22, 2012 12:20 PM

    I have the same issue and wondering where you got Rollup V4.

     

     



  • 9.  RE: Depending on how the job is run either "This device is not capable of running this task" or "After scoping and filtering no computers are left assigned to this task"

    Posted Jun 22, 2012 12:27 PM

    Rollups are obtained from Symantec Support by opening a case.  If they confirm you have an issue in your environment that is resolved by the rollup, they'll provide it to you.