![]() ![]() Whatever works is fine just as long as each ID is unique. Example: DEPW7EX64 for deploying an image of Windows 7 Enterprise 圆4, or CAPW7EX64 for capturing an image. I like to use a truncated version of what the task sequence does for the ID. The ID becomes the name of the folder for the task sequence in the deployment share’s file system hierarchy. Each task needs a unique ID for starters, and a name which can or can not be unique. ![]() The process of creating a new task sequence is wizard driven like many things in MDT. Creating folders is just as easy as starting to create a task sequence, right-click the node above and choose “New Folder.” Also, if one was to create an offline MDT deployment share, separated tasks and operating systems can make your selection profile much slimmer. I haven’t run across the need to use the same image with multiple different task sequences. Generally, one operating system image goes along with a single task sequence. MDT’s operating system and task sequence folders are the same.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |