Altiris Software Dev Kit (ASDK)

 View Only
  • 1.  Altiris

    Posted Mar 26, 2015 06:24 PM

    I've been learning/using this Symantec Altiris software for the school district I'm working in. They have a server tech that makes the images and sets up all the drivers, images for deployment and such; but I just use it to deploy the images to the pcs and laptops and make changes to the Altiris settings if we can't access the images once in PXE. The issue I'm having is they upgraded to the 7.5 Altiris and it's throwing us errors. I have given all the NIC drivers that are needed to get into PXE and have them recognize the pc/laptops by either IP or MAC address and their found. I have me and the server tech on forums and the phone with Symantec, and were still in the waiting game for a solution. This is the error I run into:

    Status: Failed 
    Return code: -1 

    Start time: 1/7/2014 11:28:19 AM 
    End time: 1/7/2014 11:28:19 AM 
    Total run time: 0 seconds 

    An unknown exception was thrown.

    Show raw exception message 
    System.Exception: SerializedParameterCollection::ToValue(): Unable to get a .NET type named Altiris.TaskManagement.Common.Tokens.TokenDefinitionCollection, Altiris.TaskManagement.Common, Version=7.5.1672.0, Culture=neutral, PublicKeyToken=99b1e4cc0d03f223 at Altiris.DotNetLib.Collections.SerializedParameterCollection.ToParameterValueCollection() at Altiris.ClientTask.Server.Data.ClientTaskServerExecutionInstance.get_InputParameterValues() at Altiris.ClientTask.Server.Execution.ClientTaskEngineExecutionThread.LoadInputParametersFromTaskInsta nceParent() at Altiris.ClientTask.Server.Execution.ClientTaskEngineExecutionThread.Execute() at Altiris.TaskManagement.Common.Execution.Engine.TaskExecutionEngine.ProcessTaskExecuteOperation(TaskI nstanceRequest request, TaskEngineExecutionThread thread) 

    Does anyone have an idea if these are caused by the configuration that the Server Tech has setup or if it's not locating specific files that the server needs to deploy?

    Sorry if I'm jumping around so much and confusing any of you, but I'd like to just ask here since sometimes someone here may have run into this type of error or others and may have the solution or suggestion that we've been waiting on Symantec to get back to use on.