Configure cloud distribution Point

Configure cloud distribution Point

A cloud Distribution Point allows to own a distribution point in the cloud. With this type of distribution point, it is possible to have the following features :

  • manage cloud distribution points individually or as members of distribution point groups
  • Use this DP as a fallback content location

Before sending content in Azure, SCCM encrypts it. Note that it is not possible to use the cloud distribution point for deployment.

Lire la suite de

Configure Cloud Management Gateway

Configure Cloud Management Gateway

This feature has been introduced in SCCM in order to manage SCCM clients over the Internet. Note that this feature requires an azure subscription to work. Thereafter, the customers have the possibility of reaching the SCCM system sites wherever they are. Client certificates and SSL certificates are required. with this article you can configure the Cloud Management Gateway

Lire la suite de

Update SCCM 2012 R2 to SCCM CB

Update SCCM 2012 R2 to SCCM CB

The SCCM 2012 R2 is approaching the end of its lifes, so it is important to upgrade to the new version (SCCM Current Branch). Depending on the ADK and SQL version used, it may be necessary to update them as well.
So we will first update ADK Windows 8.1 to ADK Windows 10. The boot images will then be read-only, it will be necessary to update them. In a second step, we will update SCCM.

Lire la suite de

Data Warehouse service point

Data Warehouse service point

From the version 1702 of SCCM, you can enable and use Data Warehouse service point. This feature allows you to save any desired data and create date with this data. The feature supports up to 2To of data. The timestamp are present for tracking any information. The data is stored with automatic synchronisation between ConfgMgr site database and the database of Data Warehouse. This information has available from the reporting services point. After the installation of the site system role, the configuration of data warehouse database is configured. Furthermore several reports are installed.

Lire la suite de

CmdLets SCCM

CmdLets SCCM

A SCCM server administration will be generally to add new drivers, images of boot or to installations and applications. This will also be to monitor the State of health of the infrastructure by looking at the logs file.
Using PowerShell with CmdLets SCCM is justified because it is thus possible to script some action and therefore to industrialize the process which some may be « heavy » when there are executed manually.

For this Microsoft provides to people wishing Cmdlets to perform the administration of one or more servers SCCM.

Lire la suite de

L’importation des pilotes Windows 10 avec SCCM 2012 R2 SP1 et SCCM 2012 SP2 peut poser des problèmes.

Après avoir effectué l’importation, l’évènement ci-dessous est présent dans le journal DriverCatalog.log

Initializing driver digest from ‘\\server\Windows10-x64\{Windows10-driver}.inf’\\server\Windows10-x64\{Windows10-driver}.inf is not applicable to any supported platforms.Driver is not applicable to any supported platforms. Code 0x80070661

Pour solutionner le problème, il est nécessaire d’installer le CU1 pour SCCM 2012 R2 SP1 et SCCM 2012 SP2. Ce dernier est disponible ici

https://support.microsoft.com/en-us/kb/3074857

Source : http://blogs.technet.com/b/configurationmgr/archive/2015/08/05/fixed-importing-windows-10-drivers-in-configmgr-2012-fails-with-driver-is-not-applicable-to-any-supported-platforms-code-0x80070661.aspx

Merci à Jean-Sébastien Duchene pour son lien.

Microsoft a modifié il y a quelques semaines, le format de l’URL des applications présentes sur le store. il n’est donc plus possible de créer une application de type Windows Phone App Package.

Le correctif est téléchargeable ici. Il s’applique à SCCM 2012 SP2 et SCCM 2012 R2 SP1

 

 

L’équipe SCCM a publié sur son blog un nouveau billet permettant de corriger un problème au niveau des agents SCCM. En effet si un poste n’émet de rapport d’inventaire, ce dernier est considéré comme inactif.

De plus le fichier ClientIDManagerStartup.log contient l’erreur suivante :

RegTask] – Client is not registered. Sending registration request for GUID:4874BD6C-CB98-4EEB-9F4F-721CC65B25C3 …
[RegTask] – Client is registered. Server assigned ClientID is GUID:4874BD6C-CB98-4EEB-9F4F-721CC65B25C3. Approval status 1
SetRegistrationState failed (0x80071770)
[RegTask] – Sleeping for 15360 seconds …

La KB3067633 permet de régler ce problème

Source : http://blogs.technet.com/b/configurationmgr/archive/2015/06/16/kb-configuration-manager-clients-become-inactive-and-do-not-send-inventory.aspx

 

.Après avoir déplacé la base de données sur un lecteur différent, il n’est plus possible d’ajouter un groupe de mises à jour ou de nouvelles applications.

L’ erreur ci-dessous est présente dans le fichier log SMSProv.log.

*** *** Unknown SQL Error! SMS Provider 14-03-2012 07:56:47 2016 (0x07E0) *~*~*** Unknown SQL Error! ThreadID : 2016 , DbError: 50000 , Sev: 16~*~* SMS Provider 14-03-2012 07:56:47 2016 (0x07E0) *** [24000][0][Microsoft][SQL Server Native Client 10.0]Invalid cursor state SMS Provider 14-03-2012 07:56:48 2016 (0x07E0) *~*~[24000][0][Microsoft][SQL Server Native Client 10.0]Invalid cursor state *** Unknown SQL Error! ThreadID : 2016 , DbError: 0 , Sev: 0~*~* SMS Provider 14-03-2012 07:56:48 2016 (0x07E0)

Ce problème est référencé chez Microsoft par la KB3057073

https://support.microsoft.com/en-us/kb/3057073