Message

The following client booted from PXE: 

Hardware Address: %1
IP: %2
Device ID: %3
ClientArchitecture: %4
Prestaged: %5

Fields

Message

The Following Client started TFTP Download: 

Client IP: %1
Filename: %2
File Size: %3
Client Port: %4
Server Port: %5
Variable Window: %6

Fields

Message

The Following Client completed TFTP Download: 

Client IP: %1
Filename: %2
File Size: %3
Client Port: %4
Server Port: %5
Variable Window: %6

Fields

Fields

Message

The Following Client failed TFTP Download: 

Client IP: %1
Filename: %2
ErrorCode: %3
File Size: %4
Client Port: %5
Server Port: %6
Variable Window: %7

Fields

Message

The following WDS Client has started: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
ClientVer: %6
WinPEVer: %7

Fields

Message

The following WDS Client has processed unattend mode: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
UnattendMode: %6

Fields

Message

The following WDS Client has selected Image: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
ImageGroup: %6
ImageName: %7
FullUserName: %8

Fields

Message

The following WDS Client has started Image Transfer: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
ImageGroup: %6
ImageName: %7
MulticastNamespace: %8

Fields

Message

The following WDS Client has ended Image Transfer: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
ImageGroup: %6
ImageName: %7
MulticastNamespace: %8

Fields

Message

The following WDS Client has downgraded Image Transfer: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
ImageGroup: %6
ImageName: %7
MulticastNamespace: %8

Fields

Message

The following WDS Client has started Image Apply: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
ImageGroup: %6
ImageName: %7

Fields

Message

The following WDS Client has ended Image Apply: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5

ImageGroup: %6
ImageName: %7

Fields

Message

The following WDS Client has started Post Apply Actions: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5

Fields

Message

The following WDS Client has ended Post Apply Actions: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5

Fields

Message

The following WDS Client has ended: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5

Fields

Fields

Message

The following WDS Client has encountered Domain Join Error: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
MachineName: %6
MachineOU: %7
ErrorCode: %8

Fields

Fields

Message

The following WDS Client has encountered Fatal Error: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
ErrorMessage: %6

Fields

Message

The following WDS Client has this message: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
Message: %6

Fields

Message

Namespace Registered: 

NamespaceName: %1
ContentProvider: %2
NamespaceType: %3

Fields

Message

Namespace Unregistered: 

NamespaceName: %1
ContentProvider: %2

Fields

Message

Multicast Session Started: 

NamespaceName: %1
ObjectName: %2

Fields

Message

Multicast Session Ended: 

NamespaceName: %1
ObjectName: %2

Fields

Message

Client joined Multicast Session: 

ClientMAC: %1
ClientIP: %2
NamespaceName: %3
ObjectName: %4

Fields

Message

Client exited Multicast Session: 

ClientMAC: %1
ClientIP: %2
NamespaceName: %3
ObjectName: %4

Fields

Message

Client forced out of Multicast Session: 

ClientMAC: %1
ClientIP: %2
NamespaceName: %3
ObjectName: %4
Reason: %5

Fields

Message

The following WDS Client has encountered an inaccessible driver package: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
DriverPackage: %6
ErrorCode: %7

Fields

Message

The following WDS Client has started offline driver injection: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5

Fields

Message

The following WDS Client has ended offline driver injection: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5

Fields

Message

The following WDS Client has encountered a failure while performing offline driver injection: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
DriverPackage: %6
ErrorCode: %7

Fields

Message

Ddp request received for the following client: 

MAC: %1
IP: %2

Fields

Message

Ddp request failed for the following client: 

MAC: %1
IP: %2
ErrorCode: %3

Fields

Message

Ddp request successfully completed for the following client: 

MAC: %1
IP: %2
NumDriverPackages: %3

Fields

Message

Client demoted to slower Multicast Session: 

ClientMAC: %1
ClientIP: %2
NamespaceName: %3
ObjectName: %4

Fields

Message

The following WDS Client has selected Image: 

SessionGuid: %1
MAC: %2
IP: %3
ClientDeviceID: %4
ClientArchitecture: %5
ImageGroup: %6
ImageName: %7
ImageLanguage: %8
ImageArchitecture: %10
FullUserName: %9

Fields

Message

The following client attempted to boot from PXE but was ignored because it is not recognized: 

Hardware Address: %1
IP: %2
Device ID: %3
ClientArchitecture: %4
Prestaged: %5

Fields

Fields

Message

[%1] %3

Fields

Fields

Message

[%1] %3

Fields

Fields

Message

[%1] %3

Fields

Fields

Message

[%1] %3

Fields

Fields

Message

[%1] %3

Fields

Fields

Message

[%1] %3

Fields

Fields

Message

[%1] %3

Fields

Fields

Message

[%1/%2] %4

Fields

Fields

Message

[%1/%2] %4

Fields

Fields

Message

[%1/%2] %4

Fields

Fields

Message

[%1/%2] %4

Fields

Fields

Message

[%1/%2] %4

Fields

Fields

Message

[%1/%2] %4

Fields

Fields

Message

[%1/%2] %4

Fields

Fields

Message

[%1/%2/%3] %5

Fields

Fields

Message

[%1/%2/%3] %5

Fields

Fields

Message

[%1/%2/%3] %5

Fields

Fields

Message

[%1/%2/%3] %5

Fields

Fields

Message

[%1/%2/%3] %5

Fields

Fields

Message

[%1/%2/%3] %5

Fields

Fields

Message

[%1/%2/%3] %5

Fields

Fields

Message

A device query was successfully processed (status %3):

Input:
%1

Output:
%2

Fields

Fields

Message

A device query failed with status %3:

Input:
%1

Output:
%2

Fields

Fields

Message

Provider [%1] processed a device query with status %5, response type %4:

Input:
%2

Output:
%3

Fields

Fields

Message

Provider [%1] failed to process a device query with status %5, response type %4:

Input:
%2

Output:
%3

Fields

Fields

Message

Provider [%1] successfully added a device with status %5:

Device Name: %2

Initial Metadata:
%3

Fields

Fields

Message

Provider [%1] failed to add a device with status %5:

Device Name: %2

Fields

Fields

Message

Provider [%1] successfully deleted device [%2]; status code %5.

Fields

Fields

Message

Provider [%1] failed to delete device [%2]; status code %5.

Fields

Fields

Message

Provider [%1] successfully modified a device with status code %5:

Device Name: %2

New Metadata:
%3

Fields

Fields

Message

Provider [%1] failed to modify a device with status code %5:

Device Name: %2

New Metadata:
%3

Note that the device may or may not be modified with the New Metadata; this is at the discretion of the Provider.

Fields

Fields

Message

Provider [%1] successfully retrieved metadata for a device with status code %5:

Device Name: %2

Metadata:
%3

Fields

Fields

Message

Provider [%1] failed to retrieve metadata for a device with status code %5:

Device Name: %2

Fields

Fields

Message

The server successfully processed a request for available providers with status code %5; %4 providers available.

Fields

Fields

Message

The server failed to process a request for available providers with status code %5.

Fields

Fields

Message

The server processed a metadata match request:

Object ID: %1

Object Metadata:
%2

Request Metadata:
%3

Match Result: %4

Fields

Fields

Message

There was an attempt to overwrite an object's metadata which failed because the request did not pass the internal filter for this object.

Object ID: %1
5nObject Filter:
%2

Request Metadata:
%3

Fields

Fields

Message

The server successfully retrieved metadata for an object with status code %3:

Object ID: %1

Object Metadata:
%2

Fields

Fields

Message

The server failed to retrieve metadata for an object with status code %3:

Object ID: %1

Fields

Fields

Message

The server successfully modified metadata for an object with status code %3:

Object ID: %1

New Metadata:
%2

Fields

Fields

Message

The server failed to modify metadata for an object with status code %3:

Object ID: %1

New Metadata:
%2

Fields

Fields

Message

A new metadata object was successfully registered in the server with status code %3:

Object ID: %1

Object Metadata:
%2

Parent: %4

Fields

Fields

Message

The server failed to register a new metadata object with status code %3:

Object ID: %1

Object Metadata:
%2

Parent: %4

Fields

Fields

Message

An object was successfully deleted with status code %3:

Object ID: %1

Fields

Fields

Message

The server failed to delete an object with status code %3:

Object ID: %1

Fields

Fields

Message

An object's parenting relationship was successfully modified with status code %3:

Object ID: %1

New Parent: %4

Fields

Fields

Message

The server failed to modify an object's parenting relationship with status code %3:

Object ID: %1

New Parent: %4

Fields

Message

WdsUtil.exe was run with the following command line:

%1

Fields

Message

A WdsUtil.exe command was successfully executed.

Command Line: %1

Status Code: %2

Fields

Message

A WdsUtil.exe command failed.

Command Line: %1

Status Code: %2

Fields

Message

The following VHDX apply has started: 

SourceFile: %1
SourceFileSize: %2
SourceDiskSize: %3 bytes
DestinationPath: %4
DestinationDiskSize:%5 bytes

Fields

Message

The following VHDX apply has completed: 

SourceFile: %1
SourceFileSize: %2
SourceDiskSize: %3 bytes
DestinationPath: %4
DestinationDiskSize:%5 bytes

Fields

Message

The following VHDX apply has failed: 

SourceFile: %1
SourceFileSize: %2
SourceDiskSize: %3 bytes
DestinationPath: %4
DestinationDiskSize:%5 bytes

Fields

Fields

Message

The PXE server processed a request from a client of architecture %1.  However there were no boot images installed for this architecture.  PXE clients of this architecture will not be able to complete the boot process successfully.  To resolve this problem, add at least one boot image for this architecture.

Fields

Message

A %3 buffer was created for reading file %1.

Fields

Message

A %3 buffer created for reading file %1 was deleted.

Fields

Message

An endpoint was opened by provider %2.

Type: %1
Address: %3

Fields

Message

An endpoint was closed by provider %2.

Type: %1
Address: %3

Fields

Message

WdsCim was invoked with the following command line:

%1

Fields

Message

A WdsCim method was successfully executed.

Command Line: %1

Status Code: %2

Fields

Message

A WdsCim method failed.

Command Line: %1

Status Code: %2

Fields