How to / Nasıl yaparım:
You can write task sequences and their related files and dependencies to a DVD or CD set or a USB flash drive. Using removable media allows you to run the task sequence on computers that do not have a network connection to your Configuration Manager 2012 site. Task sequence media can be used anywhere in the hierarchy.
You can create the following types of removable media:
Stand-alone media contains the task sequence and all associated objects that are necessary for the task sequence to run. Stand-alone media task sequences can run when Configuration Manager 2012 has limited or no connectivity to the network. Stand-alone media can be run in the following ways:
· If the destination computer is not booted, the Windows PE image associated with the task sequence is used from the stand-alone media and the task sequence begins.
· The stand-alone media can be manually started if a user is logged on to the network and initiates the installation.
The steps of a stand-alone media task sequence must be able to fully run autonomously from the network; otherwise, the task sequence step will fail. For example, a task sequence step that requires a distribution point to obtain a package or need to talk back to the MP to get additional information dynamically will fail. Common steps that are affected are: Install Software Updates, Install applications according to dynamic variable list and Auto-Apply Drivers; however if the necessary package is contained on the stand-alone media the task sequence step will succeed.
This media can be created using the create task sequence media wizard located in software library – operating systems – task sequences.
Bootable Medias contain the necessary files to start a destination computer so that it can connect to the Configuration Manager 2012 infrastructure and determine which task sequences to run based on its membership to a collection. The task sequence and dependent objects are not contained on the media; instead, they are obtained over the network from the Configuration Manager 2012 client. This method is useful for new computer or when no Configuration Manager 2012 client is present on the destination computer and no PXE Service point is available in the environment. In Configuration Manager 2012 it is now possible to provide a list of Management Points that can be contacted to get the Task Sequences advertised to the System. Furthermore, we now have the option create an internet-based media, which will contact an internet based management point.
Capture Medias allow capturing an operating system image created outside the Configuration Manager 2012 infrastructure. Capture media will prompt the user for input values like the image file destination location. If a Configuration Manager Client Agent is installed on the System, the Capture Media will ensure that it is sysprepped like the Operating System.
Prestaged Medias are hybrid wim files containing the Operating System image and a Bootable Media. It’s booting into the Bootable Media part accessing the Configuration Manager 2012 infrastructure and running available Task Sequences. When the task sequence is executing the "Apply Operating System" step it will recognize an already applied operating system and will immediately continue at the next step. This is the perfect solution to be able to hand over this Image to the OEM vendor of your systems to have your corporate image pre-applied.
As mentioned before a prestaged media file is a hybrid wim which needs to be applied on a target system. This can be done using a task sequence exported on a stand-alone media or using a windows PE to apply the image with dism or imagex.
If you decide using a task sequence to apply the image never use the apply operating system step because it will mess up the preconfigured BCD store and the system will not boot into Windows PE.
When you create media, specify a password for the media to control who has access to the files that are contained on the media. If you specify a password, a user must be present to enter the password at the destination computer when the task sequence runs.
When you run a task sequence by using media, the specified computer chip architecture contained on the media will not be recognized and the task sequence will attempt to run even if the architecture specified does not match what is actually installed on the destination computer. If the chip architecture contained on the media does not match the chip architecture installed on the destination computer, the installation will fail.