Apps hitting the network for local files?

[czechboy16]

We have a Windows XP Service Pack 2 image (including Office 2003) that
we are applying to all of our workstations. We have noticed a strange
problem on the imaged machines when users try to open local documents.


What happens is, the user can double-click on a spreadsheet or document
on their desktop and, instead of launching the associated application
right away, there is a delay of about 15 or 20 seconds where the
machine is hitting the network. If we unplug the network cable, the
app opens right away and displays the file.

On the other hand, if the user opens the application first (Word,
Excel, etc...), then opens the file within the application, it opens
instantly.

The file associations are the same as non-imaged machines that are not
having this problem. Can anybody give me a hint as to why this might
be happening? We have completely halted our image roll-out until this
issue has been addressed, so we're pretty desperate to get it resolved.

Thanks in advance,

-Karl

 

[Ramesh, MS-MVP]

Karl,

See if there are references to a network share in the registry. You may use
this article as an example:
http://windowsxp.mvps.org/rcdelay.htm

Apart from that, the Office 2003 may be trying to do an on-demand
installation while the installer package is stored in a network share? The
Event Log might help in this case.

 

[czechboy16]

Ramesh,

Thanks!!! That pointed us in the right direction and we have a fix.

Turns out that Ghost Explorer had a reg. key that was hitting the
network (UNC path). Clearing the key solved the problem.

I appreciate the help!

-Karl

 

[Ramesh, MS-MVP]

Excellent! Thanks for posting back, Karl.