kingsc

Ok... I must not have had the ethernet cable plugged all the way in or something when I was having this is issue.... took two different laptops with different NICs and it works perfectly fine... K.I.S.S. , right?

Oh I've tested this image for a while now, I've been developing it for over a month. It works on the 5 different models currently in use: Dells and Lenovos, desktops and laptops. All drivers are present and functional. It's really not THAT big of a deal, it's just one annoyance I'd like to eliminate. The driver is there, it's just that if I don't an ethernet cable physically connected to the workstation, after you log in to the machine and open up IE, it goes to the new connection wizard. If I have a live ethernet cable physically connected to the workstation while setup is going, it doesn't do this. EDIT - I will check this though right now.

If I deploy an image to a workstation, and that workstation is not currently hooked up to a LAN, the LAN Connection does not configure itself and the Create a new connection wizard pops up once you try to get on IE. Is there a way since I deploy images to multiple machines at the same time to negate this? I want the workstation ready to go with little to no user interaction so that when they open IE it actually goes to the internet instead of the setup wizard, and without having to have the workstation hooked up to the LAN while mini-setup runs.

Turns out one of the earlier posters nailed it. If you remove the InstallFilesPath from sysprep.inf, that fixes the problem. Also, as far as I can tell, it wasn't needed; there doesn't appear to be any missing files or lack of operation. All the drivers are there, all the programs including MS Office are there and functional, and the installation was completely unnattended. I started it up, came back 20 mins later, and it was at the logon screen. Pretty sweet. =)

Easiest way for you if you don't mind spending money would probably be Acronis True Image 11 Home

Ok so here's something weird. I use trend micro office scan and want to deploy it in an image. I follow the instructions from TM and copy the ImgSetup.exe to C:\Windows(I've also tried just the root of C:) and run it, it makes a registry entry in Run to run itself and that's it. The file remains. Now after deploying the image, the registry entry is still there, but the file dissappears? If I replace the file afterwards and either run it manually or reboot, it will properly execute the run command and run ImgSetup.exe which creates a new GUID for TMOS. Where can I put the file so that it doesn't dissappear after image deployment?

So, I changed the value in sysprep.inf to InstallFilesPath=C:\i386 and that didn't work. In fact, during the mini-setup, just out of curiosity I hit browse and took a look around, the first .nls file was actually in C:\Windows\system32, and there was no C:\i386 folder to be found.

I'm using it to deploy images across several computers in my home network.

Excellent info! Thanks! Guess I was right when I said I needed to read up on sysprep. EDIT - Actually..... I think this may have been fine. What if you've used NLite to remove the language components? Wouldn't you still get the same problem even if your path was correct?

Welp, added the missing .nls file and worked like a charm.... but now it's asking for a different file. EDIT - You know one thing comes to mind..... why is there even a distro in Sysprep? What does it need to install? Why is it even trying to install/use these files if you can just click cancel and it goes through just fine??? Guess I'll have to read up on Sysprep.

Awww... I like AMD.

windows-xp-sp2-x86-enu Tells me XP 32-Bit.

Not at all! I think your post was very well put together, much better then I can do for sure!!! I'm curious about a few of these things as well, since I don't want to spend hours updating/installing if I have to resort to an ISO instead of an image. The only thing I can answer for you is that there is a services tab inside of nLite that you can use to configure services. Just make sure you have the latest version. There is things that will integrate updates and such like WUP and WMP11 Integrator but I haven't had free time here at work to play around with those yet since the emphasis is images but I think it will help create one ISO with IE7, WMP11, and all updates after SP3. The IE7 is a biggie for me since it's one of the longer update downloads. I'm just starting to get wary because I know that implementing multiple programs to edit an installation file can get a little hairy.

I have the same issue, and "nLite is not to be used for corporate deployment" bla bla bla. Anyways, I looked up the extension, it seems to be a National Language Support File (font or font map). Did you remove the languages to slim down the ISO like I did? If so, maybe that's the issue. I think either on the nLite website or on the program itself it says something about removing the language packs may cause a misc issue. When I get a chance I'll rebuild the ISO without removing any languages and see if it's still a problem. If it is, I'll find this file and simply slap it into C:\sysprep\i386 ... it may have to go into $OEM$ like Cmdlines.txt.... I'm not sure.

Don't be scared, or you'll never learn We were all like you at one point or another. Actually, I came out of the womb creating universal images back in '79.

Play around with it and do some research like I did. You'll learn ALOT.

That's alright. I'll stick to DP and manually editing sysprep. WHen you say point 5, is this a set of rules listed on the forum or nlite's homepage?

OK, so Im running x86 but what difference does x64 do for me & how do I change. Did I say Im inexperienced with PCs????? X86 = 32 Bit X64 = 64 Bit That's why you may see some files that say something in the title like x86_32, you know that file is for a 32 bit operating system. The reason he brought up a 64 bit operating sytem is because I think with a 32 bit you can only access a total of... 3GB of RAM? To utilize the full four, and to better utilize multi-core processors, 64 is the way to go. However.... not all programs are written for 64 bit operating systems. It's getting better though. As for upgrading from 32 to 64...... I always have trouble with that topic, upgrading the OS in general actually. So I'm not going to comment on that area since I know very little about it, just enough to squeeze by the certification exam =D I'd recommend checking out the Microsoft website.

.NLS.... what does it stand for? I've tried looking in the driver folder I used, searched it with PSPad and it found nothing. A search on google for the extension definition showed me two things...... National Language Support and..... A Trojan So.... to those who have this issue, did you by chance remove all the language packs except English, like I did?

I know this seems probably silly, but as I've said before I'm new to this, as I've been assigned the project of creating a universal image for our Corporation. Right now I use DriverPacks to slipstream drivers into an installation, and right now I'm on the brink of having the universal image done now that I have a better understanding of how to tie in HDD controller drivers into the sysprep.inf. Now I'm in the process of making it cleaner. So, if I use nLite to slipstream drivers, how does it handle them? How are they installed and where are they kept on the HDD afterwards? In the windows\inf? I know I asked a similar question earlier, but how does it work for HDD controllers? If I use nLite to slipstream all the drivers and disk controllers, do I still have to run a sysprep and reseal before deploying the image?

OS: XP Pro Program: nLite 1.4.6(Now have 7) I just started over completely fresh and I still have the same problem. I created two extra admin accounts: ITAdmin and Testuser. ITAdmin had a password, Testuser did not. Both administrators, both checked Active. VMWare result: Only Testuser and Administrator is there; ITAdmin is nowhere to be found. The nhelper problem seemed to have went away though.

Excellent, so then I'd only need to refer sysprep to the windows\inf folder. Thanks for the info. Update, with your provided drivers I am finally able to get a single image working across every hardware platform I've tested so far in the corporation. Thank you sir. It seems so easy now, but man it was tough before... but I guess that's always the case when you're delving into things you have absolutely zero experience/knowledge of. =)

I have this error now using 1.4.6

I have the same issue too, and I used a fresh XP Pro w/SP3 slipstreamed. It only happens after perform the installation, directly after the XP splash screen I get that error exactly three times then everything's fine so I haven't worried about it. EDIT -- The wierd thing is the first couple versions I made of this didn't do it.... the only thing I remember changing is the boot option to enable ctrl-alt-del.... which by the way doesn't work but I'm too lazy to change it ;p Maybe I have an old version.

Fernando this seems like great information. One question though. Lets say I've already installed XP. Now I want to sysprep and image this PC for deployment across platforms with dissimilar hardware. If I slipstream these drivers into the installation, and perform the installation... will it keep the files in windows/inf or somewhere on the hard drive so that I can reference the image to search that location for the HDD controllers?