Sysadmin

7640 readers

22 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:
!lemmy@lemmy.ml
!lemmyworld@lemmy.world
!lemmy_support@lemmy.ml
!support@lemmy.world

founded 1 year ago

MODERATORS

DarraignTheSane@lemmy.world

00Lemming@lemmy.world

L3s@lemmy.world

Windows deployment (lemmy.ml)

submitted 1 year ago by electric_nan@lemmy.ml to c/sysadmin@lemmy.world

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

[–] SheeEttin@lemmy.world 3 points 1 year ago (7 children)

I haven't done imaging for a few years now, but it used to be that you needed at least one volume license for imaging rights. (The license center only allows you to buy five licenses, but you can do one VL and four of the cheapest thing you can find.) I think you should be able to use the builtin OEM licenses for activation.

Personally, I wouldn't bother messing with custom images, unless there's a particular setup you want them all to have right away. I'd just use a plain image and script everything else. I'd use WDS if you want to use the full Windows stack, or FOG if you prefer.

[–] electric_nan@lemmy.ml 1 points 1 year ago (6 children)

Thanks, I'll look into the feasibility of scripting. I don't think I can use WDS since we use a local AD.

[–] TheBSGamer@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (1 children)

Also to piggy back off the WDS thing, SCCM (I believe) is included with Windows Volume Licensing so you could also use Task Sequences as a route to image. I built our whole imaging setup with it and only had to build one baked image because the OS needed like 120 pieces of software or something crazy like that. That's obviously not all that it does but I prefer the flexibility of SCCM's management alongside the imaging.

Edit: yeah it's included if you use Microsoft 365.

[–] electric_nan@lemmy.ml 1 points 1 year ago* (last edited 1 year ago) (1 children)

Thanks, that does look powerful, but also big and complicated. We are at most provisioning a few boxes a week, and I am really just looking for the easiest way to not have to set them all up from scratch. As the company grows, I can see the benefit to learning and utilizing a tool like SCCM.

[–] TheBSGamer@lemmy.world 2 points 1 year ago

Agreed. Wasn't sure of your work load. I would stick with WDS in that case then.

load more comments (4 replies)