cluberti

The tool itself needs admin privs to install, but regular users should be able to run it once installed from the install location ("\Program Files\Microsoft Office\Office 12\Office Outlook Time Zone Data Update Tool\" for Office 2003). Since you say you've got AD, install it via a computer configuration container Software Installation (intellimirror) policies from a GPO that applies to client machines.

That's just the en-us MUI for x64 versions of Windows. From the "system requirements": "The 2007 Microsoft Office system programs client is a 32-bit application and can run on a Windows 64-bit platform (Windows XP, Windows Server 2003, and Windows Vista) but there may be some feature limitations as noted in the system requirements below." As far as I know, the only Office products currently in x64 are Forms Server and Sharepoint Server.

If the application is 16bit, or it's 32bit but has a 16bit installer (there are some exceptions, but they're VERY rare), then no. x64 versions of Windows are not capable of executing 16bit code at all - they can run 32bit code, but not 16bit.

Agreed - the most common mistake people make when configuring ICS is that they configure the *internal* network device (the one attached to their internal PC's or internal switch/hub) for sharing, rather than the *external* device that is attached to their ISP (modem, external NIC attached to broadband modem/router, etc). You need to configure sharing on the *external*, internet facing device. Otherwise, you're not going to get any internal machines on the internet .

I would agree with you then that your problems seem to go much deeper than Internet Explorer. Perhaps backing up your data and starting fresh with a new install of XP may be good medicine for your machine .

Autologon.exe might help.

I think you're barking up the wrong tree. I say this, because dwmapi.dll is a Vista-only dll, and efsadu.dll is only installed if you've enabled the Encrypting File System on one of your drives. Therefore, I expect that on XP, if you don't have EFS enabled on a volume, you would indeed find neither of these on your system. Also, don't trust depends entirely. Depends will find that you may be missing .dlls, but it can't determine if you need those on your system or not - in this case, you should not need either on XP for IE7 to function properly. I'd say your problems with XP and IE7 have nothing to do with missing those .dlls, so you may want to refocus your troubleshooting efforts. What you are seeing in depends is pretty much expected behavior on an XP install without an EFS volume.

There actually isn't. Just like adding local printers, the utility checks the ACL of your user account, and if you don't have an Administrator ACL, you can't do it. With printers it's power users, but for network connections I believe it's administrator.

I second removing and reinstalling the installer engine. I've seen msiexec come broken by default on OEM installs from major vendors, and a reinstall fixes it. Not sure what they do to break it though .

Use WireShark or Netmon to gather the trace from the workstation. As to the network device, you usually attach a machine to the admin port of the switch/router, or use a hub between the switch / router port and the network, with a machine attached to the hub in promiscuous mode running wireshark or netmon.

Or the built-in sc.exe, in XP, 2003, Vista, and Longhorn. C:\>sc DESCRIPTION: SC is a command line program used for communicating with the Service Control Manager and services. USAGE: sc <server> [command] [service name] <option1> <option2>... The option <server> has the form "\\ServerName" Further help on commands can be obtained by typing: "sc [command]" Commands: query-----------Queries the status for a service, or enumerates the status for types of services. queryex---------Queries the extended status for a service, or enumerates the status for types of services. start-----------Starts a service. pause-----------Sends a PAUSE control request to a service. interrogate-----Sends an INTERROGATE control request to a service. continue--------Sends a CONTINUE control request to a service. stop------------Sends a STOP request to a service. config----------Changes the configuration of a service (persistent). description-----Changes the description of a service. failure---------Changes the actions taken by a service upon failure. qc--------------Queries the configuration information for a service. qdescription----Queries the description for a service. qfailure--------Queries the actions taken by a service upon failure. delete----------Deletes a service (from the registry). create----------Creates a service. (adds it to the registry). control---------Sends a control to a service. sdshow----------Displays a service's security descriptor. sdset-----------Sets a service's security descriptor. GetDisplayName--Gets the DisplayName for a service. GetKeyName------Gets the ServiceKeyName for a service. EnumDepend------Enumerates Service Dependencies. The following commands don't require a service name: sc <server> <command> <option> boot------------(ok | bad) Indicates whether the last boot should be saved as the last-known-good boot configuration Lock------------Locks the Service Database QueryLock-------Queries the LockStatus for the SCManager Database EXAMPLE: sc start MyService

A network trace from your machine, and at your border router, simultaneously, will at least show how fast the traffic is passing on your network (likely you'll see a request from the client immediately leave from your border router), and how long it takes to get back (you'll also likely see the delay after the packets have left your border router, but when they do return, the client gets the packets almost immediately after that). It won't show you what the problem is, but you can at least be sure it isn't on your network at this point. If you're getting 100% packet loss (or anything like that), it is definitely a routing issue somewhere between you and the destination server(s). Assuming no one else is having a problem accessing those servers from outside of your ISP's network........ .

Either that, or perfmon. Looking at private bytes, virtual bytes, and working set under the process counters should give a good idea too.

Yes, most volume licenses are upgrade-only. Meaning, your machine had to come with an OEM license for it to qualify for install of a VL copy of the same or newer version of Windows via SA. And technically, you're paying about 10% or so, depending on OEM, for that original OEM license to begin with, so I'm not sure you should be complaining too much . Parf of the reason there are such deep discounts per copy of Windows is that it is assumed you've already paid a bit for the license from the OEM - don't think of it as paying twice, think of it as part of the cost of the license. You just pay part of it to two entities.

Run Process Monitor while deleting, and see where the disk accesses are coming from during this time. Usually it's antivirus, but it could be other things.

If you look at the memory counters in perfmon, or the private bytes column in Task manager, you should get an idea of where the memory usage is going.

LOL - I'll look at a dump if/when you get it.

Cool - I've got -1 messages!

Please respect other members here, as has been stated, including me. My action plan would perhaps have helped, but you can expect no such assistance in the future if you do not wish to take me seriously.

As far as I know the only way to block it would be to create a GPO hash that keeps it from installing, but it's just gonna keep trying over and over if you aren't configured for WSUS. There is no block tool for this update.

You could try to do a repair, but if you're infected or have some other sort of problem outside of the normal Windows directory structure, a repair install isn't going to fix anything. Note that the best place to start right now is probably configuring the machine for a complete memory dump, and letting us analyze one or two to see if we can pinpoint the problem.

It does. The RAM limit is 4GB, not 2GB.

Replmon should be able to assist you.

Whenever the delay occurs, if it happens to be usually 3 minutes, dump at 1.5. If it happens to be 2 minutes, dump at 1 - whatever you are normally experiencing as the delay, wait HALF of that and then dump the box (I don't care when ).