Stop office from scanning network drives in disconnected state

[Russell Reid]

I know that unmapping the network drives when disconnected is the MS solution

for solving the problem with office apps opening files slowly off network

(KB313937). But i don't remember having any users complain about this until

a month or so ago. We have been using Office 2007 in a domain environment

for several years and this issue has never occurred until recently (like that

last month or so). Is there a group policy setting or Office setting that

will prevent office from waiting for a disconnected drive to time out? We

map drives using group policy preferences and it would seem more problematic

for users (and the administrator) to have to force drives to unmap and then

remap whenever a user logs onto the domain just so that they don't have

disconnected network drives when out of the office. That is what persistent

connections are for after all. And how do i deal with users who put their

laptop in standby then disconnect? Giving the user a script to unmap the

connnections is not a great idea either. I sure hope that this issue is not

in Office 2010.

--

Russell Reid

 

[LVTravel]

"Russell Reid" wrote in message

news:EFCC8F2F-5D97-4BC7-8C51-4D547F3723EC@microsoft.com...

> I know that unmapping the network drives when disconnected is the MS

> solution

> for solving the problem with office apps opening files slowly off network

> (KB313937). But i don't remember having any users complain about this

> until

> a month or so ago. We have been using Office 2007 in a domain environment

> for several years and this issue has never occurred until recently (like

> that

> last month or so). Is there a group policy setting or Office setting that

> will prevent office from waiting for a disconnected drive to time out? We

> map drives using group policy preferences and it would seem more

> problematic

> for users (and the administrator) to have to force drives to unmap and

> then

> remap whenever a user logs onto the domain just so that they don't have

> disconnected network drives when out of the office. That is what

> persistent

> connections are for after all. And how do i deal with users who put their

> laptop in standby then disconnect? Giving the user a script to unmap the

> connnections is not a great idea either. I sure hope that this issue is

> not

> in Office 2010.

> --

> Russell Reid



I've had that issue since Office 2003 premiered and the only "fix" that

anyone came up with was drive mapping batch files with a companion to un-map

the drives. I don't know of a group policy edit since I haven't checked

into it and didn't need it for my systems (as I use non-persistent mapping

batch files for the two networks I connect to on my laptops) so I can't help

you there. I do know, because I have tried it with Office 2010, both Pro

Plus and Home and Business versions, that the hang for disconnected mapped

drives still exists.