Enable-SbecWdsBcd

Enable-SbecWdsBcd is accessible with the help of BootEventCollector module. To configure BootEventCollector, go through this link.

Synopsis

Enables the BCD settings in the offline boot images imported into the WDS server.

Description

The Enable-SbecWdsBcd cmdlet enables the Boot Configuration Data (BCD) settings in the offline boot images imported into the WDS server.

After importing a boot image (such as one modified by Enable-SbecBootImage) into Windows Deployment Services (WDS), WDS automatically generates the BCD configuration for it. Then, the boot event support must be enabled in this configuration. Because this BCD file is specially formatted, you must explicitly enable it.

Because WDS does not support the separate per-client BCD files, sharing of the same BCD files by the clients means that they must use the same secret key for the communication with the Boot Event Collector. The workaround is to use the common key for the setup, that can be either always be specified in the collector configuration as the second common key for all computers, or can be added to the collector configuration for the computers that are about to be set up, and removed after the setup is complete.

After modifying the BCD files, the WDS service must be notified (or restarted), to let it pick up the modified files. This cmdlet performs this notification unless instructed otherwise.

Parameters

-BcdPath

Specifies the explicit path of the per-image BCD file(s).

-BusParameters

Specifies the bus parameters to use to select the NIC of the target computer for communication. This value overrides the default choice of the first supported adapter. This value applies to all the computers that use this image; it can be used only if the hardware of these computers is sufficiently homogeneous. To find the value of bus parameters for a specific NIC on a machine, open Device Manager, and in Network Adapters select the desired device. Right-click the device, select Properties, select the Details tab, and then select Location information. It will display a string of the form PCI bus X, device Y, function Z. The bus parameter to specify in this example is “X,Y,Z”.

-CollectorIp

Specifies the IPv4 address of the host on which the Boot Event Collector is located.

-CollectorPort

Specifies the port number (common for the target and collector).

-Image

Specifies the Windows Deployment Services (WDS) Boot Image object(s) obtained from Get-WdsBootImage. You can also specify a manually constructed hash table instead of an object if it contains the Architecture and FileName properties.

-Key

Specifies the encryption key for the communication. This value must match the key specified in the collector configuration for this target.

-SkipNotifyWds

Indicates that this operation does not notify the WDS service about the changed files.

-WdsRoot

Specifies the root of the WDS directory tree. By default, this value is obtained from the path of the exported SMB share REMINST.

Syntax

Enable-SbecWdsBcd -BcdPath <String[]> -CollectorIp <String> -CollectorPort <UInt32> -Key <String> [-BusParameters <String>] [-WdsRoot <String>] [-SkipNotifyWds] [<CommonParameters>]

Enable-SbecWdsBcd [-Image <Array>] -CollectorIp <String> -CollectorPort <UInt32> -Key <String> [-BusParameters <String>] [-WdsRoot <String>] [-SkipNotifyWds] [<CommonParameters>]

—————–Example 1—————–
Update boot images in WDS
PS C:\> Get-WdsBootImage | Enable-SbecWdsBcd -CollectorIp “10.1.1.1” -CollectorPort 50000 -Key “w.x.y.z”
This command applies to all the boot images in WDS.

—————–Example 2—————–
Update a BCD file
PS C:\> Enable-SbecWdsBcd -BcdPath “c:\temp\boot.wim.bcd” -CollectorIp “10.1.1.1” -CollectorPort 50000 -Key “a.b.c.d” -SkipNotifyWds
This command updates the settings on a BCD file copied from WDS.

You can check the Version, CommandType and Source of this cmdlet by giving below command.

Get-Command Enable-SbecWdsBcd

You can also read about

To know more PowerShell cmdlets(Commands) on BootEventCollector click here

Click on this Link for an Single place where you get all the PowerShell cmdlet sorted based on the modules.

You can also refer other blogs on PowerShell at link

You can also refer other blogs on Microsoft at link

And also if you required any technology you want to learn, let us know below we will publish them in our site http://tossolution.com/

Like our page in Facebook and follow us for New technical information.

References are taken from Microsoft