E
Eric Hagen
We run a very basic file sharing machine to allow network
installation of software such as Symantec Antivirus. This
file sharing machine is running Windows 2000 Professional.
When we run installations off of this server, the client
machine automatically adds that remote share to the
"offline files" and tries to synchronize to that computer.
Since we have upwards of 400 machines attempting to
snychronize, if that machine is ever turned off or
rebooted, we get all sorts of calls about an "error"
contacting the "offline files server" while synchronizing.
I would like to know WHY this "server" running Win2k Pro is
making all of the clients that ever run something off of it
or map it's share a local drive now synchronize with that
location. Is there a local security policy that would turn
off this obnoxious "feature"? We have dozens of other file
servers that do not have this "problem", but we can't find
any difference between then except that this machine is
running Windows 2000 Pro instead of Windows 2000 Server.
Thanks,
Eric Hagen
installation of software such as Symantec Antivirus. This
file sharing machine is running Windows 2000 Professional.
When we run installations off of this server, the client
machine automatically adds that remote share to the
"offline files" and tries to synchronize to that computer.
Since we have upwards of 400 machines attempting to
snychronize, if that machine is ever turned off or
rebooted, we get all sorts of calls about an "error"
contacting the "offline files server" while synchronizing.
I would like to know WHY this "server" running Win2k Pro is
making all of the clients that ever run something off of it
or map it's share a local drive now synchronize with that
location. Is there a local security policy that would turn
off this obnoxious "feature"? We have dozens of other file
servers that do not have this "problem", but we can't find
any difference between then except that this machine is
running Windows 2000 Pro instead of Windows 2000 Server.
Thanks,
Eric Hagen