Tripredacus

MDT is like a WAIK automation tool. WAIK is the bare essentials but is more a manual method. Having some knowledge of WAIK will make MDT easier to figure out, but it may not be required to learn them in that order.

You have to realise that the forum is not as active on the weekend, and notice the trend that it is most active during "business" hours. There is an option to hide the IE First Run screen altogether. Would that be helpful? Contact your ESET rep. They can provide you a version of their software installer that is designed to be installed in Audit Mode. This version will remain dormant and only because active once the appropriate registry settings indicate that the OS is no longer in Audit Mode and has completed OOBE. Since these systems are destined for use in a domain, you can specify these settings in your AD GPOs. For the visual effects, you can create a theme and specify it in the unattend. Ugg this. I am wondering why you are needlessly struggling with this at all. I can't speak for your volume or purchasing department, but you should be purchasing systems with Win7 Pro and then upgrading them to Enterprise. That way you just build an Enterprise deployment that uses MAK/KMS for activation instead of trying to reverse engineer Lenovo's image.

Good you got it fixed. I brought up the RAID question because I had similar problems on a server which would either have the screen go black or the system would turn off/reboot with no Event logs relating to the shutdown. In my case, it turned out I had both a failed RAID member AND a faulty port on the backplane. The end result after troubleshooting resulted in loss of all data! But anyways, I had just remembered that behaviour so figured I'd mention it.

I'm going to wager that you've never opened WMM before, since it is trying to install it. From these logs (there is one for wlsetup and one for a DLL) it looks like something is interfering with the installation. You main error is here: SQM :00000F8C (08/07/2011 20:56:03.892) Warning: Failed waiting for the SQM session data upload (hr=0x80070109). Unfortunately, I can't find any actual fix to that problem. So here is what I'll recommend. Uninstall and reinstall Windows Live. I can tell that the version of Live you are using was installed by Lenovo or whoever you bought your computer from. Before you try, you can try to just install WMM: http://explore.live.com/windows-live-movie-maker?os=other And here is where to download WL for 2011: http://explore.live.com/windows-live-essentials?os=other

post the driver package name or the download link so we can try. Some IS setups are flagged to not allow recording.

Log file doesn't say too much really. The log file you posted, was it this one? C:\Program Files (x86)\Common Files\Adobe\Installers\Add or Remove Adobe Creative Suite 3 Design Premium 1.0.log

I recommend using an answer file to enter Audit Mode, or to pass arguments to be done in Audit Mode.

MDT and WAIK work a little differently. Are you using MDT now?

Your PatrolPro program seems to be involved in Movie Maker. What is this program doing? What's in this folder? Any logs left? C:\Users\navigator\AppData\Local\Microsoft\WLSetup\Logs\

I don't recommend using the Ctrl+Shift+F3 to enter audit mode unless absolutely necessary. Best place to use it is at the Language selection page in OOBE.

Yes that should be fine. If it doesn't deploy the way you want, you may need to invoke setup using an answer file.

Is this system using any levels of RAID?

The next step would be to use ProcMon to get a trace. Add the processname for Windows Movie Maker (I don't know what it is called) to the Filter option. Open WMM, wait for it to close. Save the trace from ProcMon and upload it (zip of course)

Prince - Diamonds and Pearls

Also in Device Manager you can choose to view Hidden devices.

I have often found it annoying that DISM doesn't check the arch of the OS before injecting a driver. This is even true of a WinPE image, which has no WoW but DISM will still install a 32bit driver in there if you tell it to. Probably would happily inject Itanium drivers too. This all just leads to documenting what drivers are put in there. And if I have to do an update, need to look for the old ones, take them out, put new ones in. Oh well.

Topics like this make me wish I still had my Iomega binder... or at least remembered more about dealing with their drives. I remember the Clik! was not a big seller and probably received less than 10 calls on it ever. As such, I can't remember anything really specific about the drive. Heck, we didn't even get one in house to test, but we did get a disk. What was the point of that? Then again, maybe Utah was paying attention to the fact that we couldn't figure out how to break any of our drives or disks to replicate customer's problems... Maybe they just figured we didn't need it. PS: I still have a bunch of the tech disks with all the software.

Try going to this website: http://74.125.226.113/

Here are your chipset drivers to install: Chipset: INF Update Utility for 848, 865, 875, 910, 915, 925 Chipset-Based Intel Desktop Boards

Something is definately corrupted. The real error you got was "The service name is invalid" but the presence of those ASCII characters reveals there are larger problems on Windows that should be looked at, and hopefully after fixing them, Security Center will work again.

Normally you should connect your HDD to port 0. Windows doesn't report disk numbers based on ports. It reports them in the order that they are enumerated by the OS. There is an underlying order of priority for disk numbering, HDDs first, then ODDs then USB. However, in rare occasions some devices that connect through the HDD channel like card readers or even USB keys can be potentially detected as Disk 0. That behaviour normally happens in a WinPE since the boot volume is a RAMDISK. If Windows is booted from the HDD, it should also make that HDD Disk 0.

Open Task Manager, go to the Processes tab and sort by name. Try to open WMM as Administrator and see if the process shows up for a second or two and then closes. Then go into Event Viewer, under Application and look for any logs within that time frame relating to the program.

Hopefully when you get this all fixed up, we won't have to go and fix the recovery partition again.

First, the winpeoem.sif is for the old version of WinPE, v1.5 based on XP. You don't have a "device manager" per se, but you can see what drivers are in your boot.wim. In fact, you should use this to get those x64 drivers out before you put in the correct 32bit drivers. DISM /IMAGE:c:\winpe_x86\mount /GET-DRIVERS This will give you a list of the drivers you have installed, including the original filename and the new filename. Find your original filename, which will show the version too, and make note of the installed filename. You'd remove it like this: DISM /IMAGE:c:\winpe_x86\mount /REMOVE-DRIVER /DRIVER:oem22.inf Of course you already know how to add the drivers.

No definately not in WinPE.... But people could use this as a quick and easy way to install drivers in their unattends.