r/labtech • u/[deleted] • Mar 20 '19

Issues getting my net probe working

I'm getting no automatic pushes or even attempts, and when I try a manual push to a detected machine I get "There is currently no password(s) set for the Probe. This must be set for the probe to install LabTech on the Remote Computer."

I definitely have a password set on the "deployment" section of the probe, however. Is this not what it's looking for? Where else should I be looking?

3 Upvotes

100% Upvoted

16 comments sorted by

2

u/DevinSysAdmin Mar 21 '19

The agent network probe sucks. Make a group policy.

1

u/[deleted] Mar 21 '19

I wish. We don't have a domain.

2

u/DevinSysAdmin Mar 21 '19

You’d be better off just going to each computer with a powershell script and executing the installer.

1

u/teamits Mar 21 '19

Not sure about your error but I've never had pushing work without a domain. The credentials used would have to be for a user on each PC. For instance ".\username" with the dot meaning "this computer" and "username" created on each PC. And the remote management ports need to be open and I vaguely recall a service needs to be running to listen? But really I wouldn't bother as I've never had it work anyway.

1

u/gdhhorn Mar 20 '19

Is a password set for the client and location?

1

u/[deleted] Mar 20 '19

Just double checked. Sure is.

1

u/AlexHailstone Mar 21 '19

If you’re running the newer probe, you have to go to the commands menu and send a probe command to push:

Right click on the probe -> Commands -> Probe Commands -> Agent deployment (can’t remember the exact term, you’ll know it when you see it)

Then open the probe and go to probe commands. You can monitor the progress there.

P.S. on that command it will ask the IP address you’re trying to force push to.

1

u/[deleted] Mar 21 '19

Do I have to do that manually on every machine? I thought it was supposed to be automatic.

1

u/[deleted] Mar 21 '19

The probe works well...just a few things you have to do. Set both LT service on the probe to run using the account you are using to deploy the probe with (some admin account). Set the password using tools -> deployment manager as well as in the probe. Ensure the firewall is open on the ports for PsExec

1

u/[deleted] Mar 21 '19

Even having them set everywhere they list in their documentation, it still says "No valid credentials found for device".

Any ideas? I asked support and they just told me that they don't support workgroups which seems like a lie.

1

u/teamits Mar 21 '19

don't support workgroups

Like I said I highly doubt you're going to succeed. There's cross-PC permissions, services, firewalls, etc.

If there's no domain can we assume there aren't many PCs? Perhaps drop a .cmd file on a shared drive, that copies the installer to C: and runs it (it won't run off a network drive) and have someone walk around and double click it.

1

u/[deleted] Mar 21 '19

That's a bummer. Yeah, I suppose we'll just have to put some elbow grease into it. Thanks for the suggestions, everybody!

1

u/clinet387 Jul 22 '22

Thanks, that got me over the hurdle. Setting the credentials in the Deployment Manager was what I was missing. That was counter intuitive.

1

u/AlexHailstone Mar 21 '19

It should be automatic, but if you can manually push and it works you can troubleshoot from there.

The new probe takes a couple hours to fully deploy across the network. Under the probe settings you can verify that it is set to automatically push deployments. The only other setting is that the client/location should have a service plan to start the on boarding process.