homeskillet

Open up Group Policy Management Console, drill down to the path listed under "Setting Path" and look for: Verbose vs normal status messages Setting Path: Computer Configuration/Administrative Templates/System Explanation Directs the system to display highly detailed status messages. If you enable this setting, the system displays status messages that reflect each step in the process of starting, shutting down, logging on, or logging off the system. This setting is designed for sophisticated users that require this information. Note: This setting is ignored if the "Remove Boot / Shutdown / Logon / Logoff status messages" setting is enabled. This tells the user EVERYTHING that is being processed before CTRL-ALT-DEL. Much more than the "classic" interface but the closest I've found to mimicing what XP did. Homeskillet

I have. It asked me to setup the Phishing Filter and such on the intro page. WMP 11 asked for what kind of setup I wanted to do, etc. Plus the other updates MU installed were on the Add/Remove Programs list. I'm going to try it again and post on Technet to see what they have to say. Any info I get I'll post here. Thanks again for the suggestions. Anthony

The only exclusion I have in customsettings.ini is: WUMU_ExcludeKB1=940157 (Windows Search). I have fired up the box, post sysprep, and ran IE and it's version 6. Same with WMP. Version 10. I checked the "Show updates" check box in Add/Remove Programs. Nothing other than the Client Side Extensions I am installing as an application showed up (as far as Windows Updates). Thanks for the suggestions... keep 'em coming! Anthony

Sorry to bump, but I could really use some ideas here!

The PC reboots twice in between the two Windows Update tasks and I forgot I do have 1 final reboot at the end of it all. The only other mod I did to the Task Sequence is put the install of Apps prior to any Windows Update tasks as I'm installing mulitple .net Frameworks and I want WU to patch them after the fact. So I take it sysprep does not uninstall Windows/Microsoft Updates for whatever reason, by design... If so, any ideas why my update dissappear before they get sent to a .wim file, or after that .wim file has been deployed to a box? EDIT: I ran Microsoft Update just before LTI would run Sysprep and noticed that it didn't install WGA during the Task Sequence. Could this be why before I waste the time in running sysprep again and find nothing has changed?

It does on it's own between the Windows Update (Pre-Application Installation) task and the (Post-Application Installation) task, but I have not setup a exclusive reboot task after the Post-App task. If that was the case (just needs a reboot), wouldn't the updates installed prior to the 1 automatic reboot that occurs on my system between the tasks still be there even if there was only 1 reboot in the whole Task Sequence? I understand the reboot would make sure the system files in use were writen, but I know there's at least 1 reboot occuring between those tasks, and no Updates remain after sysprep. Anthony

Hi all. I hope this is the right forum for this question and if it isn't, I apologise. Please move if necessary. I am using the MDT to create a Windows XP image. I have created my image and set the lite touch deployment to capture my image at the end of the process. Part of the process (the Task Sequence) prior to 'sysprep' went out and dl'ed updates from Microsoft Update. A check of Add/Remove programs verified that IE7, WMP11, and other updates were, in fact, installed. The process then syspreps the machine and I go ahead and 'capture' the image to upload to my WDS server. I get through all of that without issue. Then I blow the image from WDS back to the PC (after a format of the drive) and find everything is there that I originally installed EXCEPT IE7, WMP11, and all sorts of other updates that were there prior to sysprep. Does sysprep strip all Microsoft Updates out as part of it's process? I cannot find (and I've Googled the heck out of it) what exactly sysprep removes or if there is a switch that I was/wasn't using that caused this. The other question is if it isn't stripping them... what is? What would be the point of the Windows/Microsoft Update Task in the Task Sequences if the're going to be stripped out in the final product? Any ideas? Thanks. Anthony

An even easier solution to this issue (the Hotfix) would be to integrate RVM's Update Pack into your RIS image as it includes 888111. You'll need RogueSpear's AutoImage utility and the RVM Integrator/Update Pack to do so with RIS. I discovered this today that the Update Pack eliminated the need for the DetatchedProgram method as I was already covered by RVM's Pack. I just started using RVM's Update Pack a month or two ago the DetatchedProgram solution was a carry-over from how I did it previously... hence using 835221 in previous posts and not paying attention to what was included in the pack. If you're not interested in using the Update Pack, go with the DetatchedProgram fix mentioned before. Homeskillet

From ref.chm in the Deployment Tools. - DetatchedProgram indicates the path of the custom program that runs concurrently with the Setup program. The hotfix runs very quickly so it shouldn't slow down anything in Setup GUI mode. Funny you say that about 888111... I just realized that I'm using the two different versions while looking at some of my scripts today. Oops... 888111 should be fine to use. If not, I've had luck with 835221 on Dell equipment.

How about running the HDA Hotfix [KB835221] via DetatchedProgram? I realise this will install that hotfix on all of your machines, but it's quicker and cleaner than installing a driver on machines that don't have the particular piece of hardware. I install KB835221 to expose the Sound Card and Modem just before XP GUI Mode PnP Setup runs, then I throw the drivers at it via the OemPnPDriversPath. It's how I've been pulling it off lately. [unattended] OemPnPDriversPath = [path to modem drivers];[path to audio drivers] [GuiUnattended] DetachedProgram = "%systemdrive%\drivers\kb835221.exe" Arguments = /passive Homeskillet

Unfortunetly I don't have an answer to your question as I'm reading up on WDS now (we upgraded over the weekend). Do you think this means our RIS based 'flat' RISETUP images for XP are unusable in WDS except in Legacy or Mixed mode? I saw something in the help file about converting a RISETUP image to a WIM image, but I don't understand how that's helpful because they're two different types of images (RISETUP - flat, cd-based vs. WIM - glorified RIPREP?). It sounds like those that support Win XP get nothing out of WDS unless they want to create/support 12 different images for the different types of PC's we support. I apologize if this should have been a new thread. I'm going through similar issues with learning WDS and wanted to ask you what your thoughts were on this subject. Homeskillet

Hello all. I'm trying to run a Dell Notebook System Software setup program @ the T-39 stage of setup and I keep getting the error below: 16 bit MS-DOS Subsystem - C:\DOCUME~1\DEFAUL~1.WIN\APPLIC~1\SMBIOSSP.exe C:\WINDOWS\SYSTEM32\CONFIG.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application. My .sif looks like: [GuiUnattended] OemSkipWelcome = 1 OemSkipRegional = 1 DetachedProgram = "%systemdrive%\install\Applications\NSS\setup.exe" Arguments = "-S" TimeZone = 035 ... It appears that autoexec.nt and config.nt are not where they should be (%windir%\system32) for the NTVDM (?) to run during T-39, hence the error. Should they (autoexec.nt & config.nt) be available at the T-39 stage and if not, how does everyone else get programs like 7zip, etc. to run right @ T-39? I have an idea to place a autoexec.nt and config.nt in the %windir%\system32 directory just before I run the setup.exe program (via a batch file), but in my searches for T-39 events, I've found nothing needing to do all that for the NTVDM (?) to be available to run programs @ T-39. Does anybody have any idea what I can do here, or has anyone run into this problem? Thanks! Homeskillet

You have to shut off DEP before installing (I believe). There was a big discussion about it on the Adobe Audition Forum When you go to the link, click on "Log in as a Guest" to see the topic discussion. Read messages 5 - 13. Check it out, it may help you decide if you need to shut off DEP temporarily to get this bugger installed. Homeskillet

In the MS Office 2003 Custom Installation Wizard (Step 10), drill down to: Microsoft Office 2003 (user) --> Help --> Help | Privacy Settings... --> Enable Customer Experience Improvement Program and double click it. Select "Apply Changes" but DON'T select "Check to enable Customer Experience Improvement Program". Then click ok. That should do it.

Hey all. It just dawned on me that my registry tweaks that start with HKEY_CURRENT_USER are only being applied to the account I use to autologin ("admin" oddly enough... duh). Can you automatically change any reference from CURRENT_USER to LOCAL_MACHINE in a reg setting so the setting applies to anyone that logs into the PC (which is what I want with all of my reg settings on all the PC's)? I'm using RIS in a 7 person environment and I am currently installing everything under the "admin" account. Once the actual user logs in, they don't have half of the reg tweaks that admin has. Any ideas? Thanks.