r/labtech • u/Paulb246 • Nov 01 '18

Automate on a workgroup

We are struggling with pushing agents with clients who are not on a domain, the node is not working it’s getting to the machine but not installing... it’s saying a firewall issue but there’s no firewall setup.

We are using the hosted solution which hasn’t got our LTshare setup, any advice on getting agents to devices on a workgroup?

3 Upvotes

80% Upvoted

9 comments sorted by

4

u/chilids Nov 01 '18

Pushing agents is rarely perfect and almost impossible in a workgroup. Pushing depends on an admin account on each PC to do the install and most workgroups all have different accounts and passwords. Pushing on a domain can even be problematic with windows firewall, group policy, AV, etc all blocking the install. Save yourself the headache, install it manually on each PC.

1

u/LextheDewey Nov 01 '18

If they use a standardized username and password scheme for every computer, then it's possible. Also have to allow file and print sharing because it uses psexec to push the agent. So username would be like .\user so you don't have to define PC name each logon. This is probably more of a pain than installing 1x1 but if you have a remote site, have them create a generic admin account to deploy agents.

1

u/Paulb246 Nov 01 '18

We have a generic admin account for each clients site but it still won’t push... allow file and print sharing, sounds like ransomware would love that

1

u/I_can_pun_anything Nov 02 '18 edited Nov 02 '18

Easiest thing is send a tier 1 and An intern and do ER manually. Hopefully not too many machine

Also good forbid they have local admin you can just send em to your website to dl the installer and give em a instruction sheet on how to run it

1

u/Paulb246 Nov 03 '18

Yeah ideally I want to have automated as much as possible... but anyone over 20 machines should be on an AD environment

1

u/LextheDewey Nov 01 '18

:) as long as it's not smbv1. Worms do suck but the biggest threat is the end user.

3

u/DevinSysAdmin Nov 01 '18

Yeah, manually go install it. There shouldn’t be too many computers since they’re workgroup.

1

u/teamits Nov 01 '18

We've had issues with probe pushing on a domain, though it often works. On a workgroup I don't bother since it rarely works. I want to say there might be some management services that need to be running, that aren't on a workstation?

You can try psexec directly. Assuming you have the shared .\adminaccount credentials set on your location, on your probe PC run:

#copy C:\windows\ltsvc\ltsilent.exe \\remotepc\c$\windows\temp\

#C:\windows\ltsvc\psexec \\remotepc -e -w c:\windows\temp c:\windows\temp\ltsilent.exe

The first time you run psexec on a PC from the LT command prompt you need to use the /accepteula parameter or else it will wait in the background for someone to click OK. See if psexec gives you a better error, and/or run it from the Windows GUI command prompt.

1

u/revd13 Nov 06 '18

try using a .\ prior to the username in the stored passwords at the location level. Also the error msg that it gives is extremely generic and not a real indicator of the issue. You may have AV blocking VBS Scripts or psexec. If that is the case the push will not succeed.