cluberti

Since the error isn't really an error (0xf201 means "STATUS_READY_TO_INSTALL", might be DCOM permissions: 1. Change DCOM default security - Open Dcomcnfg - Click on the Default Security tab - Click "Edit" on "Default Access Permissions" - Add the Administrators group, Allow Access 2. Check DCOM communication - Open Dcomcnfg - Click on the Default Properties tab - In the "Default Distributed COM communication Properties" section: Default Authentication Level should be set to "Connect". Default Impersonation Level should be set to "Identify". Apply the changes and reboot the machine, and update.exe should work again.

You may be able to use WinPE and some winnt32 switches to make it work (not tested, but worth trying) - switches like /makelocalsource and /tempdrive. There is a KB article on this, but it's somewhat involved: http://support.microsoft.com/kb/830577

The LANG folder contains non-English languages (like Chinese, Arabic, Korean, etc). If you don't plan on using those, you can delete the LANG folder.

Wininstall LE is freeware that will repackage an .exe to .msi - it's basic (just takes a before/after snapshot), but good for all basic to moderately complex installations: http://www.ondemandsoftware.com/PurchaseLE.asp As to the actual motions of pushing out software via a GPO, the following article is a good primer on how to do it: http://www.windowsnetworking.com/articles_...plications.html I would obviously suggest strongly that you do neither of these things in production first, but in a test environment until you get it right.

A year and a half late is rushed? lol

Also, each framework installs to it's own directory location, so installing all three (1.1, 2.0, 3.0) makes all three available on a machine. They do not overwrite or upgrade each other.

Second vote for CutePDF via GhostScript (CutePDF printer driver that converts any document to .pdf)

What bugs are you waiting on, specifically?

I do know that StarForce drivers can cause erratic behavior in the SCSI pass-through interface, so removing those is always a good idea. Let me know how it goes this week .

Well, we shall see. With Vista being RTM'ed, it is likely that XP will hit extended support shortly after SP3, making it possibly the last SP for XP.

This is occuring due to a change in the iernonce.dll file. You can still launch the RunOnceEx process by copying the IE6 version of the iernonce.dll file into any location and executing the runonceex command using it, but IE7's iernonce.dll file is the culprit. Not sure if it's by design or an unintended consequence, but that's the long and short of it.

You know, after looking at my post, I realize that I probably shouldn't be answering that. What I will say is that it is very, very wise to adprep before adding LH DCs to your existing AD.

How are you installing the Cisco VPN client package, and is there any particular reason you are not using Windows Installer v3.1? It sounds like the error is giving you the reason it is failing, we just don't know what cli parameters it's passing to msiexec - perhaps you could get the actual .msi package if you've only got the installshield/wise/someother3rdpartypackage package and install it yourself with a simple "msiexec /i <.msipackagename>" command to see if that works?

I'm not sure about export, but the file itself is just a .pbk file in the user's profile. You could also use the CMAK on Windows Server to create a new profile and installer (that's probably a better option, btw).

You add your Longhorn server to the domain after running the updated adprep command on the LH CD. After that, you can add LH DCs to your existing TEST domains running downlevel versions of AD, and they function similarly to 2000 or 2003 DCs. There are new features, so read the help and support docs in LH once you've goten this far and they'll give you an idea of how best to integrate LH into your existing AD, and perhaps migrate forward when the time comes.

You'll have to wait, as fizban has said. If there's a localized version of a package, you can always download that - however, since Vista is language-neutral (and development of Vista apps are encouraged to be such as well), waiting for an upgrade may take some time if it's an established app or was build to run on pre-Vista OSes (which most apps are).

I think the only sure-fire way to secure internet access in this manner is to have a proxy installed on your network, whether that be a home router device from Linksys/Netgear/DLink/whatever, or a linux box running proxy or firewall software. Remove the controls for internet access from the Windows machine on to something that only you control and have access to, and you'll find it's not so easy for most people (children or otherwise) to bypass off-box restrictions.

I'm not particularly familiar with that virus, but I can tell you that common best practice when you are infected with any recurrent virus is to back up your data to a read-only medium (cd or dvd) if possible, then format and reinstall the OS. Otherwise, the typical steps would apply if you're against reinstallation - spybot, hijackthis, adaware, windows defender, an online virus scan (or two, or three), etc. And you must at least file away in the back of your mind whilst doing this that you still might not get clean without a reinstall...

Windows Service Pack Roadmap: http://www.microsoft.com/windows/lifecycle/servicepacks.mspx

Thanks for enabling special pool - you can safely disable that now. Here's the analysis, now that I can see pool: CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. Arguments: Arg1: 00000003, Process Arg2: 86534140, Terminating object Arg3: 865342a4, Process image file name Arg4: 8095aa0e, Explanatory message (ascii) Debugging Details: ------------------ PROCESS_OBJECT: 86534140 IMAGE_NAME: csrss.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: csrss FAULTING_MODULE: 00000000 PROCESS_NAME: csrss.exe EXCEPTION_RECORD: f70b6d10 -- (.exr 0xfffffffff70b6d10) ExceptionAddress: 7c81555f ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 7f00700c Attempt to read from address 7f00700c EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". READ_ADDRESS: 7f00700c BUGCHECK_STR: 0xF4_C0000005 !THREAD 85f5a7a0 Cid 0424.042c Teb: 7ffda000 Win32Thread: e1717ea8 WAIT: (Executive) KernelMode Non-Alertable f7197560 Mutant - owning thread 86778518 Impersonation token: e31bc030 (Level Impersonation) DeviceMap e26729d8 Owning Process 86534140 Image: csrss.exe Wait Start TickCount 2835 Ticks: 0 Context Switch Count 786 LargeStack UserTime 00:00:00.062 KernelTime 00:00:00.015 Win32 Start Address 0x00001a0d LPC Server thread working on message Id 1a0d Start Address 0x75a548d8 Stack Init f7597000 Current f759649c Base f7597000 Limit f7594000 Call 0 Priority 14 BasePriority 13 PriorityDecrement 0 ChildEBP RetAddr Args to Child f75964b4 80820128 85f5a7a0 85f5a848 00006101 nt!KiSwapContext+0x25 (FPO: [Uses EBP] [0,0,4]) f75964cc 8081f9de e25583b8 e25583b8 00000000 nt!KiSwapThread+0x83 (FPO: [Non-Fpo]) (CONV: fastcall) f7596510 f71a9224 f7197560 00000000 00000000 nt!KeWaitForSingleObject+0x2e0 (FPO: [Non-Fpo]) (CONV: stdcall) f759653c f71ad605 e25583b8 00000000 00000000 Ntfs!NtfsDeleteInternalAttributeStream+0x3f (FPO: [Non-Fpo]) (CONV: stdcall) f7596558 f717b64d f75967e0 e25583b8 f7596700 Ntfs!NtfsRemoveScb+0x77 (FPO: [Non-Fpo]) (CONV: stdcall) f7596574 f71ab2b5 f75967e0 e25582f0 00000000 Ntfs!NtfsPrepareFcbForRemoval+0x52 (FPO: [Non-Fpo]) (CONV: stdcall) f75965bc f71ab0b4 f75967e0 e25582f0 00000000 Ntfs!NtfsTeardownStructures+0x62 (FPO: [Non-Fpo]) (CONV: stdcall) f75965d8 f71afa3e 0194c400 00000000 dbc4c500 Ntfs!NtfsCommonCreate+0x18a4 (FPO: [SEH]) (CONV: stdcall) f75967c0 f71aac90 f75967e0 854eb008 f7596908 Ntfs!NtfsCommonCreate+0x143b (FPO: [Non-Fpo]) (CONV: stdcall) f759698c f725ed90 854eb008 f7596bfc 866f1020 Ntfs!NtfsNetworkOpenCreate+0x96 (FPO: [Non-Fpo]) (CONV: stdcall) f75969ac f726cabd 000000f2 00000000 f75969e4 fltMgr!FltpPerformFastIoCall+0x300 (FPO: [Non-Fpo]) (CONV: stdcall) f7596a04 8090f0fc 854eb008 f7596bfc 86734b78 fltMgr!FltpFastIoQueryOpen+0xa1 (FPO: [Non-Fpo]) (CONV: stdcall) f7596af8 80902fad 86736030 00000000 8654db30 nt!IopParseDevice+0x917 (FPO: [Non-Fpo]) (CONV: stdcall) f7596b78 80906a15 00000000 f7596bb8 00000040 nt!ObpLookupObjectName+0x5a9 (FPO: [Non-Fpo]) (CONV: stdcall) f7596bcc 809265cd 00000000 00000000 ffffff01 nt!ObOpenObjectByName+0xea (FPO: [Non-Fpo]) (CONV: stdcall) f7596d54 8082337b 0068f640 0068f608 0068f670 nt!NtQueryFullAttributesFile+0x152 (FPO: [Non-Fpo]) (CONV: stdcall) f7596d54 7c82ed54 0068f640 0068f608 0068f670 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f7596d64) WARNING: Frame IP not in any known module. Following frames may be wrong. 0068f670 00000000 00000000 00000000 00000000 0x7c82ed54 !PROCESS 86534140 SessionId: 0 Cid: 0424 Peb: 7f007000 ParentCid: 039c DirBase: 3176d000 ObjectTable: e191fca0 HandleCount: 448. Image: csrss.exe dt nt!_KMUTANT f7197560 +0x000 Header : _DISPATCHER_HEADER +0x010 MutantListEntry : _LIST_ENTRY [ 0x86778528 - 0x86778528 ] +0x018 OwnerThread : 0x86778518 _KTHREAD +0x01c Abandoned : 0 '' +0x01d ApcDisable : 0 '' This thread 85f5a7a0 is waiting on KMUTANT !mu f7197560 !THREAD 86778518 Cid 054c.043c Teb: 7ffdf000 Win32Thread: e2fbd808 READY Not impersonating DeviceMap e26729d8 Owning Process 8658d4b8 Image: utorrent.exe Wait Start TickCount 2835 Ticks: 0 Context Switch Count 265 LargeStack UserTime 00:00:00.015 KernelTime 00:00:00.000 Win32 Start Address 0x00401000 Start Address 0x77e6b5ff Stack Init ba578000 Current ba577648 Base ba578000 Limit ba573000 Call 0 Priority 8 BasePriority 8 PriorityDecrement 0 ChildEBP RetAddr Args to Child ba577660 80820128 86778518 867785c0 00000101 nt!KiSwapContext+0x25 (FPO: [Uses EBP] [0,0,4]) ba577678 8081f9de 00000000 00000000 e3192a28 nt!KiSwapThread+0x83 (FPO: [Non-Fpo]) (CONV: fastcall) ba5776bc f71bfcf9 f7197560 00000000 00000000 nt!KeWaitForSingleObject+0x2e0 (FPO: [Non-Fpo]) (CONV: stdcall) ba577728 f71ad831 ba577b1c e3192a28 00000001 Ntfs!NtfsCreateInternalStreamCommon+0x53 (FPO: [Non-Fpo]) (CONV: stdcall) ba577750 f71b1304 ba577b1c e3192a28 00000004 Ntfs!ReadIndexBuffer+0x26 (FPO: [Non-Fpo]) (CONV: stdcall) ba577780 f71ac4dc ba577b1c e1565068 e31d71e0 Ntfs!FindFirstIndexEntry+0x196 (FPO: [Non-Fpo]) (CONV: stdcall) ba5778a8 f71aab06 ba577b1c e3192bb8 e3192a28 Ntfs!NtfsRestartIndexEnumeration+0x6c (FPO: [Non-Fpo]) (CONV: stdcall) ba577acc f71ac180 ba577b1c 85306750 86412368 Ntfs!NtfsQueryDirectory+0x54c (FPO: [Non-Fpo]) (CONV: stdcall) ba577b00 f71ac452 ba577b1c e3192a28 85f6a8d8 Ntfs!NtfsCommonDirectoryControl+0xbc (FPO: [Non-Fpo]) (CONV: stdcall) ba577c70 f73a9aea 86412288 85306750 85f6a8d8 Ntfs!NtfsFsdDirectoryControl+0xad (FPO: [Non-Fpo]) (CONV: stdcall) WARNING: Stack unwind information not available. Following frames may be wrong. ba577ca0 80828c95 867606a8 86412288 85306750 sptd+0x14aea ba577cb8 f725fd36 8091c136 866d3bc8 85306750 nt!IofCallDriver+0x45 (FPO: [Non-Fpo]) (CONV: fastcall) ba577ce4 80828c95 85f6a8d8 85306750 0012f7b8 fltMgr!FltpDispatch+0x152 (FPO: [Non-Fpo]) (CONV: stdcall) ba577cf8 8090b989 ba577d64 0012f7b8 8091c136 nt!IofCallDriver+0x45 (FPO: [Non-Fpo]) (CONV: fastcall) ba577d0c 8091c193 85f6a8d8 85306750 86467c18 nt!IopSynchronousServiceTail+0x10b (FPO: [Non-Fpo]) (CONV: stdcall) ba577d30 8082337b 00000224 00000000 00000000 nt!NtQueryDirectoryFile+0x5d (FPO: [Non-Fpo]) (CONV: stdcall) ba577d30 7c82ed54 00000224 00000000 00000000 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ ba577d64) 0012fa8c 00000000 00000000 00000000 00000000 0x7c82ed54 !PROCESS 8658d4b8 SessionId: 0 Cid: 054c Peb: 7ffdc000 ParentCid: 036c DirBase: 2aec4000 ObjectTable: e3099420 HandleCount: 137. Image: utorrent.exe start end module name f7395000 f7466000 sptd (no symbols) Loaded symbol image file: sptd.sys Image path: sptd.sys Image name: sptd.sys Timestamp: Sat Jun 24 05:18:51 2006 (449D037B) CheckSum: 000A554B ImageSize: 000D1000 Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0 sptd.sys is the SCSI pass-through filter driver for Daemon Tools, and that's the driver that went in and corrupted pool, and we bugchecked when another application's kernel filter driver (we can't see which due to the corruption, but it's not relevant anyway) went through csrss.exe to read data in pool, and the csrss.exe process bugchecked due to the corrupted information. From the information here, I'd say disabling the sptd.sys driver and then removing Daemon Tools would be a good start.

The KB talks about that error, but it really means ultimately that the user doesn't have the rights to create or modify computer accounts in the AD (regardless of version), and that's why it works as admin without that error (don't fixate on the article too much, fixate on the actual error message and it's meaning). If you want this to work for regular, non-admin users without error, you'll need to delegate the rights to that user or user group to join machines to the domain.

If you're not afraid of vbscript, check http://www.winmag.com/fixes/ie/iecache2.htm: // // Internet Explorer Cache Cleanup 2.0 // See http://www.winmag.com/fixes/ie/iecache2.htm // var TITLE = "IE Cache Cleanup 2.0"; var wsh = WScript.CreateObject("WScript.Shell"); var fso = WScript.CreateObject("Scripting.FileSystemObject"); var env = wsh.Environment; var nfiles = 0; var nbytes = 0; function delcache(dirname) { // Open directory name, catch "not found" error try { var dir = fso.GetFolder(dirname); } catch(err) { return err; } var e; // Delete files in the current directory for (e = new Enumerator(dir.files); !e.atEnd(); e.moveNext()) { var file = e.item(); try { file.Delete(1); } catch (err) { } } // Delete subdirectories recursively for (e = new Enumerator(dir.SubFolders); !e.atEnd(); e.moveNext()) { var folder = e.item(); delcache(folder); try { folder.Delete(1); } catch (err) { } } return null; } function tally(dirname) { // Open directory name, catch "not found" error try { var dir = fso.GetFolder(dirname); } catch(err) { return err; } var e; // Count number and size of files in this directory for (e = new Enumerator(dir.files); !e.atEnd(); e.moveNext()) { var file = e.item(); nbytes += file.Size; nfiles++; } // Count files in the subdirectories as well for (e = new Enumerator(dir.SubFolders); !e.atEnd(); e.moveNext()) { var folder = e.item(); tally(folder); } return null; } // Get IE cache directory name from the registry var IEDIR = "HKCU\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell Folders\\Cache"; var iecache = ""; try { iecache = wsh.RegRead(IEDIR); } catch(err) {} if ( iecache && fso.FolderExists(iecache) ) iecache = iecache.replace(/\\$/, ""); // Get IE cache max size (in megabytes) from the registry var IEMAX = "HKCU\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\Cache\\Content\\CacheLimit"; var iemax = 0; try { iemax = wsh.RegRead(IEMAX); } catch(err) {} if ( iecache.length < 4 || !iemax ) { wsh.Popup("Cannot determine IE cache directory or settings.",0,TITLE,16); WScript.Quit(1); } if ( !iecache.match(/temp/i) ) { var msg = "Cache Folder: "+iecache; msg += "\n\nYour cache folder has a very non-standard name. "; msg += "There may be a problem with your configuration. No changes made."; wsh.Popup(msg,0,TITLE+": Too Scary To Delete!",16); WScript.Quit(1); } // Do you really want to go through with it? tally(iecache); var mb = Math.round(100*(nbytes/(1024*1024)))/100; var msg = "Internet Explorer cache will be cleaned:\n\n"; msg += "Folder:\t"+iecache+"\n"; msg += "Maximum:\t"+iemax+" MB\n"; msg += "Currently:\t"+mb+" MB, "+nfiles+" files\n"; if ( mb > iemax ) msg += "(NOTE: Cache space overflow!)\n"; msg += "\nYou will need to reboot to finish cleaning the cache."; msg += "\nDo you want to continue?"; var yn = wsh.Popup(msg,0,TITLE,36); if ( yn != 6 ) { wsh.Popup("Cancelled at your request. No changes made.",0,TITLE,16); WScript.Quit(4); } // Create batch file that will run on boot //var tmp = env("TEMP") || env("windir")+ "\\Temp"; //var batfile = tmp+"\\iecache!.bat"; var batfile = "C:\\iecache!.bat"; var fh = fso.CreateTextFile(batfile, true); fh.WriteLine("prompt $G "); fh.WriteLine(iecache.substr(0,2)); fh.WriteLine("cd \""+iecache+"\""); try { fso.GetFolder(iecache+"\\content.ie5"); fh.WriteLine("cd content.ie5"); } catch(err) { } fh.WriteLine("attrib -r -h -s index.dat"); fh.WriteLine("del index.dat"); fh.WriteLine("rem ------ IE Cache cleanup complete, please close this window. ------"); fh.Close(); // Goodbye cache, hello disk space! delcache(iecache); var ROKEY = "HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunServicesOnce"; wsh.RegWrite(ROKEY+"\\ClearCache", batfile); msg = "Please reboot NOW to complete the\nInternet Explorer cache cleanup."; wsh.Popup(msg,0,TITLE,64); WScript.Quit(0);

Yeah, it's here somewhere, but I cannot find it anymore either. Here's the Microsoft KB article that went with it - that's probably all you'll need anyway: http://support.microsoft.com/kb/136712/

Although it doesn't appear you're getting a STOP 0x9c, you're getting the same bugcheck code. This one can be a little tricky to track down, but it almost always comes down to faulty drivers or bad hardware. First, I'd strongly suggest you keep track of exactly what you are doing on your machine every time it occurs, to see if there is a pattern. Second, I'd make sure I was using the latest vendor driver for every piece of hardware in that machine that uses drivers, from sound and video to chipset. Third, I'd update everything in that machine - BIOS, firmware for all hardware if possible (including disk drives, video cards, sound cards, etc - if any update to firmware is available, flash it). Lastly, if I still had issues, I'd scale back hardware to just a video card, a stick of RAM, one disk drive, and the processor and motherboard to see if the problems continued.

Inetres.adm is the updated IE7 adm template, and copying that file from the XP machine with IE7 to your 2003 server should give you the option to use the updated IE7 policies after adding it to the Administrative Templates of the GPO(s). Note that creating IE policies on a 2003 server with IE enhanced security enabled is dangerous, so it is best to disable that on the 2003 server you will be using to modify group policies.