![]() ![]() The MDT bootable wim that has been setup to lead into the task sequence doesn't show up when booting into winpe, and if I manually import it into the wds server it will show up and launch into the task sequence environment but the computer restarts after sitting at the blank screen for a minute. ![]() The Task Sequence has been deployed to the Unknown Computers group and a few test groups, but the generally preferred method of imaging is user driven ie technicians booting into windows pe and selecting an image (or, moving forward, a task sequence). ![]() ![]() Currently we do imaging via creating large wim files and network booting however I'd like to move to imaging via SCCM task sequence to apply drivers / applications / os updates. G'day, I followed the guides to set up an MDT Task Sequence in SCCM 2012 and Distributed it to my different DPs which already have WDS and are in production. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |