sccm client verssion number

Release	Version	Build
SCCM 2012 R2 - CU5	5.00.7958.1604	7958
SCCM 2012 R2 SP1	5.00.8239.1000	8239
SCCM 2012 R2 SP1 - CU1	5.00.8239.1203	8239
SCCM 2012 R2 SP1 - CU2	5.00.8239.1301	8239

windows 10 collection

Creating a operating system-based collection query rule for Windows 10 in SCCM 2012

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like "%Microsoft Windows NT Workstation 10%"

Manual removal of the SCCM client

Manual removal of the SCCM client

Method 1: Uninstallation using CCMSetup.exe

You can proceed like the following:

• Open CMD and go to the location where CCMSetup.exe resides on the managed device then runCCMSetup.exe /uninstall command

Method 2: Uninstallation using client.msi

You can proceed like the following:

• Open CMD and go to the same location described in Method 1. Once done, go under the folder using {ID} as naming format ({181D79D7-1115-4D96-8E9B-5833DF92FBB4} for SCCM 2012 clients and {6A438387-0FF9-4620-947E-39470FB1E2E5} for SCCM 2007 ones) and run msiexec /x client.msi

Cannot remove Site system role

I am looking at one of my removed site systems that did only act as a DP and a site system and all the directories are also present....but IIS has removed the virtual directories from it's console....and the procedure I used to remove the DP was as follows:

Removed all packages/apps manually from the DP(checked to make sure all content was removed by browsing to the content directories in the SMSPKGC$.

Removed the PXE settings(Made sure that the WDS server role was completely removed after the PXE settings on the DP)

Removed the Distribution point site system role.

Deleted the site server which removes the site system role also.

I guess the deletion of the rest of the left-over directories is a manual process if you intend keeping the server for other purposes...I am blowing away all the DP servers and starting afresh with server 2012 so the manual deletion is not applicable to me!!

Download official MUI language packs for Windows 8.1, Windows 8 and Windows 7

some time you need to change your windows Display Language . and when you go to control panel   you facing the below issue (a language pack isn't available) 
so after i read and search i found very good Page to solve this issue 

http://winaero.com/blog/download-official-mui-language-packs-for-windows-8-1-windows-8-and-windows-7/

Show Disk Usage

To begin hardware inventory of Free Space, go to the following area within the admin console:

• Administration ->  Client Settings -> Right-click “Default Client Settings” and select Properties -> Hardware Inventory -> click on Set Classes
• Expand “Logical Disk (SMS_LogicalDisk)”
• Place a check on “Free Space (MB)”
• Click OK.

This will instruct all clients to update policy for Hardware Inventory and begin reporting Free Space in MB.

Depending on the hardware inventory scan cycle, it may take a few days to obtain metrics from all machines. When machines report both size of logical disks along with free space, both numbers will be in megabytes (MB). Subtracting logical disk size minus free space will yield usage. This query will perform the subtraction along with the conversion of megabytes (MB) to gigabytes (GB). In addition, it will also calculate the free space percentage for each logical disk.

select SystemName0 as 'Machine Name', DeviceID0 as 'Logical Drive', FileSystem0 as 'File System', convert(decimal(20,0),round(1.0*Size0/1024,0)) as 'Capacity GB',
convert(decimal(20,0),round(1.0*(Size0-FreeSpace0)/1024,0)) as 'UsedSpace GB', convert(decimal(20,0),round(1.0*FreeSpace0/1024,0)) as 'FreeSpace GB',
convert(decimal(20,1),round((cast(FreeSpace0 as decimal)/ cast(Size0 as decimal) * 100),1)) as 'Percent Free',
VolumeName0 as 'Volume Name'
from v_GS_LOGICAL_DISK
where (Size0 is not null) and (FreeSpace0 is not null)
Order by Systemname0, DeviceID0

For Disable or Enable anonymous authentication

open Regedit :
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]

and open =====>   restrictanonymoussam
Value     =====> 1 Enable
              =====> 0 Disable

list of computers where Programs installed recently

SELECT 
CS.Name0, 
CS.UserName0, 
ISW.ProductName0, 
ISW.VersionMajor0, 
ISW.VersionMinor0, 
ISW.Publisher0, 
ISW.RegisteredUser0, 
ISW.InstallDate0, 
ISW.InstallSource0 
FROM 
dbo.v_GS_COMPUTER_SYSTEM CS, 
dbo.v_GS_INSTALLED_SOFTWARE ISW 
WHERE 
ISW.ResourceID = CS.ResourceID 
ORDER BY 
ISW.InstallDate0 DESC, 
CS.Name0, 
CS.UserName0, 
ISW.ProductName0

Out of band microsoft security update

Microsoft has released an out-of-band security update to address a critical vulnerability in Kerberos.

https://support.microsoft.com/kb/3011780

https://technet.microsoft.com/library/security/ms14-068 The vulnerability could allow an attacker to elevate unprivileged domain user account privileges to those of the domain administrator account.

A List of SCCM Log Files

The client logs are located in the %WINDIR%\System32\CCM\Logs folder or %WINDIR%\SysWOW64\CCM\Logs (for x64 OS).

The SCCM server log files are located in the <INSTALL_PATH>\Logs or SMS_CCM\Logs folder. IIS logs can be found in %WINDIR%\System32\logfiles\W3SVC1 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 SMS\INBOXES 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 SMS\INBOXES 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:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@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.

Unable to perform any task error: TFTP Download: smsboot\x64\abortpxe.com

Solution:

https://social.technet.microsoft.com/Forums/systemcenter/en-US/4f2b4b85-ecd6-4e00-a445-b59acfcc544a/unable-to-perform-any-task-error-tftp-download-smsbootx64abortpxecom?forum=configmgrosd

I do the following -

1) Go to Unprovisioned computers and clear out the PXE adverts for those systems.
2) Go to All Systems collection and update collection membership. I'll often find an "unknown" or two in there. I delete these, update collection membership again.

90% of the time, I'm able to PXE again. Otherwise, I simply need to wait 5 or 10 minutes and the issue goes away.

Sure wish I knew the exact solution for that issue. From what I understand, there's a Regkey in WDS that can be set to delete the PXE cache, but its not recommended to make that change in Prod.

Software Updates Notification behavior and time restart

Client Settings
Open Client Settings > Computer Agent

See options

Deployment deadline greater than 24 hours – remind user every 48 hours

Deployment deadline less than 24 hours – remind user every 4 hours

Deployment deadline less than 1 hour – remind user every 15 minutes

See restart options

Display temporary notification to the user that indicates the interval before the user is logged off or before the computer restarts – 90 mins

Display a dialog box that the user cannot close which displays the countdown interval before the user is logged off or before the computer restarts – 15 mins

Deployment

I like to choose the option above when deploying the updates - show all notifications to the user and show in software center.

I also like to configure update deployments with a deadline of 1 week away (this is the default setting).

Updates available

When the device retrieves policy the user is notified that updates are available. 

User receives notification. The user is invited to "Click here for options".

If the user "clicks for options" they are informed that updates are available with a deadline of 1 week. They are invited to "Apply all required changes now" or can click to "Remind me later". Most users will choose "Remind me later".

The software update information is available in the Software Center. 


Deadline

When the deadline arrives the updates are downloaded to the computer cache. Note that this does not happen exactly at the deadline time.

It is not a great idea to deploy updates to thousands of machines at exactly the same time. Therefore each client adds a random time of up to two hours to the installation specific deadline time. This random additional time isn't configurable. (Note that Deadline Randomization is now disabled by default in SP1).

Restart

Now the restart countdown commences (90 minutes by default). 

The user is notified.

The required restart can be seen in the Software Center

Click the balloon notification to see the dialog box. The user can Hide the notification at this time. Note that even when the balloon notification disappears the restart timer remains in the system tray. The user can click on the restart timer icon in the system tray at any time to open the dialog box (assuming of course you haven't hidden notifications in the system tray).

User receives additional notification of pending restart, which can be hidden.

Countdown has entered last 15 minutes. The user is notified by a dialog box and the notification cannot be hidden or minimised. It will remain in the foreground until the computer restarts. All other applications remain in the background - no excuses for the user.