Is there a better Deployment Package tutorial?

[rinks]

We are in the process of trying to utilize more features of Lansweeper to justify the increasing costs. One way is to use the deployment package feature. It was set up to test two things, one just a basic pop-up text in CMD, and the other to remotely install LsAgent. Well, the guide for Deployment Packages isn't great. We created a read access user in AD specifically for deploying packages, added it to the PackageShare folder on the server, added the credentials to Deployment > Security options, but we constantly get an error that the network path was not found for any machine we try to deploy to. From the error, we get:

Path:\\ {computername}.{domain}\C$. |Credential(s): Global ({domain}\Lansweeper)

We aren't using the credentials for {domain}\Lansweeper, we are using a purposely made user, {domain}\Lansweeperdeployment for the credentials, so does this error mean it is trying to use the Lansweeper credential?

It does not matter if we do System, Scanning Credentials, or Currently Logged On, everything throws the same error. The user is added to the security roles to access all computers in our domain. The Lansweeperdeployment credential is in the Security options. The same user has access to the folder on the server.

Followed the deployment requirements:

• All computers are running non-Home version of Windows 10.
• Targets resolve to an IPv4 address and DNS resolution is successful
• Task Scheduler is running
• Remote Registry is running
• Remote administration exception is enabled for agentless scanning
• Remote Schedule Tasks Management rule is enabled and allowed
• Valid scanning credential with admin privileges is added
• Has access to deployment share
• Package is in the DefaultPackageShare$ folder (tested folder access with the created credential and was able to open the folder just fine)

The deployment logs go from Gathering information to Performing preliminary checks, and then errors out with the above mentioned error.

Is there a better step-by-step walkthrough for setting up deployment packages than what is on the forum? I also noticed many are having issues with deployment packages as of the latest update, which we have, so I'm also wondering if it is set up right but just completely broken right now.

[pryan67]

Have you taken one of the deployments shared here and tried it?   

[rinks]

I've tried them, but they do not work, as well as some of the built-in deployments. The main one we are using for testing is just sending the popup via command. The package we have is:

Action: Command

Step name: Test Popup

Command: msg.exe * This is a Lansweeper deployment test dialog. No changes have been made to the computer at this time. Thank you!

Success codes: 0,1641,3010

Action on success: Stop (Success)

Action on failure: Stop (Failure)

The assistance offered by Lansweeper support was "If you can reach and scan your devices, then you should be able to deploy." 😑

[pryan67]

Well that deployment certainly SHOULD work 🙂  

And support is correct...if you can reach and scan your devices you SHOULD be able to deploy.  However, as we all know the word "should" isn't the same as "can".   

You've checked the firewall rules it looks like.   

Can you access the C$ share manually using the scanning credentials you use for deployment?   Have you tried giving explicit local admin rights to that user on the  workstation as a test?

[rinks]

Yep, can navigate to the share folder with no issue on either set of credentials. The guide said not to allow administrator access but I made one anyways and tried that, still didn't work. We've been through ports and firewalls. I've even tested it on my own device/credentials which have full admin rights to just about everything and still couldn't get it to work.

This has since then been put on the backburner for now. 

Edit: Even checked to make sure there were deployment threads were assigned as we had dropped that to 0 since we never used deployments before. 

[pryan67]

Dang....

You can navigate to the share folder, but what if you tried logging into a computer with the deployment credentials and tried to browse to the target endpoint C$?  \\targethostname\c$ I mean.  

[rinks]

Yes, both the created credentials used in Lansweeper on a device, can access C$ and my own credentials in Lansweeper as I can access C$ as well as scan using my credentials without issue. Just something somewhere along the line isn't matching up, likely on the Infrastructure side, but they  have attested to the required port/firewall configurations being correct.

[clickes2000]

in our Situation was  Parameter /S the Error , after delete it the deployment working normal. 

[FrankSc]

Dear, 
The current documentation we have is indeed based on generic packages. Every customer may have different package types to deploy, like installers, commands, scripts etc. Therefor it is rather difficult to accommodate with all different scenario's or use cases in the documentation.
In general, we see that sharing different scenario's or deployment errors in the community is a real help for the users.  
You could also contact the Support team; maybe they can provide you with some tips & tricks to get certain packages to work. Although they may be also limited in comprehending the specific setup or all steps in the package.

[clickes2000]

Hallo 

i hope you could find the solution, We have also the same problem. Lnasweeper need better Documentaion. 

Lansweeper Connection Tester 7.1.0.1

Scanning Lansweeper Service (on this machine)..

Status: Running

Version: Executable not found

Pinging KUW033

Ping ok.

Scanning TCP ports..

135 open (EPMAP)

139 open (NetBIOS Session Service)

445 closed (SMB)

Checking DNS..

KUW033 resolved to: 192.168.20.10

If this is not correct, please check for DNS problems.

Checking reverse DNS..

192.168.20.10:

KUW033.net

Scanning netbios (UDP)..

Could not scan netbios

Scanning netbios (445)..

Could not scan netbios

Scanning Active Directory..

operatingSystem: Windows 11 Pro

operatingSystemVersion: 10.0 (22631)

Scanning WMI..

Computername: KUW033

If this is not correct, please check for DNS problems

Operating system: Microsoft Windows 11 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

Task was successfully scheduled

Task ran successfully

Task Deleted

Warning: Lansweeper service not found!

Done.

Result: Package timeout reached. Stopping deployment executable: Successful. Timeout: (900sec). Credential: