cluberti

Which freezes, the installation package or the shell? Also, what do you mean by "freezes" - does it hang at one point for long periods of time, or actually go unresponsive? You may also want to try installing this in safe mode: 1. Download the update package manually from the microsoft.com site, and store it on disk somewhere. 2. Create the following registry key (it won't exist by default, so create this new key): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\msiserver - (If you also want it available in Safe Mode w/ Networking, add the "msiserver" key under the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\ key found here as well) 3. Edit the "(Default)" value in the new "msiserver" registry key, and enter "Service" in the "Value Data" box. Click OK, and close the registry editor. 4. Reboot in Safe Mode and attempt to install the update there.

Moving to more appropriate forum.

What happens if you delete and recreate your profile in Windows, and don't connect to it with XP? Does it then look in the correct Vista location (\\tsclient\c\users.....\)?

Adding patches to Vista is far easier than on previous OSes - you will find what you're looking for over in Unattended Vista.

It appears that the latest ZoneAlarm release is listed as Vista-compatible. However, since Checkpoint purchased ZoneLabs, I've not recommended their software to anyone - it's buggy, slow, and not cheap. If you want to try the ZoneAlarm software and post here if it's any better than past releases, that'd be pretty useful. However, I don't think you'll find anyone who's installed it yet here, as they're pretty much hands-off right now due to the lack of quality in their previous releases over the last year or so.

It's complaining about not being able to talk to something on the box, and according to Cisco's docs on this bug, it is usually caused by 3rd party firewall software on the box. The fix is to install the latest 4.x version of the Cisco VPN client, and allow it through the firewall software.

The only issue I see with locking things down, is that the original poster is new to doing this sort of thing. If he or she goes too far, he or she will likely not have a good idea of which security lock-down caused the issue, and reversing things with group policy is not something that is necessarily easy to do. Default security on both system files and the registry in XP and Vista is quite good for most scenarios, and locking down driver installations can result in some 3rd party printers not being able to be installed, it can break smart-card software, disable the use of USB and Flash memory devices, etc. Locking things down further from the defaults takes quite a bit of careful testing and planning with every internal application and device the OP may use internally on their network, and that's not something I expect (or want) a novice to tackle. Otherwise, steps 3 - 6 are great, and I second those .

Download and run Process Monitor (from sysinternals), and run it when you're attempting to install a hotfix or package that causes this error. Once you come across the error, stop the logging in process monitor, and then find your "Access Denied". It should tell you which user account tried to access a particular registry key, and why it failed. If you can find the key you're failing to, and who is attempting to read or write from this key, you can change the permissions in regedit for that key and fix the issue (hopefully).

Unless you've installed an SDK, DDK, or Visual Studio, you won't have these header files on your system.

OK, I can see what's happening, but I can't tell you for sure why. You're exhausting nonpaged pool on the box for sure, but it's all happening in the Irp tag (a Microsoft tag) which would denote a large number of disk or network transactions. What are you doing on this box that would cause so many IRPs? Also, with only 256MB of RAM, you are really constraining kernel-mode process space - another 768MB will make XP run much better overall. Anyway, here's what I can see when the problem itself becomes too much for the box to keep up with - note the tag "Irp" with over 158,000 outstanding allocs without being freed. Something on this box is very poorly written: === Sun 6/17/2007 1:11:37 AM ComputerName=PC-1 FreePTEs=251,609 === SystemUpTime(hours)=14.62; ProcessTotalHandleCount=8,392; SystemThreads=396; SystemProcesses=37 Memory: 261672K Avail: 47772K PageFlts:39712618 InRam Krnl: 2104K P:13176K Commit: 402936K Pool N:101,404K P: 26,372K SystemUpTime(hours)=14.62 Tag Type Allocs Frees Diff Bytes Per Alloc Irp Nonp 363202 205088 158114 75643864 478 pgip Nonp 1 0 1 2867200 2867200 Wdm Nonp 2932 2396 536 2474752 4617 Devi Nonp 2577 2191 386 1608992 4168 Ddk Nonp 661515 661281 234 1287904 5503 None Nonp 288849 280896 7953 1071936 134 MmCm Nonp 715 684 31 995872 32124 10k1 Nonp 272 248 24 762704 31779 V386 Nonp 23 10 13 648568 49889 Sptd Nonp 149081 148517 564 480736 852 File Nonp 3649702 3647143 2559 390264 152 And here's what was running (process-wise) that's non-Microsoft - any of these could (and one or more IS) causing the problem: ProcessName CommandLine avguard.exe "C:\Program Files\AntiVir PersonalEdition Classic\avguard.exe" sched.exe "C:\Program Files\AntiVir PersonalEdition Classic\sched.exe" nlsvc.exe "C:\Program Files\NetLimiter 2 Pro\nlsvc.exe" PERSFW.exe "C:\Program Files\Kerio\Personal Firewall\persfw.exe" NLClient.exe /runonlyonce /tray UnlockerAssistant.exe "C:\Program Files\Unlocker\UnlockerAssistant.exe" -H pstrip.exe "C:\program files\powerstrip\pstrip.exe" devldr32.exe C:\WINDOWS\system32\devldr32.exe D4.exe "C:\Program Files\D4\D4.exe" avgnt.exe "C:\Program Files\AntiVir PersonalEdition Classic\avgnt.exe" /min AdMunch.exe "C:\Program Files\Ad Muncher\AdMunch.exe" /bt MouseFix.exe "C:\Program Files\(MouseFix)\MouseFix.exe" daemon.exe "C:\Program Files\DAEMON Tools\daemon.exe" -lang 1033 strokeit.exe "C:\Program Files\Strokeit\strokeit.exe" utorrent.exe C:\Program Files\(utorrent)\utorrent.exe" pg2.exe "C:\Program Files\PeerGuardian2\pg2.exe" flashget.exe "C:\Program Files\(FlashGet)\flashget.exe" Honestly, there's an awful lot there that could be causing it, but I think I'd start by removing the NetLimiter and Kerio software first. My reasoning for this is that the dumps you've got thus far seem to indicate that we're doing network traffic at the times of the crashes, so it is possible that it is the Kerio or Netlimiter package, as those are the ones that stick out right away as network security packages, although I think flashget, utorrent, PeerGuardian2, et al are also net packages. I'd say it'd be best to uninstall things to figure out what is causing this, because if you rebuild you're likely to put whatever package is causing this right back on the box. You could very well rebuild and have the same problem, which I'd guess would be bad .

Edit - wrong thread.

And I'd still suggest debugging with WinDBG or CDB from the Debugging Tools for Windows download anyway, as they're much more robust and configurable debuggers than the VS debugger.

Is there any reason you aren't using TCP/IP on MacOS X?

1. NLB is only needed if you want to set up session directory. 2. You don't need it for a TS farm specifically, but if you want users to be able to disconnect and reconnect to the same session every time, you will need to use it. 3. Terminal Services doesn't support clustering, only NLB/Session Directory. If you're having NLB problems with your servers, make sure you've configured everything properly as per the TS Session Directory documentation. If you've configured everything as per the documentation, but find that you cannot ping or connect to one (or both) servers after configuring NLB, then you have a problem with your switches not liking the fact that a unicast address is coming from a multicast MAC address, and you need to address this with the switch vendor themselves, or their documentation. In general, NLB works much better with managed switches than unmanaged, especially L2 unmanaged.

First, ntdll.dll is a Windows file that is responsible for handling most Win32 API calls, so you can always ignore that file if it's ever listed as the culprit in !analyze -v. Second, from the errors you're getting and the stack calls that are being made, it looks like you're running out of kernel nonpaged pool, and that is causing csrss.exe to crash. I've sent you a PM of a tool you can run to track pool allocations, and with it we may be able to see what's causing this.

The amount of memory an application gets has no bearing on how much RAM is in the box, but the amount of RAM a driver "sees" can affect it's functionality. There's no way to hide memory from a driver short of pulling sticks of RAM or booting with the /MAXMEM boot.ini option - in short, the only really good option here is to get an x64 version of the software/driver, which currently (as far as can be determined) does not exist.

Quite funny

In XP, no, keys are not interchangeable - x86 keys are for x86 only, and x64 keys are for x64 only. Note that in Vista, for retail versions of x86 and x64, one key can be used for both (once you choose which, however, it becomes an x86 or x64 key, respectively).

They aren't all there - some of them are only in the .h files you get with the SDKs and Visual Studio, etc. As to your error code, here's the error: STATUS_SXS_ASSEMBLY_NOT_FOUND ntstatus.h # The referenced assembly is not installed on your system. # as an HRESULT: Severity: FAILURE (1), FACILITY_DPLAY (0x15), Code 0x4 # for hex 0x4 / decimal 4 ERROR_TOO_MANY_OPEN_FILES winerror.h # The system cannot open the file. # 2 matches found for "0xc0150004"

I'd suggest configuring your machine for a complete dump, so the next time it occurs we can take a look if you upload it or provide a place for us to download the .dmp file.

0xc000009a - Insufficient resources. That's a very interesting error - perhaps you could configure your machine to generate a complete dump next time, and then once it happens again you could compress/upload for us to review?

Consider installing 927891 and 932494, and rebooting. That may solve it as well, as that installs the new Windows Update binaries (and fixes some of the CPU issues as well).

I used them, but only after I made sure my users were either using webmail only, or if they used Outlook, that their mailbox was on an Exchange server (and not mail in a .pst). You can use network .pst files, but if you lose connection to the network location the .pst file is on while Outlook is open, you'll get a corrupted .pst file and lost email - not good. Roaming profles are good, but they do have limitations. I usually configure roaming profiles with redirected shell folders and an Exchange server to cover my bases.

I have in the past, but only after implementing Exchange or an IMAP server for email. Keeping user's email in their profiles sync'ed to a roaming copy is an absolute nightmare.

Is this a custom email system, or something like Notes or Exchange?