Sysadmin

7643 readers

21 users here now

A community dedicated to the profession of IT Systems Administration

No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
[email protected]
[email protected]
[email protected]
[email protected]

founded 1 year ago

MODERATORS

DarraignTheSane

00Lemming

L3s

Windows deployment (lemmy.ml)

submitted 1 year ago by [email protected] to c/sysadmin

19 comments fedilink hide all child comments

I'm new to Windows deployments, and I need some help. I've gotten as far as setting up a new system from a Windows 11 image downloaded from MS, configuring it/installing software, and then running sysprep. I made a WinPE boot thumbdrive, but I'm stuck at capturing the Windows image part. Part of my problem is that I'm trying to make this in a VM. Is that more trouble than it's worth?

Is there an easier way to do this? I've seen people saying I can use Linux tools like Clonezilla, which sounds good to me, since I'm very comfortable with Linux-- but I read that might cause problems. One thing mentioned was licensing.

I would be deploying these images 100% onto Lenovo machines that we purchase from CDW, so I'm not sure how licensing would work. Is the license tied to the MAC? Will they auto-register once I boot them with the new image?

Thanks for anyone that takes the time to help me understand this :)

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 1 year ago (1 children)

Just to add more confusion, we are removing MDT from all customers and replacing with intune using the already created json templates we have plus then also deploying chocolatey with intune then calling powershell from intune to install other software. I'd say only 20% of our customers have on-premise AD the other 80% are all Microsoft Business Premium licensed unless over 300 staff, and that's why we have been transitioning customers to only that for the last few years.

MDT is the right tool for AD on premises though so don't be dissuaded from that, just more, you should know.

[–] [email protected] 1 points 1 year ago (1 children)

Can I ask why chocolatey and not just installed via policy/company portal? I'm not our Intune guy so I don't know much about the limitations.

[–] [email protected] 2 points 1 year ago

Oh because if an application doesn't exist natively in azure, ie not a MS Store app, then you can only deploy by uploading the msi which of course is one version. At an MSP with thousands of devices in dozens if not a hundred tenancies, and new software versions being released daily, you need something that will update all that.

Chocolatey is just for the poorer customers, a best effort, immybot for soe management though if the customer is full. Whenever Microsoft finishes getting their own repository fixed though, using winget could be the new chocolatey. Right now it doesn't do patching or at least it didn't 12 months ago. It could install and report but not update.

So thinking of solution life cycle you want something that doesn't need tons of manual innervation, and you can use PDQ or chocolatey or immybot or whatever. Microsoft can handle its first party software suites and rmm deployment but 3rd party at this stage is just not good enough.

Hope that helps