Microsoft Office Shortcut\Hyperlink\Hotlink Question

[anonymous1234567890]

Hi

When I drag and drop a shortcut\hyperlink\hotlink to a file that stored on a
mapped network drive into word/excel/outlook etc, the shortcut that it
actually points to changes to the UNC name rather than the network drive,
e.g. p:\hello.doc becomes \\servername\sharename\hello.doc

This causes us a big problem, not because the unc name is wrong, but because
our security software shuts down any windows that have \\ at the start of
them.

Can anyone tell me how to stop Office from changing the drive letter to a
UNC name?

Thanks in advance,

S.

 

[Bob I]

Humm, I think perhaps that security software may be a bit intrusive.

 

[anonymous1234567890]

True enough, but I work in a tough environment with users that try to break
things (a school), so we'll carry on with the security software. It's Office
that's causing my problem - anyone got a 'fix'? Openoffice works fine, but
we can't use that due to various on-line testing that we do.

 

[Bob I]

I would say that "hiding" the server to "thwart" the security software
is not the answer. If the software is any good, then selected servers
will be trusted, and that would be the route the go.

The following method will "dump/bypass" the security software.

At the command prompt

SUBST <drive letter> <unc path>

then make your link through the SUBSTituted drive letter. The Subst will
have to be performed each login, or create a CMD file to do it and put
a shortcut to it in the Startup folder.

This is NOT recommended in place of correcting the security settings,
but is only a workaround.

 

[anonymous1234567890]

Thanks for the reply - I tried using the subst command, but still get the
same result, i.e. Word (or any office app) still changes a hyperlink from
P:\ to \\servername\sharename

 

[Bob I]

You can't use the same letter as the original network drive mapping letter.

 

[anonymous1234567890]

I didn't and it didn't work.

You can't use the same letter as the original network drive mapping letter.

 

[Bob I]

Interesting, it works just fine for me here. The hyper link remains
mapped to the SUBST created drive letter. If you are actually using
"sharename" instead of the real path, then that could be the issue. Use
the UNC path as the mapping.

 

[anonymous1234567890]

Hi Bob I

You know what, I went back and tried the subst command again and this time
got the same result as you. I did use the sharename though, i.e. 'subst p:
\\servername\sharename' and it worked just fine.

We currently use a logon script (kixscript) to map our network drives, but
it looks like I'll have to find a way to use the subst commad to map them.

I don't suppose you can explain my Office handles a subst mapped shortcut
differently to a normal mapped drive?

If possible, I'd like to find a way to get the normal network drive
shortcuts to work properly rather than using the subst command (mainly due to
being stubborn ), so if you've got any more ideas, I'd like to hear them.

Thanks

 

[Bob I]

I already told you how to fix it properly. If the security software
can't/won't pass selected servers and you won't remove it or replace it
with software that will, then you can only fool it into not knowing
about the redirection going on locally.