Building a Single or Multi User Baseline Configuration

  • 项目

5/10/2007

You can create a single or multi user baseline configuration by adding the Minlogon or Winlogon components. In the Minlogon baseline configuration, the user is always logged on as the system user. You can use this configuration if your application does not require the user to log on to the system by using a local device or domain account. The Minlogon configuration is smaller than Winlogon because it has fewer component dependencies. The Minlogon configuration includes full Win32 support. This means that applications can link to Kernel32, GDI32, User32, and Advapi32 libraries.

To build a single or multi user baseline configuration

  • Follow the procedure described in Building a Kernel Baseline Configuration, then perform the following steps:

    1. Remove the Session Manager (Kernel-only configuration demo) component from your configuration.

    2. Add the Session Manager (Windows subsystem) component to your configuration.

    3. Check and resolve your dependencies.

    4. When prompted to select a session manager, select either the Minlogon component for a single user system, or Winlogon for a multi user system.

      Note

      Because Winlogon requires SCM and LSASS, you cannot remove these components.

    5. Check your dependencies again. When you are prompted to select a shell, select the Command shell component. This component offers the smallest footprint and starts Cmd.exe after logging on the user.

    6. Configure your session manager, Minlogon or Winlogon, by selecting Settings under the component in your configuration and showing Other Extended Properties.

      Note

      Minlogon does not include the PnP (User-mode) component. If user-mode Plug and Play is required to configure your device, add the PnP component. Note that PnP requires SCM.

    7. Build the run-time image.

    8. Boot the run-time image. The command shell (Cmd.exe) appears.

  • Follow the procedure described in Building a Kernel Baseline Configuration, then perform the following steps:

    1. Remove the Session Manager (Kernel-only configuration demo) component from your configuration.

    2. Add the Session Manager (Windows subsystem) component to your configuration.

    3. Check and resolve your dependencies.

    4. When prompted to select a session manager, select either the Minlogon component for a single user system, or Winlogon for a multi user system.

      Note

      Because Winlogon requires SCM and LSASS, you cannot remove these components.

    5. Check your dependencies again. When you are prompted to select a shell, select the Command shell component. This component offers the smallest footprint and starts Cmd.exe after logging on the user.

    6. Configure your session manager, Minlogon or Winlogon, by selecting Settings under the component in your configuration and showing Other Extended Properties.

      Note

      Minlogon does not include the PnP (User-mode) component. If user-mode Plug and Play is required to configure your device, add the PnP component. Note that PnP requires SCM.

    7. Build the run-time image.

    8. Boot the run-time image. The command shell (Cmd.exe) appears.

See Also

Other Resources

Baseline Configurations