Deployment Solution

Have an odd issue with our add machine to domain task. It still works but shows an error.

background - we have one build job (for new machines and rebuild)  that has apply system configuration task. This task has a specified "Altiris OU" we use for deployments then move to correct OU when built.

If the machine doesn't exist on the domain it will create the machine account specified in the dedicated altiris OU. completes successful.
After this it then runs the Power control - restart - which fails.
jobs then continues as normal.
 

If the machine does exist in  AD (Mind its been moved to correct OU) the Apply sys config task fails
The reboot toask is successful
jobs then continues as normal.

Existing machine :

new machine

Any ideas ?

DS 7.5?  Sounds familiar when moving machines. Unfortunately I don't recall the details. 1) check the KB for known issues with AD and the apply system configuration.  2) get a case escalated to see if this is duplicable in house and if it's being worked on.

If DS 7.1, you may want to check 7.5 to see if it's different (e.g. lab) but again, this sounds familiar.  It's been a while since I looked at it and now I don't have access to "insider" information.  <sigh>

Hi Thomas, Thanks for the response. Its 7.5 HF5 - never seen anything in the KB. As it works I will not bother going through support. Just thought i'd put it out there in case anyone else has encountered it.

Thanks

The main reason to go through support is to make sure there's a bug logged if they can dup it.

Hint for others that may not want to wade through support.  Put your foot down!  Don't be mean, but don't let them push you around.  For instance...

"I'm calling to find out if this is a known issue.  I've tested this several times and it always has the same results.  Will you test it as well?  No, I'll not try some other testing issues, I'd like to know if YOU test it if YOU get the same results.  You don't want to test it yourself?  Will you then please escalate me to someone who will?  Again, NO, I will not do more testing here.  You can escalate though if you're unwilling to test it yourself, I'm patient.  Thanks"

When there's a bug, it needs to be reported up.  It needs to have a public facing KB for others, and it needs to be taken seriously.   How do you know if it's taken seriously?  Another example:

"This is a known issue?  Will you please tell me what release it's slated for, for a fix?  Does this have a bug number you can share with me so I can follow-up on it at a later date?  No, a KB number is not enough, I need a bug number.  Thanks.  Can you indicate when this is expected to be fixed?  No?  Can you escalate to someone who can please?  Thanks."

Being firm like this helps the navigation of support go a LOT faster.  :D  Just saying...

To be fair - I have never really had a 'bad' experience with support. Most times they have been excellent, and to be honest if the support hadn't been as good for me I think this software would have been gone long ago. The software is only a part of my job and I want to minimise time dealing with issues. I think I have probably raised my fair share of issues/bugs anywy :-) - now - If we get a heavy discount at renewal time then thats a different story :-)

Thanks