newuzer

Member
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About newuzer

  1. This is a very old topic, but not really solved. I ran into the same msobshel.htm problem and was able to reproduce it. In my case, It's caused by creating the unattended source (including the integration of hotfixes) on a mounted network share. If I use a local harddisk, the problem is gone. NU.
  2. FYI In order to be able to mount images in your PE environment, you need to install the wim filter. I achieved this by adding this line to startnet.cmd. %SystemRoot%\System32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 X:\windows\wimfltr.inf note: wimfltr.sys needs to be in the same folder as winfltr.inf.
  3. I got the "Windows Server 2008 Enterprise (Full Installation)" option to work unattended with this <InstallFrom> section added to my XML file: <ImageInstall> <OSImage> <InstallFrom> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <Value>Windows Longhorn SERVERENTERPRISE</Value> </MetaData> </InstallFrom> </OSImage> </ImageInstall> The "Windows Longhorn SERVERENTERPRISE" value is the same value WAIK created at the bottom of the unattended.xml file: <cpi:offlineImage cpi:source="wim:<path>/install.wim#Windows Longhorn SERVERENTERPRISE" xmln s:cpi="urn:schemas-microsoft-com:cpi" /> Hope it helps.
  4. Already found the answer. config.xml should include: <Configuration Product="Enterprise"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <Setting Id="SETUP_REBOOT" Value="Never" /> </Configuration>
  5. If I unattended try to uninstall Office 2007 Enterprise, it always reboots after completion. I've tried the following: msiexec.exe /X{90120000-0030-0000-0000-0000000FF1CE} /quiet /passive /norestart /qb-! and: setup.exe /uninstall enterprise /config config.xml where config.xml includes: <Configuration Product="Enterprise"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <Setting Id="Reboot" Value="ReallySuppress" /> </Configuration> Any ideas on how to prevent that from happening?
  6. I'm experiencing the same problems, when using untrusted user accounts. As soon as I let nLite 1.3.5 integrate drivers into the source, any USB device moved or inserted will end up prompting the "Found New Hardware" dialog. However, If I integrate the drivers otherwise (e.g. using setupcopyoeminf.exe at T-39), all is fine. I Started with a clean Windows XP source and let nLite do the following in one run: - SP2 integration - post-SP2 security hotfixes and KB888111 integration ...and yes, the advanced option to remove the catalog files is not enabled. - multiple drivers integration What can be causing this behavior?