Tigrao

mdemel, I did the same fixes that you are talking about in the wbemoc.inf file. This seems to break RSoP (Resultant Set of Policies) and maybe some WMI stuff on my installs that I have tried. You probably turn off the Windows Security Center, though. I cannot do this in my situation. Do you not get errors in the event log similar to the following? The Windows Security Center Service was unable to establish event queries with WMI to monitor third party AntiVirus and Firewall. Source: SecurityCenter Event ID: 1802 Windows couldn't log the RSoP (Resultant Set of Policies) session status. An attempt to connect to WMI failed. No more RSoP logging will be done for this application of policy. Source: Userenv Event ID: 1090 I need WMI and RSoP to work in my situation. Can you check and see if you get errors like this?

I take that back. I did some further tests and winnt32.exe installs do work for me after using nLite to slipstream. There are no modifications done to the Windows source. You are correct. I apologize for making incorrect accusations. What I had done was integrate one driver after slipstreaming. I integrated the Intel Matrix Storage Manger driver so that I could install on a Dell Optiplex 755 system that was configured in a RAID 0. So, when you integrate one driver nLite makes the modifications to the wbemoc.in_ and txtsetup.sif files, etc. This is the point when the install becomes broken. Nuhi, nLite is an awesome product. I appreciate the efforts that you have made and I know that you have had countless late nights and have put in so much hard work which mostly goes unnoticed. Thank you for your efforts!

Well, as rogergh said, simply slipstreaming SP3 onto a Windows XP source with nLite causes the installation to fail when using winnt32.exe. This is not fixed with 1.4.6. I do find that nLite has modified the txtsetup.sif and wbemoc.inf files simply by doing a Service Pack slipstream and nothing else. After doing the slipstream the files show: ; customized by nLite - www.nliteos.com So there is some modification going on, thus this is why winnt32.exe installs are failing.

Well, nLite still shouldn't touch anything unless I am, for example, integrating IE7. I still don't see a reason for it to touch anything if you are simply slipstreaming a service pack. If I was slipstreaming AND adding add-on packs and cutting out system services then I would understand why nLite would need to modify other Windows source files.

No... I guess that missed that part of the license agreement. Time to find another solution.

I have been struggling ever since Windows XP SP3 came out. I am the network admin at a fairly large company. We roll out new Windows installs on a daily basis. We use Microsoft's Business Desktop Deployment to install via a PE environment. An entire system with updates and applications installed can be finished in about 20 minutes this way. I have always used nLite to facilitate this process. However, we have hit a huge wall now. Microsoft's solution does not provide a simple way to integrate drivers into the Windows source files, so I use nLite. However, as has been confirmed by the numerous posts here, if nLite touches a Windows XP SP3 source any winnt32.exe based installs are severely broken. I have tried the numerous workarounds changing the txtsetup.sif and wbemoc.inf files. I did manage to get a system installed that seemed normal. However, there are still system log entries with WMI errors. And as a perfect example the system can no longer detect if AntiVirus software is installed. Here are a couple of the event log errors: The Windows Security Center Service was unable to establish event queries with WMI to monitor third party AntiVirus and Firewall. Source: SecurityCenter Event ID: 1802 Windows couldn't log the RSoP (Resultant Set of Policies) session status. An attempt to connect to WMI failed. No more RSoP logging will be done for this application of policy. Source: Userenv Event ID: 1090 All that I need to be able to do is integrate a few SATA and RAID drivers into my Windows source files. Does anyone have any suggestions as to something else I could do to integrate drivers?

I don't understand why nLite changes anything at all in the Windows source files when simply slipstreaming a service pack. Why can't it just run the Service Pack's /integrate switch? Does it need to make modifications to inf files or sif files at all? What is the purpose of this behavior?