Deployment Solution

Hi

I run client Job to capture disk image from Windows7 Prof. computer

Job have this :

Prepare for Image capture ( with credentials to rejoin a domain after capture is complete option configured )

Create disk image

Boot to production.

Problem is :

After reboot to production computer is not jojned to AD

I receive login screen but I can set user name and password for my AD but I cant login.

In sysprep process no error

In create image process no error

Any idea ???

Regards,

Michał Matukin

Prepare for image capture had a bug in DS 7.1 where the domain name was being set incorrectly.  Where it asks for domain credentials do not type the domain part in the domain\username  just the username.

Using inventory info made a domain\domain\usename issue  so try not typing the domain name and hopefully will work for u.

nelo

You can actually do it both ways in MR2.  There were quite a few bugs for DS fixed in MR2.

Thought you should know that this is one of them.  :D

Hello Michal,

This is an issue with DS, may be its fixed in MR2. if you are not planning to shift MR2, then you can add an 'Apply System Configuration' task in your existing Deploy Image job list.

So, when the imaging is completed, the Apply System Configuration task will add the machine in domain.

Let me know if this helps.

Hi

THX for you answer

OK I check this in prepare for image capture

I have MR2 installed and problem appear.

I have additional question is this problem appear in deploy image task in this task I have field to join to domain ( example said domain/user ) ???

When I reboot to target computer then I cant log in and Apply System Configuration job applied to this computer to rejoin not work ;/

Regards,

Michał Matukin

Professional Services Department

CompFort Meridian Polska Sp. z o.o.

Al.Jerozolimskie 65/79

00-697 Warszawa

Hmmm...  If that is the case, then we've missed something, or you did.  Not sure which yet!  From our testing in MR2, it worked to join the domain with either JUST the user name (recommended above) or domain\username.  Remember to put in the domain information correctly.

As for not being able to log in, you SHOULD be able to log in locally at least.  Do you have a domain selection?  if so, then it joined the domain correctly.  If not, then it joined a workgroup of the domain name perhaps and maybe that's why you can't log in.  Try logging in locally so you can look at the settings and see what it actually did.

If you can't even log on locally, then you have a different problem.  If that is the case, I suspect you get an error message when it boots.

Let us know if any of this helps at all.  Thanks!

Hi litle update

After capture I cane pusch configuration job to this agen and rejoin to domain after that I cane log in on the domain user.

If i dont do this I have login scren but only for localy user when I write in user field momain\user I receive error mesage. 

Michal

Hello Michael,

Results for Capture machaine and target (deploy) machine will be differnt.

Capture machine will join the domian easily.

For deploy image, apply system configurattion task may not have worked as Altiris Agent takes some time to connect to NS and get Tash server. Once that is received the task will roll out.

If on your image deployment, the system doesn't join the domain, that sounds like MR1, because from our testing, this works in MR2.  We know it fails in MR1 though, and we also know that sending the configuration job fixes the problem - just like you described.

If, when you log on, you are not given a domain field to select in, then don't manually type it in, because that says it's in a workgroup and it will always give you an error.  Thus, you will NEVER need to log on with domain\user on a system joined to a domain.  This is by design and lets you know that it hasn't joined the domain.

Can you confirm through the SIM what version of DS you have installed currently?

Hi

This problem back on deferent computer.

In first my try prepare to image end without error but we can’t log in after system restore.

I use work around run configuration task to join to AD after that all work without problem.

Now we prepare another laptop and this image job don’t end with success.

On end imagining task after start agent don’t response to take configuration task like in my first step.

I create another test I try image Windows 7 profesional in VMWARE env.

Prepare task end without error

Image task end without error

But when target OS start after sysprep I receive error message like : creator cant configure…. And nothing happened OS don’t run to login screen.

I examine xml file from sysprep folder in target I see this in join domain :

<joinDomain>mostwar1.local</joinDomain>
<Domain>mostwar1.local</Domain>
In any field in configuration of this task I don’t write mostwar1.local
In user field I have mostwar1\admini and this value I set in prepare task.   

I don’t thing so this .local is right

In my installation I have DS in MR1 version. ( I see MR2 update but don’t install )

Regards,

Michał Matukin