Microsoft-Desktop

System Center 2012 Configuration Manager – Modifier la langue du clavier en mode WinPe

Grégory Bouchu — Mon, 10 Jun 2013 09:09:51 +0000

Lors des phases de troubleshooting des séquences de tâches, il peut s’avérer utile de modifier la configuration de son clavier. Cela peut être fait facilement lors de l’exécution de la séquence de tâche, voyons comment procéder !

Afin de changer la configuration du clavier lors de l’exécution de la séquence de tache, procédez ainsi :
Après le restart en mode WinPE, il suffit d’ajouter une tâche de type “Run Command Line” :

Il suffit ensuite de rajouter la ligne de commande suivante dans la fenêtre “Command line” :

wpeutil SetKeyboardLayout suivi du code langue : 100c:0000100c pour Suisse Français par exemple :

Un autre exemple pour passer votre clavier en Suisse Allemand :

Et le tour est joué. Bon troubleshooting !

The post System Center 2012 Configuration Manager – Modifier la langue du clavier en mode WinPe appeared first on Microsoft-Desktop.

Dell Computer Configuration Toolkit : Les codes erreur !

Pierre SALVY — Thu, 06 Jun 2013 08:23:49 +0000

Vous connaissez certainement l’outil “CCTK” de Dell ! Le Dell Computer Configuration Toolkit permet de configurer les BIOS des machines Dell de facon relativement simplet et automatisable.

Cet outils et très bavard et nous founir de nombeux codes erreurs pour le debugging.

Retrouvez ci dessous la liste des codes erreurs remontés par l’outils :

0	Success
1	Attempt to read write-only parameter ‘%s’
2	Password cannot exceed 16 characters
3	A BMC was either not detected or is not supported
4	This username is already in use Enter a unique username
5	Access mode not supported
6	Cannot return number of requested data bytes
7	User ID 1 cannot be assigned a username
8	Cannot execute duplicated request
9	There was an error clearing the SEL
10	Clear SEL cannot be accompanied with any other option
11	racreset cannot be accompanied with any other option
12	Cannot execute command Command, or request parameter(s), not supported in present state
13	Command not supported on given channel
14	The community string may only contain printable ASCII characters
15	Destination unavailable Cannot deliver request to selected destination
16	Cannot execute command Insufficient privilege level
17	Command illegal for specified sensor or record type
18	Invalid commstring value
19	Hardware subsystem error Invalid data field in Request
20	Invalid destination IP address
21	The GUID is invalid
22	Invalid gateway
23	Invalid hostname
24	Invalid IP address
25	Invalid DNS IP address
26	Invalid sub net mask
27	Invalid value for PEF PEF value should be between 1 and 16
28	Reservation Canceled or Invalid Reservation ID
29	Invalid Time to live value
30	Invalid VLANID value
31	Invalid Command Used to indicate an unrecognized or unsupported command
32	Command invalid for given LUN
33	Load defaults cannot be accompanied with any other option
34	There was an error loading the defaults
35	Node Busy Command could not be processed because command processing resources are temporarily unavailable
36	Out of space Command could not be completed because of a lack of storage space required to execute the given command operation
37	This parameter is not supported
38	Parameter out of range One or more parameters in the data field of the Request are out of range
39	The password may only contain printable ASCII characters
40	Password test failed
41	Requested data length invalid
42	Requested data field length limit exceeded
43	Requested Sensor, data, or record not present
44	Request data truncated
45	Command response could not be provided
46	Command response could not be provided BMC initialization or initialization agent in progress
47	Command response could not be provided Device in firmware update mode
48	Command response could not be provided SDR Repository in update mode
49	Cannot execute command, SEL erase in progress
50	Attempt to set the ‘set in progress’ value when not in the ‘set in complete’ state
51	The SOL character ‘accumulate interval’ is invalid
52	The SOL character ‘send threshold’ is invalid
53	The SOL ‘retry interval’ is invalid
54	Command completed successfully
55	Timeout while processing command Response unavailable
56	Unspecified error
57	The password may only contain printable ASCII characters
58	Username cannot exceed 16 characters
59	Invalid VLANID value Enter in ‘dddd’ format
60	Attempt to write read-only parameter ‘%s’
61	BMC is busy
62	Response data did not return successfully
63	BMC time out error
64	Invalid Configuration Option
65	Cannot execute commandParameter is illegal because command sub-function has been disabled or is unavailable
66	Option ‘%s’ requires an argument
67	The asset tag for this system is not available
68	The asset tag cannot be more than 10 characters long
69	The required BIOS interfaces cannot be found on this system
70	The BIOS version information is not available
71	There is not enough free system memory to complete the BIOS update
72	The BIOS update file version is a different version class (A00, X00) than the current system BIOS Use the –force option to use this BIOS image
73	The BIOS update file version is older than the current system bios Use the –force option to use this BIOS image
74	The BIOS update file version is identical to the current system bios Use the –force option to use this BIOS image
75	The sequence list must be a comma-separated numerical list of valid unique boot device numbers (ex: 2, 1, 3)
76	The sequence list must be a comma-separated list of valid unique device names (ex: nicemb
77	There was an error setting the sequence
78	The list is not formatted correctly See the help for more details
79	The size of returned buffer is larger than the size of allocated buffer
80	There was a problem getting the state byte
81	The state byte is not available on this system
82	There was a problem setting the state byte
83	The state byte must be a value between 0 and 255 decimal
84	The CPU information is not available
85	The dependent option ‘%s’ required for this subcommand is missing in the command line
86	Duplicate sub command ‘%s’ has been entered
87	The script file does contain not a valid DTK environment script signature (%s)
88	The format of the environment variable is incorrect
89	The –envar/-s option can only be used for a single option
90	The –envar/-s option can only be used for report operations
91	The individual sub commands should be specified for the -s option
92	Getting external serial connector settings failed
93	Setting external serial connector settings failed
94	There was an error opening the file %s
95	File ‘%s’ does not have write permission
96	The file contains invalid option ‘%s’
97	The replication information does not match for this system
98	There can only be one section in the input file
99	Bad ini file, the section [%s] cannot be found
100	The format of the bios image file is incorrect
101	Report operations and set operations must be separate
102	Help is not available for the option ‘%s’
103	The -x (–hex) option can only be used with -b or -r
104	Input file ‘%s’ not found
105	Input file ‘%s’ cannot be read
106	Invalid argument for option ‘%s’
107	Function table lookup error
108	The machine ID was not found in the file ‘%s’
109	The system memory information is not available
110	Mode can only be used with the –pci option
111	The device name or index must be present in the boot order
112	The output file ‘%s’ could not be opened Please make sure the path exists and the media is not write protected
113	Could not write to output file, disk may be full
114	The current password must be supplied with a new password using –valsyspwd
115	The current password must be supplied with a new password using –valsetuppwd
116	The current password can only be supplied when setting a new password
117	Actions are not allowed for this filter Only alerts are allowed
118	There was an error getting the option ‘%s’
119	The option ‘%s’ is not available or cannot be configured through software
120	There was an error setting the option ‘%s’
121	The -n (–namefile) option can only be used with –pci
122	The password may only contain alphanumeric characters
123	The BIOS passwords have been disabled via jumper
124	The password length must be between 1 and 32
125	This password is locked and can only be unlocked by the admin user
126	There was an error setting the password
127	The LCD string length must be between 1 and %s
128	The LCD string may only contain alphanumeric characters
129	There was an error setting the LCD string
130	The second channel can only be set if the RAID controller is set to RAID
131	The set operation, ‘%s’, requires sub commands
132	The service tag for this system is not available
133	The system ID value is not available
134	The system information string is not available
135	A system error has occured
136	Usage error
137	The uuid information is not present on this system
138	The manufacturing/first-power-on date information is not present on this system
139	Version cannot be accompanied with any other option
140	The self-identify blinker timer should be set to 0
141	Encrypt key is too long142
143	Parameter has been temporarily disabled due to a dependancy on other settings
144	The old password supplied is incorrect The new password will not be set
145	Cannot stat /etc/omregcfg file
146	Getting nicselection settings failed
147	HAPI Driver Load Error
148	Filter action power reduction is only supported for the system power warn/fail filters
149	TPM Clear settings requires setup password
150	There is currently no TPM Clear request pending
151	Password is not required for retrieving the TPM options
152	Setup password is required for setting the TPM options
153	Invalid Password override
154	Invalid TPM set option
155	There was an error setting the TPM option
156	There is no setup password installed on this system
157	The setup password supplied is incorrect Please try again
158	Profile should be custom for setting cpupowermode, memorypowermode and fanmode
159	There was an error setting the Power Option
160	The power cap value entered is out of range Please try again
161	The power cap value entered must be between 0 to 100 if unit is percent
162	Invalid IPv6 address The IPv6 address cannot be link-local or multicast
163	Invalid IPv6 address The IPv6 address specified has incorrect address format
164	Invalid IPv6 address The gateway address specified has incorrect address format
165	Invalid IPv6 address The Primary DNS server address specified has incorrect address format
166	Invalid IPv6 address The Secondary DNS server address specified has incorrect address format
167	Invalid IPv6 address The gateway address specified is invalid
168	Invalid configuration Attempting to apply IPv6 configuration on a non supported platform
169	Invalid IPv6 configuration Attempt to set DNS server address manually while DNS address source is set to auto
170	Invalid IPv6 configuration Attempt to set IPv6 address manually while IPv6 address source is set to auto
171	Invalid IPv6 configuration Attempting to apply IPv6 configuration without loading IPv6 stack
172	Invalid IPv4 configuration Attempting to apply IPv4 configuration with IPv4 disabled
173	Invalid IPv6 configuration Ipv6 address cannot be specified without specifying prefix-length
174	Invalid IPv6 configuration dnssrcv6 cannot be set to auto when ipsrcv6 is set to manual
175	Error while executing IPMI Set command
176	Error while executing IPMI Get command
177	Error during Trap Alert
178	Unspecified error
179	Unsupported device Re-try with supported device
180	Setup password is required Re-try providing setup/admin password
181	System password is required Re-try providing system password
182	The password supplied is incorrect Please try again
183	Password verification failed
184	User input password does not fit system requirement
185	Password not installed in the system
186	password status is disabled
187	Error in Validation
188	Error in Setting the Value
189	SMI call (10-0) only supports password no more than %d characters
190	This is not a Dell machine CCTK supports only Dell machines
191	Setup Password is required to change the setting Use –valsetuppwd to provide password
192	System Password is required to change the setting Use –valsyspwd to provide password
193	Password is not Installed so use only –setuppwd
194	Password is not Installed so use only –syspwd
195	The system password supplied is incorrect Please try again
196	The Sequence list must be a comma-separated list of valid unique device names (ex: hdd,cdrom)
197	The system revision information is not available for this system
198	The completion code information is not available for this system
199	The BIOS characteristics information is not available for this system
200	The password should not contain special characters
201	Please use 64-bit version of this application
202	%s cannot be modified when TPM is OFF
203	System password cannot be set when pwdlock option is in locked state (pwdlock=lock)
204	adddevice option not supported by this machine’s BIOS
205	usb device already present in this machine
206	Unable to get information from BIOS
207	%s – Error : Unable to store BIOS information
208	Duplicate entry found in the input list : %s , Operation Aborted
209	Typo found in the input list : %s , Operation Aborted
210	Asset tag can have only printable ASCII characters
211	Multiple inputs will not be accepted
212	Invalid Hex format
213	Hex value range should be 0×0 to 0xffff
214	%s – Only positive numeric values are acceptable
215	%s – Length cannot exceed two characters
216	Range for autoon hour value should be 0 to 23(24 hour format)
217	Range for autoon minute value should be 0 to 59
218	This Option Not supported on UEFI Bios
219	Unable to Set Bootorder
220	Invalid Arguments Unable to Set Bootorder
221	%s should not combine with other suboptions
222	The property ownership tag for this system is not available
223	The property ownership tag cannot be more than 80 characters for non portable machines
224	The property ownership tag is limited to 48 characters for portable systems
225	Property ownership tag can have only printable ASCII characters
226	Error in Setting the Value\nNote : In some machines, If System password is set, you can’t set Setup password
227	‘admin/root’ privileges required to execute this application
228	The option related BIOS information is not available in this machine
229	Improper Output from Bios Please try again
230	Error in Bootorder
231	The manufacturing/first-power-on date information is not present on this system
232	Not Applicable
233	Uefi bootlisttype is not supported in this Machine
234	Improper Output from Bios Please try again
235	Error in Bootorder
236	Unable to get information specific to machine
237	The input file is invalid
238	No Status Present
239	File Do not have configurable Options
240	Please provide the days to enable
241	Password is not Installed Please try again without providing –val%s
242	Please provide the old password to set the new password using –valownerpwd
243	The owner password is incorrect Please try again
244	Error in setting the value Note : Setup or system password might be set on the system
245	Owner password is not supported in file operations
246	Password operation is not supported on the system
247	The owner of the system has enabled the Owner Access feature To set the Bios configuration, create setup or system password
248	Either the system hardware or the BIOS version does not support the option To resolve the BIOS version issue, upgrade the BIOS to the latest version
249	Unable to get password information
249	Unable to get password information.

The post Dell Computer Configuration Toolkit : Les codes erreur ! appeared first on Microsoft-Desktop.

System Center Configuration Manager 2012 R2 – Présentation TechEd US 2013

Grégory Bouchu — Tue, 04 Jun 2013 15:01:32 +0000

Dans un article précédent, je vous parlais de l’annonce officielle de la sortie de System Center Configuration Manager 2012 R2.

Vous pouvez consulter ou télécharger la présentation de ce nouveau produit faite durant les TechEd US 2013 directement sur le site MSDN en suivant ce lien !

The post System Center Configuration Manager 2012 R2 – Présentation TechEd US 2013 appeared first on Microsoft-Desktop.

System Center Configuration Manager 2012 R2

Grégory Bouchu — Tue, 04 Jun 2013 08:32:07 +0000

Quelle ne fut pas ma surprise en découvrant l’annonce de la sortie de SCCM 2012 R2 !!

Pas encore de date officielle, mais quelques lignes intéressantes, retrouvez dans cet article quelques nouveautés déjà rendues publiques

– La gestion de Windows 8.1 et Windows Server 2012 R2.
– La gestion native des VHDs.
– L’arrivée de nouveaux rapports pour aider à la planification de l’infrastructure en terme de distribution logicielle.

Plus d’informations sur Configuration Manager à découvrir ICI et sur Windows Server 2012 R2 ICI

The post System Center Configuration Manager 2012 R2 appeared first on Microsoft-Desktop.

Pierresalvy.com devient Microsoft-Desktop.com, et s’ouvre à de nouveaux auteurs !

Pierre SALVY — Tue, 04 Jun 2013 07:54:49 +0000

Après 4 années de bons et loyaux services ma plateforme de blog se modernise et s’ouvre à de nouveaux auteurs ! C’est donc avec grand plaisir que pierresalvy.com se transforme en microsoft-desktop.com !

Microsoft-Desktop est donc un blog communautaire, les auteurs publient des articles de façon indépendante avec comme objectif principal le partage d’information de passionnés à curieux ou intéressés!

Mon blog devient donc Votre blog (vos publications sont les bienvenues !). Il est donc un endroit de partage et est complètement indépendant des activités commerciales de Microsoft puisque le nom Microsoft-Desktop n’a pour objectif que de définir le domaine technologique des sujets que nous abordons

Nous vous souhaitons une agréable lecture !

A très bientôt !

Pierre SALVY et les Auteurs sur Microsoft-Desktop.com

The post Pierresalvy.com devient Microsoft-Desktop.com, et s’ouvre à de nouveaux auteurs ! appeared first on Microsoft-Desktop.

Mise à jour de la documentation Configuration Manager 2012

Grégory Bouchu — Tue, 04 Jun 2013 07:18:59 +0000

Ça y est la documentation Configuration Manager 2012 du mois de Mai est en ligne avec notamment le support des installations core de Windows Server 2012 !

Découvrons ensemble les nouveautés !

What’s New in the Documentation Library for System Center 2012 Configuration Manager, May 2013

The following information lists the topics that contain significant changes since the April 2013 update.

Supported Configurations for Configuration Manager

Updated for the following updates and clarifications:
– Updated the supported list of client operating systems to include the Core installation of Windows Server 2012.
– Updated the supported list of supported Windows Embedded operating systems to include the Standard and the Industry editions of Windows Embedded 8.
– Added a clarification that the site database and the database for the reporting services point must be on a 64-bit installation of SQL Server.

Planning for Hardware Configurations in Configuration Manager

– Updated to add a note to the table in the Disk Space Configurations section to make clear that the minimum disk space listed does not include the space required for source content that is located on the site server. You can find more information about this in the Plan for Content Libraries section of the Planning for Content Management topic.

Install Sites and Create a Hierarchy for Configuration Manager

– Updated to clarify that when you upgrade an evaluation edition of Configuration Manager to a full edition, you must run the copy of Setup that is located on the site server in the Configuration Manager installation folder.

Install and Configure Site System Roles for Configuration Manager

– Updated to correct details about the service FQDN for a cloud-based distribution point. The FQDN must be unique and not match the name of a computer that is joined to a domain. This clarification is also added to the section that discusses the service certificate that you use for a cloud-based distribution point, in the Planning for Content Management in Configuration Manager topic.

Prerequisites for Reporting in Configuration Manager

– Updated to clarify that the database for the reporting services point must be on a 64-bit installation of SQL Server.

Technical Reference for Ports Used in Configuration Manager

– Updated the details for SQL Server to SQL Server connections to clarify that Configuration Manager does not require the SQL Server Browser (UDP 1434). Also updated the details in the Connections to Microsoft SQL Server section to clarify that for intersite communications, the SQL Server Service is in use, and that it defaults to port TCP 1433.

Technical Reference for Log Files in Configuration Manager

– Updated the details for the log files for cloud-based distribution points and removed an inaccurate reference to the Srvacct.log, which is not used by System Center 2012 Configuration Manager, but was used in previous versions of Configuration Manager

How to Manage Mobile Devices by Using the Exchange Server Connector in Configuration Manager

– Updated to include how to verify that the connector is installed and configured correctly.

Planning for Content Management in Configuration Manager

– Clarifications that cloud-based distribution points do not support software update packages and you must make sure that the service certificate does not define an FQDN for the cloud-based distribution point that matches an FQDN of a computer that is joined to a domain.
– Clarification in the Plan for Content Libraries section to clarify that Configuration Manager creates and maintains a content library on each site server in addition to the content library that is created on each distribution point
– Added a new section, Plan for Binary Differential Replication.

Planning for App-V Integration with Configuration Manager

– Updated to clarify that App-V 5.0 SP1 is now supported by Configuration Manager.

How to Create Applications in Configuration Manager

– Updated to warn that deployment types that contain a link to the Windows Store can be blocked by Group Policy. This information is also added to How to Create Deployment Types in Configuration Manager.

How to Create Queries in Configuration Manager

– Updated to correct the number to use when building a query to identify a Linux or UNIX client: the number to use is 13, and not 11 as previously published.

Tout le contenu ICI

The post Mise à jour de la documentation Configuration Manager 2012 appeared first on Microsoft-Desktop.

Configuration Manager 2012 – Configurer votre serveur DHCP pour le PXE

Pierre SALVY — Tue, 14 May 2013 10:37:17 +0000

Comme vous le savez sans doute, la configuration du PXE a été grandement simplifiée sous System Center 2012 Configuration Manager (SCCM 2012). Voyons ensemble comment procéder pour cette configuration !

En effet, coté console Configuration Manager, la configuration se limite maintenant à cette seule et unique page (propriétés du point de distribution) :

Une fois le PXE activé, le rôle Windows Deployement Service (WDS) sera activé et configuré automatiquement.

Il ne reste donc plus que la configuration du serveur DHCP a effectuer. Pour cela, rien de bien complexe à condition de connaitre les options à configurer. Celles-ci sont au nombre de 2 :

66 : Cette option permet de fournir au client le chemin UNC du serveur PXE.
67 : Cette option permet de fournir au client le chemin vers le fichier de boot sur le serveur PXE.

Remarque importante : Afin que le PXE fonctionne correctement, il est indispensable de s’assurer que l’image de boot x86 soit présente sur le point de distribution concerné.

The post Configuration Manager 2012 – Configurer votre serveur DHCP pour le PXE appeared first on Microsoft-Desktop.

Forefront Endpoint Protection – Récupérer et Analyser efficacement les logs du client

Pierre SALVY — Fri, 11 Jan 2013 13:17:57 +0000

Si vous avez déja implémenté donc dépanné des clients Forefront Endpoint Protection, vous savez comme il est long et compliqué donc : pénible de dépanner cet outil.

En effet, le client FEP interragit avec enormément de composants et les logs de ceux ci sont éparpillés dans près d’une dizaine d’endroits : dossiers système, Dossiers Utilisateurs, Registre, …

Après m’en être remis par désespoir au Support Premier Microsoft, ceux ci m’ont indiqués la ligne de commande suivante :

C:\Program Files\Microsoft Security Client\Antimalware\mpcmdrun -getfiles

Après avoir exécuté celle ci, vous trouverez vos logs et de nombreuses informations qui n’étaient pas visibles auparavent dans le dossier :

C:\ProgramData\Microsoft\Microsoft Antimalware\Support

n’oubliez bien sur pas de controller également le dossier :

C:\Windows\System32\CCM\logs ou C:\Windows\SysWoW64\CCM\logs

A vous de jouer !

The post Forefront Endpoint Protection – Récupérer et Analyser efficacement les logs du client appeared first on Microsoft-Desktop.

SCCM 2012 Installation et Upgrage vers le Service Pack 1

Pierre SALVY — Fri, 11 Jan 2013 09:45:06 +0000

Nous l’attendions, il est maintenant disponible auprès des abonnés Technet et MSDN, le Service Pack 1 des produits System Center 2012 est bel est bien là !

De nombreuses nouveautés sont au rendez-vous, un précédent article liste une majeure partie d’entre elles, mais voyons maintenant ensemble comment installer ce Service Pack !

Il est important de noter qu’avant toute application du service pack, il est essentiel de : vérifier la compatibilité de la version du server SQL utiliés, désinstaller WAIK, installer Windows Management Framework 3.0.

Afin de procéder à cette installation commencez par vous procurer l’iso de System Center 2012 Configuration Manager with Service Pack 1 puis suivez les étapes suivantes :

Procédez au téléchargement des prérequis, vous pouvez également utiliser les prérequis que vous aurez téléchargé via l’outil SetupDL.exe présent dans les sources d’SCCM 2012 SP1 :

Exécutez l’outil de vérification des prérequis :

Dans mon cas, les échecs remontés par l’assistant sont liées au fait que le “Windows Assessment and Deployment Kit (ADK)” est manquant puisque non requis pour SCCM 2012 RTM. Pour cela, procurez-vous les sources ICI puis suivez es étapes suivantes :

Une fois ADK installé, ré exécutez la vérification des prérequis d’installation du Service Pack :

Puis finalisez l’installation :

Votre serveur sera donc mis à jour vers le Service Pack 1 !

The post SCCM 2012 Installation et Upgrage vers le Service Pack 1 appeared first on Microsoft-Desktop.

SCCM 2012 – Ajouter le support du HTA à vos boot images

Pierre SALVY — Fri, 11 Jan 2013 09:16:47 +0000

System Center 2012 Configuration Manager permet la construction de séquences de tâches de déploiement de systèmes d’exploitation (OSD : Operating System Deployment).

Lors de l’exécution de ces séquences de tâches il est souvent utile de mettre en œuvre des assistants permettant la saisie d’informations telles que : le nom de la machine à installer, les applications, l’Unité d’Organisation de destination, …

Afin de réaliser ces assistants, une technologie est souvent utilisée : le HTA ou HTML applicatif. Nous avions d’ailleurs abordé ce sujet dans un précédent article.

Voyons ensemble comment mettre en œuvre des scripts HTA lors de l’exécution de séquences de tâches !

Pour pouvoir exécuter les scripts HTA, le “moteur” MSTHA est utile mais n’est pas présent par défaut dans les images de démarrages d’SCCM.

Afin de l’ajouter il suffit de suivre les étapes suivantes :

Parcourez les éléments suivants via votre console SCCM : Software Library > Overview > Operating System > Boot Images
Faites un clic droit sur votre Boot Image puis ouvrez les propriétés de celle-ci
Sous l’onglet “Optional Components” ajoutez le support du HTA :

Terminez l’assistant et vérifiez que votre image de boot est bien mise a jour sur vos divers points de distribution.

A vous de jouer !

The post SCCM 2012 – Ajouter le support du HTA à vos boot images appeared first on Microsoft-Desktop.