→ Having trouble accessing our new support portal or creating a ticket? Please notify our team here

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
darrenh
Engaged Sweeper II

Hi

I am trying to use deployment packages for the first time.  I already tweaked our client windows firewall settings via GPO in a test OU as port 135 and agentless was blocked, all that is now working.

The server can connect to the pc using the scanning credentials, including accessing the admin c$ share, however the last test fails for the task scheduler, plus I get the error below when I try and deploy:
using testconnection.exe:

Lansweeper Connection Tester 7.1.0.1
 
Scanning Lansweeper Service (on this machine)..
Status: Running
Version: 10.6.0.0
 
Pinging testlappytappy
Ping ok.
 
Scanning TCP ports..
135 open (EPMAP)
139 open (NetBIOS Session Service)
445 open (SMB)
 
Checking DNS..
testlappytappy resolved to: 192.168.x.y
If this is not correct, please check for DNS problems.
 
Checking reverse DNS..
192.168.x.y:
testlappytappy.testdomain
Scanning netbios (UDP)..
Computername: TESTLAPPYTAPPY
Domain: TEST
 
Scanning netbios (445)..
Could not scan netbios (i have netbios disabled on all clients, as we use full dns).
 
Scanning Active Directory..
operatingSystem: Windows 10 Pro
operatingSystemVersion: 10.0 (19044)
 
Scanning WMI..
Computername: TESTLAPPYTAPPY
If this is not correct, please check for DNS problems
 
Operating system: Microsoft Windows 10 Pro
\root\cimv2 Remote WMI access test OK
 
Operating system: Windows 10 Pro 
\root\default Remote WMI access test OK
 
Checking C$ Access
Deployment Folder: OK
Access Rights: OK
 
Checking Task Scheduler
The network path was not found. (Exception from HRESULT: 0x80070035)
 
Done.

Result: Deployment ended: Incorrect function. Stop(Failure). Credential: (TEST\lansweeper). ShareCredential: (lsdeploy).
Command: "\\testserver\testshare\windowsclient\Setup.exe" -silent INSTALLLEVEL=100

the credentials are all ok, and work to access the share. lsdeploy is a normal domain user per the recommendations of using deploy as password is a reversible hash.  lansweeper user itself which is scanning credential has admin rights.

 

1 ACCEPTED SOLUTION
darrenh
Engaged Sweeper II

I figured it out. remote registry was disabled in GPO, even though the script had tried to enable it.

View solution in original post

6 REPLIES 6
darrenh
Engaged Sweeper II

I figured it out. remote registry was disabled in GPO, even though the script had tried to enable it.

Obi_1_Cinobi
Lansweeper Tech Support
Lansweeper Tech Support

Hello there!

Glad to hear that! Happy deploying!

darrenh
Engaged Sweeper II

error now is Result: Deployment ended: Unknown error (0xffffffff). Stop(Failure). Credential: (TEST\lansweeper). ShareCredential: (lsdeploy).
Command: "\\testserver\testshare\windowsclient\Setup.exe" -silent INSTALLLEVEL=100

Obi_1_Cinobi
Lansweeper Tech Support
Lansweeper Tech Support

Hello there!

If you require further assistance, you can reach out to support: https://www.lansweeper.com/contact-support/

Obi_1_Cinobi
Lansweeper Tech Support
Lansweeper Tech Support

Hello there!

 
One of the requirements for being able to successfully perform deployments on remote computers is the ability to access the Task Scheduler on these remote computers. The error you're receiving indicates that the task scheduler can currently not be accessed remotely.
 

Hi, i did read that and ran the vbs script as an admin on the win10 client.

will take another look to see if there's anything else required.

the win10 firewall is also entirely disabled on the client temporarily.