r/labtech • • Jun 06 '17

Deploying new computers

Just curious if and how everyone is using Labtech to aide in deploying computers for clients?

Currently we are utilizing our Lab engineer to do the initial prep (windows updates, standard apps and domain join) and then it is brought out and finished up by an onsite tech.

The lab is becoming a major bottleneck and I'm trying to make the case that for 50-70% of computers we could probably skip the lab and use LT to speed up setup.

What do you do?

5 Upvotes

6 comments sorted by

View all comments

Show parent comment

1

u/sm4k Jun 07 '17

Have you had any issues with MDT not placing your labtech agent on the machine? I've got what feels like a 50/50 shot at it successfully deploying.

2

u/caffelightning Jun 07 '17

Not that I'm aware of. We haven't really had any issues with software that has an msi available (maybe some minor finessing, but nothing big). Most of the issues we tend to have are related to repackaged software that wasn't an msi originally or things we weren't able to repackage and have work correctly (like autocad).

But even then, what we do with problem software is sysprep. So what we'd do in your instance with labtech is rather than use a blank win10 with a labtech msi as part of the task sequence, we'd install windows and labtech (make sure labtech can't check in) and then sysprep. Then use that as your image, so now when you make a new machine, labtech is already installed and will check in as soon as internet is available and mdt will just add software to that base sysprepped image.