11/3/2011

Microsoft System Center Configuration Manager 2007 provides a robust management solution for desktop computers, mobile computers, and servers (referred to in this document as traditional client computers). Windows Embedded Device Manager 2011 extends the capabilities of Configuration Manager to enable the management of specialized devices (specifically; thin client, point of service, digital signage, and kiosk). The result is a comprehensive device management solution that is robust and seamless, and provides an experience similar to managing traditional client computers.

For more information about Device Manager 2011, see the Windows Embedded Device Manager 2011 Administration Guide (http://go.microsoft.com/fwlink/?LinkId=211070) on Microsoft TechNet and the Windows Embedded Device Manager 2011 SDK Documentation (http://go.microsoft.com/fwlink/?LinkId=211072) on MSDN.

This document provides information about how to install Device Manager 2011 SP1, and also describes known issues with Device Manager 2011. This information is divided into the following sections:

Installing Device Manager 2011 Server

This section provides information about how to install Device Manager 2011 server.

Server Installation Requirements

The installer determines whether a system can host Device Manager 2011 server according to its Configuration Manager role, such as primary site, SMS Provider, or management point.

Important:
You must install Server Core Components for Device Manager 2011 on the computer that has the Configuration Manager WMI provider role installed. Server Core Components require Configuration Manager WMI SDK, which is available only on computers that have the Configuration Manager WMI provider role installed. You can install Device Manager 2011 on multiple primary site servers. Do not install Device Manager 2011 server on a secondary site server. For more information on installing Device Manager 2011 on multiple servers in a Configuration Manager hierarchy, see the Windows Embedded Device Manager 2011 Administration Guide (http://go.microsoft.com/fwlink/?LinkId=211070) on TechNet.

The installer retrieves the following information from Configuration Manager:

  • SQL database information:

    • SQL database computer name

    • SQL server instance

    • Database name

  • Site information:

    • Site name

    • Primary site or secondary site

    • Site code

    • Site server computer name

The installer also provides status and error messages, if any errors occur during installation.

The following table shows the server requirements for Device Manager 2011. For more information about hardware requirements, see the Hardware Requirements section in Configuration Manager 2007 General Supported Configurations (http://go.microsoft.com/fwlink/?LinkID=205865) in Configuration Manager Help.

Component Requirement

Hardware

733 MHz Pentium III processor, minimum required (2.0 GHz or faster recommended).

256 MB of RAM minimum required (1024 MB or more recommended).

5 GB of available hard disk space minimum (15 GB or more recommended if you are using operating system deployment).

Site system computers must have network connectivity to other Configuration Manager site systems.

Software

Configuration Manager 2007 R2 with Service Pack 2 (SP2) or later versions.

The Windows Server 2003 SP2 or Windows Server 2008 SP2 operating system (or later versions).

Note:
Download and install Windows Installer 4.5 before you install Device Manager 2011 server on a computer running Windows Server 2003 SP2.

Additional

Internet Information Services (IIS) and the .NET Framework 3.51, SP1 must be installed on the server where Server Core Components is installed.

The user account performing the installation must be in the Administrator group on the computer that has Device Manager 2011 server installed (or where it will be installed). This user account must also be a domain account and must have Administrator class permissions for all security rights on the site server.

The user account that is used for installation must have access to the log on as a service command. For information about how to grant user rights for a service account manually, see Grant User Rights to a Service Account (http://go.microsoft.com/fwlink/?LinkID=205852) on TechNet.

You must install Device Manager 2011 Server Core Components on the computer that has the Configuration Manager provider role installed. Server Core Components requires Configuration Manager WMI SDK, which is available only on computers that have the Configuration Manager provider role. Do not install Device Manager 2011 server on a secondary site server.

Installing All Server Components

This section provides information about how to use the Device Manager 2011 Setup Wizard to install all Device Manager 2011 server components on a primary site server.

Device Manager 2011 includes the server installer and the server upgrade installer. The upgrade installer should only be used if you have Device Manager 2011 server with no service packs installed.

After you upgrade to the latest version of Device Manager 2011, Device Manager 2011 collections from before the upgrade are retained under a new All Windows Embedded Devices Legacy collections node. All collections in that node have the appendage “Legacy” added to their name. You should re-create any collections that you or a third party created in the appropriate location in the collection hierarchy under All Windows Embedded Devices. After the first scheduled inventory is complete, all devices that belong in the predefined collections are added to the new predefined collections under All Windows Embedded Devices.  Before you delete the All Windows Embedded Devices Legacy collections node; you should associate any existing advertisements with the new device collections, and then wait for any actions associated with the legacy collections (for example, deploying advertisements to devices) to complete.

To install all server components
  1. Double-click the appropriate executable file for the language that you want to install.

    Language

    Installer Filename

    Upgrade Installer Filename

    English

    WEDMSvr_SP_ENU.exe

    WEDMSvrUpgrade_SP_ENU.exe

    French

    WEDMSvr_SP_FRA.exe

    WEDMSvrUpgrade_SP_FrA.exe

    German

    WEDMSvr_SP_DEU.exe

    WEDMSvrUpgrade_SP_DEU.exe

    Japanese

    WEDMSvr_SP_JPN.exe

    WEDMSvrUpgrade_SP_JPN.exe

    Russian

    WEDMSvr_SP_RUS.exe

    WEDMSvrUpgrade_SP_RUS.exe

    Simplified Chinese

    WEDMSvr_SP_CHS.exe

    WEDMSvrUpgrade_SP_CHS.exe

  2. On the welcome screen, click Next.

  3. On the End-User License Agreement screen, review the license agreement. If you agree to the terms, click I accept the terms of the License Agreement, and then click Next.

  4. (Optional) On the Custom Setup page, click Browse to change the installation location, and then click Next to install all three components on a site server.

  5. On the Pre-requisites page, click Next to confirm that you are installing the Server Core Components, Console Add-in, and Device Imaging Service.

  6. (Optional) On the Automatically create collections for Windows Embedded devices page, clear the Automatically create collections for Windows Embedded devices box to disable automatic generation of collections, and then click Next.

  7. On the ConfigMgr Credentials page, enter the following information and then click Next:

    • Site Server Name: Enter the name of the Configuration Manager site server that has the provider role installed.

    • ConfigMgr Admin Username: Enter the name of a user who is a member of the Configuration Manager Administrator group.

    • Password: Enter the password for the Configuration Manager administrator.

    • Confirm Password: Re-enter the password that you typed into the Password field.

    • Domain: Enter the name of the network domain for the Configuration Manager administrator.

  8. On the Summary page, review the summary of the installation that you are about to perform, and then click Next.

  9. On the Ready to Install page, click Install.

Known Issues with Installation

Column Names in the Configuration Manager Console Appear in English Only

Issue: Currently in Configuration Manager 2007, there is no support for localization of column names in Configuration Manager Console. All column names appear in English only.

Workaround: Install Configuration Manager 2007 SP2 R2 hotfix KB [2271736] (http://go.microsoft.com/fwlink/?LinkId=210772). To apply this hotfix, you must have System Center Configuration Manager 2007 Service Pack 2 (SP2) installed. 

Device Manager 2011 Server Installation on a Secondary Site Server Fails

Issue: When you install Device Manager 2011 server on a secondary site server, the installation fails.

Workaround: None. Installing Device Manager 2011 server on a secondary site server is not supported. The Device Manager 2011 server installer file will not prevent the installation on a secondary site server, but the installation will fail.

Known Issues with Device Configuration

Issues with Configuration Packages that Change Internet Explorer Settings

Issue: Each time a user tries to complete installation of a configuration package that changes Internet Explorer settings, the Internet Explorer First Run wizard appears.

Workaround: Run the Internet Explorer First Run wizard before you distribute a configuration package that configures Internet Explorer settings on a device.

Known Issues with Write Filters

Restarting Large Numbers of Devices with Write Filters Enabled Can Cause Performance Issues

Issue: The typical behavior for traditional client computers managed by Configuration Manager is to only provide changes in inventory information when devices are inventoried after restarting. With Device Manager 2011, devices with write filters enabled send complete inventory information when they are restarted instead of sending only the changes that have occurred since the last inventory cycle. Updating these devices with either advertisements that have write filter support or custom task sequences that have write filter support will cause the devices to restart.

You may experience performance issues (for example, excessive CPU usage or network traffic) when more than 500 devices with writer filters enabled are managed by a single site server and are restarted at the same time. The more devices with write filters enabled that you have on the network, the greater the performance issues will be.

Workaround: To avoid this issue, only deploy advertisements that have write filter support or custom task sequences that enable and restore write filters to collections of less than 500 devices that have write filters enabled.

Changing the Write Filter State of Devices Can Cause Inaccurate Inventory Information

Issue: If you add a new device with disabled write filters, let one or more inventory cycles run, and later enable the write filters on that device, then after each restart of the device the inventory information for this device will not be accurate until several inventory cycles have run. Specifically, one less inventory cycle than the number of inventory cycles that occurred after the write filter was enabled must be completed before inventory information for this device is accurate.

Workaround: Before you connect devices with write filter support to Configuration Manager, use File-Based Write Filter (FBWF) Manager or Enhanced Write Filter (EWF) Manager to enable the write filters on those devices. For more information about FBWF Manager, see FBWF Manager (http://go.microsoft.com/fwlink/?LinkId=210233) on MSDN. For more information about EWF Manager, see EWF Manager (http://go.microsoft.com/fwlink/?LinkId=210247) on MSDN. For more information about how to use a command-line tool with Configuration Manager, see Run Command Line (http://go.microsoft.com/fwlink/?LinkId=210268) in Configuration Manager Help.

Issues with Write Filter Handling and Windows Embedded Standard EWF RAM Mode or RAM Reg Mode

Issue: Devices running Windows Embedded Standard 7, Windows XP Embedded, and Windows Embedded Standard 2009 that use EWFs in RAM Mode or RAM Reg Mode should not use the following optimization options if they will be managed by Device Manager 2011 server: Use Less Overlay Space and Use Less Overlay Space and Less Writes. Using these optimization options for devices that are managed by Device Manager 2011 server (or for other devices that will have write filters enabled and disabled frequently) causes a corruption of the file system on the device. When an advertisement or task sequence with write filter handling is deployed to such devices, the file system on those devices will be corrupted.

Workaround: Devices that use EWF in RAM Mode or RAM Reg Mode should only use the default optimization option (Optimal Performance) if they will be managed by using Device Manager 2011 server. This issue can also be addressed by the device manufacturer if they use KB2393911 when creating the operating system image for their device.

Known Issues with Device Imaging

Obsolete Client Records Appear in Collections and Provide Incorrect Information in the Image Deployment Summary View

Issue:  Configuration Manager keeps a record of each device and traditional client computer. This is known as a client record. Occasionally, client records might become obsolete. Devices with obsolete client records are listed in collections and in the Image Deployment Summary view. When you try to deploy an operating system image to a collection of devices and that collection includes obsolete client records, the device imaging deployment finishes, but some devices do not appear to be imaged. The devices that do not appear to be imaged may be those with obsolete client records. The state of devices with obsolete client records shown in the Image Deployment Summary view will vary depending on the implementation of the device imaging component.

Workaround: To remove obsolete client records from a collection, see Delete Obsolete Client Discovery Data Task Overview (http://go.microsoft.com/fwlink/?LinkId=207705) on TechNet.

Other Known Issues

The WMI Standard Put Method Is Not Supported

Issue: The standard Windows Management Instrumentation (WMI) Put method is not supported for the EDM_ImageDeployment, EDM_ProvisoiningPackage, or EDM_ProvisoiningItem classes in Device Manager 2011. Calling the Put method from one of these classes causes the following exception: Invalid Class (WBEM_E_INVALID_CLASS).

Workaround: Use the following replacement methods for the standard WMI Put methods that are not supported in this release:

  • As a replacement for void EDM_ImageDeployment::Put, use static void EDM_ImageDeployment::Update.

  • As a replacement for void EDM_ProvisioningPackage::Put, use static int EDM_ProvisioningPackage::Put.

  • As a replacement for void EDM_ProvisioningItem::Put, use static void EDM_ProvisioningItem::Put.

Issues with Device Manager 2011 Deployments Across Time Zones

Issue: When scheduling any kind of request on Device Manager 2011 servers that are set to a different time zone than the Configuration Manager console, the request begins at the local time on Device Manager 2011 servers.

Workaround: None.