SCCM 2012 R2 Log File for Software Updates and Network Access Protection issues

Software Updates and Network Access Protection

The following table lists the log files that contain information related to software updates and Network Access Protection.

Log name	Description	Computer with log file
ccmcca.log	Records details about 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.	Client
ccmperf.log	Records activities related to the maintenance and capture of data related to client performance counters.	Client
PatchDownloader.log	Records details about the process of downloading software updates from the update source to the download destination on the site server.	The computer hosting the Configuration Manager console from which downloads are initiated
PolicyEvaluator.log	Records details about the evaluation of policies on client computers, including policies from software updates.	Client
RebootCoordinator.log	Records details about the coordination of system restarts on client computers after software update installations.	Client
ScanAgent.log	Records details about scan requests for software updates, the WSUS location, and related actions.	Client
SdmAgent.log	Records details about tracking of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance. This log file is shared with compliance settings.	Client
ServiceWindowManager.log	Records details about the evaluation of maintenance windows.	Client
smssha.log	The main log file for the Configuration Manager Network Access Protection client and it 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.	Client
Smsshv.log	This is the main log file for the System Health Validator point and records the basic operations of the System Health Validator service, such as the initialization progress.	Site system server
Smsshvadcacheclient.log	Records details about the retrieval of Configuration Manager health state references from Active Directory Domain Services.	Site system server
SmsSHVCacheStore.log	Records details 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.	Site system server
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:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL	Site system server
smsshvregistrysettings.log	Records any dynamic change to the System Health Validator component configuration while the service is running.	Site system server
SMSSHVSetup.log	Records the success or failure (with failure reason) of installing the System Health Validator point.	Site system server
SmsWusHandler.log	Records details about the scan process for the Inventory Tool for Microsoft Updates.	Client
StateMessage.log	Records details about software updates state messages that are created and sent to the management point.	Client
SUPSetup.log	Records details about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.	Site system server
UpdatesDeployment.log	Records details about deployments on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.	Client
UpdatesHandler.log	Records details about software update compliance scanning and about the download and installation of software updates on the client.	Client
UpdatesStore.log	Records details about compliance status for the software updates that were assessed during the compliance scan cycle.	Client
WCM.log	Records details about software update point configurations and connections to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.	Site server
WSUSCtrl.log	Records details about the configuration, database connectivity, and health of the WSUS server for the site.	Site system server
wsyncmgr.log	Records details about the software updates synchronization process.	Site server
WUAHandler.log	Records details about the Windows Update Agent on the client when it searches for software updates.	Client

PowerShell Commmand to Disable DHCP on the Network Interface

PowerShell Commmand to Disable DHCP on the Network Interface

• In Server we generally dont use DHCP to assign IP address.
• We usuall set Static IP Address to Server.
• So we need to disable the DHCP.
• To disable DHCP from Powershell use the Command "Set-NetIPInterface" with option -DHCP Disabled

Set-NetIPInterface -InterfaceAlias "Admin" -DHCP Disabled -PassThru

• You should specifyf or which interface you want to disable the DHCP, So you have to give the InterfaceAlias as well.

Get-NetAdapter: PowerShell Command to find Network Adapater Alias name and Index Number

PowerShell Command to find Network Adapater Alias name and Index Number

• If you have to do changes to your Network Adapter then you need to know the Alias Name and Index Number
• You can find those easily in PowerShell
• The Command is "Get-NetAdapter"
• You can see the "Name" which is Alias and ifIndex which is the "Index Number"

Test-Connection:Powershell alternate command to Ping is Test-Connection

Powershell alternate command to Ping is Test-Connection

• Ping is the first network utility that we use to test the connection
• In Powershell Ping is called Test-Connection
• It provides the same functionality of Ping

Easy way to access your network cards and configure them - ncpa.cpl

Easy way to access your network cards and configure them -ncpa.cpl

• Opening the network card is a bit of challenge in the computer. It usually takes to network page from where you have to again click on another tab to go to your network card. I was always feeling if there is easy way to do it and the yes there is
• Click on Start --> in search box type "ncpa.cpl"
• This will directly open the Network card page.
• I hope it makes your life easier like mine :)

Create Virtual Network in your Azure - Step by Step

Create Virtual Network in your Azure

• Before you Create your Virtual Server , you need to create your virtual network in your Azure platform. or else you cant assign static IP to your Server.
• Login to your Azure portal and click on Networks

• Click on "Create a Virtual Network"

• Now enter your Virtual Network Name and enter the Location
• Next  enter the DNS server Name and IP.

• Select the Subnet and select the Range.

• Click next and your Virtual Network is created.