Deployment Solution

 View Only
Expand all | Collapse all

Computer identity does not correspond to the correct machine!?

  • 1.  Computer identity does not correspond to the correct machine!?

    Posted Jun 05, 2012 06:12 AM

    Hello!

    I have a very strange problem with DS 7.1 SP1.

    When running a job or task in DS web console it does not run on the corresponding machine.

     

    For example, When running a job with quick run, choosing for example Computer "machine1", and OK - it all seems to proceed the right way. 
    But then when you go under details of the job and check status, it have run the job on a whole different computer?

    I've only been lucky I have not reinstalled a "wrong" machine...

    Can someone please help me understand this problem?

    I Also do have a problem when task fails, but in fact it has really gone through OK. This is especially on run CMD or MSI-exes. Do I have to add some "exit" line in end of every task/script?

    (Sorry for the bad english, but I hope you can understand my problem here).

    Thank you very much in advance!


     



  • 2.  RE: Computer identity does not correspond to the correct machine!?

    Posted Jun 05, 2012 11:39 AM

    However, see if this helps.

     

    First, the only time I see a task scheduled for one system execute on another is if you have duplicate GUIDS in the console.  If more than one system were imaged with a computer that was not properly prepared prior to imaging, you can see this kind of behavior.  Not often, so we may need more details to properly determine what is happening, like screen shots.  You can go to both the target systems and look at the NS Agent and see if the GUID is the same youself or not as well.

    The second issue with a task that completes but shows failures can be several things.  1) if the return code is anything but 0, by default, we show that as failed.  ONLY a return code of 0 is success.  2) if the system shows failure on the main screen but shows success in a drill-down screen, then it's a known product limitation when you go beyond the scheduled time of execution (default is 30 minutes).  Again, we will likely need more information for full diagnosis.