Hi!
Just a short post for reference.
In my line of work I sometimes need to find the product description or version (build) number of a product.
While searching for them I stumbled upon a perfect website for most regular Microsoft products!
https://buildnumbers.wordpress.com/
Products like AX, CRM, Exchange, Office, SCCM, SCDPM, SCOM, SCSM, SCVMM, Sharepoint, SQL Server, TMG/ISA
I don’t know who is behind the site but a great cheerio for him/her or them! 🙂
/Stephan
This is just a reminder for the built-in Task Sequence variables in ConfigMgr 2012 R2.
You can also find them at: https://technet.microsoft.com/en-us/library/hh273375.aspx
| Built-in Variable Name | Description |
| _SMSTSAdvertID | Stores the current running task sequence deployment unique ID. It uses the same format as a Configuration Manager software distribution deployment ID. If the task sequence is running from stand-alone media, this variable is undefined. Example: ABC20001 |
| _TSAppInstallStatus | For System Center 2012 R2 Configuration Manager only: The task sequence sets the _TSAppInstallStatus variable with the installation status for the application during the Install Application task sequence step. The task sequence sets the variable with one of the following values:
|
| _SMSTSBootImageID | Stores the Configuration Manager boot image package ID if a boot image package is associated with the current running task sequence. The variable will not be set if no Configuration Manager boot image package is associated. Example: ABC00001 |
| _SMSTSBootUEFI | For System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager only: The task sequence sets the SMSTSBootUEFI variable when it detects a computer that is in UEFI mode. |
| _SMSTSClientGUID | Stores the value of Configuration Manager client GUID. This variable is not set if the task sequence is running from stand-alone media. Example: 0a1a9a4b-fc56-44f6-b7cd-c3f8ee37c04c |
| _SMSTSCurrentActionName | Specifies the name of the currently running task sequence step. This variable is set before the task sequence manager runs each individual step. Example: run command line |
| _SMSTSDownloadOnDemand | Set to true if the current task sequence is running in download-on-demand mode, which means the task sequence manager downloads content locally only when it must access the content. |
| _SMSTSInWinPE | This variable is set to true when the current task sequence step is running in the Windows PE environment, and it is set to false if not. You can test this task sequence variable to determine the current operating system environment. |
| _SMSTSLastActionRetCode | Stores the return code that was returned by the last action that was run. This variable can be used as a condition to determine if the next step is run. Example: 0 |
| _SMSTSLastActionSucceeded | The variable is set to true if the last action succeeded and to false if the last action failed. If the last action was skipped because the step was disabled or the associated condition evaluated to false, this variable is not reset, which means it still holds the value for the previous action. |
| _SMSTSLaunchMode | Specifies the task sequence launch method. The task sequence can have the following values:
|
| _SMSTSLogPath | Stores the full path of the log directory. This can be used to determine where actions are logged. This value is not set when a hard drive is not available. |
| _SMSTSMachineName | Stores and specifies the computer name. Stores the name of the computer that the task sequence will use to log all status messages. To change the computer name in the new operating system, use the OSDComputerName variable. Example: ABC |
| _SMSTSMDataPath | Specifies the path defined by the SMSTSLocalDataDrive variable. When you define SMSTSLocalDataDrive before the task sequence starts, such as by setting a collection variable, Configuration Manager then defines the _SMSTSMDataPath variable once the Task Sequence starts. |
| _SMSTSMediaType | Specifies the type of media that is used to initiate the installation. Examples of types of media are Boot Media, Full Media, PXE, and Prestaged Media. |
| _SMSTSMP | Stores the name or IP address of a Configuration Manager management point. |
| _SMSTSMPPort | Stores the management point port number of a Configuration Manager management point. Example: 80 |
| _SMSTSOrgName | Stores the branding title name that is displayed in a task sequence progress user interface dialog box. Example: XYZ Organization |
| _SMSTSPackageID | Stores the current running task sequence ID. This ID uses the same format as a Configuration Manager software package ID. Example: HJT00001 |
| _SMSTSPackageName | Stores the current running task sequence name specified by the Configuration Manager administrator when the task sequence is created. Example: Deploy Windows 7 task sequence |
| _SMSTSRunFromDP | Set to true if the current task sequence is running in run-from-distribution-point mode, which means the task sequence manager obtains required package shares from distribution point. |
| _SMSTSSiteCode | Stores the site code of the Configuration Manager site. Example: ABC |
| _SMSTSType | Specifies the type of the current running task sequence. It can have the following values: 1 – indicates a generic task sequence. 2 – indicates an operating system deployment task sequence. |
| _SMSTSTimezone | The _SMSTSTimezone variable stores the time zone information in the following format (without spaces): Bias, StandardBias, DaylightBias, StandardDate.wYear, wMonth, wDayOfWeek, wDay, wHour, wMinute, wSecond, wMilliseconds, DaylightDate.wYear, wMonth, wDayOfWeek, wDay, wHour, wMinute, wSecond, wMilliseconds, StandardName, DaylightName Example: For the Eastern Time U.S. and Canada, the value would be 300,0,-60,0,11,0,1,2,0,0,0,0,3,0,2,2,0,0,0,Eastern Standard Time,Eastern Daylight Time |
| _SMSTSUseCRL | Specifies whether the task sequence uses the certificate revocation list when it uses a Secure Socket Layer (SSL) certificate to communicate with the management point. |
| _SMSTSUserStarted | Specifies whether a task sequence is started by a user. This variable is set only if the task sequence is started from the Software Center. For example, if _SMSTSLaunchMode is set to SMS. The variable can have the following values:
|
| _SMSTSUseSSL | Specifies whether the task sequence uses SSL to communicate with the Configuration Manager management point. If your site is running in native mode, the value is set to true. |
| _SMSTSWTG | For System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager only: Specifies if the computer is running as a Windows To Go device. |
| SMSTSAssignmentsDownloadInterval | For System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager only: Use this variable to specify the number of seconds to wait before the client will attempt to download the policy since the last attempt (which returned no policies). By default, the client will wait 0 seconds before retrying. You can set this variable by using a prestart command from media or PXE. |
| SMSTSAssignmentsDownloadRetry | For System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager only: Use this variable to specify the number of times a client will attempt to download the policy after no policies are found on the first attempt. By default, the client will retry 0 times. You can set this variable by using a prestart command from media or PXE. |
| SMSTSAssignUsersMode | Specifies how a task sequence associates users with the destination computer. Set the variable to one of the following values.
|
| SMSTSDownloadProgram | For System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager only: Use this variable to specify an Alternate Content Provider, a downloader program that is used to download content instead of the default Configuration Manager downloader, for the task sequence. As part of the content download process, the task sequence checks the variable for a specified downloader program. If specified, the task sequence runs the program to perform the download. |
| SMSTSDownloadRetryCount | For System Center 2012 R2 Configuration Manager only: Use this variable to specify the number of times that Configuration Manager attempts to download content from a distribution point. By default, the client will retry 2 times. |
| SMSTSDownloadRetryDelay | For System Center 2012 R2 Configuration Manager only: Use this variable to specify the number of seconds that Configuration Manager waits before it retries to download content from a distribution point. By default, the client will wait 15 seconds before retrying. |
| SMSTSErrorDialogTimeout | When an error occurs in a task sequence, a dialog box is displayed that is automatically dismissed after a number of seconds specified by this variable. By default, the dialog box is automatically dismissed after 900 seconds (15 minutes).. |
| TSErrorOnWarning | For System Center 2012 R2 Configuration Manager only: Use this variable to specify whether the task sequence engine considers a detected warning as an error during the Application Installation task sequence step. The task sequence sets the _TSAppInstallStatus variable to Warning when one or more applications, or a required dependency, did not install because a requirement was not met. When you set the TSErrorOnWarning variable to True and the _TSAppInstallStatus variable is set to Warning, it is treated as an error. A value of False is the default behavior. |
| SMSTSLanguageFolder | For System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager only: Use this variable to change the display language of a language neutral boot image. |
| SMSTSLocalDataDrive | Specifies where temporary files are stored on the destination computer while the task sequence is running. This variable must be set before the task sequence starts, such as by setting a collection variable. Once the task sequence starts, Configuration Manager defines the _SMSTSMDataPath variable once the Task Sequence starts. |
| SMSTSMPListRequestTimeout | For System Center 2012 R2 Configuration Manager only: Use this variable to specify how many milliseconds a task sequence waits before it retries to install an application after it fails to retrieve the management point list from location services. By default, the task sequence waits 60,000 milliseconds (60 seconds) before it retries the step, and retries up to three times. This variable is applicable only to the Install Application task sequence step. |
| SMSTSPersistContent | For System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager only: Use this variable to temporarily persist content in the task sequence cache. |
| SMSTSPostAction | For System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager only: Specifies a command that is run after the task sequence completes. For example, you can use this variable to specify a script that enables write filters on embedded devices after the task sequence deploys an operating system to the device. |
| SMSTSPreferredAdvertID | Forces a specific targeted deployment on the destination computer to be run. This can be set through a prestart command from media or PXE. If this variable is set, the task sequence overrides any required deployments. |
| OSDPreserveDriveLetter | For System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager only: This variable determines whether or not the task sequence uses the drive letter captured in the operating system image WIM file when applying that image to a destination computer. In Configuration Manager with no service pack, the drive letter captured in the WIM file is used when applying the operating system image WIM file. In Configuration Manager SP1, you can set the value for this variable to False to use the location that you specify for the Destination setting in the Apply Operating System task sequence step. For more information about the Apply Operating System task sequence step, see the Apply Operating System Image section in the Task Sequence Steps in Configuration Manager topic. |
| SMSTSRebootDelay | Specifies how many seconds to wait before the computer restarts. The task sequence manager will display a notification dialog before reboot if this variable is not set to 0. Examples: 0 30 |
| SMSTSRebootMessage | Specifies the message to display in the shutdown dialog box when a restart is requested. If this variable is not set, a default message will appear. Example: This computer is being restarted by the task sequence manager. |
| SMSTSRebootRequested | Indicates that a restart is requested after the current task sequence step is completed. If a restart is required, just set this variable to true, and the task sequence manager will restart the computer after this task sequence step. The task sequence step must set this task sequence variable if it requires the restart to complete the task sequence step. After the computer is restarted, the task sequence will continue to run from the next task sequence step. |
| SMSTSRetryRequested | Requests a retry after the current task sequence step is completed. If this task sequence variable is set, the SMSTSRebootRequested must also be set to true. After the computer is restarted, the task sequence manager will rerun the same task sequence step. |
| SMSTSUDAUsers | Specifies the primary user of the destination computer. Specify the users by using the following format. Separate multiple users by using a comma (,). Example: domain\user1, domain\user2, domain\user3 For more information about associating users with the destination computer, see How to Associate Users with a Destination Computer. |
Just a quick reference for finding the client logs during an Operating System Deployment.
As we all know ConfigMgr moves the logs during a deployment depending on the stage of deployment.
We can define 4 major stages in regard to the log file locations:
After the completion of the OSD the Task Sequence log file can be found in:
“c:\windows\ccm\logs\smsts.log
Probably you will find 2 of those, 1 with a date appended. This is because log files can’t grow unlimited!
So you got your brand new Dell or other manufacturer’s hardware, deploy an OS with ConfigMgr 2012 and he, no go – chrash – missing drivers etc.
Well you might need the new Kernel Mode Driver Framework 1.11 (here) or the User Mode Driver Framework 1.11 (here).
But wait, this is an Windows Update! And I am doing OSD.
To successfully add the Driver Framework use good old dism
during OSD. Of course you will build a new reference image but in the meantime you have some deployment to do.
Okay let’s start.
First extract the files out of the .msu (I am using the x64 version for this). Use WinRar or 7zip for this.
In this folder create a batch file – install.cmd – containing following code:
Dism.exe /Image:%1\ /Add-Package /PackagePath:"%~dp0Windows6.1-KB2685811-x64.cab" /NoRestart
So the content of folder will now look like this (b.t.w. we do not need the .msu in the package ;-))
Create a ConfigMgr package from these files. No program needed! Distribute the content.
Now we can apply this in our Task Sequence. It has to be done AFTER the ‘Apply Operating System’, but BEFORE the installation of the ConfigMgr client.
Add a ‘Run Command Line’ and enter following as command:
Cmd.exe /c install.cmd %OSDTargetSystemDrive%
Reference the package.
Now the KMDF will be installed during the deployment!
You can do the same steps for the UMDF.
When you are having problems with your boot images (corruption or just malfunctioning) there might come a time you need to (re)-create one or maybe both.
This is a very straight forward process which will be described below.
You use the Windows ADK for this process. Depending on your version of ConfigMgr this will be the 8 (http://www.microsoft.com/en-us/download/details.aspx?id=30652) or 8.1 (http://www.microsoft.com/en-us/download/details.aspx?id=39982) version.
Run the ‘Deployment and Imaging Tools Environment’ As Administrator
This will open up the environment
Depending on the architecture the command to issue will be the following:
32-bit boot-image:
COPYPE.CMD x86 C:\WINPE86\
64-bit boot-image:
COPYPE.CMD amd64 C:\WINPE64\
ARM boot-image:
COPYPE.CMD arm C:\WINPEARM\
The target folder can be a folder of choice!
This will only take a few seconds.
And there it is, your freshly created boot image!
You can find this in the C:\WINPE64\media\sources folder.
In the ConfigMgr console go-to ‘Software Library – Overview – Operating Systems – Boot Images’, right-click and select ‘Add Boot Image’
Select your new image:
Provide information:
And there it is, your boot image in ConfigMgr.
Now you can work with this image as well!
Just remember to distribute the image, and when needed to enable ‘Deploy this boot image from PXE-enabled distribution point’
When doing OSD in SCCM 2012 R2 you can view the deployment information in the Task Sequence reports, but the Status Messages is really the preferred place for this.
First thing you need is to get the deployment ID of the Task Sequence you wish to monitor. You have to setup a query for each Task Sequence.
Go to Monitoring, Overview, Deployments.
(The Deployment ID are not displayed by default so you have to select this. Right-click and select ) and take a note of the Deployment ID
Deployment ID:
Build the Status Message Queries:
select
SMS_StatusMessage.*,
SMS_StatMsgInsStrings.*,
SMS_StatMsgAttributes.*,
SMS_StatMsgAttributes.AttributeTime
from SMS_StatusMessage
left join SMS_StatMsgInsStrings
on SMS_StatMsgInsStrings.RecordID = SMS_StatusMessage.RecordID
left join SMS_StatMsgAttributes
on SMS_StatMsgAttributes.RecordID = SMS_StatusMessage.RecordID
where SMS_StatMsgAttributes.AttributeID = 401 and SMS_StatMsgAttributes.AttributeValue = “ODV20002”
and SMS_StatMsgAttributes.AttributeTime >= ##PRM:SMS_StatMsgAttributes.AttributeTime## order by SMS_StatMsgAttributes.AttributeTime DESC
To launch the Query:
And an overview of the result!
Oke so sometimes your OSD Task Sequence in ConfigMgr 2012 (or even 2007..) fails on you? Tried all the usual troubleshoot steps..
Well maybe not all, check your Windows Updates!
Yes, Microsoft has confirmed that there are updates out there that will break your Task Sequence.
This is the KB about that:
KB2894518 – Software Updates That Require Multiple Reboots may Cause Task Sequence Failure within Configuration Manager (http://support.microsoft.com/kb/2894518)
If a Configuration Manager (ConfigMgr 2007 or ConfigMgr 2012) Task Sequence that leverages the Install Software Updates step installs a software update that triggers multiple reboots, the task sequence may fail to complete successfully. This occurs because the first reboot initiated by the software update is properly controlled by the Task Sequence, however the second reboot request is initiated by a Windows component (typically Component-Based Servicing) and therefore not controlled by the Task Sequence.
In short the following updates are affecting your OSD Task Sequence:
Especially the 2862330 has the statement in the description 😉
After you install security update 2862330 on a computer that is running Windows 7 or Windows Server 2008 R2, your computer may restart two times. The additional restart is required to make sure that the security update is completely installed. Installation of this update may leave the system in a partly updated and therefore vulnerable state. To address this issue, the update performs an additional step to update the computer. This additional step may require an additional restart of the computer.
Note Task sequence could fail in System Center Configuration Manager if the task sequence uses an “Install Software Updates” step to install a software updates that require multiple restarts.
SCCM 2012 R2 has some hotfixes you might need:
An update is available for the “Operating System Deployment” feature of System Center 2012 R2 Configuration Manager
This update resolves the following issues in Microsoft System Center 2012 R2 Configuration Manager.
Issue 1
After you enable the PXE Service Point role (http://msdn.microsoft.com/en-us/library/jj217832.aspx) on an instance of a specific distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running. Additionally, entries that resemble the following are logged in the Windows Application log:
Faulting application name: svchost.exe_WDSServer, version: 6.3.9600.16384, time stamp: 0x5215dfe3
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
Exception code: 0xc0000005
Fault offset: 0x000000000005f61a
Faulting process id: 0xae4
Faulting application start time: 0x01cec5d767184634
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll
Note This problem affects only distribution points that are installed on site servers.
Issue 2
When operating system image files are downloaded to Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behavior when the target client is running Windows PE or a full Windows operating system.
Per-computer variables for imported computers are not read in System Center 2012 R2 Configuration Manager
Per-computer task sequence variables that are defined for imported computers are filtered out of client policies. This prevents the variables from being read during task sequence execution. This problem does not affect per-computer variables that are defined for existing clients.
November 2013 anti-malware platform update for Endpoint Protection clients
This anti-malware platform update contains the following improvements:
José Rodas has made a nice overview of all the new features of the What’s New in System Center 2012 R2!
Here is the overview:
Configuration Manager R2
Operations Manager R2
Virtual Machine Manager
Orchestrator
Data Protection Manager R2
Other Resources
The original post can be found here!
I was going through the Optional Componets you can select to inject in your SCCM 2012 SP1 Boot image. Then I found this reference to the excellent Microsoft site:
http://technet.microsoft.com/en-us/library/hh824926.aspx
Here is an overview for the components. First the standard and then the optional ones!
|
Area |
Optional component name |
Description |
|
Scripting |
WinPE-Scripting |
WinPE-Scripting contains a multiple-language scripting environment that is ideal for automating system administration tasks, such as batch file processing. Scripts that run in the Windows Script Host (WSH) environment can call WSH objects and other COM-based technologies that support Automation, such as WMI, to manage the Windows subsystems that are central to many system administration tasks. Dependencies: Install WinPE-Scripting to make sure that full scripting functionality is available when you are using WinPE-NetFX4 and WinPE-HTA. The installation order is irrelevant. |
|
Scripting |
WinPE-WMI |
WinPE-WMI contains a subset of the Windows Management Instrumentation (WMI) providers that enable minimal system diagnostics. WMI is the infrastructure for management data and operations on Windows-based operating systems. You can write WMI scripts or applications to automate administrative tasks on remote computers. Additionally, WMI supplies management data to other parts of the operating system and products. |
|
Startup |
WinPE-SecureStartup |
New for Windows 8. WinPE-SecureStartup enables provisioning and management of BitLocker and the Trusted Platform Module (TPM). It includes BitLocker command-line tools, BitLocker WMI management libraries, a TPM driver, TPM Base Services (TBS), the Win32_TPM class, the BitLocker Unlock Wizard, and BitLocker UI libraries. The TPM driver provides better support for both BitLocker and the TPM in this preboot environment. Dependencies: Install WinPE-WMI before you install WinPE-SecureStartup. |
|
Network |
WinPE-WDS-Tools |
WinPE-WDS-Tools includes APIs to enable the Image Capture tool and a multicast scenario that involves a custom Windows Deployment Services client. It must be installed if you intend to run the Windows Deployment Services client on a custom Windows PE image. |
Optional Components
| Area |
Optional component name |
Description |
| Database |
WinPE-MDAC |
WinPE-MDAC supports Microsoft® Open Database Connectivity (ODBC), OLE DB, and Microsoft ActiveX® Data Objects (ADO). This set of technologies provides access to various data sources, such as Microsoft SQL Server®. For example, this access enables queries to Microsoft SQL Server installations that contain ADO objects. You can build a dynamic answer file from unique system information. Similarly, you can build data-driven client or server applications that integrate information from a variety of data sources, both relational (SQL Server) and non-relational. |
| File management |
WinPE-FMAPI |
WinPE-FMAPI provides access to the Windows PE File Management API (FMAPI) for discovering and restoring deleted files from unencrypted volumes. The FMAPI also provides the ability to use a password or recovery key file for the discovery and recovery of deleted files from Windows BitLocker Drive Encryption encrypted volumes. |
| Fonts |
WinPE-Font Support-JA-JP |
WinPE-Font Support-JA-JP contains two Japanese font families that are packaged as TrueType Collection (TTC) files. MS Gothic is the Windows Japanese user interface font in versions of Windows before Windows Vista®. MS Gothic contains a large character set and embedded bitmaps to ensure legible rendering at small sizes. Meiryo, a font that was introduced in Windows Vista, is designed specifically for use in a Microsoft ClearType® rendering environment. Meiryo does not include embedded bitmaps. Instead, Meiryo relies on hinting instructions to produce legible characters at small sizes. In addition, the module contains two Japanese bitmap fonts, App932.fon and Vga932.fon. The module also contains a bitmap-only TrueType font, Jpn_font.ttf. This font is used on boot screens. |
| Fonts |
WinPE-Font Support-KO-KR |
WinPE-Font Support-KO-KR contains three core Korean font families: Gulim, Batang and Malgun Gothic. Gulim is the legacy UI font and, as a TTC file, contains Gulim, GulimChe, Dotum and DotumChe. Batang is the legacy text font and is also a TTC file, containing Batang, BatangChe, GungSuh and GungSuhChe. Malgun Gothic, a font that was introduced in Windows Vista, is designed specifically for use in a ClearType rendering environment. Malgun Gothic does not include embedded bitmaps and instead relies on hinting instructions to produce legible characters at small sizes. |
| Fonts |
WinPE-Font Support-ZH-CN |
WinPE-Font Support-ZH-CN contains two Chinese font families that are packaged as TTC files. Simsun is the Simplified Chinese user interface font in Windows versions before Windows Vista. Simsun contains embedded bitmaps to ensure legible rendering at small sizes. The other TTC font is MingLiu. MingLiu has embedded bitmaps and provides support for the Hong Kong Supplementary Character Set (HKSCS). YaHei, a font that was introduced in Windows Vista, is designed specifically for use in a ClearType rendering environment. YaHei does not include embedded bitmaps. YaHei relies on hinting instructions to produce legible characters at small sizes. In addition, the module contains one bitmap-only TrueType font, Chs_boot.ttf. This font is used on boot screens. |
| Fonts |
WinPE-Font Support-ZH-HK and WinPE-Font Support-ZH-TW |
The Hong Kong and Taiwan optional components contain two Chinese font families that are packaged as TTC files. Simsun is the Simplified Chinese user interface font in Windows versions before Windows Vista. Simsun contains embedded bitmaps to ensure legible rendering at small sizes. MingLiu has embedded bitmaps and provides support for the HKSCS. JhengHei, a font that was introduced in Windows Vista, is designed specifically for use in a ClearType rendering environment. JhengHei does not include embedded bitmaps. JhengHei relies on hinting instructions to produce legible characters at small sizes. In addition, the module contains one bitmap-only TrueType font, Cht_boot.ttf. This font is used on boot screens. |
| HTML |
WinPE-HTA |
WinPE-HTA provides HTML Application (HTA) support to create GUI applications through the Windows Internet Explorer® script engine and HTML services. These applications are trusted and display only the menus, icons, toolbars, and title information that you create. |
| Microsoft .NET |
WinPE-NetFX4 |
WinPE-NetFX4 contains a subset of the .NET Framework 4.5 that is designed for client applications. Not all Windows binaries are present in Windows PE, and therefore not all Windows APIs are present or usable. Due to the limited API set, the following .NET Framework features have no or reduced functionality in Windows PE:
Dependencies: Install WinPE-WMI before you install WinPE-NetFX4. |
| Network |
WinPE-PPPoE |
WinPE-PPPoE enables you to use Point-to-Point Protocol over Ethernet (PPPoE) to create, connect, disconnect, and delete PPPoE connections from Windows PE. PPPoE is a network protocol for encapsulating Point-to-Point Protocol (PPP) frames inside Ethernet frames. PPPoE enables Windows users to remotely connect their computers to the web. By using PPPoE, users can virtually dial from one computer to another over an Ethernet network, to establish a point-to-point connection between the computers. The computers can use this point-to-point connection to transport data packets. |
| Network |
WinPE-RNDIS |
WinPE-RNDIS contains Remote Network Driver Interface Specification (Remote NDIS) support. WinPE-RNDIS enables network support for devices that implement the Remote NDIS specification over USB. Remote NDIS defines a bus-independent message set and a description of how this message set operates over various I/O buses. Therefore, hardware vendors do not have to write an NDIS miniport device driver. Because this Remote NDIS interface is standardized, one set of host drivers can support any number of bus-attached networking devices. |
| Windows PowerShell |
WinPE-PowerShell3 |
WinPE-PowerShell3 contains Windows PowerShell–based diagnostics that simplify using Windows Management Instrumentation (WMI) to query the hardware during manufacturing. You can create Windows PowerShell–based deployment and administrative Windows PE–based tools. In addition to deployment, you can use Windows PowerShell for recovery scenarios. Customers can boot in Windows RE and then use Windows PowerShell scripts to resolve issues. Customers are not limited to the toolsets that run in Windows PE. Similarly, you can build scripted offline solutions to recover some computers from no-boot scenarios. WinPE-PowerShell3 has the following known limitations:
Dependencies: Install WinPE-WMI > WinPE-NetFX4 > WinPE-Scripting before you install WinPE-PowerShell3. |
| Windows PowerShell |
WinPE-DismCmdlets |
WinPE-DismCmdlets contains the DISM PowerShell module, which includes cmdlets used for managing and servicing Windows images. For more info, see Deployment Imaging Servicing Management (DISM) Cmdlets in Windows PowerShell. Dependencies: Install WinPE-WMI > WinPE-NetFX4 > WinPE-Scripting > WinPE-PowerShell3 before you install WinPE-DismCmdlets. |
| Windows PowerShell |
WinPE-StorageWMI |
WinPE-StorageWMI contains PowerShell cmdlets for storage management. These cmdlets use the Windows Storage Management API (SMAPI) to manage local storage, such as disk, partition, and volume objects. Or, these cmdlets use the Windows SMAPI together with array storage management by using a storage management provider. WinPE-StorageWMI also contains Internet SCSI (iSCSI) Initiator cmdlets for connecting a host computer or server to virtual disks on external iSCSI-based storage arrays through an Ethernet network adapter or iSCSI Host Bus Adapter (HBA). Dependencies: Install WinPE-WMI > WinPE-NetFX4 > WinPE-Scripting > WinPE-PowerShell3 before you install WinPE-StorageWMI. |
| Recovery |
WinPE-WinReCfg |
WinPE-WinReCfg contains the Winrecfg.exe tool, and it enables the following scenarios:
Before Windows 8, the Winrecfg.exe tool was included in the Windows 7 OEM Preinstallation Kit (Windows OPK). |
| Setup |
Winpe-LegacySetup |
Winpe-LegacySetup contains all Setup files from the \Sources folder on the Windows media. Add this optional component when you service Setup or the \Sources folder on the Windows media. You must add this optional component together with the optional component for the Setup feature. To add a new Boot.wim file to the media, add the parent WinPE-Setup, either of the children (WinPE-Setup-Client or WinPE-Setup-Server), and Media optional components. Media Setup is required to support Windows Server® 2008 R2 installation. |
| Setup |
WinPE-Setup |
WinPE-Setup is the parent of WinPE-Setup-Client and WinPE-Setup-Server. It contains all Setup files from the \Sources folder that are common to the client and the server. |
| Setup |
WinPE-Setup-Client |
WinPE-Setup-Client contains the client branding files for the parent WinPE-Setup optional component. Dependencies: Install WinPE-Setup before you install WinPE-Setup-Client. |
| Setup |
WinPE-Setup-Server |
WinPE-Setup-Server includes the server branding files for the parent WinPE-Setup optional component. Dependencies: Install WinPE-Setup before you install WinPE-Setup-Server. |
| Storage |
WinPE-EnhancedStorage |
New for Windows 8. WinPE-EnhancedStorage enables Windows to discover additional functionality for storage devices, such as encrypted drives, and implementations that combine Trusted Computing Group (TCG) and IEEE 1667 (“Standard Protocol for Authentication in Host Attachments of Transient Storage Devices”) specifications. This optional component enables Windows to manage these storage devices natively by using BitLocker. |