Hi Guys!

I have an unsusal issue that you cal possibly help me with.

Situation.
I am trying to deply xp pro sp2
I use Altiris deployment server to run a scripted build.
First.. I use nlite to inject the dirvers I need thsese are Nic, SVGS and Sound drivers
I then copy the I386 directory to a location and use deployment server to run and unattend.txt against it. it rund fine

issue
When then join the domain in (this a test domain with not policies set)
and log in as a authenticated user (basic user that i have created in ad)
When I put in my usb mouse, keyboard and usb key I get a prompt asking for credencial from local adminstrator and password.
this only happens when iuse nlite. it somehow changes some security feature the askes me to authenticated anly usb devive i plug in

any ideas ???

Did you remove the Volume Shadow service?

Hi Nuhi,


No I don't think so, the unattend.txt file works fine before i used nlite to import drivers, if I use may unattend.txt file and an windows xp source that is not updated with drivers using nilite, it works fine i do not get the authentication problem when i put a usb device in.

if this is not what you mean please elaborate, i am very interested to know your trail of thought.

This post has been edited by Omar123: Jul 9 2007, 04:48 AM

I meant did you remove the component named Volume Shadow from the services, in the nLite - Components page?

Hi Nuhi,

No! i just used the default options i.e started nlite up, imported drivers nothing more then that

thanks!

If you just imported the drivers and selected only the Driver page and ISO page then I can't say it makes any sense. See if you used some other tool as well.

Did this get resolved?

I also appear to have this issue.

I have winpe installing XP SP2 over a network and after using Nllite to make a singular driver addition I can no longer move USB mouse or Keyboard from one USB port to another without a Hardware Wizard Dialogue appearing.

With the same XP source prior to Nlite this is not the case.

Only settings changed in Nlite was 1 driver installed.

Well after further investigation I've found the culprit being syssetup.dll - Now looking into a way to fix this...

It appears this issue has been brought up check - http://xp.modrica.com/board/lofiversion/in...php/t94362.html

Doesn't appear to have a full resolution yet tho...

This post has been edited by adom: Feb 6 2008, 12:50 AM

That helps. nLite returns signed syssetup.dll after the install to avoid such issues but since you do manual install from winpe then it might have got skipped. Do you use /unattend:winnt.sif switch? Can you try it next time just to confirm. Let me know if you do, thx.