cluberti

Actually, the last time I saw this problem it was the ATI drivers and winlogon hooks causing the problem. Enable process and login auditing on the domain for your workstations, and when it happens go back to the security logs to trace it back.

Exactly.You could consider 2008 x64 and use a bunch of Hyper-V VMs if the coldfusion apps can run across multiple IIS web servers...

The latest IE cumulative security update was MS08-031. If the updates that you downloaded are included in that update, then you only need to install the cumulative. If the patches are for issues NOT included in that rollup, then you need the rollup + those extra patches. I'm pretty sure the patches you have for IE7 are included in MS08-031, as I don't think there are any public IE patches since June.

IIS is not technically able to use anything other than the 2GB (or 3GB with /3GB in boot.ini) VA per w3wp worker. However, if the coldfusion apps running within the w3wp process are AWE aware, then they should be able to map in a window to use the AWE memory above 4GB. However, IIS itself (and thus the w3wp.exe pools) are not AWE-aware. Technically running an Enterprise 2003 box with /PAE will allow better memory utilization, it won't fix your problem if I understand what you are saying correctly. You'd probably be better off running x64 2003 and trying to get the coldfusion apps to work (I'm assuming this is not Coldfusion 8.x?).

No, that's what VMs are for .

MacBook Pro running Vista SP1.

Good luck, and keep coming back for help if needed. Impart knowledge too, if you can - keep MSFN the best Windows board there is (well, I'm biased ).

What did you use to image it? At this point, it might be best to convert it to a VM and run it on VMWare or Virtual Server (or hyper-v, as the case may be) to get it off that hardware, if it's not got the disk space you need. It'll be easier (much) to use something like VMWare converter and put it in a VM you can resize.

Does it repro immediately after install? If the answer is yes (without installing any additional drivers or software), it would be great to see a procmon of the file copy, and perhaps even hang dumps of explorer at intervals to see what the heck it's (not) doing.

The only really good documentation on system restore registry keys/values from Microsoft are here. As to what the script does, it's using the WMI namespace to access the SystemRestore classes and modify the running service via the API calls. You don't (easily) do this via the registry in XP without risking hosing the whole box, and in Vista forget it. Stick to WMI - good tool to learn to use, too.

You can find your answers if you search.

No, it's not case-sensitive.

Have you been able to successfully load Vista SP1 from original media? Hard to say without knowing if it does the same thing after Vista images from the DVD are copied down and the same steps are run after that.

Depending on your requirements, FOG might be a valid option too.

I have to agree. Intel really didn't seem to care much about the low-end desktop and even mobile CPU market (mobile P4 anyone? blech) until AMD started pushing them around with good product. Intel fought back with pretty good products that were technically equivalent to their AMD counterparts, and with their heft they fought AMD off really well. If AMD becomes a non-competitor, I loathe to think what will happen to the non-server CPU market again. If history repeats itself, Intel will suck again. (...and maybe AMD sticks it out and repeat that history too? who knows...) It'd be too bad too, AMD makes pretty good products.

I don't really see a question in the previous (non-bump) post. What question exactly are you bumping?

Well, it might be better for you and your techs to make factory images, that way you get a shot at installing drivers and software before the reseal - you could bring the image down, have a tech install the sound card drivers (and any other drivers that don't inject properly), then reseal the box. Also, when you run your generalize pass, are you using the PersistentAllDeviceInstalls setting in the Microsoft-Windows-PnPSysprep section of your sysprep.inf? This is supposed to keep the device drivers from being whacked during the sysprep (regardless of whether or not it actually works with your drivers/software). Maybe you have. In any case, in what you are seeing, a factory build is probably best for these machines and your techs.

What about dosbox for this? NTVDM isn't really meant as anything but a stopgap solution...

Apparently yes .

I would suggest installing XP into this same VPC machine (start clean XP install, format existing virtual disk from XP setup, install, try networking) to see if it's the VPC or the nLite'd XP causing the issue.

From the forum rules you were supposed to read before posting: Since you are new, I will ask you - from where did you download "someone's" unattended XP? It wasn't Microsoft. Do not ask further questions about this XP copy. Use your own, or use none at all.

http://download.zonealarm.com/bin/free/pre...ccessIssue.html

I have to second softgrid (Application Virtualization) as a potential replacement. I almost forgot about that.

Yes, I've been using hyper-V VMs to build my Vista images, and then injecting drivers to the WIM post-sysprep to solve this very problem with Realtek drivers. They don't survive sysprep, but work fine if injected afterwards.

It sounds more like DNS and/or AD is busted on that certsrv box, not IIS...