cluberti

1. Log in as a local administrator on the target system. 2. If possible, configure antivirus so it does not scan any of the files of subfolders of "%windir%\system32\wbem\repository". 3. Execute the following batch file to clear out the existing repository and autorecovery cache. %systemdrive% cd %windir%\system32\wbem sc config winmgmt start= disabled net stop winmgmt /y if exist repository.old rmdir /s/q repository.old rename repository repository.old if exist autorecover.old rmdir /s/q autorecover.old rename autorecover autorecover.old md autorecover 4. Export the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM" to a REG file for backup (i.e. WBEM_org.REG). Then Import the following REG file to set the WBEM logging level to verbose, increase the maximum log size to 5 MB, and clear out the autorecovery list. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM] "Logging"="2" "Log File Max Size"="5000000" "Autorecover MOFs"=hex(7):00,00 "Autorecover MOFs timestamp"="" 5. Execute the following batch file to rebuild the repository and autorecovery list. The duplicate lines are intentional. This batch file will take several minutes to complete. %systemdrive% cd %windir%\system32\wbem sc config winmgmt start= auto for /f %%s in ('dir /b *.mof *.mfl') do mofcomp %%s for /f %%s in ('dir /b *.mof *.mfl') do mofcomp %%s for /f %%s in ('dir /b *.mof *.mfl') do mofcomp %%s WINMGMT.EXE /REGSERVER WINMGMT.EXE /CLEARADAP WINMGMT.EXE /RESYNCPERF 6. Wait approx 15 minutes after running the above batch file to allow the performance counter resynchronization to complete. Then run WMIDIAG (cscript wmidiag.vbs) to establish a baseline report. 7. Execute the following batch file to clear out the WBEM logs. %systemdrive% cd %windir%\system32\wbem\logs del /Q *.*

I know RIS had the ability to store "tools" floppy images (I used this for hardware test boot disks, for example), but I don't think WDS has the same functionality.

Can you boot and login in safe mode? If so, I'd suggest reinstalling the latest IE cumulative update (http://support.microsoft.com/kb/939653) if you can, otherwise run sfc /scannow. If that doesn't work, or you can't even get in from safe mode, you'll have to do a repair installation.

Also correct!

You can make a WinPE Discover image, but that will have to run from CD or USB key - too big for a floppy.

Wow, that's kinda funny at 2AM - but I know I'm not gonna hire either of ya for any networking projects anytime soon .

I've got to second GTOOOOOH's sentiment - hardware independent images with anything prior to Vista is just not feasible. You can get close, yes, but never 100% independent. And the post is spot-on about applications and updates, too - unless you're imaging a base Windows install and post-installing all apps and updates, it really makes it hard to stay current. I don't do desktop deployment anymore for a variety of reasons, but when I did, I had a RIS server that could push out a base XP or 2000 OS, from a flat install source (not an image) and install and configure all apps in about 90 minutes a machine, from POST to ready-to-go. And if I wanted to update the image, I could re-write a script or replace an app on the RIS server or deployment point and never have to touch much to keep things updated. I wish you luck if you go the image route - 2 weeks is pretty unrealistic.

The processor detected a hardware error somewhere in the machine, and Windows logs this event whenever it occurs. The hardware diagnostic tools (like MCAT) will tell you more... OK, so you've either got a bad processor on slot 0, or bad RAM in the box. Have the hardware vendor run a diagnostic check, because this could very well be a bad processor (almost all MCE are).

Silly question, but have you tried it in a different outlet? Also, if it powers up and down again, I'm quite certain your power supply is fine - this sounds more like thermal protection in the BIOS powering the box off (without warning, as it does). You sure your processor and heat sink are OK?

CompUSA died, at least in my opinion, due to the fact that they couldn't really appeal to the "general public" who know nothing about computers - partly because the staff knew less than the customers in most cases, and partly because they never had anything new or really gotta-have-it in the store, and when they did, it was more expensive than CC and BestBuy. And, most self-respecting geeks buy most everything online, shopping at chains like that for the basics (blank CDs/floppies, emergency supplies, etc) - that isn't gonna make you money, ever.

You could simply have a vbs that runs constantly from logon that checks for share availability and sleeps, and when one comes active (hence machine has network connectivity and is on the local LAN), run gpupdate and map network drives...

Is it always "provider load failure"? Have you considered running process monitor from sysinternals while launching the app to see which provider load failed, and perhaps why?

XP and 2003 can support up to 10 displays (not sure about Vista yet), so theoretically you could have 10 single output cards, or 5 dual output cards, or a few multiple output cards in a box (as long as it's not Vista, they don't have to match drivers either). If you've got PCI-X slots in that server, consider something like the Nvidia Quadro NVS line (they have models, like the 440, that come with 2 RAMDACs and can drive 4 displays via dual DMS-59 ports on the card). If you've only got PCI slots, consider 2 NVS 280s instead.

Run process monitor when you try to browse to http://www.msfn.org, and see what happens with either "Not Found" or "Access Denied". It sounds like there is some sort of mime handler issue - do other www.<whatever>.org sites work in IE?

Autoit was made for this type of issue.

Have you read this? It might give you some clues as to why it's not working. Has it ever worked before, and can you try it on another XP or Vista machine?

If you remove it temporarily, does the problem persist, or does the boot time improve?

No, the burn utility in Vista is only for writing files to the disc as-is, it cannot create bootable .iso's. You will have to use another utility to do this.

That is correct - it should slipstream just fine into an RTM source (and technically, that is recommended), but installing into a running box requires (at least right now) that the box be running SP1.

I'm not sure you'll find an integrated RDP manager that also does SSH clients without using mRemote, as that's the only one I'm aware of. I use SmartCode VNC manager to manage my RDP and VNC connections, and it also works on my Virtual Server machines as well - but it doesn't do SSH. I use PuTTY for SSH management, and that works fine for me, but nothing integrated to do both other than mRemote (and I don't use that for the same reasons you give for wanting to use something else - it's still buggy, and lacks features).

To install a MUI language pack, you need to be running Business, Enterprise, or Ultimate.

Why would Administrators need anything other than read access to this key? You should only be adding things here if you specifically need to lock down the CA chain for your users, and even then, you can (and should) start regedit from a command prompt running as the SYSTEM account anyway.

Depends on what you're doing with it - the SCSI controller and drives support things like NCQ and out-of-order execution, whereas (most) SATA controllers nor disk drives do not. If you're just talking about day-to-day workloads, SATA is cheaper and will give similar performance. If you're talking about disk-intensive work, SCSI will be faster.

If you aren't doing anything crazy like ABE with the file server, almost anything made in the last 10 years should work just fine. Disk speed and network speed will matter far more than CPU horsepower.

// The thread that was "freezing" XP - note that before you caused the bugcheck, // this thread had been trying to acquire a spinlock for almost 15 seconds... 1: kd> !thread 89c0bda8 THREAD 89c0bda8 Cid 0004.003c Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 1 IRP List: 86497e00: (0006,01fc) Flags: 00000070 Mdl: 00000000 Not impersonating DeviceMap e10020f0 Owning Process 89c0e660 Image: System Wait Start TickCount 141908 Ticks: 934 (0:00:00:14.593) Context Switch Count 8546 UserTime 00:00:00.000 KernelTime 00:00:14.781 Start Address nt!ExpWorkerThread (0x804e22f1) Stack Init f78e3000 Current f78e2d24 Base f78e3000 Limit f78e0000 Call 0 Priority 12 BasePriority 12 PriorityDecrement 0 DecrementCount 0 *** ERROR: Module load completed but symbols could not be loaded for sptd.sys *** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys *** ERROR: Module load completed but symbols could not be loaded for ezplay.sys ChildEBP RetAddr Args to Child f78e280c f75697fa 000000e2 00000000 00000000 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo]) f78e2828 f7569032 0009a0d8 01dc00c6 00000000 i8042prt!I8xProcessCrashDump+0x237 (FPO: [Non-Fpo]) f78e2870 804db90f 888a4e18 8909a020 01010009 i8042prt!I8042KeyboardInterruptService+0x21c (FPO: [Non-Fpo]) f78e2870 806ff85e 888a4e18 8909a020 01010009 nt!KiInterruptDispatch+0x45 (FPO: [0,2] TrapFrame @ f78e2894) f78e29d0 804e13d9 88e4d638 88c37b08 89111190 hal!KfAcquireSpinLock+0x2e (FPO: [0,0,0]) f78e2a6c 8050c76d f78e2dcc f73b7252 f73b7560 nt!IopfCallDriver+0x31 (FPO: [0,0,0]) f78e291c f739dd73 89bab420 8910e008 89111190 nt!IoGetDriverObjectExtension+0x33 (FPO: [Non-Fpo]) WARNING: Stack unwind information not available. Following frames may be wrong. f78e29a0 804f39b1 0000000f 88c37b08 64747053 sptd+0x21d73 f78e29c0 8908e200 8908e008 f78e29d0 00000000 nt!ExAllocatePoolWithTagPriority+0x58 (FPO: [Non-Fpo]) f78e2a6c 8050c76d f78e2dcc f73b7252 f73b7560 0x8908e200 f78e2a84 f739ebcb 88c240e0 20f31678 00000000 nt!IoGetDriverObjectExtension+0x33 (FPO: [Non-Fpo]) f78e2b10 804e13d9 88e4d638 86497e00 86497e00 sptd+0x22bcb f78e2b20 f7718115 86497edc f771803a 88ceddb0 nt!IopfCallDriver+0x31 (FPO: [0,0,0]) f78e2b48 f77172e1 88ceddb0 86497e00 86497ef8 PxHelp20+0x1115 f78e2bf4 f759b6ef 88d28b50 86497e00 86497e00 PxHelp20+0x2e1 f78e2c88 f74e847f 88d28b50 86497e00 88e7d310 cdrom!CdRomDeviceControlDispatch+0x4b7 (FPO: [Non-Fpo]) f78e2ca4 804e13d9 88d28b50 86497e00 89107518 CLASSPNP!ClassDeviceControlDispatch+0x48 (FPO: [Non-Fpo]) f78e2cb4 f75a7a35 f78e2d00 f75a8c28 88d2fc60 nt!IopfCallDriver+0x31 (FPO: [0,0,0]) f78e2cbc f75a8c28 88d2fc60 86497e00 00000000 redbook!RedBookSendToNextDriver+0x35 (FPO: [Non-Fpo]) f78e2d00 804e13d9 88d2fc60 86497e00 e24a4508 redbook!RedBookDeviceControl+0x548 (FPO: [Non-Fpo]) f78e2d10 f6ac662e 88e650d0 88e7d310 88e65018 nt!IopfCallDriver+0x31 (FPO: [0,0,0]) f78e2d40 f6ad601e 88e7d310 f78e2d73 f78e2d77 ezplay+0x562e f78e2d68 8056d03c 88e65018 88e7d310 805694fc ezplay+0x1501e f78e2d7c 804e23b5 86643b58 00000000 89c0bda8 nt!IopProcessWorkItem+0x13 (FPO: [Non-Fpo]) f78e2dac 80574128 86643b58 00000000 00000000 nt!ExpWorkerThread+0xef (FPO: [Non-Fpo]) f78e2ddc 804ec781 804e22f1 00000001 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo]) 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 // sptd.sys has this IRP as one of it's parameters, and it's the IRP we're working // on in this thread at the time of the freeze/hang: 1: kd> !irp 86497e00 Irp is active with 5 stacks 4 is current (= 0x86497edc) No Mdl: System buffer=86f31678: Thread 89c0bda8: Irp stack trace. Pending has been returned cmd flg cl Device File Completion-Context [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000004 00000000 86ff8568 00000000 >[ e, 1] 0 0 88e4d638 00000000 f759a6cc-8662a740 \Driver\aixpwfa2 cdrom!CdRomClassIoctlCompletion Args: 0000004c 0000004c 0004d014 00000000 [ e, 0] 0 0 88d28b50 00000000 00000000-00000000 \Driver\Cdrom Args: 0000004c 0000004c 0004d014 00000000 // The driver we're in at the time, looks like your CD ROM driver? 1: kd> lmvm aixpwfa2 start end module name f6b40000 f6ba6000 aixpwfa2 (no symbols) Loaded symbol image file: aixpwfa2.SYS Image path: \SystemRoot\System32\Drivers\aixpwfa2.SYS Image name: aixpwfa2.SYS Timestamp: Mon Jun 04 01:12:12 2007 (46639F2C) CheckSum: 0005673F ImageSize: 00066000 Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0 // I think this is the culprit though - if you uninstall Daemon Tools and // the SCSI Pass-Through filter Driver it installs, I think your problems // will go away: 1: kd> lmvm sptd start end module name f737c000 f7466000 sptd (no symbols) Loaded symbol image file: sptd.sys Image path: sptd.sys Image name: sptd.sys Timestamp: Mon Jun 18 17:13:19 2007 (4676F56F) CheckSum: 000A7CF2 ImageSize: 000EA000 Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0