Werbung: SecurityConsole.de verwaltet Ihre Computer mit Security Essentails aus der Cloud!
30 Tage kostenfrei testen und 20% Rabatt für Ihre Bestellung mit Promocode: WBF2685582
(Promocode gültig bis 31.12.2011)

Group:  English: General » microsoft.public.windows.group_policy
Thread: Restriction on Windows Applications preventing links in Outlook

HTVi
TV Discussion Newsgroups

Restriction on Windows Applications preventing links in Outlook
"Steele" <ksteele[ at ]summitnetworking.net> 11/20/2008 4:15:28 PM
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?


Re: Restriction on Windows Applications preventing links in Outlook
<andy_c[ at ]hotmail.com> 12/5/2008 2:14:58 PM
the updates you talk of must have altered outlook.exe. Remove it from the
list of .exes, save the list and readd outlook.exe.


"Steele" <ksteele[ at ]summitnetworking.net> wrote in message
news:uYGiXvySJHA.3668[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text]
>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?
>


Re: Restriction on Windows Applications preventing links in Outlook
"Steele" <ksteele[ at ]summitnetworking.net> 12/23/2008 6:52:30 PM
I tried that, and it didn't make a difference.

Any other thoughts?

<andy_c[ at ]hotmail.com> wrote in message
news:%23jyNcPuVJHA.2080[ at ]TK2MSFTNGP06.phx.gbl...
[Quoted Text]
> the updates you talk of must have altered outlook.exe. Remove it from the
> list of .exes, save the list and readd outlook.exe.
>
>
> "Steele" <ksteele[ at ]summitnetworking.net> wrote in message
> news:uYGiXvySJHA.3668[ at ]TK2MSFTNGP03.phx.gbl...
>>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?
>>
>
>


Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net
Suche nach Orten, Städten, Postleitzahlen, Vorwahlen, Kfz-Kennzeichen