Rather than having separate instances of an
object, it is globally defined and then referenced by other BCD objects as needed. Some
examples of these inheritable objects are listed in Table 1-6.
Table 1-6. Examples of Inheritable Objects
Alias GUID Description
{badmemory} 5189b25c-5558-
4bf2-bca4-
289b11bd29e2
Global RAM defect list
{bootloadersettings} 6efb52bf-1766-
41db-a6b3-
0ee5eff72bd7
Settings that should be
inherited by all Windows
boot loaders
{dbgsettings} 4636856e-540f-
4170-a130-
a84776f4c654
Debugger settings that can
be inherited by any boot
application
{emssettings} 0ce4991b-e6b3-
4b16-b23c-
5e0d9250e5d9
Emergency Management
Services settings that can
be inherited by any boot
application
{globalsettings} 7ea2e1ac-2e61-
4728-aaa3-
896d9d0a9f0e
Settings that should be
inherited by all boot
applications
{resumeloadersettings} 1afa9c49-16ab-
4a5c-901b-
212802da9460
Settings that should be
inherited by all resume
applications
16 Microsoft Windows Server 2008 Administration
As you can tell from the sample list, the objects are typically general global settings
that propagate to multiple objects. In addition to this, each inheritable object is classified
under two classes: library class and application class. Library class inheritable objects
can be inherited by any BCD object, whereas application class inheritable objects can be
inherited only by specified BCD applications.
Pages:
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50