Deployment Solution

 View Only
  • 1.  BSOD after "successful" rdeploy - but NOT rdeployT??

    Posted Feb 24, 2011 04:27 PM

    Hey guys - anyone seen this:  

    Upon trying to restore a disk image to a PC, when I manually use rdeploy, the restore notes as successful, but upon reboot the machine is BSOD'd.

    Using the same disk image, however, with the Deployment Console and a preset job, which uses rdeployT when it runs, the job completes fine and the PC is just fine as well.

    I tried this on the same, known good, PC - obviously the DC job first, successfully, because upon manually running rdeploy I got the BSOD yet again.

     

    This, of course, is problematic because if I can't get to the PC via the deployment console, then that means I can't restore it? Yikes.

     

    Anyway, ever seen that happen before? 

     

    I'm using Altiris version 6.8



  • 2.  RE: BSOD after "successful" rdeploy - but NOT rdeployT??

    Posted Feb 25, 2011 01:08 AM

    Hi,

    Have you checked which parameters are different between your manual deployment and the Sample job? There are multiple switches you can / should be using if you want to run RDeploy thru either a script from the DS console or a DeployImage job.

    When checking default settings against the jobs (predefined and manually created), I think you will find that the sample job has some settings different to the one you manually create...

    -BBC



  • 3.  RE: BSOD after "successful" rdeploy - but NOT rdeployT??
    Best Answer

    Posted Feb 25, 2011 11:14 AM

    Thanks for the note...I was probably vague when I said "preset" job - it wasn't a sample one, but one that I've created and used many times before (actually, I've manually used rdeploy many times before as well; this is a new wrinkle that's just cropped up).

    HOWEVER - it did get me thinking, and I took a note of the specific switches/flags used in redeployT during the automatic jobs and tried running rdeployT manually with the identical (well, similar at least) switches -- and so far (in 2 attempts) this has been successful.

    So it DOES look like something changed somewhere in the graphical rdeploy.  Hrm.  At least now I can restore all the PCs I bricked during my experimentation :) and then dig a little deeper once I get some breathing room.