The following features are not supported in this beta release of Configuration Manager v.Next:

• Network Access Protection (NAP)
  
  
• Out of band management
  
  
• Native mode (and Internet-based client management) except for supporting mobile devices
  
  

WORKAROUND    None.

If you run Setup from a network share instead of running it locally, Setup might crash after the Setup Prerequisite Checker finishes.

WORKAROUND    Copy the installation media locally, and then run Setup from this local copy.

On the Setup Action Status Monitoring page of the Setup Wizard, the Initialize Database Replication Service action might continue to display the status of In Process and never update.

WORKAROUND    Providing that the remaining snapshot actions finish successfully, you can safely ignore the In Process status.

Running prereqchk.exe /? displays Help for the Setup Prerequisite Checker that includes options for SLP, FSP, and RSP that are not implemented.

WORKAROUND    None.

If KB977443 is not installed on the computer that is running Microsoft SQL Server and that you use for the site database, the Setup Prerequisite Checker prevents Setup from continuing. However, if the SQL Server instance that is used for the site database resides on a computer other than the site server computer, the Setup Prerequisite Checker displays the name of the site server computer instead of displaying the name of the computer that is running SQL Server.

WORKAROUND    Install KB977443 on the computer that is running SQL Server instead of the site server computer.

Replication between Configuration Manager sites requires that SQL Server is configured to use the static TCP port 1433. Additionally, SQL Server Service Broker requires the static TCP port 4022 to send and receive messages. For replication to be successful when Windows Firewall is enabled, there must be a firewall exception for one of the following:

• Sqlservr.exe
  
  
• Ports TCP 1433 and TCP 4022
  
  

Configuration Manager Setup Prerequisite Checker verifies that these exceptions are configured correctly when you install a central administration site or a primary site and Windows Firewall is enabled. However, by default, SQL Server named instances use dynamic ports, and you must manually reconfigure your named instance to use the static TCP port 1433. SQL Server named instances also require the SQL Server Browser Service, which uses both TCP and UDP port 1434. If you select a named instance for SQL Server, the Setup Prerequisite Checker does not verify or warn you about these additional requirements.

WORKAROUND    If you use a SQL Server named instance for your site, manually verify the following:

• The SQL Server named instance is configured to use the static TCP port 1433. For more information about how to configure SQL Server to listen on a specific port by using SQL Server Configuration Manager, see How to: Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager) (http://go.microsoft.com/fwlink/?LinkID=189544).
  
  
• Windows Firewall is configured to allow TCP  ports 1434 and UDP 1434.
  
  

Secondary sites in Configuration Manager v.Next use SQL Server to replicate data with their primary site. When the secondary site server has Windows Firewall enabled, and the ports required for SQL Server-based replication are not allowed, secondary site installation fails.

WORKAROUND    Before you install a secondary site, configure Windows Firewall on the secondary site server to allow the following ports:

• TCP 1433
  
  
• TCP 4022
  
  
• TCP and UDP 1434 (required only if you are using SQL Server Express or a SQL Server named instance)
  
  

To support mobile devices in native mode, the server that is running the management point requires Internet Information Services (IIS) to be configured to use a Web Server certificate for server authentication. The Setup Prerequisite Checker does not verify or warn you that this native mode certificate is missing, and in this scenario, the management point fails to install, and the SMS Provider and WMI Provider stop responding.

WORKAROUND    Manually verify that the default Web site in IIS is configured with the required Web Server certificate before you install a Configuration Manager site to support mobile devices.

If you install a site system role on a computer other than the site server, installation fails if the destination server does not have the Microsoft .NET Framework 4 installed. In this scenario, you see Fatal MSI Error in the installation .msi log file for the site system role.

WORKAROUND    Install the full version of the Microsoft .NET Framework 4 (http://go.microsoft.com/fwlink/?LinkID=193048) before you install any site system roles on computers other than the site server.

On the Database Server page of the Setup Wizard, Setup performs a version check for the specified Microsoft SQL Server. However, if Microsoft SQL Server 2008 is detected without SP1, you see the following error message:

Configuration Manager requires Microsoft SQL Server 2008 or later. You must upgrade SQL Server before installing Configuration Manager.

This error message should say that Configuration Manager requires Microsoft SQL Server 2008 Service Pack 1 or later.

WORKAROUND    Install Microsoft SQL Server 2008 SP1 on the computer running Microsoft SQL Server.

When the SQL Server Agent for a primary site is configured to use an account other than Local System, Setup finishes installing the primary site but cannot configure the permissions required for database replication. In this scenario, the ConfigMgr_SQL Replication group contains the NT AUTHORITY\NETWORK SERVICE account instead of the computer account for the primary site server, and the following information is logged in the ConfigMgr_Setup.Log file:

INFO: Adding NT AUTHORITY\NETWORK SERVICE to group ConfigMgr_SQLReplication on parent site database server <ServerName>.

WORKAROUND    Reconfigure the SQL Server Agent service logon account so that it uses Local System account. Then, remove the NT AUTHORITY\NETWORK SERVICE account from the ConfigMgr_SQL Replication group and add the computer account for the primary site server to this group. No further action is required.

Setup is logically separated into two parts: the core setup and monitoring. After the core setup is complete, the site server continues to be configured in the background while Setup monitors the status of those background tasks. On the Setup Action Status Monitoring page of the Setup Wizard, a list of actions that Setup has to complete and the status of each action are displayed. However, the Next button is enabled before the Setup program finishes, which lets you complete the Setup Wizard and open the Configuration Manager console for a site that is still being configured. This could potentially cause data loss or other unexpected behavior if you make changes on a new primary site before the configuration is completed.

WORKAROUND    Before you connect to a new primary site and make changes in the Configuration Manager console, verify that all actions listed on the Setup Action Status Monitoring page are successfully completed. If you close the Setup Wizard, click Monitoring in the Configuration Manager console, click Database Replication, and then verify that database replication is completed for the site. Do not make any changes on the primary site until database replication has completed successfully.

You can use a scripted installation by using SETUP.EXE /SCRIPT <path>\<script.ini> to fully automate the installation of a site. However, if the option to download the latest Configuration Manager updates is selected within the script file, Setup displays a Command Prompt window that requires you to click Close before Setup can continue.

WORKAROUND    When you use scripted installations, ensure that you have already downloaded the latest Configuration Manager updates to a local path by using SetupDL.exe, and then choose the option to use files that have already been downloaded. In the <script.ini> file, the Options section appears as follows:

[Options]

PrerequisiteComp=1

PrerequisitePath=<path to already downloaded updates>

If you install a primary site and you do not have the ConfigMgr Administrator role assigned to your account at the central administration site, you might not be able to see objects in the Configuration Manager console and new connections that you make to the primary site fail to connect. When the initial replication from the central administration site is completed, you see fewer objects in the console.

WORKAROUND    In the central administration site, assign the ConfigMgr Administrator role security role to your account.

When a secondary site fails to install correctly, the Configuration Manager console displays the site to be in a Failed state. You cannot retry or repair the failed secondary site installation, even if you correct the underlying issue.

WORKAROUND    After you correct the underlying issue, delete the failed secondary site and reinstall it by using the Create Secondary Site Wizard.

Migration from Configuration Manager 2007 to Configuration Manager v.Next uses SQL Server communication and the following network protocols: NetBIOS, SMB, RPC (for WMI calls). If Windows Firewall or external firewalls block this communication, migration cannot be completed.

WORKAROUND    Allow the following traffic and communication between the site servers in the Configuration Manager v.Next hierarchy and the specified site servers in the Configuration Manager 2007 primary site:

• NetBIOS/SMB - 445 (TCP)
  
  
• RPC (WMI) - 135 (TCP)
  
  
• SQL Server - 1433 (TCP)
  
  

If you migrate an advertisement from Configuration Manager 2007 to a software deployment in Configuration Manager v.Next, change the optional or assigned advertisement configuration in Configuration Manager 2007, and then migrate the advertisement again, the newly migrated software deployment will not be configured for the optional or assigned change.

During the migration process, the advertisement configuration for optional and assigned is converted to the software deployment purpose of Available for an optional advertisement and Required for an assigned advertisement.

WORKAROUND    Delete the migrated software deployment in Configuration Manager v.Next, and create a new software deployment with the updated deployment purpose of Available or Required.

If you run the Migration Job Wizard, select the job type Object migration, by collection, and then select a collection that has no advertisements or software update deployments applied to it, the Object Migration page displays no objects and a popup window informs you that the system is collecting dependencies. In this scenario, no objects are displayed, and the Back and Next buttons in the wizard are disabled. You cannot complete the wizard.

WORKAROUND    Click Cancel to exit the wizard. Run the wizard again, and select only collections that have advertisements or software update deployments applied to them.

An operating system image or operating system drivers from Configuration Manager 2007 fails to migrate to Configuration Manager v.Next if the SMS Provider in the Configuration Manager v.Next site that runs the migration job does not have Read permission to the source file location of the operating system image or operating system drivers. In this scenario, you might see error messages similar to the following in the Smsprov.log on the computer running the SMS Provider in the Configuration Manager v.Next site:

Error messages related to an operating system image:

*~*~<drive>:\<folder>\<folder>\siteserver\sdk_provider\smsprov\sspimagepackage.cpp(475) : Failed to get the image property from the source WIM file due to error 80070005~*~*

*~*~Failed to get the image property from the source WIM file due to error 80070005 ~*~*

Error messages related to an operating system driver:

*~*~<drive>:\<folder>\<folder>\siteserver\sdk_provider\smsprov\ssppackage.cpp(3278) : CIContentSourcePath - '\\Server\Share\driverslocation\' could not be found~~*~*

*~*~CIContentSourcePath - '\\<Server>\<Share>\<driverslocation>\' could not be found~ ~*~*

WORKAROUND    Configure the source file location of the operating system image files and operating system drivers with Read permission for the computer account running the SMS Provider in the Configuration Manager v.Next site. By default, the SMS Provider is installed on the site server computer.

The default collection in Configuration Manager 2007 named All Unknown Computers is incorrectly detected to contain devices and users. Collections that contain devices and users cannot be migrated. As a result, Configuration Manager v.Next cannot migrate this collection and any advertisements, task sequences, or packages associated with this collection.

WORKAROUND    If you use the All Unknown Computers collection in Configuration Manager 2007 and you want to migrate this collection and its associated objects (advertisements, task sequences, packages), perform the following steps:

1. In Configuration Manager 2007, identify which advertisements are targeted to this collection.
   
   
2. In Configuration Manager 2007, identify which task sequences and packages are configured for these advertisements.
   
   
3. In Configuration Manager v.Next, create a migration job that selects these task sequences and packages.
   
   
4. In Configuration Manager v.Next, after the migration job is completed, recreate the advertisements by creating software deployments that are configured with the migrated task sequences and packages, and then assign these software deployments to the All Unknown Computers collection.
   
   

When you migrate from Configuration Manager 2007 to Configuration Manager v.Next, you cannot select software update templates.

WORKAROUND    Create new software updates templates in Configuration Manager v.Next.

When you edit the migration exclusion list, you might see duplicate object entries. This duplication is a display issue only.

WORKAROUND    None.

When you create a migration job that is configured to overwrite a previously migrated object, the migration fails if this object was previously migrated with a different primary site mapping that contains a different destination. In this scenario, you will see error messages similar to the following in the migmctrl.log file:

[MigrationManager]: Set the status of the entity SMS_Package.PackageID='<ID>' to Failed.~~ $

ERROR: [MigrationManager]: Entity SMS_Package.PackageID='<ID>' failed with: Provider Exception: ~instance of SMS_ExtendedStatus~{~CauseInfo = "4";~Description = "CSspPkgProgram: Unknown package error!";~  ErrorCode = 2152205061;~  File = "<path>\\siteserver\\sdk_provider\\smsprov\\ssppackage.cpp";~  Line = 927;~  Operation = "PutInstance";~  ParameterInfo = "";~  ProviderName = "ExtnProv";~  StatusCode = 2147749889;~};~~~ $

[MigrationManager]: Mark the job as failed so that admin can restart the job~~

WORKAROUND    Migrate the object again and use the same primary site mapping that was previously used to migrate this object.

When you configure a primary site mapping and select Use the Local system Account from the destination Configuration Manager v.Next site server to connect to the Configuration Manager 2007 site serverfor the SMS Provider, all migration jobs fail. In this scenario, the following error message is logged in the migmctrl.log on the site server to which the primary site mapping applies:

ERROR: [MigrationManager]: Could not decrypt credentials~~

WORKAROUND    For the Configure Mapping option, do not select Use the Local system Account from the destination Configuration Manager v.Next site server to connect to the Configuration Manager 2007 site server for the SMS Provider. Instead, select User Account and then specify a user account for the SMS Provider.

When you have boot images that are available on Configuration Manager 2007 distribution points and Configuration Manager v.Next distribution points, and the content version for these boot images are the same, the might be incorrectly directed to the Configuration Manager 2007 distribution point. When a boot image is migrated, the content version remains the same but the content format is changed. The Configuration Manager 2007 boot image content is not compatible with Configuration Manager v.Next.

If the Configuration Manager v.Next client tries to run the boot image with the Configuration Manager 2007 format, the task sequence associated with this action will fail and you might see a pop-up dialog box with the following error message on the Configuration Manager v.Next client:

Task sequence: <name> has failed with error code (0x80091007). For more information, please contact your system administrator or helpdesk operator.

This error message is also recorded in the task sequence log file (smsts.log) on the client.

WORKAROUND    After you migrate the boot image, create a copy of boot image and distribute it to Configuration Manager v.Next distribution points. Then, configure the migrated task sequence that referenced the migrated boot image so that it now references copied boot image.

When you migrate packages from Configuration Manager 2007 to Configuration Manager v.Next, the migration job attempts to copy the compressed source files for the packages from the Configuration Manager 2007 site. If the account specified as the SMS Provider connection for the source site in the primary site mapping does not have Read permission to the compressed source files location, the package is migrated to Configuration Manager v.Next without the compressed source files. In this scenario, the Configuration Manager v.Next site server running the migration job records the following error in the Migmctrl.log file:

WARNING: [MigrationManager]: Failed to copy content for object SMS_Package.PackageID='V4C00008': Access to the path '\\SCCM10328\SMS_CPSC$\V4C00008.PCK' is denied.. Continuing

When you try to distribute software that references these compressed source files, and the source files are not available from the specified location, the following status message is displayed:

SMS Distribution Manager failed to process package "Package Name" (Package ID = <number>)

WORKAROUND    Configure the compressed source file location with Read permission for the account specified as the SMS Provider connection for the source site. Then create another migration job to include the packages that contain the compressed source files and select the option Migrate the updated data and overwrite the existing data in the Configuration Manager v.Next site.

When you migrate packages and advertisements from Configuration Manager 2007, and the packages remain available from Configuration Manager 2007 distribution points, Configuration Manager v.Next clients might be unable to access this content. This occurs when the package is updated (the source version is incremented) in Configuration Manager 2007. In this scenario, although the package in Configuration Manager v.Next correctly synchronizes with the later version, the package’s associated migrated advertisement fails to update the package version.

WORKAROUND    Create a new migration job that includes the advertisement and that is configured to overwrite the existing objects in Configuration Manager v.Next.

There are two migration scenarios where Configuration Manager v.Next clients cannot access package files from Configuration Manager 2007 distribution points:

• When you map a Configuration Manager 2007 site to the Configuration Manager v.Next central administration site. Although the distribution points from the Configuration Manager 2007 site are associated with the central administration site, the central administration site does not support the distribution point site role, and so these distribution points are not available to Configuration Manager v.Next clients that request content for migrated packages.
  
  
• When you map a Configuration Manager 2007 secondary site to a Configuration Manager v.Next site. Configuration Manager v.Next does not synchronize the content location for migrated packages when the content resides on Configuration Manager 2007 distribution points in secondary sites.
  
  

WORKAROUND    None.

Configuration items that you import into Configuration Manager 2007 might not display all their objects and settings in the Configuration Manager console. In this scenario, Configuration Manager 2007 displays as much as it can interpret. If the imported configuration item does not contain any data that it can interpret, the Configuration Manager 2007 console displays it as an uninterpreted configuration item.

Configuration Manager v.Next cannot support these configuration items, and they are not migrated. If you select them to be migrated, the following error is recorded in the Migmctrl.log log file:

Failed to validate the xml ---> System.ArgumentException: Invalid package document

WORKAROUND    None.

When you specify the site for your source hierarchy, and you specify a server computer name in the same format (NetBIOS or FQDN) that has previously been specified, you see the following error message:

The ConfigMgr Provider reported an error connecting to the ConfigMgr site database server. Verify that the SQL Server is online and that ConfigMgr site server computer account is an administrator on the ConfigMgr site database server.

WORKAROUND    None. You cannot specify a source hierarchy more than one time.

When you configure a primary site mapping, you do not see all the Configuration Manager 2007 sites and the number of clients available for migration is lower than expected. This occurs when the source hierarchy is mapped to a site other than the site that is at the top of the Configuration Manager 2007 hierarchy. For example, this occurs when the source hierarchy is mapped to a child primary site or to a secondary site.

WORKAROUND    Configure a new source hierarchy and for the Source primary site server option, specify the site server in the site that is at the top of the Configuration Manager 2007 hierarchy. In a hierarchy that has multiple primary sites, the site at the top of the hierarchy is the central site. In a hierarchy that has a single primary site with secondary sites, the site at the top of the hierarchy is the primary site.

Per-computer task sequence variables that have been configured in a Configuration Manager 2007 hierarchy do not migrate when you migrate client computers to a Configuration Manager v.Next hierarchy. Any task sequences in the Configuration Manager v.Next site that relies on these variables fails.

WORKAROUND    After the client computers have migrated to Configuration Manager v.Next, manually configure the required per-computer task sequence variables.

Configuration Manager 2007 advertisements can have a priority of Low, Medium, and High. The default is Medium. Configuration Manager v.Next deployments have only two priorities: Normal and High. When you migrate an advertisement that has the priority of Medium, the resulting deployment is configured for a priority of High.

WORKAROUND    If you want the deployment to have a priority of Normal, after migration is completed, edit the deployment. On the Deployment Settings tab, change Priority from High to Normal.

Objects that are modified in a Configuration Manager 2007 hierarchy after they are migrated to Configuration Manager v.Next are incorrectly marked as completed instead of modified when a migration job runs with the configuration Keep the existing records in the Configuration Manager v.Next site.

WORKAROUND    Configure migration jobs with the setting to overwrite migrated objects.

Clients do not install if you do not specify a site code in the Client Push Installation Wizard, and the selected clients are not in the boundaries of any site.

WORKAROUND    In the Client Push Installation Wizard, enable the option Install clients from site, and then select a site.

The Group Policy templates for client installation and assignment refer to Configuration Manager 2007.

WORKAROUND    None. This is a display issue only and does not affect the functionality of the Group Policy templates.

When you enable software update-based client deployment, the Configuration Manager client does not publish to the software update point. The following error is logged in WCM.log:

ERROR: Failed to publish sms client to WSUS, error = 0x80131622

WORKAROUND    From the Microsoft Connect site (http://go.microsoft.com/fwlink/?LinkID=67307), download the software updates WSUS-KB13166-x64.exe and WUS-KB131665-x86.exe and install either the 64-bit or 32-bit software update on all software update point site system roles.

When you upgrade a client from Configuration Manager 2007 to Configuration Manager v.Next, any virtual applications that were deployed by using Configuration Manager 2007 R2 might fail to run after the client is upgraded. In Configuration Manager v.Next, the client installation folder and the location for running virtual applications has changed from those used in Configuration Manager 2007. However, upgrading the client does not update the shortcuts that reference these locations.

WORKAROUND    After you upgrade the client, restart the client computer. This action automatically updates the shortcuts for the client.

The General tab of the Software Catalog Web site point Properties displays a warning to recommend the use of native mode for this site system role, but native mode is not supported with this release of Configuration Manager v.Next.

WORKAROUND    None.

Configuration Manager Software Center might load without displaying any data when the client (Ccmexec.exe process) initializes. This problem occurs when a computer has restarted, or the Ccmexec service has been recently started, and a user runs the Software Center application.

WORKAROUND    After the Ccmexec service starts, wait for 2 minutes before running Software Center.

If you install the Configuration Manager v.Next client on Windows Server 2008 R2, the Microsoft .NET Framework 4 is automatically installed. The .NET Framework usually requires a restart to complete Windows registration. If the registration is not complete, the Software Center notification application will crash and you might see a dialog box quickly display.

WORKAROUND    Before you install the Configuration Manager v.Next client on Windows Server 2008 R2, ensure that you have the .NET Framework version 3.0 or later installed (version 4.0 is recommended). Alternatively, after you install the Configuration Manager v.Next client, restart the computer.

If the local time on the Configuration Manager site server is in UTC time plus an offset, applications with the deployment purpose of Available and without a configured schedule are displayed in the Configuration Manager Software Catalog when the UTC time is UTC plus any offset configured on the site server.

For example, the site server is configured for the UTC+2 time zone. At 8 A. M., create and deploy an application, and on the Scheduling page of the Deploy Software Wizard, accept the default values. The application is not displayed as Available in the Software Catalog until 10 A. M. UTC.

WORKAROUND    On the Scheduling page of the Deploy Software Wizard, configure a schedule, even when you want the application to be available as soon as possible. To make an application available as soon as possible, specify the time as UTC minus the offset time on the site server. Using the previous example, configure the time as 6 A. M. (UTC).

When the Software Catalog Web site point and the Software Catalog Web service point are installed on separate site system servers, users see the error message There was a problem connecting with the server and they are unable to browse the Configuration Manager Software Catalog.

WORKAROUND    Install the Software Catalog Web site point and the Software Catalog Web service point on the same site system server.

Software deployments that are configured for the Include all sub-collection(s) of the specific collection for targeting option prevent a user from installing or requesting software from the Software Catalog when the user is contained in the collection and in any of the subcollections or linked collections. The user will see the following error message in the Software Catalog:

There is a problem connecting with the server.

WORKAROUND    When you create an available software deployment, do not select the Include all sub-collection(s) of the specific collection for targeting option. Alternative software deployment configurations are as follows:

• Specify a collection that does not have subcollections or linked collections.
  
  
• Specify a collection that does not have members that are also contained in any of that collection’s subcollections or linked collections.
  
  

After a task sequence runs on a Configuration Manager client computer, the notification icon in the Configuration Manager Software Center does not update. The Installation in progress icon is displayed and it does not change, even after additional software is deployed to the client computer and the notification should display as Available.

WORKAROUND    When the next software deployment runs that is not a task sequence, the icon updates to the correct status.

You cannot change the software deployment purpose of a package and program from Available to Required, or from Required to Available.

WORKAROUND    Delete the deployment, and create a new deployment that has the new deployment purpose.

When you create an application and select the Microsoft Application Virtualization deployment type, the wizard automatically creates operating system requirement rules that are based on the supported operating system list available in the .osd files of the Application Virtualization package. When you update an Application Virtualization package by using sequencing and a different set of operating system requirements, Configuration Manager creates a new operating system requirement rule during the package import, and this process duplicates the previous operating system requirement rule. When you have duplicate operating system requirements rules for the Microsoft Application Virtualization deployment type, clients fail to evaluate all application deployments. In this scenario, you see the status Unknown for all applications in Configuration Manager Software Center.

WORKAROUND    After updating a Microsoft Application Virtualization deployment type and refreshing the content, make sure that there is only one operating system requirement rule for each deployment type. If necessary, delete any duplicate operating system requirement rules.

If you migrate from Configuration Manager 2007 to Configuration Manager v.Next and you have overlapping boundaries between the Configuration Manager 2007 hierarchy and the Configuration Manager v.Next hierarchy, clients that are installed by using automatic site assignment might be assigned to the wrong hierarchy.

WORKAROUND    During the migration period, do not use automatic site assignment when you install clients. Instead, assign clients directly to their site. When you have migrated the clients that were using the boundary in the Configuration Manager 2007 hierarchy, you can delete the boundary in the Configuration Manager 2007 site. When the boundary configuration is unique to a site in the Configuration Manager v.Next hierarchy, you can use automatic site assignment again.

Migrated distribution points that are shared by a Configuration Manager 2007 site and a Configuration Manager v.Next site display in the Content Locations tab for package properties. If you select these buttons, the content is not redistributed or removed because the distribution point is owned by the Configuration Manager 2007 site.

WORKAROUND    None.

The Deploy Software Wizard does not display distribution points that are migrated and shared by a Configuration Manager 2007 site and a Configuration Manager v.Next site. The Deploy Software Wizard cannot finish if you do not distribute content to at least one distribution point.

WORKAROUND    Distribute the package to at least one Configuration Manager v.Next distribution point.

When you run the Export Content Wizard from a remote Configuration Manager console and then click OK, the content is not exported. There is no progress bar to indicate that the content associated with the application is exporting to the destination file and the ExportContent.log file in the <ConfigMgrInstallationPath>\AdminUI\AdminUILog folder is not created. If you click , the wizard closes.

WORKAROUND    Run the Export Content Wizard from the Configuration Manager console on the site server.

The user experience Notification setting of Show all notifications for software deployment and automatic grouping rules does not enable notifications for the software deployment or the automatic grouping rule.

WORKAROUND    None.

If you use a remote desktop connection with credentials that are different than the logged-on local session and install software from the software catalog, the installation fails with the error message Software installation could not start.

WORKAROUND    Use the same credentials for the remote desktop connection as those supplied for the logged-on local session.

When you select a collection from Assets and Compliance and view the Recent Deployments tab, software update deployments that are targeted to the collection are not displayed.

WORKAROUND    Verify which software updates have been deployed by viewing the properties of a software update group or a software update, and then click the Deployment tab.

Software updates can automatically be deployed by using an automatic grouping rule even when the software update has an associated EULA that has not been accepted. However, you see the following error message when you open the properties for a deployment that contains a software update with a EULA that has not been accepted:

ErrorCode = 1078462208

One or more updates are present for which a EULA exists which hasn't been approved

WORKAROUND    Accept all EULAs that are associated with software updates in the deployment.

If you deploy software updates from a collection, a ConfigMgr Provider error displays the error message Operation has failed, information display may be incomplete, and you cannot complete the Deploy Software Updates Wizard.

WORKAROUND    To deploy software updates, select a software update group or software updates from the Software Library, and then run the Deploy Software Updates action.

If you edit the properties of an update group, automatic validation does not accept a name that includes the characters / and #. The default name includes the date that is formatted with the character /.

WORKAROUND    If you edit the properties of an update group, modify the name so that it does not include the character / or #.

When you specify a different collection in an existing automatic grouping rule, the change does not create a new software update deployment.

WORKAROUND    You must create a new automatic grouping rule to create a software update deployment that targets the new collection.

If you add software updates to an update group, and you do not download these software updates, you can create a software updates deployment with this update group, but clients fail to install these software updates.

WORKAROUND    Either download the software updates before deploying the update group, or ensure that you download the software updates before the software update deployment runs on the clients. To verify that the software updates are successfully downloaded, you can create a Search folder or add filter criteria on the All Updates node and specify the following object properties:

• Deployed equals Yes
  
  
• Downloaded equals No
  
  

If you use role-based administration and assign an administrative user a security role other than ConfigMgr Administration role, and use the built-in security scope All, the administrative user might see error messages in the Deploy Software Updates Wizard and cannot perform any of the following:

• Select templates from the Deploy Software Updates Wizard or the Create Automatic Grouping Rule Wizard.
  
  
• Select distribution points to distribute software updates.
  
  
• Create new automatic grouping rules.
  
  

WORKAROUND    Use the security scope of All when you assign the ConfigMgr Administration role to the administrative user who configures the software updates.

The Software Updates report Management 7 – Updates in a deployment missing content does not contain any data.

WORKAROUND    To verify that deployed software updates have been downloaded successfully, you can create a Search folder, or add filter criteria on the All Updates node and specify the following object properties:

• Deployed equals Yes
  
  
• Downloaded equals No
  
  

If the client setting Restart Final Notification is greater than the client setting Restart Countdown, the user does not see any log-off notifications.

WORKAROUND    Configure the client setting for Restart Countdown to be greater than the Restart Final Notification setting.

If you delete a driver from Driver Packages in the Configuration Manager console, the driver is deleted from Configuration Manager instead of removing the driver from the package.

WORKAROUND    To remove a driver from a driver package without deleting the driver from Configuration Manager, select Add or Remove Driver to Packages instead of Delete.

The Status Message Viewer does not display any messages on the central administration site for task sequences that you deploy from a primary site.

WORKAROUND    View status messages from the deployment site.

Migration in Configuration Manager v.Next supports Configuration Manager 2007 distribution points so that Configuration Manager v.Next clients can download package files from these distribution points when they host migrated packages. In Configuration Manager v.Next, the System Status Summarizer attempts to perform a disk space check for these Configuration Manager 2007 distribution points, which fails. This failure results in the status of these site systems to display with Critical status in the Configuration Manager v.Next console.

WORKAROUND    Ignore the Critical status as reported in the Configuration Manager v.Next console, and monitor these site systems by using the Configuration Manager 2007 console.

The Configuration Manager console fails to connect and prompts you for user credentials if your account is not a member of the SMS Admins local security group on the site server, the database server, or the computer that has the SMS Provider installed. This problem also occurs if DCOM is not enabled for Remote Activation on the site server or the computer that has the SMS Provider installed.

WORKAROUND    Perform the following configuration steps:

• Add your user account to the SMS Admins group on the site server, the database server, and the computer that has the SMS Provider installed.
  
  
• On the site server and on the computer that has the SMS Provider installed, configure the DCOM permissions to enable Remote Activation for the SMS Admins group. For information about how to configure DCOM Remote Activation permissions, see How to Configure DCOM Permissions for Configuration Manager Console Connections (http://go.microsoft.com/fwlink/?LinkID=192620).
  
  

If you have a security role that is assigned to a security scope other than All, you might not be able to see a distribution point from another site and you will not be able to select the distribution point to distribute software.

WORKAROUND    Specify a distribution point group that contains the distribution point from the other site.

If you create new custom client settings and you have a security role that is assigned to a security scope other than All, the Configuration Manager console might crash with the error message Microsoft.ConfigurationManagement.exe has stopped working.

WORKAROUND    Log in with an account that is assigned a security role that is configured to use a security scope of All. Alternatively, change the current security scope to All for your assigned security role.

In the Configuration Manager console, when you use the Group By option in a list view and then click outside the items in the list view, the console crashes with the error message Microsoft.ConfigurationManagement.exe has stopped working.

WORKAROUND    None.

When you configure the Search Folder date criteria and you use the is between operator, any changes that you make to the end date and time fields of the search condition is incorrectly saved to the start date and time fields. The end date and time is automatically reset to the date and time when the search folder was created.

WORKAROUND    None.

If you run Resource Explorer, and you are not a local administrator for the computer running the Configuration Manager console, and Resource Explorer has not successfully run previously, it fails to load with the error message MMC has detected an error in a snap-in and will unload it.

WORKAROUND    Log on as a local administrator, and then run Resource Explorer. When you run Resource Explorer subsequently on the same computer, you do not have to be a local administrator.

When you install the Configuration Manager console on a computer running Windows 7 or Windows Server 2008 R2, and then start Windows Performance Monitor from within the console, Performance Monitor fails to run with the error message The parameter is incorrect.

WORKAROUND    Do not use the Configuration Manager console to run Performance Monitor, but run it in Windows.

When you select the Limit to collection option for a query, this action does not affect the results returned by the query.

WORKAROUND    Add criteria to the query to limit the returned results.

If you select the first status filter rule, and then click Increment Priority, or you select the last status filter rule, and then click Decrement Priority, the console might crash with the error message Microsoft.ConfigurationManagement.exe has stopped working.

WORKAROUND    None.

If you run the Configuration Manager console as a low-rights user on a computer that has user account control (UAC) enabled, the console does not write to the log file, SmsAdminUI.log.

WORKAROUND    Run the Configuration Manager console by using the Run as administrator option.

In the Configuration Manager console, if you click Monitoring in the navigation pane, click Reports, and then click Create Report, and you have not installed the reporting services point, the Configuration Manager console crashes with the error message Microsoft.ConfigurationManagement.exe has stopped working.

WORKAROUND    Install the reporting service point site system role before you click Create Report.

Unlike Configuration Manager 2007, Configuration Manager v.Next does not support configuration item properties that cannot be viewed or edited in the console. If you try to import configuration data that contains properties that cannot be interpreted, the import fails, and you see the following error message:

The following file(s) contain invalid or inconsistent data.

Possible causes could be:

   Malformed xml data.

   Invalid schema.

   References to items not in the system or cab file.

   Circular references among items in the cab file.

WORKAROUND    If necessary, import the configuration data into a Configuration Manager 2007 site, and then perform the following steps:

1. In the Configuration Manager 2007 site, edit the configuration data and delete any configuration item properties or configuration items that cannot be interpreted.
   
   
2. Export the remaining configuration data.
   
   
3. Import the configuration data into the Configuration Manager v.Next site.
   
   

If you migrate a configuration item or configuration baseline to one Configuration Manager v.Next primary site, and then migrate this configuration data again to a different Configuration Manager v.Next primary site in the same hierarchy and select the option Migrate The Updated Data And Overwrite The Existing Data In The Configuration Manager V.Next Site, you cannot edit this migrated configuration data in Configuration Manager v.Next.

WORKAROUND    Delete the migrated configuration data from the last Configuration Manager v.Next site to which it was migrated. This deletes the configuration data from the Configuration Manager v.Next hierarchy. Then migrate the configuration data again to Configuration Manager v.Next.

When you disable a configuration item compliance rule and then assign a configuration baseline that contains this compliance rule, the compliance rule is evaluated on client computers even though it is disabled. If the disabled compliance rule is configured to enforce a setting, this setting is enforced on client computers. However, the results of this disabled compliance rule is not sent to the site and so does not affect the compliance information displayed in the Configuration Manager console or in reports.

WORKAROUND    Delete any compliance rules that you do not want to run on client computers.

If you create a configuration item file system setting of the type File or Folder and use a path containing the environment variable %programfiles%, and the option This file or folder is associated with a 64-bit application is not selected, the %programfiles% environment variable is incorrectly evaluated as C:\Program Files, instead of C:\Program Files (x86).

WORKAROUND    Specify an absolute path for the %programfiles% folder.

Although you can configure compliance rules to validate permissions for the configuration item settings Registry Key and File, these permissions are not evaluated by client computers

WORKAROUND    None.

If you create a configuration item file system setting of the type File or Folder and the Path text box or File or folder name text box contain any of the unsupported characters $, (, and ), and then add this configuration item to a configuration baseline, the evaluation of this and subsequent configuration baselines fail.

WORKAROUND    Do not use the characters $, (, and ) in the Path text box and File or folder name text box of a file system configuration item setting. If a configuration baseline fails because of this issue, remove the setting from the configuration item, and then reassign the configuration baseline.

If you create a configuration item setting type of Registry Key, Registry Value, Script, or WMI and configure the Data Type value as Date/Time, any compliance rules that have the configuration option Enforce selected do not remediate these values on client computers.

WORKAROUND    None.

Users that have not been assigned the Content Manager role on the reporting folder in SQL Reporting Services will see the following error message when they run a report in the Configuration Manager console: Unable to load report for viewing. Verify you have necessary security rights to run the report

WORKAROUND    Assign the Content Manager role on the reporting folder in SQL Reporting Services to all users or groups that will run reports.

The Asset Intelligence reports are classified into hardware and software and include a number and letter designator in the title (for example, 1A). The numbers and letters in the available report titles are not consecutive and might give the impression that some reports are missing.

WORKAROUND    None.

Using Assets and Compliance in the Configuration Manager console, some tasks related to Asset Intelligence might not be displayed in the Tasks pane. For example, you click Software Inventory and do not see Edit Asset Intelligence Reporting Class Settings in the Tasks pane.

WORKAROUND    Press F5 to refresh the console. Alternatively, click another node in the console, and then click the original node.

You can use the Asset Management role for Asset Intelligence operational activities, such as running reports and defining categorization, but not for the configuration of Asset Intelligence. If you use role-based administration and assign an administrative user the security role of Asset Management role or ConfigMgr Administration role, and use the built-in security scope Default, the administrative user cannot perform any of the following:

• Configure the Asset Intelligence synchronization point
  
  
• Synchronize the catalog
  
  
• Edit the Asset Intelligence reporting class settings
  
  

WORKAROUND    Use the security scope of All instead of the security scope of Default when you use the Asset Management role or ConfigMgr Administration role.

Configuration Manager v.Next does not create default collections for the following mobile device operating systems:

• Windows Mobile 6.1 Standard
  
  
• Windows Mobile 6.1 Professional
  
  
• Windows Mobile 6.5 Standard
  
  
• Windows Mobile 6.5 Professional
  
  

WORKAROUND    You can create collections for these mobile devices by using the following queries.

Windows Mobile 6.1 Standard

select * from SMS_R_System where SMS_R_System.ClientType = 3 and SMS_R_System.OperatingSystemNameandVersion like '%6.1%' and SMS_R_System.OperatingSystemNameandVersion like '%Standard%'

Windows Mobile 6.1 Professional

select * from SMS_R_System where SMS_R_System.ClientType = 3 and SMS_R_System.OperatingSystemNameandVersion like '%6.1%' and SMS_R_System.OperatingSystemNameandVersion like '%Professional%'

Windows Mobile 6.5 Standard

select * from SMS_R_System where SMS_R_System.ClientType = 3 and SMS_R_System.OperatingSystemNameandVersion like '%6.5%' and SMS_R_System.OperatingSystemNameandVersion like '%Standard%'

Windows Mobile 6.5 Professional

select * from SMS_R_System where SMS_R_System.ClientType = 3 and SMS_R_System.OperatingSystemNameandVersion like '%6.5%' and SMS_R_System.OperatingSystemNameandVersion like '%Professional%'

If you run the query All Windows Mobile Devices, the query results do not include mobile devices running Windows Mobile 6.1 and Windows Mobile 6.5.

WORKAROUND    None.

Mobile devices might fail to enroll if you try to enroll mobile devices too soon after you install the mobile device enrollment point and mobile device enrollment proxy point roles. For example, the New Enrollment Profile Wizard might fail to complete. You might experience this enrollment failure for up to one hour after you install these site system roles because the settings for these new site system roles have not yet replicated to the database.

WORKAROUND    After you install the mobile device enrollment point and mobile device enrollment proxy point roles, restart the SMS_SITE_COMPONENT_MANAGER service.

Mobile device enrollment fails if the Active Directory computer account that you created for the mobile device has not yet replicated to the domain controller that tries to enroll the mobile device when you use the Create Mobile Device Wizard or you add a new mobile device by using the Software Catalog. In this scenario, the following error message is logged to the <IISInstallationPath>\inetpub\wwwroot\enrollmentweb\logs\EnrollmentWeb.log file:

EndEnrollDevice: Exception: The server was unable to process the request due to an internal error

WORKAROUND    Wait for Active Directory replication to complete before you enroll a mobile device.

Mobile device enrollment fails if you specify a name for the mobile device in the Create Mobile Device Wizard that is the same name as an existing Active Directory user name. The following error is logged to Enrollmentservice.log.

EnrollDevice: Exception: Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)

WORKAROUND    Enroll the mobile device again and specify a different name for the mobile device.

If you have more than one Windows Mobile Cabinet deployment type in a deployment, they will all be installed instead of using the priority setting to install only one.

WORKAROUND    None.

Although you can specify settings for the user experience and schedule for the Windows Mobile deployment type in the Deploy Software Wizard, these settings do not work.

WORKAROUND    None.

If you configure Enable hardware inventory on computers to be False, this also disables hardware inventory for mobile devices.

WORKAROUND    If you need hardware inventory for mobile devices, ensure that the client agent setting Enable hardware inventory on computers is configured as True.

If you enable any of the following mobile device hardware inventory classes in the smsdef.mof file, this action does not collect information from mobile devices:

• class Device_OwnerInformation
  
  
• class Device_CertificateInformation
  
  
• class Device_Certificates
  
  
• class Device_Display
  
  
• class Device_Network
  
  

WORKAROUND    None.

If an application name is longer than 215 characters, mobile devices cannot download and install the application.

WORKAROUND    Ensure that application names are not longer than 215 characters if you want to install the applications on mobile devices.

If an application name contains any of the following characters, mobile devices cannot download and install the application: & * | ? : < > \ / ".

WORKAROUND    Ensure that application names do not contain these characters if you want to install the applications on mobile devices.

Although you can specify that software deployments are available for mobile devices, they are not displayed in the Software Catalog and cannot be installed with this configuration.

WORKAROUND    To install software on mobile devices, configure the software deployment purpose to be Required.

The following mobile device reports do not contain data:

• ActiveSYNC Service Status
  
  
• Desktop information by device name
  
  
• Desktop information by SMS Unique ID
  
  
• Device Client Agent Deployment Failure Report
  
  
• Device Client Agent Deployment Status Details
  
  
• Device Client Agent Deployment Success Report
  
  
• Device Client Agent Health Summary
  
  
• Device Client Information
  
  
• Device Clients in Healthy condition
  
  
• Device Clients in unhealthy condition due to certificate issues
  
  
• Device Clients in unhealthy condition due to communication issues
  
  
• Device Clients in unhealthy condition due to local client issues
  
  
• Devices by owner of SMS client computers
  
  
• Devices with critically low battery
  
  
• Devices with low disk space
  
  
• SMS client computers reporting ActiveSync-connected devices without SMS Device Client
  
  
• SMS client computers reporting an ActiveSync-connected SMS Device Client
  
  

WORKAROUND    None.

Some applications might fail to install on mobile devices because these applications are unsigned.

WORKAROUND    Create an operating system configuration item that applies to Windows Mobile. On the Mobile Device Settings page, select Security, and then configure the following settings:

• Block unsigned .cab file installation: No
  
  
• Prompt for unsigned files: No
  
  
• Block unsigned application: No
  
  
• Remediate noncompliant settings
  
  

Add this configuration item to a configuration baseline, and then assign the configuration baseline to a collection that contains the mobile devices. When you assign the configuration baseline, select Remediate noncompliant rules when supported.