Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-12-2019 06:14 PM
We recently started upgrading our environment to windows 10 and noticed that our Lansweeper software deployment packages are now failing with the following: Preliminary checks failed! Task Service Error. The network path was not found. (Exception from HRESULT: 0x80070035) Credential: (jjjjjjjj) ShareCredential: (kkkkkkkkk).
Still works fine on windows 7 machines. Any help or feed back would be appreciated.
Thanks!
Still works fine on windows 7 machines. Any help or feed back would be appreciated.
Thanks!
Labels:
- Labels:
-
General Discussion
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-15-2019 08:01 PM
Thanks for the response. It wasn't my issue but it did help me solve the problem. Once I set remote registry to manual start I got a slightly different error message and that led me to the solution which was:
On Windows 10 machines you need to enable Remote Scheduled Tasks Management.
You will then be allowed to deploy software packages to Windows 10 machines.
On Windows 10 machines you need to enable Remote Scheduled Tasks Management.
You will then be allowed to deploy software packages to Windows 10 machines.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2019 10:24 AM
jblamire wrote:
Thanks for the response. It wasn't my issue but it did help me solve the problem. Once I set remote registry to manual start I got a slightly different error message and that led me to the solution which was:
On Windows 10 machines you need to enable Remote Scheduled Tasks Management.
You will then be allowed to deploy software packages to Windows 10 machines.
This fixed it for me. It helped me to run "%ProgramFiles(x86)%\Lansweeper\Actions\testconnection.exe" from the LanSweeper server to find out what the problem was.
I had to enable the firewall rule "Remote Scheduled Tasks Management (RPC)".
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-14-2019 05:45 PM
The error 'The network path was not found' is given back when Lansweeper is unable to access the C$ of the machine where the package is being deployed on. Being able to access C$ on the target computer is a requirement in order to successfully deploy: https://www.lansweeper.com/knowledgebase/deployment-requirements/
Ensure that the scanning credentials submitted under Scanning\Scanning Credentials in the Lansweeper web console have access to C$ on the target machines, as Lansweeper uses this folder to store an executable called RemoteDeployment that will run the deployment. If access to C$ is denied, your deployments will fail. You can test this by browsing to \\hostname\c$ from the Lansweeper server to the target computer with a failed deployment using the same credentials as you are using to deploy.
You can also check the following articles on how to enable admin shares:
https://support.microsoft.com/en-us/help/946937/network-location-cannot-be-reached-when-accessing-shares
https://superuser.com/questions/328461/how-to-access-c-share-in-a-network
Ensure that the scanning credentials submitted under Scanning\Scanning Credentials in the Lansweeper web console have access to C$ on the target machines, as Lansweeper uses this folder to store an executable called RemoteDeployment that will run the deployment. If access to C$ is denied, your deployments will fail. You can test this by browsing to \\hostname\c$ from the Lansweeper server to the target computer with a failed deployment using the same credentials as you are using to deploy.
You can also check the following articles on how to enable admin shares:
https://support.microsoft.com/en-us/help/946937/network-location-cannot-be-reached-when-accessing-shares
https://superuser.com/questions/328461/how-to-access-c-share-in-a-network
