Unable to "SEE" .bat files on unc share

[Jaan]

I'm really confused as i've never seen this behaviour before. I've also put in the server 2016 section as i'm able to replicate this on both windows 7 and 10 machines to my server 2016 file server share.

 

Sorry if it's in the wrong place

 

Ok long story short, i've been trying to deploy a av client via an ad startup script and it's been failing to install. it uses a .bat file located on a hidden unc share that all users have access to.

 

If i launch (or try) to launch the .bat via unc path i get an this location (or rather file) doesn't exist error.

 

If i launch the .bat file direct from a mapped network location it works fine.

 

see the screenshots below, both locations are on the same server in the same share location. The only difference is that the one where 3 files are visible i've used a mapped drive to view the location. And the one showing 2 files is using a unc path.

 

Any Ideas?

 

 

[computer_expert]

I see you have a space in the path of your network share. Have you put quotes around the path in the batch file?

 

for example:

"\\server\file share\path1\path 2\program.exe"

[Jaan]

I see you have a space in the path of your network share. Have you put quotes around the path in the batch file?

 

for example:

"\\server\file share\path1\path 2\program.exe"

 

Yeah like i say the .bat file works fine when i launch it directly from the a mapped drive location.

 

if i \\ into the server share i can't even see the .bat file.

 

as per the screenshots

[Davit2005]

If this is a startup script or logon script you could put in the sysvol share or a sub folder. If you are running AD.

 

Normally when you create these gpo it gives you the opportunity to do this.

Edited January 24, 2018 by Davit2005

[Jaan]

Sorry guys, i think i've over complicated my description of the issue i'm having.

 

To clarify, i have managed to get the client av software to install (typo on the .exe i was trying to launch) one of those days.

 

What leaves me baffled is that i can't "see" bat files on a server share i access via a unc path. I can only "See" them via a mapped network drive. as per the screenshots

[Arthur]

What leaves me baffled is that i can't "see" bat files on a server share i access via a unc path. I can only "See" them via a mapped network drive. as per the screenshots

It sounds like it might be related to this...

 

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee844140(v=ws.10)

 

If a user is logged on to a computer running Windows Vista or Windows 7 and if UAC is enabled, a program that uses the user's filtered access token and a program that uses the user's full administrator access token can run at the same time. Because LSA created the access tokens during two separate logon sessions, the access tokens contain separate logon IDs.

 

When network shares are mapped, they are linked to the current logon session for the current process access token. This means that if a user uses the command prompt (cmd.exe) together with the filtered access token to map a network share, the network share is not mapped for processes that run with the full administrator access token.

 

To work around this problem, configure the EnableLinkedConnections registry value.

[mavhc]

Offline files, or, but not in your case, multiple DFS shares

[Accura2k7]

sharing permissions? It would be thing only thing I can think of that could do this?

 

Can you UNC to it on the server?

 

How about a \\server\c$\batfiles\something.bat path rather than the share name?

[Jaan]

This seems to have resolved itself overnight. Totally baffled.