Using Microsoft Deployment Toolkit (MDT) UDI as Custom OSD Frontend in Microsoft SCCM

hi my name is Justin shellphone I'm the engineering lead at patch my PC we develop a third-party patch management solution that integrates into Microsoft SCCM prior to my current role is also a premier field engineer at Microsoft supporting SCCM in this video it's going to be a follow up video of our video about the introduction to OSD covering some of the basics around images drivers boot images and task sequences so if you haven't watched that and you're not familiar with OSD you're gonna want to start with that video first in this video we're gonna be showing you how you can integrate Microsoft deployment toolkit into config manager and use the UDI piece of that or the user driven installation I would often use this when I was a PFE at Microsoft for customers who needed to make their deployments more dynamic so for example if they wanted to give their IT technician to the ability to do things like joining custom oh used selecting different groupings of applications there's a lot of different wizard panes that we can add to our customizer to make the task sequence more flexible MDT is not the only way there's also some community tools out there I know Jason Sandi's has one called UI plus plus you could even use something as basic as like a VB script that inputs a message box or a HTA script that would display different options for the user to select at the end of the day what we're doing is we're basically assigning different variables that are gonna play out within our tasks sequence based on what the user selects so UDI is probably one of the easier options because you do most of it through a wizard designer tool and we'll go through all that process within this video so we'll go ahead and get started what I've got here is just a 18:03 site where I'm sorry 18:02 SCCM site but i have pre downloaded MDT so i've downloaded the latest version of their MSI to install on my SCCM server or wherever you're running the SCCM console that would be where you'd want to install this MSI I'll also include a link to that as well so it's all pretty basic just an MSI we'll go all the default options here and then install that alright that's done we'll finish that the next thing that we need to run is the if we go out and search for MDT Microsoft deployment toolkit there's going to be this thing here called the configure config manager integration so we're gonna run that as administrator and we're gonna choose the option here to install the extensions for config manager so it should read all your site information if you have the console and then we'll just leave that and then do finish well make sure that it completed successfully and then finish here now in order for this to take effect what we need to do is reopen our config manager console and then there's going to be a new option here to create a MDT task sequence so if we come back into our operating systems task sequences we see this option here on the top create MBT task sequence so we'll go ahead and just get that going and go right through this process we want to make sure for the template we keep the default option of a client cache sequence for the task sequence name I'm just gonna call this deploy Windows client I'm gonna keep it pretty generic because when we go through this I'm going to do things like giving the user the ability to install multiple operating systems so for example we'll go through and add Windows 7 and Windows 10 so it can be pretty dynamic and a single task sequence now for this option we're gonna join a domain we're gonna choose to join contoso dot local that's just the domain that we're using here in the lab for the domain joint account we have a account called SCCM underscore DJ go ahead and enter the password for that and okay I just fill in this with contoso it.4 just the generic information here for the window settings if you had a product key you could enter that here one setting I do want to enable is I want to define the local administrator account just in case the task sequence fell is to join the domain or something during our testing we could have the ability to log in with the local administrator account we're not going to use it to capture an image so we're going to keep that checked here that will never be used to capture an image for the boot image we're gonna be deploying 64 bit of Windows 7 and Windows 10 so we'll just choose the default boot image that I have here for 64-bit now this is something that we're going to have to create here so we need to create a MDT toolkit package so what I'm going to do it I just have a UNC path where I keep my different package source files and I've created a folder under OSD called MDT so what we're gonna do we're just gonna create a new folder here called MDT toolkit package and this can really be whatever you want I'll just keep it toolkit package so it just kind of matches with what we're making here but you certainly could have multiple different packages here if you needed to do different task sequences so this is just going to copy the different script files that we need for our MDT package and it's going to copy it to that folder so I'll just give some information here this is my MDT toolkit package used for UDI deployments the image so we'll go ahead and just choose a default image here so I'll choose that enterprise image that we created in the previous video and we're going we're going to go around and we're going to customize this a little bit more but for now we're just make this task sequence created with that default image now this option is important we want to do the user driven installation so we're going to give it the front-end that the users are going to go through to do customization so you want to make sure you choose that option otherwise it would do a zero touch where it just goes through the task sequence you wouldn't get prompted for any customizations for the config manager client package we're just going to choose the default client package that should be created with SCCM so that's where it's gonna install the SCCM client from for the u.s. MT package there should also be a u.s. empty package that's just built in so I'll choose that package here we'll do OK on that and then next here now for the settings package what we're gonna do is we're going to create another folder here and we're just gonna call it MDT settings package so this is where the unattended custom settings are gonna go for MDT so we'll just do it MDT settings package copy that path and we're gonna create a new package and it's gonna copy the files there I'll just call this the same thing here MDT settings package with 1.0 for the version no sysprep that's not needed and then next here so if we actually look in these folders now we can see our toolkit package just getting all the different scripts and binaries that are going to actually run that allows us to customize this deployment so these are pretty much just everything that's going to be running in the backend that the cash sequence engine is going to be calling in that settings package we can see we have our custom settings I and I this is what the MDT package uses just some default options we don't have to customize that for this video and then it's just going to create an unattended appointment on the back end so that all looks fine looks like we created that ok and then we're gonna do finish alright so looking at this task sequence if we edit it it can be a bit intimidating because it's gonna be quite a bit larger than what you would do if you just created a native task sequence through config manager but I just want to kind of quickly go over this and most of these steps in the tasks sequence here actually never going to run most of these are going to be conditioned based so for example let's say that the state capture step so this would only be if your if we look at this condition here if you're not in winpe so the state capture would only happen for example if you were deploying this to an existing OS and you wanted to do a u.s. MT capture for like a reimage scenario so even though this is quite a long pass once most of these are going to be condition based and most of them actually won't even run so they're gonna be conditioned based on for example what the UDI wizard we create based on the options the user selects will kind of determine which one of these steps run here you just want to cover that real quickly before we actually start editing this so the first thing that we're going to do is go over to our toolkit package and in the scripts folder we're gonna just go ahead and copy that path and then within MBT it's going to install something called the UDI wizard designer so if we open up that tool and then we click open and browse out to the package that we had in that scripts folder there's going to be a file in here that we want to edit called the UDI wizard underscore config dot XML so this is the actual XML that controls what Wizards are displayed to the end users when they're deploying an image and this is where we can do our customization so there's a few different groups here there's a new computer group and that's gonna be what we're using primarily in this video so this would be if you're booting up a machine using pixie or USB image and it's going directly to winpe to image the device this would be considered a new computer scenario the other scenario that you might do in some scenarios would be the replaced scenario or the refresh that would be if you deployed to an existing device that's already running config manager and it's into full OS and you wanted to reimage it so if you wanted to have a different set of wizard panes that you show there we could you know configure these different grouping options for that scenario but we're gonna be working with today is this new computer scenario so within the designer we have the different pages that we can customize one thing to note here that this preview option it's broken within the UDI designer but on the back end we do have the ability to call this preview directly using a command-line so if we open a command prompt i'ma paste in what we need to run I'm gonna just copy that path for the XML file so you di wizard underscore config dot XML in my UNC path and what we're going to do is change that XML path we're going to double quote it paste it and then end the double quote so what we're doing here is we're running under the installation directory for M DT there's a templates folder distribution tools x64 and then there's going to be this OSD setup wizard exe within that we're gonna run a forward slash preview and then a forward slash XML colon and then the path to your actual XML file within the package so if we wanted to just see what that default wizard would look like if we didn't customize it we can run this preview installer we can see in the bottom here it's in the preview mode so the first pane that we have is the welcome pane so just some basic information we can change this text if we want then we have BitLocker we can see that it's enabled by default it's set to use a TPM and pin by default so all these can be customized but this preview is just showing you what that default XML is set to do so it's just got a generic Windows 7 image is the name of it so we're definitely going to change that optionally if you want to have it format or clean the drive we could have that pre-selected as well but we'll go through all this in the wizard us empty backup that's this page here the deployment readiness that will check things like whether the laptop has power network connection a few just things that we might want to verify before we start imaging a device this is where we could enter the computer name give it a domain and then a domain joint account local admin password if you wanted to allow the user to who's deploying this to create a custom local password usually we just disable all that I can't see a good reason to set that at the user level if you wanted to set user device affinity we could do that in this page different language options installing different packages or applications and then the summary page here so that's kind of what the generic one would look like if you were to just keep everything default in my case I'm going to go ahead and click on that BitLocker page and under the page here this will just show a little screenshot of what we're doing under the BitLocker mode since I'm going to be generally deploying this to VMs I'm gonna check that box that says do not initially check it I'm also going to have it just to store the BitLocker key in the TPM I'm not gonna require a pin here but if you're using things like M BAM or if you wanted to delete this page completely that would be totally fine as well so it looks good for BitLocker under the volume we're definitely gonna do some customization here so the first thing we want to look at is the images so we can see we've got the windows 7 image here but what I'm gonna do I'm just gonna click manually add an operating system image and I'm just gonna give it a friendly name here so Windows 10 Enterprise x64 I'm gonna do that for the display name that looks good for the actual image name I think I'm actually gonna make this more generic Windows 10 I'm gonna remove the spacing here because this is going to be a variable that we're going to use when we actually go and configure our cache sequence for multiple images so I'm gonna just set this OSD image name equals I'm gonna just paste this in here so I can reference this when we come back so that looks good the display name is what's actually going to show to the user so that looks good that's better there and then it's a 64-bit image so that looks good I'll copy this here and then I'm going to delete that Windows 7 1 because we're not going to use that for now I'm going to manually add another one here paste in that but for this one we're going to do this for Windows 10 education so Windows 10 education I'm just gonna delete the name here just delete the spaces make this 64-bit for the architecture and then okay I'm gonna paste that in there as well just so we've got that now if you have images in your SCCM you can't actually choose to select an existing image that will browse out to your site you might have to go to the config manager tab and tell your site give it the site code and a server and choose validate if you had never set this up before otherwise it wouldn't load that so if you wanted to you could actually use that option and then we could browse out and choose our windows 7 enterprise 64 bit but if we look at this sometimes the names can be kind of doesn't look right so for example this one read the disk name so that's why I usually just manually create it but what we're do will change that variable for the image name to get rid of the spaces here and then we'll copy that zoom out let me just paste in Oh all right so just copy those since I over wrote them so that this looks good we've got three different image selections that we can do here under the user data we're gonna choose the option to pre select the format drive so this will just have the format format option pre-selected by default so this can be helpful so they wouldn't have to go and click that since in most cases you do want to format the disk if you're doing a new machine so that looks good under the Select target so this would be the US MT option if you wanted to make this available since we're doing this for a new computer it's probably unlikely that we would need to use any type of user state so what I'm going to do is right-click that page and choose to remove the item and that's just going to get that rid of that for our wizard the deployment readiness option so this will be if you want to have those checks in place so optionally you could add any type of custom scripts that you wanted here in my case I think we'll just leave everything default and keep that page in there okay so the new computer details this is one that we're gonna change quite a few things so there's gonna be where they enter the computer name the domain the öyou and the domain joint account so what we're gonna do here I'm going to leave the computer name just empty by default so they would have to type that in if you wanted to pre-fill that like you can use some different scripts that could run before this - maybe pre fill it with things like the serial number depending on your naming conventions I'm just gonna leave it empty here and have that just where the user selects that what I do want to do here is add the domain so contoso dot local for the friendly name we'll just call it contoso once that domains added we're going to have the ability to right-click it and choose to search the domain for OU's so this is where we can go and select what OU's we want to make available for our users we can select multiple by holding the control so I'm going to include the servers and the workstations oh you here if you want you can optionally rearrange these so I'm gonna make the workstations show up here first and then for the actual setting let's see what we got here network details what I'm going to do is make the domain name checked by default and I'm also going to lock it so they wouldn't have the ability to go and change it to the workgroup for the domain join credentials I really want to just set this to be my default account here so that contoso backslash SCCM underscore DJ so I'm just gonna pre fill in that account and I'm going to lock that account here I'm also gonna lock the password value we're actually not going to provide this we're gonna enter this account in on the back end of the task sequence but what we need to do to make that work is we can't have it do the credential check because there's not going to be any credentials actually entered during the wizard so we're going to disable the ad check for these two options down here otherwise that the the check wouldn't work because the password wouldn't be defined here so that looks good the admin password like I mentioned we're not going to give the end user or the IT tech the ability to change that or set that during the sequence I'm just going to delete that stuff completely user device affinity I'm not too worried about that in my scenario same thing with language so we're just gonna be working with the English language here so I'm going to remove that page as well the install program so this can be one that can be quite helpful so what we're going to do here this is gonna be the default options just going to be a generic sample application that doesn't do anything so we're gonna remove that I'm gonna rename this from general software to base applications okay so the base applications are going to be anything that we want to force to install and lock it so the user can't uncheck it so one thing we have to do in order to install applications is under this configuration manager up in the ribbon what we have to do make sure you have your site integrated and you actually have to create a collection for targeting applications too so this is just going to be a dummy collection in my case it looks like it read it from my previous configuration so I've got an application collection named MDT apps so if we come and look at my collections I've created one under the OSD folder called MDT apps we can see currently we don't have anything to deploy to that collection so in order for the udi wizard to actually be able to get policy that it's going to create for dynamically installing applications we need to target the application to that dummy collection in order for us to actually see the application in the wizard and select it for deployment so if I were to click add software to group and go out and choose the application and then choose to select an application and search here you do want to make sure you don't have this option show Windows app packages only I think that's enabled by default but what we can see here even though I have applications showing up in my applications within SCCM they're not showing up in the UDI wizard because we have to target them to that collection so for example if we were to click that collection choose deploy application I'm going to deploy the local administrator password solution application first so that's gonna be one that I'm gonna include as a base application that always installs this is a this is just so we can get the policy so I'm just going to keep everything default here this this is never gonna go to any computers so one thing you can notice as well just to make sure people didn't accidentally create any computers that were added we can see that we're actually limiting this collection to the unknown computers which would only contain two objects that represent unknown computers so even if you accidentally tried to create a query they wouldn't get these apps deployed because we're doing that limiting to only unknown computers so now we have that application deployed if we come back here in search we can see that it's now showing up so if I click ok on that and choose finish we can now see that this is under the base applications so what I'm going to do is right click the application here and choose to lock it so that means that the user could not unselect this at runtime and then what we're going to do is create a new software group and we'll call this accounting so say you had a scenario where you wanted to make different applications available for different groupings of departments within your organization so if we were to come in here and add software to group we're gonna add an application and what we're going to do is come back to that collection we're gonna choose deploy application and then we'll choose Java for this one I'm gonna do next here just all the defaults we're just getting this so we have the policy that we can select the app so if we go and search again we can now see we have Java showing up so that looks good so we'll add that here we'll also create another department here called information technology information technology we're going to create this as a root level we're gonna add software to group I'm gonna go ahead and deploy the 7-zip application target that to this collection next next next for all the defaults and if we search now now if you notice 7-zip is actually grayed out because this is something that is easy to miss if you didn't go into your application under the properties of it and if you didn't enable the option to allow it to install and task sequence it's gonna show us that grayed out option so if we go and change that and then come back to our wizard search again we can now see that it's available so that's something that can be pretty easy to miss just wanted to make sure that I covered that as well and we have one more app let's do Foxit reader so we have to deploy that first so we'll go to deploy application Foxit reader we'll get that deployed now for packages you don't have to do any type of pre deployment to them they should just show up if you were to add a package so come back in here and do a search Foxit reader it looks like I also did not have the option enabled for the task sequence to run from it so if I come back in here and enable that we do ok and then if we do a search we can see that it's now showing available so this looks good so if we go ahead and go back to my flow looks like that was really the last page so we had the summary here I'll leave that page but now we're going to go ahead and choose to save that XML file we're going to overwrite the existing one all right so I've been having some weird permission issues let me just save that over to my desktop so it's got those two files let me see if I can paste this over all right let me see if I can copy that to the local path I think I have something weird going on with my sharing permissions there we go so we got those files saved here successfully where that package is um so now what we want to do is go into our packages so SCCM when you created your MDT packages and settings package within the wizard for your task sequence it's going to automatically create the package within SCCM so what you want to do is right click and choose the update distribution point that's going to make sure that we have the latest XML that we just updated and get that on to our content library so then what we're going to do is go ahead and make sure we have these two packages distributed to our distribution point so in our case we just have a single one for this lab and we'll get that distributed alright so if we come back and run that preview again see what we have going on so we've got the welcome screen we didn't change any of the text there we can see that BitLocker is now unchecked by default we've got our three different image options here the deployment check the new computer we've got our öyou available we've got our application grouping so if we wanted to select any additional apps and we're deploying it that looks good and then the summary page so that looks good I think for what I want to test out here but going back to our task sequence we do have to do some customizations here to support what we did with multiple images so if we come to our sequence and look at the the first thing that might change here is the apply driver so like I mentioned in the previous video we did usually I don't like using the auto apply driver step because it just kind of searches out and you never really know what drivers that might try to apply placed on the plug-and-play ID so the apply driver package is usually what I like going with so we're gonna create a new group here we're gonna call it apply drivers Windows 10 x64 alright and then for the condition if we remember our image names so we're only gonna have this folder run we're gonna use an if statement and if any of the conditions match here so under that if statement we're gonna add the task sequence variable so on the back end depending on what they select it's gonna set the OSD image name variable and it's going to be based on that value that we copied from the UDI wizard so if it's Windows 10 Enterprise x64 or Windows 10 Education x64 we're gonna go through this step for these drivers for Windows 10 so that looks good we're copying this step paste it down just move that one step down here so it's on the same level and we're just going to rename this to Windows 7 x64 and we're going to copy that windows 7 OS the image name that we created and we're gonna go ahead and change this variable we're going to delete one remove that one and then we're gonna change the existing one to the windows 7 variable so we can see that these two apply driver steps are going to be condition based based on the image name is going to determine whether they run so if we come here I think I do have one driver package for the surface book so let me just copy that step should be able to just paste that directly into the Windows 10 folder so that condition should automatically have had the surface book that we had for searching for the model so we can see this looks pretty good so we're only going to run the Windows 10 folder if the image name is a Windows 10 image name that we had and then it's still gonna have condition base for each model for the driver packages that you might have within there now one thing I want to note if you're using a custom Mac key you would also have to have two different apply window setting steps so let me just copy that to show you what that would look like in case you were using a Mac key instead of instead of like kms because you would have different Mac keys let me also shorten these names I think that looks better when we can see it all when 7 x64 alright so we had those when apply Windows settings we're gonna paste in the same settings here and then we're gonna make this one win 7 x64 and what we're gonna do we're going to add the same conditions that we had for the image names here so I'm just going to pause the video while I add that alright so I added those conditions so we can see the windows 10 option for the settings and then we have the condition for Windows 7 now like I mentioned this would really only be needed if you're using a Mac key here instead of kms I just want to show you how in case you were using that so it looks good so now what we're going to do is go down to our apply image step so apply operating system image so as you can expect we also need to condition-based the apply image step based on what image is selected so if you remember we had the enterprise 1 by default so that's going to be what what's here by default so we want to add a condition task sequence variable OSD image name so if it equals the Windows 10 Enterprise if they select that option we're going to have that apply that OS so I'm going to rename this step to apply OS - win 10 x64 enterprise we'll go ahead and copy that step paste that here and then what we're going to do we're going to copy the education one so we do have a education here so if you remember we had that installed out wim the default one from the ISO and that one contained multiple different indexes so that looks good so education is the first index so we shouldn't need to change anything and we're going to only run this step if you had the education Edition variable now one thing to note here if we come back and look at the designer for our image selection if we choose that option select an operating system image if you look at the Windows 10 the installed out wim you can see that's going to load all these different indexes so for example the education enterprise so if you wanted to have multiple indexes the pro index for example you can see that the index here is going to change so if we were to select that option and add that to the wizard you can see it's automatically going to change the OSD image index to number 5 so if you wanted to have you know if you were using the installed out wim and had multiple indexes or additions essentially of Windows 10 you could come in here and add the index variable or just select the index from the image so that would select based on this drop down it would dynamically select the index that you assign to the image that you had in the udi wizard so that's an easy way you could use the default installed out wim and you can make all these options available by adding these different steps based on the conditions that we're running so I'm going to copy this one paste in that and we're just going to rename this one for Windows seven windows 7 Enterprise we're gonna browse out I'm going to select my windows 7 image and then we're going to copy our variable name and overwrite that existing one so we can see here that we've got three different apply os's I'm gonna just do a new grouping of ply OS just and add these all up here just to make it a little bit more organized okay all right that looks good so determining what the user selects in the UDI designer when this displays is going to determine which apply OS index or image runs based on that variable that we're selecting here all right you can see we've got a few different things running like software updates for example in my case I don't have any software updates deployed to the unknown computers so what I'm gonna do I'm gonna just disable this so the task sequence runs a little bit faster because we don't have to evaluate updates here you can see we're installing any packages so based on whether you added packages to that application they're gonna all go into a variable name and then it's going to dynamically install them we can also see the applications here it's going to dynamically install applications so any application that's selected in the wizard it's gonna put it into this variable and then dynamically install all of those within this step of the task sequence but I think that's pretty good I think that covers most of the main things that are actually going to run here based on the conditions that we have that we added I don't think I have anything else that we really need to cover here then we just make sure we apply all these changes and then I'm going to deploy this task sequence to the unknown computers collection so I'm going to just be using an unknown device to pixie boot up here so we're going to target the unknown computers looks good we're going to make the task sequence only available in median pixie so it could only be pixie booted to deploy this or a USB Drive created I'll leave all the defaults here none of these should really apply for a pixie boot distribution point we're a la fallback in the scenario that we didn't have the package there I don't think that should apply in our scenario and then we'll deploy that then close okay we look at the references tab of our TAS sequence we can see it looks like all of our packages are distributed to our distribution points and they're all compliant so that looks good we shouldn't have any failures because our contents not there so if we come over to one of our machines let's see if we can get this guy pixie booted and see what we get here all right so that looks good so we can see we have our cast sequence showing up here to play Windows client okay let me just open see them trace and what we do in the background is go to our temp folder SM STS log and then we'll go ahead and open the task sequence log so we can see what's going on when we start running this it looks like I do have the OSD computer name variable still on the unknown computer's collection that's why we're getting prompted for this usually this wouldn't happen unless in the secm console under the unknown computers collection so this is from the previous video where we were just using the computer name variable directly on the collection just the the most simple way we can give it a computer name so we don't need that anymore because we're gonna define the computer name directly in the UDI wizard so I'll just leave this empty and choose next so the first thing that we can see that's gonna happen is it's going to go download the toolkit package so all the script files and the and the things that need to run for us to use MDT that's what's going to download here first all right so we can see that it is now showing us the designer so if we actually look at what's happening on the bottom here we can just see that it's running the command that's calling that XML file so that's going to be what's showing us this wizard here so this is the welcome screen that we added so we just have next here we can see that BitLocker is unchecked by default but we didn't lock that so a user could optionally come in here and enable that option if they wanted to in our case this is just the VM I don't have TPM setup on it so that obviously would not be something we want to enable here we can see we have the different images so we have our enterprise our Windows 10 education and then Windows 7 enterprise for this test let's go ahead and just do education since that's not the default option and just make sure that all works ok we can see that we have it set to partition the disk by default because we enabled that option so that looks good we've got the different checks that are going on here so checking things like power the application one that usually shows warnings based on what I've seen in the past that should be fine though a new computer name so we're just gonna call this OSD demo UDI if we have the domain you can see we only had the single domain but you could add multiple here if you did have multiple domains and then you can see we have our different Oh use so we've got the workstations by default and that's where we want this machine to go so which is next here we've got the based applications here so that's that applications going to be locked and let's just say we want to go and do the information technology so act like this was an IT computer and then it's going to install those two sub applications that we've added the final summary screen we do finish and this is going to go through the process of formatting the disk so if we look back on our tasks sequence it's going to basically dynamically go through this based on the variables that were selected based on your wizard so in our case this is the new computer group so this is where we showed the udi wizard and this is the actual step that we're running to format the disk so that's kind of what's going on here now it's going to use the toolkit package once more and then it should go through and kind of download the image so we'll pause while we wait for that all right so we can see that it downloaded the wim file it looks like I did not rename the step so it says it's actually applying Windows 10 enterprise but that is actually if we come back and look at my tasks sequence here you see how we kept this step both of these enterprise but if we look at the actual variable it is education that I added here and the actual image that's being applied here is the education image so what I could do is simply rename this but I'll wait for this task sequence to actually complete just so we don't have any policy conflicts but this should be applying the education Edition and we'll verify that once the imaging is done we could actually verify that now so the package it looks like is ends in 72 so if we actually come back here and look at our images we can see that it is in fact using the 72 which is that default install dot wim and we can verify that the image index for education is image index 1 so that looks good I just forgot to rename that all right so looks like at this point we are now about to install the software so let me see if I can copy see them trace over here all right so at this point we just restarted and we perform the ubi or out of box experience and now it's at the point where it's actually installing the config manager client so if we go to see Windows CCM setup logs and then look at our CCM setup log what we should see is at this point it's going to be installing the client so it looks like that just completed so we'll wait for it to go on to the application step so if we look at the app enforce log in the CCM logs folder we can actually see the MSI is being installed here so this was Sara's information like the command line that's running this should be pretty quick we only had the three applications here all right that looks good all right so the last thing that's gonna show up here is the deployment complete wizard now this will shows information about how long it took the status about different applications that were installed and then we can go ahead and click start Windows now if you didn't want to have this last pane show up what you can do in your task sequence is there's a task that's called report done if you want to disable this step that will also disable that last step wizard so instead of having to click start at the end it would take us right here to the login screen all right so we are all logged in I'm gonna do a quick look here we can see that we've got Windows 10 education so it looks like our image applied successfully take a look at our apps we can see that we've got our three different apps that we installed here so that looks good looks like we did everything we did some customization using UDI that should be all I think I wanted to cover in this video hopefully this was helpful for you and thank you for watching

Channel: Patch My PC

Views: 48,481

Keywords: SCCM OSD, ConfigMgr, ConfigMgr OSD, Operating System Deployment, MDT, SCCM MDT, User Driven Installation, SCCM UDI, ConfigMgr UDI, SCCM OSD Frontend, OSD Frontend

Id: UREhjeKM-TM

Length: 47min 17sec (2837 seconds)

Published: Mon Jul 09 2018