
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-18-2014 08:25 PM
Hi,
We have just noticed that we are no longer able to connect to the C$ and ADMIN$ from the advanced actions list.
I have checked the location and permissions of the file and manually accessing the locations and nothing seems to be amiss.
Could you please advise.
thank you
We have just noticed that we are no longer able to connect to the C$ and ADMIN$ from the advanced actions list.
I have checked the location and permissions of the file and manually accessing the locations and nothing seems to be amiss.
Could you please advise.
thank you
Labels:
- Labels:
-
Archive
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-10-2014 02:22 PM
Thanks for the info, we now have this back up and running.
It turns out that we had Lansweeper & Lansweeper5 folders. We were updating one and running from the other.
Rooky mistake, but thanks for the assistance.
It turns out that we had Lansweeper & Lansweeper5 folders. We were updating one and running from the other.
Rooky mistake, but thanks for the assistance.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2014 01:45 AM
We were also unable to use Open C$ and Open Admin$ custom actions
For us it looks as though it is a problem with windows explorer.
We are using Explorer++ instead
copy the executable to your lansweeper share
these custom actions should work
{actionpath}Explorer++.exe \\{smartname}\Admin$
{actionpath}Explorer++.exe \\{smartname}\c$
Works well for our environment
If logged in as an elevated user Open C$ and Open Admin$ custom actions are no problem here
We are logged in as a restricted user
We are using alternate elevated credentials to launch the browser
We have two domains with an elevated user for each domain
Hope this helps someone
EDIT: It turns out that our problem was associated with group policy not properly applying to the clients. But Explorer++ worked without the policy on the client.
For us it looks as though it is a problem with windows explorer.
We are using Explorer++ instead
copy the executable to your lansweeper share
these custom actions should work
{actionpath}Explorer++.exe \\{smartname}\Admin$
{actionpath}Explorer++.exe \\{smartname}\c$
Works well for our environment
If logged in as an elevated user Open C$ and Open Admin$ custom actions are no problem here
We are logged in as a restricted user
We are using alternate elevated credentials to launch the browser
We have two domains with an elevated user for each domain
Hope this helps someone

EDIT: It turns out that our problem was associated with group policy not properly applying to the clients. But Explorer++ worked without the policy on the client.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-19-2014 10:37 AM
The file shellexec.vbs should be located in the lansweeper\actions folder.
You can reinstall the website to get all the latest actions.
You can reinstall the website to get all the latest actions.
