cluberti

If you are the system builder of these computers, you buy OEM licenses and media to go with the PCs, and you install the OEM copies (and use the OEM PID keys) on these computers. However, if you are not the system builder building and selling these PCs, you buy and install the retail versions of Windows on these PCs.

Are you upgrading this server, or replacing it entirely?

You cannot have multiple gateways if a machine is used for routing. You should configure a GW only on the external interface, and configure everything else using the ICS wizard, or install RRAS. Windows does NOT like multiple gateways.

You could query the data with WMI, but the best way is to pop it open and take down serial numbers and part numbers for anything you can access. If you think it's old, why specifically?

I have to second Diskeeper, especially if you have Active Directory - DK has AD integration, so you can configure DK settings from within a GPO and apply them to all clients running the software. Very useful, and a good defrag engine to boot.

If you'd like to provide something constructive to this conversation, like being that "discerning eye" to add value, please do (I'm sure help on this project isn't frowned upon). However, if you simply want to bash, take it somewhere else on the 'net where that sort of thing isn't frowned upon, because it's against the rules here. Relevant forum rule:

Yes - it's called "Access Based Enumeration", or ABE. Note that if you have a high volume of users that access the server, it will bring the server to it's knees by chewing up all CPU cycles .

One question - have you modified the permissions that affect the REMINST folder? I've seen this in beta testing when the "Authenticated Users" group was removed from the NTFS permissions on the share - for whatever reason, when these permissions didn't apply to the REMINST share when SP2 was applied, the BINLSVC service wasn't removed, and the WDS service was set to manual (and all other sorts of service issues ensued even after the binlsvc was removed manually). If we restored the same image to the box but set the permissions to what they were default after the RIS installation, everything worked just fine. Same box, just different permissions on the REMINST folder, and different behavior entirely during the SP2 install.

First of all, Content Advisor was never meant to be a _proxy_, it was meant to be used in parental controls. I know there are KB articles on how to do this, but it's not supported, and for valid technical reasons - for one, Content Advisor loads every page you visit (allowed or not) in a hidden browser window, then scans the page to see if it should be allowed or not. Honestly, the best way to do this is to use a proxy .pac file as the autoconfiguration address in IE, and only allow access to one site (and only to https: traffic to that site), and then point all other traffic somewhere else (like 127.0.0.1).

There is so much incorrect about that statement - while you are correct that allowing Windows to manage virtual memory in NT is wise, you are completely incorrect about Windows not using the paging file unless RAM is full - unless an application is using the "Lock pages in memory" allocation type (and has rights to do so), all virtual memory allocations are backed by the page file. Kernel paged pool memory is backed by the paging file. All files that are not memory-mapped can (and will, on a busy system) be backed by the page file. Just to name a few obvious uses of the paging file that no one can avoid...

Are you trying to enable PAE on an x64 build of Windows? Because PAE is a 32bit construct - you can't enable PAE on x64 (it isn't needed or supported). As to memory remapping, if you can't disable it, you're SOL. That memory is likely being reserved by the BIOS - try running msinfo32 to see what shows up as installed memory on the system. That might give you a clue as to what's happening - if the installed memory is significantly less than 4GB, you've got a BIOS issue with recognizing the full amount of RAM installed; if the installed memory is 4GB but available is significantly less, you need to find a way to reduce the amount of memory the BIOS reserves (not sure how to do that other than contacting the motherboard vendor or the PC manufacturer).

And this has been posted here before, and many times elsewhere on the 'net (even a post on a Microsoft blog). I believe it's a bug in explorer.exe on Vista, and we've not heard of any movement towards a fix for it as of yet. The file isn't growing or shrinking in size (I've seen this bug show negative file sizes too, very funny), thankfully, but explorer is displaying the size data incorrectly in the status bar. Please search before posting a dupe of something that's been discussed here before and elsewhere many times. Thank you.

settings are stored per user - so I don't think this is going to work at all the way you want it to. Your best bet is to preconfigure the router using whatever security encryption method you desire, and then send the hardware onto it's destination with step-by-step instructions on how to get it working on his machine.

Just be aware that if the update caused it, there'd be more reported cases of this, not to mention that the first time I saw this happen was many years ago. It'll be the print drivers, or a need to reinstall the print drivers (Xerox drivers are also notorious, btw). Have you tried removing the print queues and uninstalling the drivers from the advanced options of the printers and faxes GUI?

.NET framework versions are not cumulative, they are stand-alone. Most applications will have no problem with this and will use the installed version if it is compatible, but some applications will be written to specific versions of the framework, and you must have that version installed to use the application. I find it best practice to have all versions installed on machines, that way the application can always attempt to use the framework version it was written for.

Is the print spooler "clean", or does the user have print drivers installed? I've seen this before caused by HP Print Processors installed in the spooler (that are _completely unnecessary_, btw, for almost all day-to-day printing tasks). Consider that it isn't spoolsv.exe itself, but something running inside of it. Now, if the spooler is really clean, then that's something .

How about running Process Monitor in boot mode with a filter on this file? It would show you what binary was touching the file...

Have you tried attaching the boxes to a Gb switch yet? I've seen some Gb ethernet cards on Nvidia-based motherboards with the Marvell Yukon chipset that just wouldn't negotiate at anything above 100Mbps with a crossover cable (even when pinned-out correctly). Attach them to a switch via straight-though CAT5e, and viola, 1Gbps. between the same two machines. Marvell NICs are nothing but trouble, in my experience, and they're on that motherboard for a reason (and it isn't because they were the best - they're the cheapest MAC bulk money can usually buy that can be customized).

Before everyone goes crazy telling the user to rebuild, let's do something that may actually HELP... like configure the Windows Installer service to run in safe mode: 1. Boot into Safe Mode. 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 back into Safe Mode, and the Windows Installer service should now run and allow you to add or remove programs in Safe Mode. If you STILL can't boot after uninstalling your product at this point, _THEN_ you might want to consider a repair install or a rebuild.

If you look at the process object in perfmon for the firefox application, what do the "virtual bytes", "private bytes", and "working set" counters show as values when the "leak" gets bad?

Please don't ever disable the event log service - this code lives in services.exe, and can cause... interesting.... behavior with all sorts of things running as services. There's really no reason to disable this service that I can think of, either.

Looks like someone has configured it in a domain or OU GPO, because that's what it looks like when that has been done. Check the following registry location for data regarding SUS server, update frequency, and such: http://technet2.microsoft.com/windowsserve...3.mspx?mfr=true

Could be - file handle invalid means a process has a handle to a file that is either no longer there, or has moved and the handle table wasn't updated. I'd say replace the failed drive and reboot, but you probably will need to restore the data from a backup (or re-backup the data on the client machines to recreate the backup store).

Not really - something on your machine was written against the VC 8.0 runtimes, and it's failing (thus the MSVCR80.dll), but other than that, no. It just sounds like one of the apps on your box isn't Vista compatible 100%, and is causing the issue. BTW, I couldn't download the last dump you PM'ed me about.

Is it server 2003 Standard or Enterprise edition, and is the processor x64 capable? If so, that's because /PAE is enabled by default in this scenario, and /PAE allows addressing of memory above the 4GB boundary. Unless you really want to research the Intel documentation as to how this memory is reserved (and bore yourself to death), I'll save you the trouble and give you a "high-level" synopsis - the BIOS "moves" the 4GB boundary down to 3GB or 3.5GB (or whatever) so that it can reserve the memory above it for devices. Since /PAE allows a machine running a server-class Windows OS (or an x64 OS) to see "above" the new "boundary" the BIOS artificially creates, server 2003 and x64 OSes can then see this memory the BIOS has reserved, and can actually use most of it if the BIOS doesn't lock it. Since client OSes (non x64) cannot see above 4GB with or without /PAE enabled, they'll still only see 3 or 3.5GB (or whatever) when /PAE is enabled, whereas server OSes can and will see above the artificial 4GB boundary when /PAE is enabled.