Microsoft

So far we’ve been able to show you how to configure your MDT task sequences, customsettings.ini, and automatically update your Operating System media via OSDBuilder. Part 1: Citrix + Microsoft MDT + Powershell + Tools: The Beginning. – https://verticalagetechnologies.com/index.php/2020/03/04/citrix-microsoft-mdt-powershell-tools-the-beginning Part 2: Building multiple Citrix Images with one Microsoft MDT task sequence – https://verticalagetechnologies.com/index.php/2020/03/16/building-multiple-citrix-images-with-one-microsoft-mdt-task-sequence Part 3:…

Now that we’ve started down this “MDT” train, there’s no getting off until we discuss some of the more important parts. If you haven’t read the previous posts you can find them here: Post 1: https://verticalagetechnologies.com/index.php/2020/03/04/citrix-microsoft-mdt-powershell-tools-the-beginning Post 2: https://verticalagetechnologies.com/index.php/2020/03/16/building-multiple-citrix-images-with-one-microsoft-mdt-task-sequence Today we will be focusing on automating the procedures for always having an updated Windows OS…

Continuing on the discussion of Automating the Citrix Image build process with MDT. One small problem is that there’s never just one image to do. You probably have an Image for a couple different line of businesses, another Image for these 3 Developers, an Administrator image, and maybe a few more images for other miscellaneous…

Building Golden Images, Master Images, References Images (whatever you want to call them) is a necessity in today’s world. All too often I see Citrix customers using persistent VMs built manually. Sometimes 20-50 of the same VMs, going through the same manual clicks for upgrades, the same manual motions for software pushes, windows updates, etc……