The extended attributes are inconsistent

Ian,

Doing scripted installs on Blades is not the best way to go. It is more easy to use a program like Nlite to build your image and then use Deployment to deploy the image to the blades.
Regards
ErikW

Thanks Erik, I am looking into this now, as I have not heard of nlite before.

In nlite how do you configure it so that you get the network correct when deployed through DS? Do you just use teh defaults and then DS will assign them, or do you use %COMPNAME%, etc?

Thanks in advance!

When you use Nlite, and there is a good tutorial on the juice, then you deploy it once to a blade. That server you need to use to build your image.
That image can then be deployed with DS, and DS will set the machine name.

Regards
Erik

Hi Erik,

I am able to use nlite perfectly for x86 architecture, but not for ia64, which is what I need to achieve, as I do not believe it supports it. Any other ideas?

Cheers
Ian

Try it with Vlite. That is also described on the Juice, but i'm not sure if it is also for win2003.

Regards
Erik

Hi All,

I logged a case for this issue, and there are apparently a few issues with integrity machines and the DS communicating with them. THe fixes for these are going into the product, but apparently it is all resolved already in RDP.

Hope this helps.
Ian