Tripredacus

All of the MSP changeovers I've had experience with didn't do a straight up "drop" like your post is implying. Any time a new MSP comes in, usually there is a period of time (1-3 weeks) where a transition is done to get one company out and another company in. This way they can learn about the customers environment without jumping right into it. This isn't so much a software question, so I'll put this in GD for now.

Could be related to this: <meta http-equiv="X-UA-Compatible" content="IE=edge" /> I can find mixed results of using the Edge value. Some have problems, some say its made for HTML5. From what I understand, using edge will force IE8 to use the IE8 renderer instead of the IE7 (Compatibility) renderer. Then again, I've also read that IE8 may totally ignore this value, so not sure if it is related.

Some programs, even if running in the background, can keep the screensaver from coming. Do you have a screensaver set to a time less than the sleep of the monitors?

When you say Windows Update, do you mean the website is in English? Also, if this notebook connected to the internet via a Swedish ISP?

You can also make a recovery partition with Ghost and Acronis.

If it is 0x3b, it is likely due to memory corruption of some sort. But that isn't much info you provided. There should be other Events listed under Application or System with more info. Is this BSOD reproduceable?

This seems less a Windows 7 issue and more of a network/server issue, since it is confirmed that allowing microsoft.com to not be authenticated will fix the problem, but your IT won't allow that. Have you tried allowing WDS to prestage all systems into a specific OU, then you can allow that group to access microsoft.com without authentication. Or even have these systems use a specific user account that has access through the proxy.

OK let me understand this. You are (basically) using your deployment server to be the proxy between the clients and the MS Activation Server? When you say you disable the firewall and it works, disable it on where, the client or the server?

The ports that Activation uses should already be allowed by the built-in firewall... as it uses IE to do the activation. http://support.microsoft.com/kb/291983

Did you already see this kb? http://support.microsoft.com/kb/921471

Not so far that we can tell, however the site that had done the (Ultimate) DVD install is notorious for not relaying problems back to us... I know they did not use the WDS to image it because I haven't put the NIC drivers in the boot.wim yet. We have another one coming in I can test again. I'll at least try deploying another (different) image to it.

How is your notebook set up to use this monitor? By saying that both are on, you can either be using an extended or cloned display. My notebook will turn its screen off as soon as I connect an external monitor to it, so the behaviour is different than in your case.

Since not all users see this I wonder about something. Are your AD profiles set to store display setting data? Do these users get the Classic or XP style when they log into an XP machine? Have you determined if these working users never log into an XP machine? See where I'm getting to?

Of course, I was expanding the topic a little. And I see you caught my typo IDK about that post on reboot.pro... I already ready from WMI in WinPE, but didn't know if it knew what a battery was. I'll have to test some to see if I can get some of the values that GSM posted.

USB Root Hub 3:07 - 3:12 (5 minutes) >>> [Setup online Device Install (Hardware initiated) - usb\root_hub20\4&133b7487&0] >>> Section start 2011/08/24 03:07:27.506 dvi: Searching for hardware ID(s): dvi: usb\root_hub20&vid8086&pid1c2d&rev0005 dvi: usb\root_hub20&vid8086&pid1c2d dvi: usb\root_hub20 dvi: HardwareID - USB\ROOT_HUB20 dvi: InfName - C:\windows\System32\DriverStore\FileRepository\usbport.inf_x86_neutral_f9abf85fd00186bd\usbport.inf ump: Server install process exited with code 0x000005b4 03:12:34.920 <<< Section end 2011/08/24 03:12:34.920 <<< [Exit status: FAILURE(0x000005b4)] Numeric Data Processor 3:07 - ( minutes) >>> [Setup online Device Install (Hardware initiated) - acpi\pnp0c04\4&e214901&0] >>> Section start 2011/08/24 03:07:35.212 dvi: HardwareID - *PNP0C04 ndv: Waiting for previous device install to complete. 03:07:35.586 ndv: Waiting for previous device install to complete. 03:08:35.600 ndv: Waiting for previous device install to complete. 03:09:35.613 ndv: Waiting for previous device install to complete. 03:10:35.626 ndv: Waiting for previous device install to complete. 03:11:35.640 ndv: Waiting for previous device install to complete. 03:12:35.653 ndv: Waiting for previous device install to complete. 03:13:35.666 ndv: Waiting for previous device install to complete. 03:14:35.680 ndv: Waiting for previous device install to complete. 03:15:35.693 ndv: Waiting for previous device install to complete. 03:16:35.706 ndv: Waiting for previous device install to complete. 03:17:35.720 ndv: Waiting for previous device install to complete. 03:18:35.733 ndv: Waiting for previous device install to complete. 03:19:35.746 ndv: Waiting for previous device install to complete. 03:20:35.759 ndv: Waiting for previous device install to complete. 03:21:35.773 ndv: Waiting for previous device install to complete. 03:22:35.786 ndv: Waiting for previous device install to complete. 03:23:35.799 ndv: Waiting for previous device install to complete. 03:24:35.813 ndv: Waiting for previous device install to complete. 03:25:35.826 ndv: Waiting for previous device install to complete. 03:26:35.839 ndv: Waiting for previous device install to complete. 03:27:35.853 ndv: Waiting for previous device install to complete. 03:28:35.866 ndv: Waiting for previous device install to complete. 03:29:35.879 ndv: Waiting for previous device install to complete. 03:30:35.892 ndv: Waiting for previous device install to complete. 03:31:35.906 ndv: Waiting for previous device install to complete. 03:32:35.919 ndv: Waiting for previous device install to complete. 03:33:35.932 ndv: Waiting for previous device install to complete. 03:34:35.946 ndv: Waiting for previous device install to complete. 03:35:35.959 ndv: Waiting for previous device install to complete. 03:36:35.972 ndv: Waiting for previous device install to complete. 03:37:35.986 ump: Server install process exited with code 0x000005b4 03:42:40.763 <<< Section end 2011/08/24 03:42:40.763 <<< [Exit status: FAILURE(0x000005b4)] There are a bunch of other "waiting for previous device install to complete" messages for other drivers, such as: Quite a few have that failure message as well. Setup.app.log doesn't show anything interesting. See attachment for full setupapi.dev.log (rar) setupapi.dev.rar

WHICH WinPE? jaclaz I wasn't specifically referring to the OP, but to As for WinPE, I'm thinking Win PE 3.0 x64.

I knew I was forgetting something. I'll have to shelve this project for now since they shipped the unit... I'll try to get a recreation done at another location, might take a few days tho.

Will WMI still detect a battery if it is not present in the system? We do not put batteries in until much later. Also, do you expect that WMI can find a battery from a WinPE?

I should have noticed where you were creating that .ini file. You didn't post the OS of the client. Vista, 7 and 2008 regard the root of the volume to be protected. As expected you seem to have run into a permissions issue. The reason why you didn't get any MsgBox about it may be due to what Local account VS was using to create the file.

Yes you can disable Driver Signature Enforcement. I have two notebooks that the "unsigned driver" screen comes up in 32bit. In 64bit the device does not even install, but we can't disable that option for our installs. So there is some manual steps for the techs to do for those two systems.

In your .cmd that launches in Audit Mode to run sysprep, just have it kill sysprep.exe process first before doing anything else.

Also, Outlook Express has been replaced by Windows Live Mail.

We're testing out a new bare-bone AIO PC that has an Intel DH61AG motherboard in it. After deploying Windows 7 Professional SP1 x86 on it, and during first boot, it was taking an extremely long time to install devices. The system seems fine otherwise, and the first boot after sysprep is normal. No drivers are missing in Device Manager either. I have confirmed the slowness in the setupact.log (snippet) Windeploy log from setupact.log in UnattendGC folder: There are no other logs for the relevant timeframe of 2011-08-24 03:07 to 06:18. Note: Date and time is incorrect due to the BIOS not being updated yet. And as such, this is a known working image on other hardware.

Ah, well there are (were) a bunch of different ways to run Quake in Win98. Besides WinQuake, GLQuake, (or the DOS version) and I'm thinking there was a Quake98 also.

I detect notebooks via checking the Model (or Manufacturer) in WMI, then compare against a list of supported model numbers in a text file that is on the server. If the model matches up (at this point it doesn't matter if its a notebook or desktop) it runs the appropriate commands for that model.