djtech2k Posted September 7, 2005 Share Posted September 7, 2005 (edited) I just updated my 2003 unattend/sysprep to include SP1 slipstreamed. Since I did this, now when I begin the sysprep process, along the way it starts prompting me to approve unsigned drivers. These drivers are apparently being enumerated and it prompts me several times and proceeds to go down the list of drivers. I did not originally change anything fromt he original build. Could this be a SP1 thing?Anyway, I have done several things to the winnt.sif and sysprep.inf, aloing with adjusting the security template with no success.Thanks,DJ Edited December 3, 2005 by Bâshrat the Sneaky Link to comment Share on other sites More sharing options...
djtech2k Posted September 7, 2005 Author Share Posted September 7, 2005 anyone? Link to comment Share on other sites More sharing options...
ccooper33 Posted November 30, 2005 Share Posted November 30, 2005 Hey DJ--Did you ever get it figured out?I started using nLite yesterday. Got my unattend build working great. But when I run sysprep, I get prompted with the unsigned driver dialog for what appears to be every PnP driver that Windows knows about.If I build a box with the original 2003 CD this doesn't happen. It must be related to my customizations or nLite.Windows Server 2003 X64 StandardnLite RC1 Link to comment Share on other sites More sharing options...
Bâshrat the Sneaky Posted December 3, 2005 Share Posted December 3, 2005 Check the nLite forum and use a version that doesn't have this problem. Link to comment Share on other sites More sharing options...
ccooper33 Posted December 7, 2005 Share Posted December 7, 2005 Thanks, but if RC3 worked for me I would. (-: Link to comment Share on other sites More sharing options...
ccooper33 Posted December 1, 2006 Share Posted December 1, 2006 Hey Nuhi--if you're listening....It seems that RC8 didn't have the trouble with sysprep and driver signing.Yesterday (a year since the previous post) I updated to 1.2.1 and the issue is back.Mind you, I've only used nLite for x64 versions of Windows Server 2003, so I don't know if this is an issue with XP.This could stem from another issue that I noticed with 1.2.1. When integrating a text mode driver, the hardware IDs were not inserted into txtsetup.sif. This was for a Dell PERC 5i. We inserted three lines manually. Maybe that caused the driver signing to fail?I know this is an nLite issue (maybe a user issue) because installing 2003 Standard from the network (using winnt.exe) causes no issues with sysprep and driving signing. (I shouldn't have to disable driving signing when the drivers are signed.)Any thoughts? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now