Embedded Lockdown Manager (ELM) Technical Reference (Standard 8)
June 3, 2016
Learn how to install Embedded Lockdown Manager (ELM) for Windows Embedded 8 Standard (Standard 8).
You can use the Embedded Lockdown Manager (ELM) to configure lockdown features on a Windows Embedded 8 Standard (Standard 8) device.
ELM is a snap-in to the Microsoft Management Console (MMC). You can use ELM directly on a Standard 8 device, or you can use ELM on a development computer and then remotely connect to a Standard 8 device.
ELM automatically detects which lockdown features are installed on the device, and displays configuration options for only those features. ELM uses Windows Management Instrumentation (WMI) to detect and change configuration settings.
You can use ELM to configure the following lockdown features for Standard 8:
Prevents undesirable pop-up windows and dialog boxes from appearing on the screen.
Suppresses undesirable key combinations, such as Ctrl+Alt+Delete.
Launches an alternate shell instead of the standard Windows 8 shell.
Protects physical media from write operations.
To connect to a device, you must use an administrator account and the password cannot be blank.
If you want to use ELM to remotely manage your device, you may need to configure your device for remote access. For more information, see Configure a Device for Remote Management.
The WMI service cancels Lockdown feature tasks when there is insufficient physical memory available. To resolve this issue, read the KB article.
Install Embedded Lockdown Manager
To install ELM, the following are required:
The computer or device must meet or exceed the following requirements:
- 1 GHz 32-bit or 64-bit processor
- 1 GB of operating system memory (32-bit system) or 2 GB of operating system memory (64-bit system)
- 2 GB of free hard drive space for complete installation
To install ELM on a development or host computer, the computer must meet or exceed the following requirements:
- It must be running one of the following operating systems:
- Windows 7 (x86 or x64)
- Windows 8 (x86 or x64)
- Windows Server 2008 R2 (x64 only)
- Windows Server 2012 (x64 only)
- It must have the following software installed:
- .NET Framework 2.0 on Windows 7
- .NET Framework 3.5 on Windows Server 2008 R2
- .NET Framework 4.0 or later on Windows 8 and Windows Server 2012
- Microsoft Management Console (MMC)
Installing the ELM snap-in on Windows Server 2008 R2 that has the .NET Framework 4.0 installed will cause MMC to throw an error. To work around this issue, uninstall .NET Framework 4.0 before you install the ELM snap-in.
To install Embedded Lockdown Manager on a development or host computer
Navigate to the root folder on the Windows Embedded 8 Standard Toolkit disk.
If you are installing ELM on a 32 bit OS, run:
- Windows6.1-KB2758707-x86.msu if you are installing on Windows 7
- Windows8-RT-KB2758707-x86.msu if you are installing on Windows 8
If you are installing ELM on a 64 bit OS, run:
- Windows6.1-KB2758707-x64.msu if you are installing on Windows 7 or Windows Server 2008 R2
- Windows8-RT-KB2758707-x64.msu if you are installing on Windows 8 or Windows Server 2012
Follow the instructions on the Install Wizard.
When installation is complete, on your development or host computer, configure ELM to connect to a remote device. You may need to configure the device to enable remote WMI traffic. For more information, see Configure a Device for Remote Management.
To install Embedded Lockdown Manager on a Standard 8 device by using IBW or ICE
Add the Embedded Lockdown Manager feature module when you are building a device image with IBW or ICE.
When the image is installed and running on your device, follow the procedure in the ELM Help file to connect to Local computer.
Do not use the .msu files intended for installation on a development or host computer to install ELM on a Standard 8 device at run time. ELM must only be added to a Standard 8 image by using IBW or ICE at design time.
Where to Find Embedded Lockdown Manager
In a typical installation, ELM can be found at the following location:
Be sure that ELM is installed on a device before applying ELM update packages. ELM update packages may appear to install successfully even when ELM does not exist on the device.