System Center 2012 Configuration Manager RC Now Available

System Center 2012 Configuration Manager provides a unified management infrastructure across physical, virtual, and mobile client environments. System Center 2012 Endpoint Protection builds on this infrastructure to provide industry-leading antimalware protection for client and server operating systems.

 

http://www.microsoft.com/en-us/server-cloud/system-center/configuration-manager.aspx

 

Microsoft Application Virtualization 4.6 SP1 is now supported on Configuration Manager 2007 R3 with Configuration Manager 2007 SP2

The changes will be reflected in the Supported Configuration pages within a few months.

Microsoft Application Virtualization 4.6 SP1 is now supported on Configuration Manager 2007 R3 with Configuration Manager 2007 SP2

System Center Configuration Manager 2007 R3 with System Center Configuration Manager SP2 now supports Microsoft Application Virtualization (App-V) 4.6 SP1 Desktop Client and Application Virtualization Client for Remote Desktop Services. This client release enables support for Windows 7 SP1 and Windows Server 2008 R2 SP1.

The following are the limitations and workaround to import App-V packages using Configuration Manager.

Configuration Manager fails to import App-V packages when there is more than one XML in the package folder. App-V Sequencer 4.6 SP1 creates the file Report.xml when creating an App-V package. Configuration Manager expects to find only one xml file in the package folder and will fail when it identifies more than one XML file in the folder. To work around this problem delete the file report.xml manually from the package folder before you import the App-V package.

No software updates are required.

PowerCFG – a bit further….

A bit further using PowerCFG…

Found this nice list on Richard Smiths blog

sets the power configuration to High Performance
powercfg -setactive 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

tweaks the basic power settings
powercfg -change -hibernate-timeout-ac 0
powercfg -change -hibernate-timeout-dc 0

turns hibernation off
powercfg -hibernate OFF

require password when console wakes up (0=false, 1=true)
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c fea3413e-7e05-4911-9a71-700331f1c294 0e796bdb-100d-47d6-a2d5-f7d2daa51f51 0
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c fea3413e-7e05-4911-9a71-700331f1c294 0e796bdb-100d-47d6-a2d5-f7d2daa51f51 0

also needed to show up on Power Menus…
powercfg -setacvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e fea3413e-7e05-4911-9a71-700331f1c294 0e796bdb-100d-47d6-a2d5-f7d2daa51f51 0
powercfg -setdcvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e fea3413e-7e05-4911-9a71-700331f1c294 0e796bdb-100d-47d6-a2d5-f7d2daa51f51 0

power plan type (0=power saver, 1=high performance, 2=balanced)
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c fea3413e-7e05-4911-9a71-700331f1c294 245d8541-3943-4422-b025-13a784f679b7 1
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c fea3413e-7e05-4911-9a71-700331f1c294 245d8541-3943-4422-b025-13a784f679b7 1

hard disk timeout
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 0012ee47-9041-4b5d-9b77-535fba8b1442 6738e2c4-e8a5-4a42-b16a-e040e769756e 0
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 0012ee47-9041-4b5d-9b77-535fba8b1442 6738e2c4-e8a5-4a42-b16a-e040e769756e 0

wireless adapter power (0=max perf, 1=low power saving, 2=med power saving, 3=max power saving)
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 19cbb8fa-5279-450e-9fac-8a3d5fedd0c1 12bbebe6-58d6-4636-95bb-3217ef867c1a 0
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 19cbb8fa-5279-450e-9fac-8a3d5fedd0c1 12bbebe6-58d6-4636-95bb-3217ef867c1a 0

sleep timeout
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 238c9fa8-0aad-41ed-83f4-97be242c8f20 29f6c1db-86da-48c5-9fdb-f2b67b1f44da 0
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 238c9fa8-0aad-41ed-83f4-97be242c8f20 29f6c1db-86da-48c5-9fdb-f2b67b1f44da 0

close action (0=do nothing, 1=sleep, 2=hibernate, 3=shutdown)
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 4f971e89-eebd-4455-a8de-9e59040e7347 5ca83367-6e45-459f-a27b-476b1d01c936 0
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 4f971e89-eebd-4455-a8de-9e59040e7347 5ca83367-6e45-459f-a27b-476b1d01c936 0

also needed to show up on Power Menus…
powercfg -setacvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e 4f971e89-eebd-4455-a8de-9e59040e7347 5ca83367-6e45-459f-a27b-476b1d01c936 0
powercfg -setdcvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e 4f971e89-eebd-4455-a8de-9e59040e7347 5ca83367-6e45-459f-a27b-476b1d01c936 0

processor power cstate (0,1=power saver, 2,3=balanced, 4,5=high perf)
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 54533251-82be-4824-96c1-47b60b740d00 68f262a7-f621-4069-b9a5-4874169be23c 4
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 54533251-82be-4824-96c1-47b60b740d00 68f262a7-f621-4069-b9a5-4874169be23c 4

minimum processor state
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 54533251-82be-4824-96c1-47b60b740d00 893dee8e-2bef-41e0-89c6-b55d0929964c 100
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 54533251-82be-4824-96c1-47b60b740d00 893dee8e-2bef-41e0-89c6-b55d0929964c 100

processor power perfstate settings
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 54533251-82be-4824-96c1-47b60b740d00 bbdc3814-18e9-4463-8a55-d197327c45c0 4
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 54533251-82be-4824-96c1-47b60b740d00 bbdc3814-18e9-4463-8a55-d197327c45c0 4

monitor timeout
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 7516b95f-f776-4464-8c53-06167f40cc99 3c0bc021-c8a8-4e07-a973-6b14cbcb2b7e 0
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 7516b95f-f776-4464-8c53-06167f40cc99 3c0bc021-c8a8-4e07-a973-6b14cbcb2b7e 0

multimedia settings (0=take no action, 1=prevent computer from sleeping, 2=enable away mode)
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 9596fb26-9850-41fd-ac3e-f7c3c00afd4b 03680956-93bc-4294-bba6-4e0f09bb717f 2
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 9596fb26-9850-41fd-ac3e-f7c3c00afd4b 03680956-93bc-4294-bba6-4e0f09bb717f 2

set the absentia power scheme (the scheme used when no one is logged in)
powercfg -setabsentia 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

MP has discarded a report when processing Ddr

I encountered the problem when running af side-by-side migration (ConfigMgr to Configmgr)

I had both management points in Active directory

Bascialliy it will happen when you deploy a new site site system with a new Management Point without removing old Management Point from System Container in Active Directory.

Error found in SMS_MP_CONTROL_MANAGER

MP has discarded a report when processing Ddr
Possible Cause: Corruption or invalid user definition.
Solution: Check the logs to identify the cause. If the problem is persistent raise the issue with Microsoft Support.

Solution:

1.Browse Active Directory

2.Open Systems Management Container

3. Delete old record SMS-MP-site Code-machinename

4. Restart site server

Configuration Manager 2007 SP2 and Windows PE 3.1

Actually very good article provided by Chaohao Xu

The Windows Automated Installation Kit (AIK) for Windows 7 SP1 is released and can be downloaded from the following location:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0aee2b4b-494b-4adc-b174-33bc62f02c5d

You don’t have to upgrade to Windows PE 3.1 to deploy Windows 7 SP1 and Windows Server 2008 R2 SP1. But if you want to upgrade to Windows PE 3.1, this post provides information about how you can do this with your existing Configuration Manager 2007 SP2 site. We also list some known issues that you might encounter when you use Configuration Manager operating system deployment with Windows PE 3.1.

Upgrade Steps:

  1. Use the following instructions to upgrade to Windows PE 3.1: from http://go.microsoft.com/fwlink/?LinkId=139690.
  2. Add a boot image based on Windows PE 3.1:
    1. In the Configuration Manager console, navigate to Computer Management -> Operating System Deployment -> Boot Images -> Add Boot Images.
    2. Specify the UNC path for the Windows PE 3.1 .wim file and select the image from the WIM file.
    3. Use the wizard to create the x86 and x64 boot images.
  3. Update the source of the default boot image to Windows PE 3.1 by running the ExportDefaultBootImage() WMI method:
    1. WMI Namespace is rootsmssite_<site_code>
    2. WMI Object is SMS_BootImagePackage
    3. WMI Method is ExportDefaultBootImage
    4. Parameters:
      • Architecture (x86 or x64)
      • ExportImagePath (\<site _server>sms_<site_code>OSDbooti386boot.wim or \site_server>sms_<site_code>OSDbootx64boot.wim)
      • ImageIndex (1)
  4. Update the distribution points for the default boot images.

Known Issues:

  1. Configuration Manager does not support using Windows PE 3.0 as a boot image after Windows PE 3.1 is upgraded. This means any boot images, including the default boot images, that are based on Windows PE 3.0 cannot be updated in Admin UI anymore. In this scenario, you will see the following error because the Windows PE 3.0 images are not compatible with the optional component (OC) and language packs from Windows PE 3.1:

    To resolve this problem, update all the boot images to use Windows PE 3.1.
  2. Task sequence fails when trying to apply drivers. You might see the following errors logged if task sequence fails to apply drivers.Failed to find the certificate context.. Cannot find object or property. (Error: 80092004; Source: Windows)
    Failed to initialize the online driver catlog.  Code 0x80092004
    Failed to auto provision drivers.  Code 0x80092004
    Failed to run the action: Apply Device Drivers. Cannot find object or property. (Error: 80092004; Source: Windows)This problem is caused by the Configuration Manager 2007 client generating an embedded NULL character into the friendly name for the certificate that is related to the driver apply. To resolve this issue, see KB977203 and run CCMCertFix.exe either before you run the task sequence or add it as a step in the task sequence.

New Features WinPe 3.1

New features in Windows PE 3.1:

  • The number in the Version registry value is 3.1 to reflect the new Windows PE version.
  • The Windows PE 3.1 base image contains Remote Network Driver Interface Specification (RNDIS) binaries. These binaries are also available for Windows PE 3.0 as a hotfix. For more information, see Knowledge Base Article ID: 979265.
  • Windows PE 3.1 includes 802.1x binaries as an optional component. The file name of this package is WinPE-Dot3Svc.cab. This optional component is also available for Windows PE 3.0 as a hotfix. For more information, see Knowledge Base Article ID 972831.
  • The Windows PE 3.1 base image contains fixes that are related to 4k/512e drive support. These fixes are also available for Windows PE 3.0 as a hotfix. For more information, see Knowledge Base Article ID: 982018.
  • Windows PE 3.1 includes bug fixes that are related to the Windows PE version that is included with Windows 7 SP1.

Windows Automated Installation Kit for Windows 7 SP1 can be downloaded from Microsoft Download Center, or directly using the direct download link: waik_supplement_en-us.iso (English).

To install the WinPE 3.1 for Windows 7 SP1 supplement, mount the ISO image and copy the content on the DVD ISO image to replace the Windows AIKToolsPETools folder.

Configuration Manager 2007 SP2, R2 and R3 supports Windows 7 SP1 and Windows Server 2008 R2 SP1

Configuration Manager 2007 SP2, R2 and R3 supports Windows 7 SP1 and Windows Server 2008 R2 SP1

The following software update is required to add Windows 7 SP1 and Windows Server 2008 R2 SP1 to the Supported Platforms list:

  • KB 2489044 – Update for System Center Configuration Manager 2007 SP2 to add Windows Server 2008 R2 SP1 and Windows 7 SP1 clients as supported platforms
  • KB 977203 – User state migration is unsuccessful on a SCCM 2007 SP1 client or on a SCCM 2007 SP2 client

Read more at: http://blogs.technet.com/b/configmgrteam/archive/2011/03/24/configuration-manager-support-announcements-for-march-2011.aspx

Description of the prerequisite hotfix for System Center Configuration Manager 2007 R3

This article describes the prerequisite hotfix for System Center Configuration Manager 2007 R3.

This hotfix is required for the following computers that are running System Center Configuration Manager 2007 Service Pack 2 (SP2):

  • Primary and secondary site servers
  • Remote administrator console servers
  • Remote provider servers
  • Client computers

read more: http://support.microsoft.com/default.aspx?scid=kb;en-us;977384&sd=rss&spid=12769