SCCM SCCM Log Files

Introduction:

This post is really helpful for the people who are looking for SCCM log files. The log files can be viewed with a tool called CMTrace tool located in the path : <SCCM setup DVD>SMSSETUP/TOOLS. The client logs are located in the path : %WINDIR%System32/CCM/Logs folder.
For 64 Bit Operating System :  %WINDIR%SysWOW64CCMLogs. The SCCM server log files are located in the: <INSTALL_PATH>Logs or SMS_CCMLogs folder.


Client Log Files

• CAS – Content Access Service. Maintains the local package cache.
• Ccmexec.log – Records activities of the client and the SMS Agent Host service.
• CertificateMaintenance.log – Maintains certificates for Active Directory directory service and management points.
• ClientIDManagerStartup.log – Creates and maintains the client GUID.
• ClientLocation.log – Site assignment tasks.
• ContentTransferManager.log – Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.
• DataTransferService.log – Records all BITS communication for policy or package access.
• Execmgr.log – Records advertisements that run.
• FileBITS.log – Records all SMB package access tasks.
• Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) – Windows Management Instrumentation (WMI) provider for software inventory and file collection.
• InventoryAgent.log – Creates discovery data records (DDRs) and hardware and software inventory records.
• LocationServices.log – Finds management points and distribution points.
• Mifprovider.log – The WMI provider for .MIF files.
• Mtrmgr.log – Monitors all software metering processes.
• PolicyAgent.log – Requests policies by using the Data Transfer service.
• PolicyAgentProvider.log – Records policy changes.
• PolicyEvaluator.log – Records new policy settings.
• Remctrl.log – Logs when the remote control component (WUSER32) starts.
• Scheduler.log – Records schedule tasks for all client operations.
• Smscliui.log – Records usage of the Systems Management tool in Control Panel.
• StatusAgent.log – Logs status messages that are created by the client components.
• SWMTRReportGen.log – Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

Server Log Files

• Ccm.log – Client Configuration Manager tasks.
• Cidm.log – Records changes to the client settings by the Client Install Data Manager (CIDM).
• Colleval.log – Logs when collections are created, changed, and deleted by the Collection Evaluator.
• Compsumm.log – Records Component Status Summarizer tasks.
• Cscnfsvc.log – Records Courier Sender confirmation service tasks.
• Dataldr.log – Processes Management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.
• Ddm.log – Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager.
• Despool.log – Records incoming site-to-site communication transfers.
• Distmgr.log – Records package creation, compression, delta replication, and information updates.
• Hman.log – Records site configuration changes, and publishes site information in Active Directory Domain Services.
• Inboxast.log – Records files that are moved from the management point to the corresponding SMSINBOXES folder.
• Inboxmgr.log – Records file maintenance.
• Invproc.log – Records the processing of delta MIF files for the Dataloader component from client inventory files.
• Mpcontrol.log – Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.
• Mpfdm.log – Management point component that moves client files to the corresponding SMSINBOXES folder.
• MPMSI.log – Management point .msi installation log.
• MPSetup.log – Records the management point installation wrapper process.
• Ntsvrdis.log – Configuration Manager 2007 server discovery.
• Offermgr.log – Records advertisement updates.
• Offersum.log – Records summarization of advertisement status messages.
• Policypv.log – Records updates to the client policies to reflect changes to client settings or advertisements.
• Replmgr.log – Records the replication of files between the site server components and the Scheduler component.
• Rsetup.log – Reporting point setup log.
• Sched.log – Records site-to-site job and package replication.
• Sender.log – Records files that are sent to other child and parent sites.
• Sinvproc.log – Records client software inventory data processing to the site database in Microsoft SQL Server.
• Sitecomp.log – Records maintenance of the installed site components.
• Sitectrl.log – Records site setting changes to the Sitectrl.ct0 file.
• Sitestat.log – Records the monitoring process of all site systems.
• Smsdbmon.log – Records database changes.
• Smsexec.log – Records processing of all site server component threads.
• Smsprov.log – Records WMI provider access to the site database.
• SMSReportingInstall.log – Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.
• SMSSHVSetup.log – Records the success or failure (with failure reason) of installing the System Health Validator point.
• Srvacct.log – Records the maintenance of accounts when the site uses standard security.
• Statmgr.log – Writes all status messages to the database.
• Swmproc.log – Processes metering files and maintains settings.

Admin Console Log Files

• RepairWizard.log – Records errors, warnings, and information about the process of running the Repair Wizard.
• ResourceExplorer.log – Records errors, warnings, and information about running the Resource Explorer.
• SMSAdminUI.log – Records the local Configuration Manager 2007 console tasks when you connect to Configuration Manager 2007 sites.

Management Point Log Files

• MP_Ddr.log – Records the conversion of XML.ddr records from clients, and copies them to the site server.
• MP_GetAuth.log – Records the status of the site management points.
• MP_GetPolicy.log – Records policy information.
• MP_Hinv.log – Converts XML hardware inventory records from clients and copies the files to the site server.
• MP_Location.log – Records location manager tasks.
• MP_Policy.log – Records policy communication.
• MP_Relay.log – Copies files that are collected from the client.
• MP_Retry.log – Records the hardware inventory retry processes.
• MP_Sinv.log – Converts XML hardware inventory records from clients and copies them to the site server.
• MP_Status.log – Converts XML.svf status message files from clients and copies them to the site server.

Mobile Device Management Log Files

• DmClientHealth.log – Records the GUIDs of all the mobile device clients that are communicating with the Device Management Point.
• DmClientRegistration.log – Records registration requests from and responses to the mobile device client in Native mode.
• DmpDatastore.log – Records all the site database connections and queries made by the Device Management Point.
• DmpDiscovery.log – Records all the discovery data from the mobile device clients on the Device Management Point.
• DmpFileCollection.log – Records mobile device file collection data from mobile device clients on the Device Management Point.
• DmpHardware.log – Records hardware inventory data from mobile device clients on the Device Management Point.
• DmpIsapi.log – Records mobile device communication data from device clients on the Device Management Point.
• dmpMSI.log – Records the MSI data for Device Management Point setup.
• DMPSetup.log – Records the mobile device management setup process.
• DmpSoftware.log – Records mobile device software distribution data from mobile device clients on the Device Management Point.
• DmpStatus.log – Records mobile device status messages data from mobile device clients on the Device Management Point.
• FspIsapi.log – Records Fallback Status Point communication data from mobile device clients and client computers on the Fallback Status Point.

Mobile Device Client Log Files

• DmCertEnroll.log – Records certificate enrollment data on mobile device clients.
• DMCertResp.htm (in temp) – Records HTML response from the certificate server when the mobile device Enroller program requests a client authentication certificate on mobile device clients.
• DmClientSetup.log – Records client setup data on mobile device clients.
• DmClientXfer.log – Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.
• DmCommonInstaller.log – Records client transfer file installation for setting up mobile device client transfer files on client computers.
• DmInstaller.log – Records whether DMInstaller correctly calls DmClientSetup and whether DmClientSetup exits with success or failure on mobile device clients.
• DmInvExtension.log – Records Inventory Extension file installation for setting up Inventory Extension files on client computers.
• DmSvc.log – Records mobile device management service data on mobile device clients.

Operating System Deployment Log Files

• CCMSetup.log – Provides information about client-based operating system actions.
• CreateTSMedia.log – Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.
• DriverCatalog.log – Provides information about device drivers that have been imported into the driver catalog.
• MP_ClientIDManager.log – Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.
• MP_DriverManager.log – Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.
• MP_Location.log – Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.
• Pxecontrol.log – Provides information about the PXE Control Manager.
• PXEMsi.log – Provides information about the PXE service point and is generated when the PXE service point site server has been created.
• PXESetup.log – Provides information about the PXE service point and is generated when the PXE service point site server has been created.
• Setupact.log Setupapi.log Setuperr.log Provide information about Windows Sysprep and setup logs.
• SmpIsapi.log – Provides information about the state migration point Configuration Manager 2007 client request responses.
• Smpmgr.log – Provides information about the results of state migration point health checks and configuration changes.
• SmpMSI.log – Provides information about the state migration point and is generated when the state migration point site server has been created.
• Smsprov.log – Provides information about the SMS provider.
• Smspxe.log – Provides information about the Configuration Manager 2007 PXE service point.
• SMSSMPSetup.log – Provides information about the state migration point and is generated when the state migration point site server has been created.
• Smsts.log – General location for all operating system deployment and task sequence log events.
• TaskSequenceProvider.log – Provides information about task sequences when they are imported, exported, or edited.
• USMT Log loadstate.log – Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.
• USMT Log scanstate.log – Provides information about the USMT regarding the capture of user state data.

Network Access Protection Log Files

• Ccmcca.log – Logs the processing of compliance evaluation based on Configuration Manager NAP policy processing and contains the processing of remediation for each software update required for compliance.
• CIAgent.log – Tracks the process of remediation and compliance. However, the software updates log file, *Updateshandler.log – provides more informative details on installing the software updates required for compliance.
• locationservices.log – Used by other Configuration Manager features (for example, information about the client’s assigned site) but also contains information specific to Network Access Protection when the client is in remediation. It records the names of the required remediation servers (management point, software update point, and distribution points that host content required for compliance), which are also sent in the client statement of health.
• SDMAgent.log – Shared with the Configuration Manager feature desired configuration management and contains the tracking process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance.
• SMSSha.log – The main log file for the Configuration Manager Network Access Protection client and contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.

System Health Validator Point Log Files

• Ccmperf.log -Contains information about the initialization of the System Health Validator point performance counters.
• SmsSHV.log – The main log file for the System Health Validator point; logs the basic operations of the System Health Validator service, such as the initialization progress.
• SmsSHVADCacheClient.log – Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.
• SmsSHVCacheStore.log – Contains information about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.
• SmsSHVRegistrySettings.log – Records any dynamic changes to the System Health Validator component configuration while the service is running.
• SmsSHVQuarValidator.log – Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKLMSOFTWAREMicrosoftSMSSHVLogging@GLOBAL

Desired Configuration Management Log Files

• ciagent.log – Provides information about downloading, storing, and accessing assigned configuration baselines.
• dcmagent.log – Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes.
• discovery.log – Provides detailed information about the Service Modeling Language (SML) processes.
• sdmagent.log – Provides information about downloading, storing, and accessing configuration item content.
• sdmdiscagent.log – Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items.

Wake On LAN Log Files

• Wolmgr.log – Contains information about wake-up procedures such as when to wake up advertisements or deployments that are configured for Wake On LAN.
• WolCmgr.log – Contains information about which clients need to be sent wake-up packets, the number of wake-up packets sent, and the number of wake-up packets retried.

Software Updates Site Server Log Files

• ciamgr.log – Provides information about the addition, deletion, and modification of software update configuration items.
• distmgr.log – Provides information about the replication of software update deployment packages.
• objreplmgr.log – Provides information about the replication of software updates notification files from a parent to child sites.
• PatchDownloader.log – Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server.
• replmgr.log – Provides information about the process for replicating files between sites.
• smsdbmon.log – Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.
• SUPSetup – Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.
• WCM.log – Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.
• WSUSCtrl.log – Provides information about the configuration, database connectivity, and health of the WSUS server for the site.
• wsyncmgr.log -Provides information about the software updates synchronization process.

WSUS Server Log Files

• Change.log – Provides information about the WSUS server database information that has changed.
• SoftwareDistribution.log – Provides information about the software updates that are synchronized from the configured update source to the WSUS server database.

Software Updates Client Computer Log Files

• CAS.log – Provides information about the process of downloading software updates to the local cache and cache management.
• CIAgent.log – Provides information about processing configuration items, including software updates.
• LocationServices.log – Provides information about the location of the WSUS server when a scan is initiated on the client.
• PatchDownloader.log – Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
• PolicyAgent.log – Provides information about the process for downloading, compiling, and deleting policies on client computers.
• PolicyEvaluator – Provides information about the process for evaluating policies on client computers, including policies from software updates.
• RebootCoordinator.log – Provides information about the process for coordinating system restarts on client computers after software update installations.
• ScanAgent.log – Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
• ScanWrapper – Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.
• SdmAgent.log – Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.
• ServiceWindowManager.log – Provides information about the process for evaluating configured maintenance windows.
• smscliUI.log – Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.
• SmsWusHandler – Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.
• StateMessage.log – Provides information about when software updates state messages are created and sent to the management point.
• UpdatesDeployment.log – Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
• UpdatesHandler.log – Provides information about software update compliance scanning and about the download and installation of software updates on the client.
• UpdatesStore.log – Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.
• WUAHandler.log – Provides information about when the Windows Update Agent on the client searches for software updates.
• WUSSyncXML.log – Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

Windows Update Agent Log File

• WindowsUpdate.log – Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.

Network Troubleshooting with Microsoft Message Analyzer

Most of the time you find yourself wishing for a single window where you could view and manage all of these diverse sources of information. And that is exactly where Microsoft Message Analyzer comes to your aid.

An amazing interface

  As the name implies, the “message” forms the basis of data. This “message” takes on different formats, ranging from a captured frame or packet to an event found on Event Viewer. You are able to merge or “stack” these messages into conversations and sessions.

Remote capture capabilities

Microsoft has ensured that the Message Analyzer stays relevant and powerful with time. That’s why beginning with Windows 8.1/2012, the tool’s capture driver is integrated with the Windows operating system. What this signifies is effective WinRM configuration – the kind you are able to capture using a remote machine. That’s not all! You are now able to capture from more than one machine at the same time.
When you’re beginning a new live trace, you have the option of editing the target systems and entering either the IP or the name of the computer you actually want to capture from.
There’s another method you can use to capture. This involves capturing at the Windows Firewall level prior to the local IPsec encryption, or even at the actual application level before it gets encrypted by HTTPS.

More intelligence to better handle different scenarios

If you thought Microsoft Message Analyzer’s capabilities ended with catching HTTP and IPsec traffic, you were wrong – that was only the beginning. This tool allows you to perform captures or traces that you can use to troubleshoot SMB directly, along with Bluetooth and USB.
At the time of setting up the trace, make sure you pick only the required trace scenario out of multiple options. That’s all you need to do! Moreover, this tool is capable of intelligent operations, checking the messages for anomalies, errors, or warnings with the utmost care.
You are able to choose between the views that provide information as per your demand. In fact, there are a couple of views that enable you to look at the timing of the packets, the associated responses, along with the kernel module as well as the process name.

Final thoughts

Network troubleshooting has always been tricky owing to the different components involved and the trouble the user has to cope with just to switch panes. However, not only does the Microsoft Message Analyzer allow you to network troubleshoot at the professional level, it adds to your repertoire of IT tricks that can be used in a plenitude of different aspects in your career and life.

 

 

 

 

 

System Center Configuration Manager (Current Branch)

Utilisez Windows BranchCache avec Configuration Manager quand vous l’activez sur des points de distribution, puis configurez les clients pour l’utiliser en mode de cache distribué.
Configurez les paramètres de BranchCache sur un type de déploiement d’applications, sur le déploiement d’un package et pour les séquences de tâches. À partir de la version 1802, BranchCache est activé par défaut.
Quand les conditions requises de BranchCache sont remplies, cette fonctionnalité permet aux clients situés à des emplacements distants d’obtenir le contenu des clients locaux qui ont un cache actif du contenu.
Par exemple, quand le premier client BranchCache demande du contenu à un point de distribution configuré en tant que serveur BranchCache, le client télécharge et met en cache ce contenu. Ce contenu est ensuite rendu disponible pour les clients sur le même sous-réseau qui celui qui a demandé ce contenu.
Ces clients mettent également en cache le contenu. Les autres clients du même sous-réseau n’ont pas à télécharger le contenu à partir du point de distribution. Le contenu est distribué sur plusieurs clients, en vue de transferts futurs.

Activer BranchCache dans Client Settings

To enable BranchCache on computers using Client Settings:

1. Open the Client Settings policy you want to apply to clients (it is recommended that a new policy be created to apply custom settings rather than editing the Default Client Settings policy)
2. Tick the box on the General tab to include Client Cache Settings
   

   Create Custom Client Settings
3. Select the Client Cache Settings tab
   • Change Configure BranchCache to Yes
   • Change Enable BranchCache to Yes
   

   Edit Client Cache Settings
4. Deploy the settings (See Create and Deploy Custom Client Settings for more information).

NOTE
Unlike Group Policy, if you want to disable BranchCache you must explicitly disable it using Client Settings or an alternate method. Simply removing the client setting to enable it won’t revert it to it’s previous state. In addition, while the feature will add the firewall rules to Windows Firewall, it will not remove them when the feature is disabled.

Verify BranchCache is Enabled

After the new client settings are retrieved and updated on clients, you will notice BranchCache is enabled.

Netsh

From a command prompt, run netsh to confirm that BranchCache is now running in Distributed Caching mode and the cache size is configured as per the Client Settings.

1	netsh branchcache show status all

Confirm BranchCache Enabled

CAS.log

You will see the following entries in CAS.log:

1 2 3 4

Enabling BranchCache.   ContentAccess   13/05/2017 6:45:30 PM   2600 (0x0A28) EnablePeerDistribution: Successfully enabled PeerDistribution   ContentAccess   13/05/2017 6:45:32 PM   2600 (0x0A28) Setting BranchCache size to 10 of disk  ContentAccess   13/05/2017 6:45:32 PM   2600 (0x0A28) SetCacheSize: Successfully set cache size   ContentAccess   13/05/2017 6:45:32 PM   2600 (0x0A28)

Firewall Rules

Windows Firewall rules will be configured as per the table below:

Name	Group	Profile	Enabled	Action	Override	Program	Local Address	Remote Address	Protocol	Local Port	Remote Port
BranchCache Content Retrieval (HTTP-In)	BranchCache – Content Retrieval (Uses HTTP)	All	No	Allow	No	SYSTEM	Any	Any	TCP	80	Any
BranchCache Content Retrieval (HTTP-In)	BranchCache – Content Retrieval (Uses HTTP)	Domain,Private	Yes	Allow	No	SYSTEM	Any	Any	TCP	80	Any
BranchCache Hosted Cache Server (HTTP-In)	BranchCache – Hosted Cache Server (Uses HTTPS)	All	No	Allow	No	SYSTEM	Any	Any	TCP	80,443	Any
BranchCache Peer Discovery (WSD-In)	BranchCache – Peer Discovery (Uses WSD)	All	No	Allow	No	%SYSTEMROOT%\system32\svchost.exe	Any	Local subnet	UDP	3702	Any
BranchCache Peer Discovery (WSD-In)	BranchCache – Peer Discovery (Uses WSD)	Domain,Private	Yes	Allow	No	%SYSTEMROOT%\system32\svchost.exe	Any	Local subnet	UDP	3702	Any

Compare GPO with Policy Analyzer

Policy Analyzer is a tool released a couple of years ago that allows an administrator to easily compare two or more GPOs to find the differences between them.  It's a little clunky to use for quick troubleshooting, but for in-depth GPO work, this is a great tool for helping review and organize GPOs.  Here, we'll walk through how to get started and interpret the results.

Get Set Up
To get started, download the Policy Analyzer tool from Microsoft at https://www.microsoft.com/en-us/download/details.aspx?id=55319.  This download points to the Microsoft Security Compliance Toolkit, which Policy Analyzer is a part of.  On the download page, you can opt to only download "PolicyAnalyzer.zip" which is the only file we need.  Once that's downloaded, copy it up to a server in the environment you are working on.  It can either be a DC or a member server with the Group Policy console installed.  From there, unzip the file and run PolicyAnalyzer.exe

Preparing GPOs
To compare GPOs, we must first back them up to a folder on the local server.  To do so:

1. Open the Group Policy Management Console
2. Expand the OUs or Group Policy Objects container to find the GPOs you want to compare
3. Right click the first GPO and select "Back up…"
   
4. Enter a path to save the backup to.  Ensure the folder you select doesn't contain any other GPO backups, or the Policy Analyzer may have trouble importing them.
5. Press the "Back Up" button
6. Repeat steps 2-5 for each GPO you want to compare, ensuring you create a separate folder to store each GPO backup like in the structure below.  Note that the GUID folder is created automatically by the backup, but the friendly folders (STIG 2012 R2 DC and Member Server) were created manually:
   

Importing the GPOs to Policy Analyzer
Before you can compare the GPOs, they must be imported into the Policy Analyzer tool.   This process reads the GPO backup you created and creates a policy definition file that the tool can use.

1. In Policy Analyzer, click the "Add…" button
2. In the popup, click File, then "Add Files from GPO(s)…"
   
3. Browse to and select the folder where you saved the backup
4. The importer tool will show the different types of settings detected
5. Click the "Import…" button
6. Save the policy rule definition file to the default folder, giving it a meaningful name
   
7. Repeat steps 1-7 for each GPO that you backed up previously

Comparing the GPOs
With everything prepared, we can now actually compare 2 or more GPOs.  In the main Policy Analyzer window, select the GPOs you want to compare, and click the "View / Compare" button.  You'll get a pop up with all the defined settings and what they are set to in each of the GPOs you are comparing.  Gray cells indicate that setting isn't configured in that policy, while yellow cells indicate values that conflict between the GPOs that are being compared.  To find where each GPO option is configured, click the row in the table, and the Policy Path in the bottom detail window shows the path to the GPO option.



Exporting to Excel
If you have Excel installed on the computer you are running Policy Analyzer on, you can use the Export > "Export Table to Excel" feature to save the data to an Excel workbook.  Since you probably don't have Excel installed on your DCs, you can run Policy Analyzer locally on your workstation.  To do so, copy the GPO backup folders to your computer after backing them up in the Group Policy Console on the server, and then import them into Policy Analyzer on your local PC.  That will allow you to run the comparison and export the data to Excel for analysis.

Summary
This tool is helpful for in-depth analysis of Group Policy to help determine how GPOs in the domain differ from each other.  You can use it for basic comparisons of GPOs, comparing custom compliance GPOs to a known-good baseline, or to help guide the consolidation of multiple GPOs.

For more information about Policy Analyzer, see the official documentation.

Installer le shell Bash (Linux) sous Windows 10

Activer le sous-système Linux de Windows. Pour cela, tapez « fonctionnalités » dans la barre de recherche et cliquez sur « Activer ou désactiver des fonctionnalités Windows« .

Vous verrez alors apparaitre cette fenêtre. Cochez la case « Sous-système Windows pour Linux » et faites OK. Votre ordinateur devra ensuite redémarrer.

 





Première chose à savoir, votre C: se trouve dans /mnt/c

Ensuite, et bien c’est comme sous Ubuntu… Vous pouvez installer des paquets avec la commande « apt-get install … « , et les mettre à jour avec « apt-get update » et « apt-get upgrade ».