System-Center.fr

Tweet

Hi all,

Great news, Package Conversion Manager (PCM) V 2.0 is available for System Center Configuration Manager 2012 (SCCM 2012) !!!

What’s Package Conversion Manager  (PCM) V2.0?

———————————————————–

Click HERE for read the complete post

———————————————————–

Tweet

Hi all,

Just a post for you annouce that the support end date for SCCM 2007 is now to the 7/9/2019 !!!

SCCM SP1 & SP2 note:

Support ends 12 months after the next service pack releases or at the end of the product’s support lifecycle, whichever comes first. For more information, please see the service pack policy at

http://support.microsoft.com/lifecycle/#ServicePackSupport.

Click HERE for read on Microsoft Website!

Tweet

Hi all geek friend,

&

It’s with a big pleasure that i write you a post for explain How to install and configure System Center Configuration Manager 2012 RTM and how to configure System Center EndPoint Protection 2012 Definition!!!!

For start, i want to say that Microsoft work with a lot force for improve SCCM 2012, all feedback realize by all MVP SCCM are hear with attention for you big pleasure!

How to install and configure System Center Configuration Manager 2012 RTM:

PS:Just for information, the SQL, OS  install and some configuration by default not indicate in this post…

In first time, download SCCM 2012 RTM HERE

Environnement requirements :

1 Active Directory Domain controller

1 Server for SCCM 2012

Software and hardware requirements source HERE

——————————————————————————-

Launch Splash

And select Install

Click Next

Select Install a configuration Primary Site Server and click Next

Select evaluation or enter you product Key and click Next

.

.

Accept licence terms and click Next

.

Select all options and click Next

Indicate the download source path and click ok

Download in Progress

Click Next

Select language client and Click Next

In my example, i select MVP for Site Code and put this information for Site Name (Primary Site SCCM 2012 RTM France Michael BERTUIT )

Let default Installation folder and Install Admin console and click Next

Select Primary Site will be installed as a standalone site click Next

Click Yes

Click Next

Click Next

Click Next

Select Join and click Next

Click Next

The prerequisite Check start and indicate if you miss install a component for SCCM 2012 and click Begin Install (exemple: If you have not 8 GB (it’s the prerequisite ) , you have a issue message for indicate that you do upgrade you server more RAM memory) and click Begin Install

Install in progress ! you can see the log since the install, click on View log

Install in progress!

Install finish succesfully !!!

Select the Configuration Manager Console shorcut and launch…

Great jobs for the SCCM 2012 console (POWERED by DOTNET4) to Microsoft Team !!!!!

How to configure System Center EndPoint Protection 2012 Definition !!!

PS:Just for information, the role and some SCCM configuration by default not indicate in this post…

..For start, it’s necessary to install the EndPoint Protection role and the software Update role (not detailled HERE=Let parameters by default) in Administration>>Servers and Site System Roles >> Select Windows Server and add roles…

Select Settings

Select Software Update Point

Select Activate software update point on site server in General TAB and Apply

Select Definition Updates in Classifications TAB and Apply

Select Forefront EndPoint Protection 2010 in Products TAB and Apply

Select Enable in Sync Shedules TAB and configure a Simple Schedule and Apply

Select Default Client Settings in Administration >> Site Configuration >> Clients Settings

Activate and configure the client Software Updates TAB (see the copy screen)

Activate and configure the EndPoint Protection  TAB (see the copy screen)

Now, you do realize an Update synchronisation in click Synchronize Software Updates

Select Yes

The synchronisation Start !

Synchronisation is finish!

Check if the SCEP Definition is good downloaded…

Create a Automatic Deployement Rule in select Software Library>> Software Updates >> Automatic Deployement Rule

Indicate a name, select a collection target (for me All Collections it’s just an example )and click Create a new Software Update Group… and Enable the Deployment…and Click Next

Click Next

Criteria : Select Product >> Forefront EndPoint Protection 2010 >> click OK

Click Next

Select Enable …and click Next

Select As soon as possible for both and click Next

Click Next

Click Next

Click Next

Select create a new deployement share, see the copy screen for the example and click Next

Add DP or DP GROUP and click Next

Click Next

Click Next

Click Next

Click Close

Select the rule and click on Run now

Click OK

Package distribution in progress…:-)

Select Asset and Compliance TAB >> Endpoint Protection >>  Antimalware Policies >> And select  Default client Antimalware Policy

And right click on Default client Antimalware Policy >> Properties

Select Defnition updates >>Set Sources >> Select Updates distributed from Configuration Manager and Updates distributed from WSUS and click OK

Click OK

You can (after some times) check that the version of definition is the same apply to the client example for me

>> Definition Update for Microsoft Endpoint Protection – KB2461484 (Definition 1.125.1605.0)

Check on a first ConfigMgr Client >> The SCEP 2012 definition version is the same that the ConfigMgr Server !

>> Definition Update for Microsoft Endpoint Protection – KB2461484 (Definition 1.125.1605.0)

Check on a second ConfigMgr Client >> The SCEP 2012 definition version is the same that the ConfigMgr Server !

>> Definition Update for Microsoft Endpoint Protection – KB2461484 (Definition 1.125.1605.0)

Finish !!!

No, it’s NEVER Finish with Microsoft System Center Configuration Manager and Microsoft System Center EndPoint Protection !

Soon

Michael Bertuit

Others Interesting Link :

TOP 10 of New changes to know for System Center 2012 Configuration Manager (SCCM 2012)

How to deploy Windows 8 (Windows Developper Preview) with System Center Configuration Manager 2012 (SCCM 2012 Beta 2) PART 2

System Center 2012 Configuration Manager Survival Guide available !!!

SCCM 2012 | How to import lot of computers information with CSV file option (Import Computer Information) for deploy Microsoft Windows Operating System

New Security features with System Center Configuration Manager 2012 (RBAC) and System Center Endpoint Protection 2012

New Quizz test for System Center 2012 Configuration Manager | SCCM 2012| (Learning, tests and improve for certification)

Tweet

Hi all,

Just a reminder information for all person have problem when you want capture and restore Data users in a task sequence with SCCM and what you do for resolve the specifically error (Failed to find client signing certificate. Code 0×80092004).

Example of error log, the error is present in the smsts.log files on the target workstation :

<![LOG[Loading client certificates.]LOG]!><time= »14:21:03.039+-120″ date= »05-03-2011″ component= »OSDSMPClient » context= »" type= »0″ thread= »2988″ file= »smpclient.cpp:855″>
<![LOG[Failed to find client signing certificate. Code 0x80092004]LOG]!><time= »14:21:03.180+-120″ date= »05-03-2011″ component= »OSDSMPClient » context= »" type= »3″ thread= »2988″ file= »smpclient.cpp:896″>
<![LOG[ClientRequestToMP::DoRequest failed (0x80092004).]LOG]!><time= »14:21:03.180+-120″ date= »05-03-2011″ component= »OSDSMPClient » context= »" type= »3″ thread= »2988″ file= »smpclient.cpp:1160″>
<![LOG[ExecuteCaptureRequestMP failed (0x80092004).]LOG]!><time= »14:21:03.180+-120″ date= »05-03-2011″ component= »OSDSMPClient » context= »" type= »3″ thread= »2988″ file= »smpclient.cpp:2688″>
<![LOG[ExecuteCaptureRequest failed (0x80092004).]LOG]!><time= »14:21:03.180+-120″ date= »05-03-2011″ component= »OSDSMPClient » context= »" type= »3″ thread= »2988″ file= »smpclient.cpp:2762″>
<![LOG[OSDSMPClient finished: 0x00002004]LOG]!><time= »14:21:03.180+-120″ date= »05-03-2011″ component= »OSDSMPClient » context= »" type= »1″ thread= »2988″ file= »main.cpp:120″>
<![LOG[Process completed with exit code 8196]LOG]!><time= »14:21:03.195+-120″ date= »05-03-2011″ component= »TSManager » context= »" type= »1″ thread= »320″ file= »commandline.cpp:1102″>
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time= »14:21:03.195+-120″ date= »05-03-2011″ component= »TSManager » context= »" type= »1″ thread= »320″ file= »instruction.cxx:3010″>
<![LOG[Failed to run the action: Request State Store.
Unknown error (Error: 00002004; Source: Unknown)]LOG]!><time= »14:21:04.383+-120″ date= »05-03-2011″ component= »TSManager » context= »" type= »3″ thread= »320″ file= »instruction.cxx:3101″>

For resolve this error, you create a package with the CCMCertfix.exe files.

1-Download the KB977203

2-Unzip the KB977203 with the password send by email and install the KB on the ConfigMgr Server…

3-Copy the CCMcertfix.exe become folder F:\Program Files (x86)\Microsoft Configuration Manager\Logs\KB977203 and paste to a new folder named CCMcertfix

4- Create a package CCMCertFix with this program parameter  with the following example settings:

Run: Hidden

Run whether or not a user is logged on
Run with administrative rights

Command line = CCMcertfix.exe CCMcertfix.log

For see localy on the target computer the result , see the log present in cache client folder :

for X86 client:

(example: C:\windows\System32\ccm\cache\packagename)

for X64 client:

(example: C:\windows\SysWOW64\CCM\cache\packagename)

After deploy CCMCertfix.exe on all sccm client with in error state, the problem is resolve!!!

For the next time and if you use the push method or task sequence for deploy new sccm client:

1-create a share with KB

2-put the command line in install properties client

And for the task sequence, insert the command line Here under:

1. Click Setup windows and ConfigMgr.
2. In the Installation properties box, type the following:

For ConfigMgr 2007 SP1:

PATCH= »%_SMSTSMDataPath%\OSD\<Package_ID>\i386\hotfix\KB977203\SCCM2007AC-SP1-KB977203-x86.msp »

For ConfigMgr 2007 SP2:

PATCH= »%_SMSTSMDataPath%\OSD\<Package_ID>\i386\hotfix\KB977203\SCCM2007AC-SP2-KB977203-x86.msp »

Reminder on what USMT version to use on all migration data users scenarios:

USMT 4.0 does only work in these scenarios

WIN7 to WIN7
Vista to Vista
Vista to WIN7
Win7 to Vista
WinXP to Vista
WinXP to WIN7

USMT 3.0 does only work in these Scenarios:
Win XP to Win XP

The result of Capture data users succes in video under !!! :