Home
Join

27 Replies

  • Sorry.

    I gave up on Windows long ago ;)

    Linux at work is fine (along with Docker/Kubernetes K8s/K3s/...) and macOS, even better. Otherwise there will be (inevitable) blockers on my Jira and Kanban boards plus KPI and KRI impacts.

    Spice (1) flagReport
    0 of 12 found this helpful thumb_up thumb_down
  • On the plus side, it's not a whole lot of work to get MDT set up alongside WDS, and that seems to still be supported:

    Text
    You can still run Windows Setup from a network share. Workflows that use a custom boot.wim, such as MDT or Configuration Manager are not affected by this change.
    

    I recommend that anyway, as it's far more customizable.

    Switched from WDS-only to WDS and MDT back when Win10 came out, and I couldn't be happier with the decision.

    Spice (14) flagReport
    6 found this helpful thumb_up thumb_down
  • No big deal for me as we don't use it.

    Spice (2) flagReport
    1 found this helpful thumb_up thumb_down
  • M

    D

    T

    Spice (3) flagReport
    Was this post helpful? thumb_up thumb_down
  • Big Green Man wrote:

    I recommend that anyway, as it's far more customizable.

    Switched from WDS-only to WDS and MDT back when Win10 came out, and I couldn't be happier with the decision.

    That's what I do as well. Using MDT works wonders, especially if you want to apply extra scripts, or run multiple tasks, and installers during the deployment of a Windows image. 

    Spice (2) flagReport
    1 found this helpful thumb_up thumb_down
  • I was at a place that used FOG servers for deployment. It was a pain in the dupa to setup but it worked well. Setup a drive the way you wanted it, sysprep it, copy the image to a server and put it back on HD's when you wanted to use it. We use MDT here but it seems unnecessarily complex. Haven't tried Windows 11 yet so we'll see.

    Some day I'd like to try a Clonezilla server

    Spice (2) flagReport
    1 found this helpful thumb_up thumb_down
  • Spoke to the person who handles deployment here. He uses the WDM PXE to get into PE and then uses MDT....

    And yes, I like Turtles!

    Spice (3) flagReport
    Was this post helpful? thumb_up thumb_down
  • Big Green Man wrote:

    On the plus side, it's not a whole lot of work to get MDT set up alongside WDS, and that seems to still be supported:

    Text
    You can still run Windows Setup from a network share. Workflows that use a custom boot.wim, such as MDT or Configuration Manager are not affected by this change.
    

    I recommend that anyway, as it's far more customizable.

    Switched from WDS-only to WDS and MDT back when Win10 came out, and I couldn't be happier with the decision.

    Indeed, I think this is the MS way of saying, "there are better tools available now." Also, it seems that it is the out-of-box boot.wim file that is the main concern so it may be possible to still cobble together a WDS deployment of Win11 using a customized boot.wim, which is kind of what MDT does anyway.

    Was this post helpful? thumb_up thumb_down
  • Turtles are pretty great.  I'd love to own a giant tortoise at some point.

    Spice (6) flagReport
    Was this post helpful? thumb_up thumb_down
  • We have massive diversity in our end-user configurations, so baking everything in to a few golden images has never been a thing. Building out a new base image in WDS with a half-hour effort has made refreshes easy. The MDT deployment I did a few years back (2017?) moldered quickly and gave us essentially no advantages vs a solid, quickly deployed up-to-date image from plain WDS.

    Nowadays, I can't imagine my desktop tech coordinating with my CAD Manager for the 40 odd machines he has to fuss over, let alone two different Controls groups. MDT was a pedantic pain in the ass for a lot of things, I guess we'll have to revisit it now though.

    Big Green Man wrote:

    On the plus side, it's not a whole lot of work to get MDT set up alongside WDS, and that seems to still be supported:

    Text
    You can still run Windows Setup from a network share. Workflows that use a custom boot.wim, such as MDT or Configuration Manager are not affected by this change.
    

    I recommend that anyway, as it's far more customizable.

    Switched from WDS-only to WDS and MDT back when Win10 came out, and I couldn't be happier with the decision.

    Spice (2) flagReport
    Was this post helpful? thumb_up thumb_down
  • The only thing I got out of this is the amount of people that prefer the "I like turtles" with the period at the end vs. without... 
    :thumbs up:

    Spice (5) flagReport
    Was this post helpful? thumb_up thumb_down
  • Ouch. WDS and MDT was great when we use to image computers with PXE boot. 

    Now that we are using Azure AD and Intune/Endpoint to manage devices, we no longer needed WDS/MDT. We now deploy computers using a USB drive that loads an FFU image and a configuration profile from windows configuration designer. This just loads a clean Windows 10 install, joins the device to our Azure AD, then Intune/Endpoint deploys the apps automatically. 

    Unfortunately not all apps are Intune/Endpoint friendly, so some of our computer labs require some manual intervention for things like Creative Cloud and CAD. This is a small percentage of our fleet, but still an added hassle. 

    I wonder if they will eventually try to phase out MDT as well? 

    Spice (1) flagReport
    Was this post helpful? thumb_up thumb_down
  • Brianinca wrote:

    We have massive diversity in our end-user configurations, so baking everything in to a few golden images has never been a thing. Building out a new base image in WDS with a half-hour effort has made refreshes easy. The MDT deployment I did a few years back (2017?) moldered quickly and gave us essentially no advantages vs a solid, quickly deployed up-to-date image from plain WDS.

    Nowadays, I can't imagine my desktop tech coordinating with my CAD Manager for the 40 odd machines he has to fuss over, let alone two different Controls groups. MDT was a pedantic pain in the ass for a lot of things, I guess we'll have to revisit it now though.

    Big Green Man wrote:

    On the plus side, it's not a whole lot of work to get MDT set up alongside WDS, and that seems to still be supported:

    Text
    You can still run Windows Setup from a network share. Workflows that use a custom boot.wim, such as MDT or Configuration Manager are not affected by this change.
    

    I recommend that anyway, as it's far more customizable.

    Switched from WDS-only to WDS and MDT back when Win10 came out, and I couldn't be happier with the decision.

    Let me know when you get to that point, and we can work together to get it all streamlined. MDT doesn't really have to be (much) more complicated than WDS. Driver management is a bit more complex, but using the standard client task sequence template to create a few task sequences and pointing them to your pre-existing WIMs will yield very similar results to deploying straight from WDS. Obviously there's a lot more that can be done, and the more you do, the more complex it gets, but that certainly doesn't have to be the case.

    Spice (5) flagReport
    5 found this helpful thumb_up thumb_down
  • Thanks! 

    Big Green Man wrote:

    Brianinca wrote:

    We have massive diversity in our end-user configurations, so baking everything in to a few golden images has never been a thing. Building out a new base image in WDS with a half-hour effort has made refreshes easy. The MDT deployment I did a few years back (2017?) moldered quickly and gave us essentially no advantages vs a solid, quickly deployed up-to-date image from plain WDS.

    Nowadays, I can't imagine my desktop tech coordinating with my CAD Manager for the 40 odd machines he has to fuss over, let alone two different Controls groups. MDT was a pedantic pain in the ass for a lot of things, I guess we'll have to revisit it now though.

    Big Green Man wrote:

    On the plus side, it's not a whole lot of work to get MDT set up alongside WDS, and that seems to still be supported:

    Text
    You can still run Windows Setup from a network share. Workflows that use a custom boot.wim, such as MDT or Configuration Manager are not affected by this change.
    

    I recommend that anyway, as it's far more customizable.

    Switched from WDS-only to WDS and MDT back when Win10 came out, and I couldn't be happier with the decision.

    Let me know when you get to that point, and we can work together to get it all streamlined. MDT doesn't really have to be (much) more complicated than WDS. Driver management is a bit more complex, but using the standard client task sequence template to create a few task sequences and pointing them to your pre-existing WIMs will yield very similar results to deploying straight from WDS. Obviously there's a lot more that can be done, and the more you do, the more complex it gets, but that certainly doesn't have to be the case.

    Spice (2) flagReport
    Was this post helpful? thumb_up thumb_down
  • My needs are simple enough I never bothered with MDT ( I'm only supporting around 100 machines, and it's just me, so not a lot of time (or need) to get fancy with things). 

    I started using WDS at a previous job when we rolled out Windows 7 to replace XP.  Someone else did most of the setup there and it worked well.  Once I came to this gig, I setup WDS, and never got everything FULLY automated, just enough to make it easy to finish the machine (I don't, for instance, bother preloading a bunch of drivers, and I never got the answer files completely working).  My images are somewhat dated right now and W11 is gonna be a while, so I don't know when I'll make changes. 

    I just used WDS to deploy a W10 1909 image to a laptop only to have to immediately update it to 20H2, because THAT image is a pain to setup as it includes several oddball programs. 

    Spice (2) flagReport
    Was this post helpful? thumb_up thumb_down
  • WDS is an abomination. It's Windows zero point configuration, which by itself isn't so bad. But the fact that Windows is configured out of the box to scan for devices that have it enabled, and AUTOMATICALLY ADD THEM TO THE WORKSTATION is beyond incredulous. Further, it uses Microsoft's own built in drivers, which many manufacturers will not support. I know, I work for a copier company. 

    Yes I know there are ways to prevent this behavior. I don't care. I don't want Microsoft making things I have to turn off! 

    Spice (1) flagReport
    Was this post helpful? thumb_up thumb_down
  • Slyldawg wrote:

    WDS is an abomination. It's Windows zero point configuration, which by itself isn't so bad. But the fact that Windows is configured out of the box to scan for devices that have it enabled, and AUTOMATICALLY ADD THEM TO THE WORKSTATION is beyond incredulous. Further, it uses Microsoft's own built in drivers, which many manufacturers will not support. I know, I work for a copier company. 

    Yes I know there are ways to prevent this behavior. I don't care. I don't want Microsoft making things I have to turn off! 

    The topic here is WDS=Windows Deployment Services, not WSD (whatever it stands for), that funky thing that maddeningly adds random network printers to a computer without you asking.  I agree though...it's an abomination, at least in a corporate network.  Maybe OK at home.

    Spice (1) flagReport
    Was this post helpful? thumb_up thumb_down
  • Change is inevitable, which is nice because I am not above bending over to pick it up

    Spice (4) flagReport
    Was this post helpful? thumb_up thumb_down
  • Another vote for MDT here.  WDS for network boot, MDT for all the imaging and application installing.  Once I started having issues with WDS alone (after Windows 10 started needing deployments), I added MDT and never looked back.  I get the impulse to want to stick with it, but MDT is free, relatively easy to setup alongside WDS and will make your life easier in the long run......until MS stop supporting that, too.

    Spice (1) flagReport
    Was this post helpful? thumb_up thumb_down
  • I was a long-time WDS user and fan, until Gorfmaster1​ showed me the power of MDT. 

    I would say to take some time and learn MDT, you won't be sorry that you did.

    Spice (2) flagReport
    Was this post helpful? thumb_up thumb_down
  • And if we have any audiovisual learners here, I always recommend BTNHD's channel. His videos are fantastic.

    https://www.youtube.com/channel/UCQI6M3qcTuz-iXfG1loE9lQ

    Spice (2) flagReport
    Was this post helpful? thumb_up thumb_down
  • It's a matter of collecting the tools and re-implementing something from four years ago, and two workstations ago. Annoying at the time, and remains so today. C'est la Vie!

    jonahzona wrote:

    I was a long-time WDS user and fan, until Gorfmaster1​ showed me the power of MDT. 

    I would say to take some time and learn MDT, you won't be sorry that you did.

    Spice (1) flagReport
    Was this post helpful? thumb_up thumb_down
  • IMHO, WDS is extremely primitive compared to MDT. I can see why they would abandon support for it. MDT seems like all the R&D has been put into it for many years. I still use WDS to boot my MDT boot image, but that is about it. With MDT, you can take a standard image and create a task for every deployment need. It is very easy to make changes as you find issues that may have crept into your "Golden Image". I will agree that is is a little complicated to get started in, but once you figure it out (and there are a ton or resources to help with that). I can PXE boot, start the task process and know that it will be ready to go when it is finished. There is nothing I have to do to it once it is finished imaging since all the steps in the task sequence do anything I would normally do with a fresh Windows Install. I know there are a ton of other solutions, I haven't tried them all, but I would recommend MDT over anything I have used.

    Was this post helpful? thumb_up thumb_down
  • Eh, I kept a VM image updating from 1709 to 1803 and I don't feel the effort paid off in enough time savings to warrant. Regardless, Microsoft has declared this the Way To Do Things. For us, the Golden Image is a mythological creature, so iterating a bunch of images to match every deployment scenario was a lot of leg work and ultimately not worth it. 

    I've been doing deployments via PXE for hmmmm.....22 years now, there is a lot of water under that bridge.

    Gorfmaster1 wrote:

    IMHO, WDS is extremely primitive compared to MDT. I can see why they would abandon support for it. MDT seems like all the R&D has been put into it for many years. I still use WDS to boot my MDT boot image, but that is about it. With MDT, you can take a standard image and create a task for every deployment need. It is very easy to make changes as you find issues that may have crept into your "Golden Image". I will agree that is is a little complicated to get started in, but once you figure it out (and there are a ton or resources to help with that). I can PXE boot, start the task process and know that it will be ready to go when it is finished. There is nothing I have to do to it once it is finished imaging since all the steps in the task sequence do anything I would normally do with a fresh Windows Install. I know there are a ton of other solutions, I haven't tried them all, but I would recommend MDT over anything I have used.

    Was this post helpful? thumb_up thumb_down
  • I need to install Windows 11 this week. While MDT sounds like the future, I unfortunately don't have time this week to learn about MDT. I have however found articles on the Internet that suggest you can boot Windows 11 using a Windows 10 boot image and windows 11 install image and it seems to work. What fails is the windows 11 boot image.

    I will be testing this tomorrow as I have a working WDS with Windows 10 images. So in theory, I should be able to install windows 11 using the existing boot images I have on the WDS server.

    I will have to investigate what exactly MDT can do (that I would actually use) that cannot be done using just WDS. I think the only thing that I would really like to improve is injecting the latest Windows feature update into the image before deploying new machines using an image that is a year or two old. It is stupid to deploy say a 1903 image and then wait forever for it to update to 21H2. Otherwise I use logon and startup scripts to customise windows for things such as task bar, start menu, registry settings etc. So I don't really have any use for an all singing all dancing MDT. Assuming that Windows 11 boots tomorrow using the W10 boot image.

    Was this post helpful? thumb_up thumb_down
  • I can confirm that using a Windows 10 boot image works perfectly for installing Windows 11. I had no issues installing Windows 11 from WDS.

    1 found this helpful thumb_up thumb_down
  • Can confirm that though I had a Server 2022 boot.wim on my Server for WDS...

    Server 2022 boot.wim gives deprecated warning but lets you continue... unlike a Windows 11 boot.wim

    Spice (1) flagReport
    1 found this helpful thumb_up thumb_down

Read these next...

  • Snap! Win 8.1, hybrid IT models, robo-fish, Jovian Vortex Hunters, & more

    Snap! Win 8.1, hybrid IT models, robo-fish, Jovian Vortex Hunters, & more

    Spiceworks Originals

    Your daily dose of tech news, in brief. Welcome to Friday! It has been a big week here as we launched Spiceworks News & Insights a few days ago. Do you know who else had their sights set high? Kenneth Arnold. On June 24, 1947, civilian pilot Ken...

  • Chrome is a memory hog?

    Chrome is a memory hog?

    Windows

    I have a win 10 pro machine with 21H2.Running chrome  102.0.5005.115.  I will open a bunch of tabs during the day (right now, 49).  And including other things that are running, there's 80% of the 12GB of RAM in the box.I've noticed that when I go into ...

  • When you are just starting out

    When you are just starting out

    IT & Tech Careers

    HI Spiceworld,I was reading some discussions around the community and I see that here it’s like we’re all part of a family, so I venture to open this discussion, hoping that you can help me/understand me or at least bring your experiences. I am a c...

  • Spark! Pro Series - June 24th 2022

    Spark! Pro Series - June 24th 2022

    Water Cooler

    Compulsion: 1: a very strong urge to do something He felt a compulsion to say something. 2: a force that makes someone do something She was acting under compulsion. 3: an act or the state of forcing an action They ...

  • Sublets and the Network

    Sublets and the Network

    Networking

    I have a situation where one of the offices is looking to sublet for 1 day a week. They want one port to put their firewall/router on and drive their network from there. My first notion is to say no and require them to pull in their own connection. I want...