Running an Executable from a Mapped Drive - No Permissions

I have a 2003 std server sp2 installed as a File Server on a domain. I have
mapped several drives to programs that I want to install on this server, but
when I click on the Setup File it tells me: "Windows cannot access the
specifed device, path, or file. You may not have the appropriate permissions
to access the item."

I am signed on as the administrator and have added just about every right I
can find to both my 2003 server and the server hosting the program. Any
suggestions?

In news:50B45F07-AB71-4D8E-8EF5-(E-Mail Removed),
gthomps07876 <(E-Mail Removed)> typed:
> I have a 2003 std server sp2 installed as a File Server on a domain.
> I have mapped several drives to programs that I want to install on
> this server, but when I click on the Setup File it tells me: "Windows
> cannot access the specifed device, path, or file. You may not have
> the appropriate permissions to access the item."
>
> I am signed on as the administrator and have added just about every
> right I can find to both my 2003 server and the server hosting the
> program. Any suggestions?

Is it actually mapping the drive? Can you open that drive letter and
physically run the file?


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Having difficulty reading or finding responses to your post?
Instead of the website you're using, try using OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. Anonymous access. It's free - no username or password
required nor do you need a Newsgroup Usenet account with your ISP. It
connects directly to the Microsoft Public Newsgroups. OEx allows you
o easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject. It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

"Quitting smoking is easy. I've done it a thousand times." - Mark Twain

I am having EXACTLY the same problem and am going cross-eyed trying to figure
it out. Does anyone have any suggestions?

In answer to the MVP, yes, the drive really is mapped -- I can open up files
and read them from the mapped drive, I just can't run executables.

Lee Silverman
(E-Mail Removed)

"gthomps07876" wrote:

> I have a 2003 std server sp2 installed as a File Server on a domain. I have
> mapped several drives to programs that I want to install on this server, but
> when I click on the Setup File it tells me: "Windows cannot access the
> specifed device, path, or file. You may not have the appropriate permissions
> to access the item."
>
> I am signed on as the administrator and have added just about every right I
> can find to both my 2003 server and the server hosting the program. Any
> suggestions?

In news:8E5D290A-5C24-4D0D-A513-(E-Mail Removed),
lsilverman <(E-Mail Removed)> typed:
> I am having EXACTLY the same problem and am going cross-eyed trying
> to figure it out. Does anyone have any suggestions?
>
> In answer to the MVP, yes, the drive really is mapped -- I can open
> up files and read them from the mapped drive, I just can't run
> executables.
>
> Lee Silverman
> (E-Mail Removed)

Interesting issue. I haven't come across this, therefore I don't have a
solution. However I have seen issues mapping to the volume share (c$, etc)
that has caused problems whereas when I specicically share a folder out with
Share: Admins FC and on the Sec tab: Admin FC it will work. I think it has
something to do with a DCOM issue, but I can't verify this.

Ace

I found a solution using group policies for the domain. First, the
fileserver needs to be added to the intranet security zone. Why it's not
already in the intranet security zone is beyond me, but after I added
\\server to the zone, the error went away. Instead of getting "You don't
have access..." A dialog popped up asking me if I trusted the publisher of
the application. Definite progress.

However, since I'm trying to run this program in a script, the dialog hung
the script in its tracks. About two hours worth of digging later, I
discovered that the group policy objects under user
config/windows/components/.../attachment manager (I forget exactly where it
is but it's in there somewhere) control how clients deal with executables of
different levels of risk. When I added ".exe" to the list of suffixes with
"Moderate" risk instead of high risk (and ran gpupdate on the client) the
dialog box stopped appearing. According to the doc where I discovered this,
if the source of the .exe file is in the "trusted" or "intranet" zones, the
behavior is no dialog; if the source is in the "internet" zone, the
"untrusted publisher" dialog still pops up.

Hope that helps everyone else who runs into this problem!

Lee Silverman

"Ace Fekay [MVP]" wrote:

> In news:8E5D290A-5C24-4D0D-A513-(E-Mail Removed),
> lsilverman <(E-Mail Removed)> typed:
> > I am having EXACTLY the same problem and am going cross-eyed trying
> > to figure it out. Does anyone have any suggestions?
> >
> > In answer to the MVP, yes, the drive really is mapped -- I can open
> > up files and read them from the mapped drive, I just can't run
> > executables.
> >
> > Lee Silverman
> > (E-Mail Removed)
>
> Interesting issue. I haven't come across this, therefore I don't have a
> solution. However I have seen issues mapping to the volume share (c$, etc)
> that has caused problems whereas when I specicically share a folder out with
> Share: Admins FC and on the Sec tab: Admin FC it will work. I think it has
> something to do with a DCOM issue, but I can't verify this.
>
> Ace
>
>
>

In news:3815E2A4-26EA-4F24-ABBF-(E-Mail Removed),
lsilverman <(E-Mail Removed)> typed:
> I found a solution using group policies for the domain. First, the
> fileserver needs to be added to the intranet security zone. Why it's
> not already in the intranet security zone is beyond me, but after I
> added \\server to the zone, the error went away. Instead of getting
> "You don't have access..." A dialog popped up asking me if I trusted
> the publisher of the application. Definite progress.
>
> However, since I'm trying to run this program in a script, the dialog
> hung the script in its tracks. About two hours worth of digging
> later, I discovered that the group policy objects under user
> config/windows/components/.../attachment manager (I forget exactly
> where it is but it's in there somewhere) control how clients deal
> with executables of different levels of risk. When I added ".exe" to
> the list of suffixes with "Moderate" risk instead of high risk (and
> ran gpupdate on the client) the dialog box stopped appearing.
> According to the doc where I discovered this, if the source of the
> .exe file is in the "trusted" or "intranet" zones, the behavior is no
> dialog; if the source is in the "internet" zone, the "untrusted
> publisher" dialog still pops up.
>
> Hope that helps everyone else who runs into this problem!
>
> Lee Silverman

That is great that you found it. How did you come across that? Did you
follow an article or another post elsewhere?

Also, if you can be more specific with the section in the GPO for others
benefit, that would be great.

Thanks and glad you found it.

Ace

In news:3815E2A4-26EA-4F24-ABBF-(E-Mail Removed),
lsilverman <(E-Mail Removed)> typed:
> I found a solution using group policies for the domain. First, the
> fileserver needs to be added to the intranet security zone. Why it's
> not already in the intranet security zone is beyond me, but after I
> added \\server to the zone, the error went away. Instead of getting
> "You don't have access..." A dialog popped up asking me if I trusted
> the publisher of the application. Definite progress.
>
> However, since I'm trying to run this program in a script, the dialog
> hung the script in its tracks. About two hours worth of digging
> later, I discovered that the group policy objects under user
> config/windows/components/.../attachment manager (I forget exactly
> where it is but it's in there somewhere) control how clients deal
> with executables of different levels of risk. When I added ".exe" to
> the list of suffixes with "Moderate" risk instead of high risk (and
> ran gpupdate on the client) the dialog box stopped appearing.
> According to the doc where I discovered this, if the source of the
> .exe file is in the "trusted" or "intranet" zones, the behavior is no
> dialog; if the source is in the "internet" zone, the "untrusted
> publisher" dialog still pops up.
>
> Hope that helps everyone else who runs into this problem!
>
> Lee Silverman

Lee, can you provide a link to the doc you found please? Thanks!

Just to add...

For others out there, after a quick look, I found these settings under this
section:

User Configuration\Administrative Templates\Windows Components\Attachment
Manager:

Setting,State
Default risk level for file attachments,Not configured
Inclusion list for high risk file types,Not configured
Inclusion list for moderate risk file types,Not configured
Inclusion list for low file types,Not configured
Trust logic for file attachments,Not configured
Do not preserve zone information in file attachments,Not configured
Hide mechanisms to remove zone information,Not configured
Notify antivirus programs when opening attachments,Not configured

Double click on the "Inclusion list for moderate risk file types", enable
it, and type in .exe.


Ace