Can't open hyperlinks to files

[Steele]

I have a Windows Server 2003 R2 Terminal Server, and have a pretty
restrictive GPO applied to it. The users are restricted from most system
tasks, and I set "Run only allowed Windows applications" under User
Configuration\Administrative Templates\System. I have a list of .exe files
set that they are able to run, and they are prevented from running anything
else.

MS Office 2003 is installed on this Terminal Server and the users are able
to launch all of those applications. This was working fine for awhile, but
after we installed some Microsoft Updates earlier this year, we found that
users could not click on links in the Outlook email messages and open files
off of their mapped drives. For example, if a user has a hyperlink in their
email message to G:\CustomerFolder\Customer1.xls, they are not able to click
on it and open it directly. However, if they browse to that location through
Windows Explorer or MS Excel, they can open the file without any problems.

If I set the "Run only allowed Windows applications" to "Not configured",
the users no longer have any problems opening the links, so I think there
might be something in there that I need to change, but I haven't been able
to figure out what. I've tried adding G:\*.*, \\server\share, file://server,
and even the full path to one of the files that we're trying to open, but
that doesn't seem to work.

Does anyone have any suggestions on how I can open this up so that the users
can just click on the links?

 

[Diane Poremsky [MVP]]

This is not an outlook problem - you need to check with server experts for
the resolution.

--
Diane Poremsky [MVP - Outlook]



Outlook Tips by email:
(e-mail address removed)

EMO - a weekly newsletter about Outlook and Exchange:
(e-mail address removed)

You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point your
newsreader to msnews.microsoft.com.

 

[Kaedya]

I disagree. I am also having a problem similar to this.
When sending an Excel file as an attachment in Outlook 2007, (file is saved
on our "G: drive" and has cell references to another file on our G: drive) an
error of '#REF' was displayed when the file was opened, and when the cell was
looked at the reference no longer stated the path through the G: drive but
was referencing the C: drive instead.
When the same file was sent directly through Excel, the problem no longer
existed.
Also, the file was sent to two different people, one with access to the G:
drive and one without. Both recieved the same '#REF' error when the file was
sent as an attachement and both saw the correct data when the file was sent
through Excel.

Any help?

This is not an outlook problem - you need to check with server experts for
the resolution.

--
Diane Poremsky [MVP - Outlook]



Outlook Tips by email:
(e-mail address removed)

EMO - a weekly newsletter about Outlook and Exchange:
(e-mail address removed)

You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point your
newsreader to msnews.microsoft.com.

I have a Windows Server 2003 R2 Terminal Server, and have a pretty
restrictive GPO applied to it. The users are restricted from most system
tasks, and I set "Run only allowed Windows applications" under User
Configuration\Administrative Templates\System. I have a list of .exe files
set that they are able to run, and they are prevented from running
anything
else.

MS Office 2003 is installed on this Terminal Server and the users are able
to launch all of those applications. This was working fine for awhile, but
after we installed some Microsoft Updates earlier this year, we found that
users could not click on links in the Outlook email messages and open
files
off of their mapped drives. For example, if a user has a hyperlink in
their
email message to G:\CustomerFolder\Customer1.xls, they are not able to
click
on it and open it directly. However, if they browse to that location
through
Windows Explorer or MS Excel, they can open the file without any problems.

If I set the "Run only allowed Windows applications" to "Not configured",
the users no longer have any problems opening the links, so I think there
might be something in there that I need to change, but I haven't been able
to figure out what. I've tried adding G:\*.*, \\server\share,
file://server,
and even the full path to one of the files that we're trying to open, but
that doesn't seem to work.

Does anyone have any suggestions on how I can open this up so that the
users
can just click on the links?