Client Management Suite

 View Only
  • 1.  Image Jobs Failing post 7.5 SP1 upgrade

    Posted Jun 11, 2014 01:23 PM

    We have our image jobs which put a base os then once they get into windows install various applications using quickdelivery in order

    Now after SP1 I am seeing this behavior

    When I have a new machine that is not in altiris everything seems to run through as normal, but when re-imaging a machine that is already in altiris things appear to just freeze with the tasks and eventually timeout.  The only difference I can tell is that when its already in the system the first time it checks into altiris it is getting a lot of policies vs a new machine takes a little time for it to be added to the policies.

     

    Any thoughts on why my tasks seem to now be failing or freezing in this situation?



  • 2.  RE: Image Jobs Failing post 7.5 SP1 upgrade

    Broadcom Employee
    Posted Jun 11, 2014 03:44 PM

    Hi SonicGT,

    Are you using an old image for re-imaging a machine? Otherwise, you're using an image, which was created in 7.5 Orion (maybe with some hotfix installed) or image was created in 7.5 SP1 version?

    • To get correct work for Client Task Agent with Task Server, you need to have same up-to-date version of Symantec Management Agent in image for client machine as it has your current Task Server.

    Its just a 1st thing what came to me to consider. Probably there is something another, which causes this problem in your setup.

    Thanks,

    IP.



  • 3.  RE: Image Jobs Failing post 7.5 SP1 upgrade

    Broadcom Employee
    Posted Jun 12, 2014 03:32 AM

    Hi,

    Task server with newer version should work OK with old clients if "Legacy Agent Communication" mode turned on. If it does not work - this is a bug.

    Thank you,

    Alex.



  • 4.  RE: Image Jobs Failing post 7.5 SP1 upgrade

    Posted Jun 12, 2014 10:16 AM

    We actually do not have the agent in the image itself.

    Below is a general outline of our imaging process, which was working fine prior to SP1 with either new machines and reimage machines.  Now post SP1 this works fine with new machines (record created in altiris during this process) but not with reimages (records already exists)

    The main difference I see happening between the 2 is on machines that already have a record the first time altiris talks back it gets all the software policies we created since it is already aware of the system, but on the new record it takes some time for this to happen and it doesn't get them right away, which seems to then not possibly conflict with the tasks needing to run??

     

    1. boot to pxe

    2. deploy ghost file

    3. copy files from share to windows drive and commands to batch file that runs when windows loads for the first time. (these files include the altiris agent install)

    4. Boot to windows

    5.  Batch file runs to Install altiris agent and sub agents (new versions - software management, DS, inventory, patch) before altiris communication occurs.  We release the IP so there is no network connection, then install altiris, then renew ip so it now gets network connectivity and to the NS it is none the wiser that altiris was not there prior to first communication in Windows 7

    6.  Altiris starts to communicate and continues the job

    7.  Job continues and installs applications using quick delivery

    8.  Job runs a cleanup script that removes autoadmin etc and reboots to finish

    9.  Done

     



  • 5.  RE: Image Jobs Failing post 7.5 SP1 upgrade

    Posted Jun 30, 2014 05:43 PM

    In your NBS general settings, there is now a new menu for pre-existing machines called "Redeployment (Managed Computer) Menu". After the upgrade to SP1, this menu in now available to be populated with your chosen images just as was done with your Initial deployment menu. Until you populate this menu, you wont be able to image pre-existing machines. Hope this helps.

    The path is Settings>Deployment>NBS General Settings>Redeployment (Managed Computer) Menu

    Click on the down arrow, check the box "respond to managed computers, chooses your PXE boot image, then populate your images. Click SAVE CHANGES> After that you should be good to go.

    I didn't have to, but you may need to recreate your preboot configuration.

    Have fun.



  • 6.  RE: Image Jobs Failing post 7.5 SP1 upgrade

    Posted Jul 01, 2014 11:05 AM

    This is not correct, at least not the way we use DS.  We disable PXE from responding to known computers since we only want it to respond when we send a tasks telling the pc to boot to pxe.  We have no issues with the machines actually getting to PXE or running parts of the job, just the reboot to production task tends to timeout as well as quick delivery software tasks once the pc is in windows 7