ccooper33

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?

Here's the rest of the story. All of this is to get our Altiris Solutions up and going on a new server. After I turned off DEP to allow .Net to install, I had re-booted the machine normally, which turned it back on. The Altiris install helper said the worng version of .Net was installed, but a minor registry hack took care of that. Then, as I understand it, the Altiris applications wouldn't run properly because of DEP. Needless to say, DEP has been changed to a different mode for good. I guess we'll have to look at a corporate policy on DEP now. Have a great weekend, all! Thanks for your support.

If you're installing .Net 1.1 on 64-bit Windows, beware of DEP. I had to learn the hard way that with DEP set to 'Always on,' the .Net 1.1 installer would fail. Note that I've got server hardware and I was nLite-ing Server 2003 R2 x64. But I think nLite may have supplied the offending line in my winnt.sif. Removing the lines below fixed my issue. [SetupData] OSLoadOptionsVar = "/noexecute=alwayson" See my post over here.

Thanks, folks. I do appreciate the feedback! @crahak, great point about the logs. I had already checked and that's how I knew for sure what was failing. @Camarade_Tux, yes the event log is also a great tool. Unfortunately, in this case, there was less in the event log than in the installers' logs. I'm merely trying to install .Net 1.1 on an existing server that was built using an nLited image. .Net 2.0 isn't needed at this time. I was following the theory that nLite RC8 did something that kept the setup routine from succeeding. (Remember that this is Windows Server 2003 R2 Standard x64. .Net 1.1 is not included in the OS on 64-bit versions.) Yeah, I know nLite 1.0 and later are out, but I'm using RC8 because I'm trying to find and fix something that was broken in a build that I originally created with RC8. I didn't want to change too much before I knew for sure the cause, you know? I'm sorry I lost the faith Nuhi. I should've known better. It's not an nLite issue...well not entirely. Through the process of elimination, I finally figured out the issue was DEP! I can't remember for sure now, but I think nLite stuck the offending line in my winnt.sif at some point. Not knowing any different, I had left it in. Symptom .Net Framework 1.1 setup failed while registering components. Here's the important parts of the log. Registering System.EnterpriseServices.dll Executing: ERROR: Process returned non-0 value! CMDLINE: "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\RegSvcs.exe" /bootstrapi Executing: Failed Issue Windows was started with the switch /noexecute=alwayson in boot.ini, which turns on Data Execution Prevention (DEP) for all processes. (See http://support.microsoft.com/kb/875352 for more information.) Resolution I knew this issue was related to our custom unattend/sysprep image which was built with an nLited CD. I started by removing items in winnt.sif and rebuilding a test box until the issue disappeared. Then I gradually eliminated/added back items to determine the root cause. This section is in winnt.sif. [SetupData] OSLoadOptionsVar = "/noexecute=alwayson" Removing the above section from winnt.sif resolved the issue when installing a customized OS. But on the existing server (where my current issue is), the ability to turn off DEP was disabled. (See the screenshot.) I had to create a new entry in boot.ini and re-boot to force DEP to its default state. (See http://support.microsoft.com/kb/875352 for more information.) The system was re-booted normally (with the switch) after the .Net 1.1 updates were applied. Thanks gang for your support! nLite rocks, Nuhi!

Anyone else seen this? Nuhi, can you point me in any direction? I used nLite 1.0 RC8 to create an ISO for Windows Server 2003 R2 Standard x64. Very few tweaks were used, all simple GUI mods. The installation goes great. Downloaded the .Net Framework 1.1 installer from Microsoft. Ran the isntaller, but it gets to registering System.EnterpriseServices.dll and it begins rolling back. Regsvcs.exe is what fails, but I can't figure out why. .Net 2.0 installs without issues, but I need .Net 1.1 for a specific application. In response to Google results: Nothing having to do with mscoree.dll makes any difference. Tried to clean-up the install: the tool hangs. (Aaron Stebner's WebLog - "Removal tool to fix .NET Framework install failures") Changed the TEMP and TMP variables: didn't help. Is there something specific that I've turned off and need to turn back on to make this installer run correctly? Is there anything within nLite that would cause this type of issue? Nuhi? Anyone? Thanks

Thanks, but if RC3 worked for me I would. (-:

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 Standard nLite RC1