cluberti

Well, since your screenshot isn't the entire services list, this isn't exhaustive, but disabling COM+ seems like a bad idea to me. If COM isn't running, you will most likely see event log issues, and you'll have problems with other things that contain COM subscribers (like WMI) that can and do fire off during login.

MSJVM hasn't been developed in ages - you really should be using Sun's JVM instead, unless you have an application written in J# that you must use msjvm for. The support for it ends in December of this year as well, so not even security updates at that point.

64bit machines are better at opening larger files quicker, they're faster at "number-crunching" (like compiling code, loading files, etc), and give access to twice the registers that 32bit Windows does (although this will benefit 32bit apps very little). Windows itself, being 64bit, will operate faster than it's 32bit counterpart given more RAM, too, but otherwise, not much.

If it's an SBS version of Server 2003, then obviously you will be installing Exchange on your DC, as the SBS version is tweaked to work under the loads it is capable with both roles. However, for any other version of Windows Server 2003, you would want to separate your Exchange and DC roles, and if it's going to be a busy TS, you would want to have a separate server for that as well. You should be able to use Windows Server 2003 Standard for these servers, depending on the user load you are going to be putting on these boxes.

That'd be because 5.7 was just released, and I had no idea... : http://www.microsoft.com/downloads/details...;DisplayLang=en

What happens if you reinstall the Windows Script Host 5.6 package? You can get it from www.microsoft.com/downloads.

That would work, unless they had Firefox or Opera (or some other browser). The best way to do it is to put a proxy in place on your network connection. If you can force your users to only using IE, you could use an autoproxy script to deny users access to the internet via group policy - put all of the "non-internet" users into one OU, or create a group for users in an existing OU and filter a policy on that group's users to use the autoproxy as their proxy to the internet (the proxy would need to be configured to direct every protocol to 127.0.0.1). http://technet.microsoft.com/en-us/library/bb496457.aspx

You say things like "session log", and I freak out - the term "session log" doesn't sound like a 1-byte endeavor .

Well, actually I was talking about using wireshark or network monitor to capture all packets between the hosts. However, it's interesting to see what amounts to a UDP request to a multicast address during the transaction - another reason to see the actual network trace, because something is happening between the machines that we'll probably not see without all of the packets back and forth.

If you boot into safe mode, does it reboot properly from there?

Ummm.... queue up Mr. Mackey voice: Using the registry for database storage of anything other than app settings are bad, mkay? Storing data in the registry causes the registry to grow in size, which can cause kernel memory pressure, registry corruption and fragmentation, and even an inability to boot if the hive or hives get too large to mount on boot. Store volatile data in files, not the registry. Please .

Hm - I don't think this has anything to do with the RPC services themselves, but something the installer is trying to communicate with that isn't responding to the RPC requests by the installer. What is the actual source for those error messages? Because there are about 10 for both error numbers, from ASP.net to userenv. Giving the source as well as the error # is almost always necessary to see what is happening. More importantly, what happens if you follow this support article about this exact issue from InstallShield's support pages?

of course it is broke, didn't anyone tell you cluberti I guess I missed it. I'm always the last to know these things...

Does it happen for all users on the box, or just specific user accounts?

Well, have you gotten a network trace of a failed SMB connect to a C$ share, or a failed Remote Registry connect attempt? If the reg entries are there, the services are running, and no firewall or TCP filtering is enabled, next step is a network trace to see what is coming along the wire (preferrably run at the same time on both the connecting machine, and the machine being connected to).

Windows update is broken? Please explain...

Scriptlogic does generally have you set up an administrator account and a regular user account, so you could likely get scriptlogic to push this out. However, ADM templates are usuallly cleaner from a deployment standpoint, but you do have to watch out for the "tattoo" effect if you ever want to roll this back later.

Every COM object has a CLSID. I mentioned both because they're generally intertwined, and when that message occurs one or both are missing permissions. I don't think it'll fix the SP2 not installing issue, but it'll fix the COM errors. As to SP2 not installing, can the install be attempted in safe mode? Do we get the same results there, or does it work? I also second downloading the whole thing from the microsoft.com/downloads site, rather than trying to use the windows update binaries.

What is the actual error? Also, if the RPC service isn't starting, you have bigger problems

What happens if you grant the Network Service account local activation permissions on the following 2 DCOM components (if they exist): - IIS Admin Service - IIS WAMREG You can see these by running "dcomcnfg", and browsing Component Services > Computers > My Computer > DCOM Config

It's spitting out an error that mstsc.exe can't find the .rdp file - perhaps run process monitor while attempting to launch the vbscript to see where it's actually looking for the file?

If you're replacing the shell with the rdp client vbscript, this should work as long as the user has the rights to run the script. Otherwise, you'll need to launch the vbscript via a .cmd file if running the .vbs directly doesn't work.

Sure: 1. Open mmc (start > run > mmc) 2. Click File > Add/Remove snapin 3. Click "Add" 4. Select "Security Configuration and Analysis" from the list, and click "Add" 5. Click "Close" 6. Click "OK" 7. Right-click the "Security Configuration and Analysis" option under "Console Root", and click "Open Database" 8. Type in a name for the new database you are creating (can be anything), then click "Open" 9. From the list of templates (if you do not see any .inf templates, browse to %windir%\security\templates) select "setup security.inf" and click "Open" 10. Right-click the "Security Configuration and Analysis" option under "Console Root", and click "Analyze Computer Now" 11. Click "OK" when prompted to create an Error log file path This will analyze your system against the .inf file that was applied when the OS was first installed, showing you the differences.

Today (Thursday, Aug 9) Temp: 102°F Sky: Sunny Wind: W 9mph Relative Humidity: 27% Dewpoint: 62°F Pressure: 29.85in Visibility: 10 miles Walking around is like swimming in a hot pool. No real rain for weeks, and it should be in the 90s until September. I love summer .

Legally, no, you cannot. Source for Windows can be had under the shared source program if you so choose, but it's not for copying or recompiling, only for viewing the source when writing your own applications so your apps can theoretically be written better. Closing this thread as per forum rule #1: