Compare and query creation handy tool

This tool will be useful in creating query for adding bulk of machine in CM12 device collections. This will reduce the time taken to form the query structure. Just placing the input and clicking the button will provide the querystructure and the device information can be compared.

Click here to Download






Created  SCCM Query for Adding bulk of machines in collection:
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.Name in ("mnop","ijkl","efgh","abcd") and SMS_R_System.Obsolete != "1" and SMS_R_System.Client = "1"


Compare:
Comparing strings in two columns and identifying the availability of stings in both the column.



If we are part of Patch Deployment and release work, this options make our work easier 





Configuration Manager 2012 client Architecture Data Flow




Configuration Manager client Architecture for Deadline Data flow
Configuration Manager client Architecture for Activation Data Flow


Application Deployment Troubleshooting in Depth


Before proceeding with this Application deployment Troubleshooting it is advised to understand the data flow of Configuration Manager Client architecture .
Lets take a sample Application and Deployment targeted for a collection.

In order to troubleshoot the application deployment, it is advised to note the deployment id and CI Unique ID for the deployment and application. As per our example, we are going to verify the flow of client that is targeted to get Mozilla Firefox Application. I have highlighted the Deployment id and CI Unique ID for the example that we are going to follow.

Sample Application:





Let us start Analyzing the logs from the Policy download to Appenforce in sequential order.

Step 1: PolicyAgent.log

As an initial step, verify the policy agent log for the deployment id, you have targeted. I have highlighted the deployment id of my collection and could see the initialization for download of policy.

Compiling policy '{647B4CE3-E844-4E26-8248-B219063DCEAA}' version '1.00' hash 'SHA256:02B6FA58508B6CF9583580C64522ED5D5D186D4FFA8F4E1FE62888B34040511A'
Initializing download of policy 'CCM_Policy_Policy5.PolicyID="{647B4CE3-E844-4E26-8248-B219063DCEAA}",PolicySource="SMS:LN1",PolicyVersion="1.00"' from 'http://SCCMAD.local.test/SMS_MP/.sms_pol?{647B4CE3-E844-4E26-8248-B219063DCEAA}.SHA256:02B6FA58508B6CF9583580C64522ED5D5D186D4FFA8F4E1FE62888B34040511A'

Step 2: DataTransferservices.log

After the initialization policy, job created in data services for downloading policy data.

DTSJob {97D08EA3-7188-4B09-9AC4-D99551B4F643} created to download from 'http://SCCMAD.local.test:80/SMS_MP' to 'C:\Windows\CCM\Temp'.
DTSJob {97D08EA3-7188-4B09-9AC4-D99551B4F643} in state 'PendingDownload'.
DTSJob {97D08EA3-7188-4B09-9AC4-D99551B4F643} in state 'DownloadingData'.
DTSJob {97D08EA3-7188-4B09-9AC4-D99551B4F643} in state 'RetrievedData'.
DTSJob {97D08EA3-7188-4B09-9AC4-D99551B4F643} successfully completed download.
DTSJob {97D08EA3-7188-4B09-9AC4-D99551B4F643} in state 'NotifiedComplete'.


Step 3: PolicyAgent.log

Once the download job succeeded, policy starts downloading through BITS

Download of policy CCM_Policy_Policy5.PolicyID="{647B4CE3-E844-4E26-8248-B219063DCEAA}",PolicySource="SMS:LN1",PolicyVersion="1.00" completed (DTS Job ID: {97D08EA3-7188-4B09-9AC4-D99551B4F643})
DownloadMethod = "BITS";
DownloadSource = "http://SCCMAD.local.test/SMS_MP/.sms_pol?{647B4CE3-E844-4E26-8248-B219063DCEAA}.SHA256:02B6FA58508B6CF9583580C64522ED5D5D186D4FFA8F4E1FE62888B34040511A";PolicyNamespace = "\\\\.\\ROOT\\ccm\\Policy\\Machine\\RequestedConfig";

Step 4: Policy Evaluator.log

Policy evaluator starts updating and applying the policy

Updating policy CCM_Policy_Policy5.PolicyID="ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/Application_6e4c5a44-5b99-46ed-92b1-5d195a3d1108/CA",
Applied policy CCM_Policy_Policy5.PolicyID="ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/Application_6e4c5a44-5b99-46ed-92b1-5d195a3d1108/CA",PolicySource="SMS:LN1",PolicyVersion="1.00"

Step 5: Ccmexec.log

CCMexec component notifies the DCM agent with Assignment id. Here on, the Assignment id is used to verify


Notifying endpoint 'DCMAgent' of __InstanceCreationEvent settings change on object CCM_ApplicationCIAssignment.AssignmentID="{647B4CE3-E844-4E26-8248-B219063DCEAA}" for user 'S-1-5-18'.

Step 6: Scheduler.log

Scheduler Trigger with condition for the assignment id notified by ccmexec in above process.


Initialized trigger ("DD7A4B8000080001") for schedule 'Machine/{647B4CE3-E844-4E26-8248-B219063DCEAA}':Conditions=1 with deadline 4320 minutes
SMSTrigger 'DD7A4B8000080001' for scheduler 'Machine/{647B4CE3-E844-4E26-8248-B219063DCEAA}' will fire at 04/26/2016 07:32:57 AM without randomization.

Step 7: CIStore.log

Successfully persisted CI Site_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/SUM_40170f7c-955b-4d24-9791-ba7f18830801.200

Step 8: CIStatestore.log


CCIStateStore::SendStateMessages - ModelName: ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a, Version:2 UserID:, Priority: 5
CCIStateTransition::ExtractStateDetails - CI ModelName ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a, version 2 not found in store.

Step 9: DcmAgent.log

DCM state machine creates CIAgent job. Note the CI Agent id and search it in CIAgent.log



Queued 0x0 action for assignment id={647B4CE3-E844-4E26-8248-B219063DCEAA} name=Mozilla Firefox 17.0.1 (x86 en-US)_Windows 7 PCs_Install targeted to machine
DCMAgentJob({3BD4F33D-996D-49BC-AD94-DEC1CC19C065}): CDCMAgentJob::SetupJob - Add assignment Mozilla Firefox 17.0.1 (x86 en-US)_Windows 7 PCs_Install({647B4CE3-E844-4E26-8248-B219063DCEAA})

DCMAgentJob({3BD4F33D-996D-49BC-AD94-DEC1CC19C065}): CDCMAgent::InitiateCIAgentJob - Starting CI Agent Job {FE10E492-57E5-4248-ACF7-2A24D00A6064} for target: machine. Refer to this CI agent job ID in ciagent.log for more details


Step 10: CIAgent.log


CIAgent initiate CI Task for the particular CIAgent job seen above.


CIAgentJob({FE10E492-57E5-4248-ACF7-2A24D00A6064}): CAgentJob::HandleEvent(Event=DownloadCIs, CurrentState=WaitingForAssignedCI) CIAgent 26/04/2016 07:33:00 2020 (0x07E4)
CIAgentJob({FE10E492-57E5-4248-ACF7-2A24D00A6064}): TransitionState(From=WaitingForAssignedCI, To=DownloadingCIs) for Event=Transition CIAgent 26/04/2016 07:33:00 2020 (0x07E4)


Step 11: CIDownloader.log

CIAgentJob({FE10E492-57E5-4248-ACF7-2A24D00A6064}): Started CIDownloadJob({0FDC994C-19E2-43F0-870B-CDFA767D2F24})


Step 13: DataTransfer.log


Added (source=.sms_dcm?Id&DocumentId=ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a/2/PROPERTIES&Hash=A62E05FBEAD2B422C893EAFDA1FE6DE3C8A7B6F2155A7548B4F58204BB0003BC&Compression=zlib,dest={7F74E4AA-F23B-40EC-A3FE-AC2DC6C4D5C7}_2.zip) pair from manifest.


DTSJob {6558E7A6-8503-455E-8B03-5AC9E650DEF0} successfully completed download.


Step 14: CIDownloader.log



CCIDigestStore::CheckCIExists - Digest missing. CI does not exist.


CCIDownloadItem::AddToManifest - Starting download of CI content document with DocumentName urn:policy-platform:policy.microsoft.com:smlif:ms.dcm.Site_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717.SUM_194bd67e-5a32-4ae0-b71c-bf936fdf734c:200:VL, DocumentVersion 200 (VL) CIDownloader 26/04/2016 07:33:55 3692 (0x0E6C)


Digests are stored in C:\Windows\CCM\CIDownloader\DigestStore

Step 15: CIAgent.log:


CIAgentJob({82483D8D-FE28-413A-B166-1610D79A4B84}): StartEnactment - CI - ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/RequiredApplication_6e4c5a44-5b99-46ed-92b1-5d195a3d1108 CIAgent 26/04/2016 07:34:55 5068 (0x13CC)

CIAgentJob({82483D8D-FE28-413A-B166-1610D79A4B84}): StartEnactment - Attempting to invoke Policy Platform Client CIAgent 26/04/2016 07:34:55 5068 (0x13CC)


Step 16: AppDiscovery.log



Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a" AND Revision = 2)" AppDiscovery 26/04/2016 07:34:55 1524 (0x05F4)

Performing detection of app deployment type Mozilla Firefox 17.0.1 (x86 en-US) - Windows Installer (*.msi file)(ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a, revision 2) for system. AppDiscovery 26/04/2016 07:34:55 1524 (0x05F4)


+++ Application not discovered. [AppDT Id: ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a, Revision: 2] AppDiscovery 26/04/2016 07:34:56 1524 (0x05F4)


+++ Did not detect app deployment type Mozilla Firefox 17.0.1 (x86 en-US) - Windows Installer (*.msi file)(ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a, revision 2) for system. AppDiscovery 26/04/2016 07:34:56 1524 (0x05F4)

Step 17: CIAgent.log


The Lantern jobs succeeded and reports obtained. Actually this lantern job started from step 7



DCM::LanternUtils::ScopeAndBindPolicies - [ScopedPolicies] ScopeId_C1C68F21_3BA1_4AE3_93E3_974C0FBEB717_DeploymentType_1b345708_f58f_44ac_a256_26da0531ed1a_2_Requirements_PolicyDocument CIAgent 26/04/2016 07:34:55 5068 (0x13CC)


Lantern job:E29879ED-34BA-464C-B4B9-2806024FD3C0 succeeded. CIAgent 26/04/2016 07:34:56 5068 (0x13CC)
CIAgentJob({82483D8D-FE28-413A-B166-1610D79A4B84}): QueueDebug - Executing Event. CIAgent 26/04/2016 07:34:56 5068 (0x13CC)
CIAgentJob({82483D8D-FE28-413A-B166-1610D79A4B84}): Invocation succeeded for policy platform job E29879ED-34BA-464C-B4B9-2806024FD3C0 CIAgent 26/04/2016 07:34:56 5068 (0x13CC)

CIAgentJob({82483D8D-FE28-413A-B166-1610D79A4B84}): ReportMethodInvocation :: Enactment succeeded CIAgent 26/04/2016 07:34:56 5068 (0x13CC)
CIAgentJob({82483D8D-FE28-413A-B166-1610D79A4B84}): ReportMethodInvocation :: Obtained lantern reports CIAgent 26/04/2016 07:34:56 5068 (0x13CC)

Step 18: AppIntentEval.log

Evaluating and checking for Dependencies

* Evaluating Application policies for Machine AppIntentEval 26/04/2016 07:34:56 5068 (0x13CC)


DT id = ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/RequiredApplication_6e4c5a44-5b99-46ed-92b1-5d195a3d1108/2, technology = MSI AppIntentEval 26/04/2016 07:34:56 5068 (0x13CC)

ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, ConfigureState = NotNeeded, Title = Mozilla Firefox 17.0.1 (x86 en-US) - Windows Installer (*.msi file) AppIntentEval 26/04/2016 07:34:56 5068 (0x13CC)

ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/Application_6e4c5a44-5b99-46ed-92b1-5d195a3d1108/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, ConfigureState = NotNeeded, Title = Mozilla Firefox 17.0.1 (x86 en-US) AppIntentEval 26/04/2016 07:34:56 5068 (0x13CC)

ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/RequiredApplication_6e4c5a44-5b99-46ed-92b1-5d195a3d1108/2 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, ConfigureState = NotNeeded, Title = ApplicationIntentPolicy AppIntentEval 26/04/2016 07:34:56 5068 (0x13CC)

No dependencies for DeploymentType ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a/2. AppIntentEval 26/04/2016 07:39:50 4696 (0x1258)

Step 19: DCMReporting.log

CDCMReporting::ProcessCIReports DCMReporting 26/04/2016 07:34:56 5068 (0x13CC)

CDCMReporting::GenerateXMLReports DCMReporting 26/04/2016 07:34:56 5068 (0x13CC)


Skipping many unwanted entries and logs.....

Step 20: CIAgent.Log:



CIAgentJob({82483D8D-FE28-413A-B166-1610D79A4B84}):State - Reporting (scan):: Install Policy Type - ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/RequiredApplication_6e4c5a44-5b99-46ed-92b1-5d195a3d1108:2 - State = NonCompliant ResolvedState = Compliant Applicability = Applicable ConfigureState= NotNeeded


Step 21: CITaskmgr.log


Initiating task ContentDownload for CI ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a.2 (Mozilla Firefox 17.0.1 (x86 en-US) - Windows Installer (*.msi file)) for target: , consumer: {482B8DB8-69BA-427C-B585-EDB72104CDE5} CITaskMgr 26/04/2016 07:34:56 3944 (0x0F68)

Step 23: CAS.log


Submitted CTM job {0C468474-92A1-4CD7-94C3-CF4D6260A375} to download Content Content_99518703-fa76-43c4-9e87-6db0039d99eb.1 under context System ContentAccess 26/04/2016 07:34:57 3944 (0x0F68)

Successfully created download request {2D609AC3-21F7-40B3-9FAA-20D56B4D634F} for content Content_99518703-fa76-43c4-9e87-6db0039d99eb.1 ContentAccess 26/04/2016 07:34:57 3944 (0x0F68)


Here on, check locationservices, dataservices and contenttransfer.log to verify the content download Process

Step 24: CIStatestore.log

Once the CI Enforce state for content download succeeded, the Application is enforced

[ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/RequiredApplication_6e4c5a44-5b99-46ed-92b1-5d195a3d1108:2] CIEnforceState changed: DownloadContentSuccess --> Enforcing

Step 25: Appenforce.log


Detecting the App deployment type and starting to install


Performing detection of app deployment type Mozilla Firefox 17.0.1 (x86 en-US) - Windows Installer (*.msi file)(ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a, revision 2) for system. AppEnforce 26/04/2016 07:38:56 4936 (0x1348)

+++ Application not discovered. [AppDT Id: ScopeId_C1C68F21-3BA1-4AE3-93E3-974C0FBEB717/DeploymentType_1b345708-f58f-44ac-a256-26da0531ed1a, Revision: 2] AppEnforce 26/04/2016 07:38:56 4936 (0x1348)

App enforcement environment:
Context: Machine
Command line: msiexec /i "mozilla-firefox(17.0.1).msi" /q
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 2
Content path: C:\Windows\ccmcache\e
Working directory: AppEnforce 26/04/2016 07:38:56 4936 (0x1348)
Prepared working directory: C:\Windows\ccmcache\e AppEnforce 26/04/2016 07:38:56 4936 (0x1348)
Exit code 0

Successfully Installed Application.


SQL Server Reporting service

In Configuration Manager , the reporting service point communicates with SSRS(SQL Server Reporting Service)to copy the SCCM reports to a specified folder. Reporting service role plays a major role in configuration Manager 2012 for pulling organised information about inventory, application deployment, patching and  software mettering data.  Configuration Manager provides report definitions for over 450 reports in over 50 report folders, which are copied to the root report folder in SQL Server Reporting Services during the reporting services point installation process. The reports are displayed in the Configuration Manager console and organized in subfolders based on the report category.
Before proceeding with the configuration,
1. Make sure SQL Server Reporting service installed
2. Make sure the connectivity of Reporting Services with site database.
SQL Server Reporting service installation
To verify the SQL server reporting service installation in  windows server 2008, click Start ->click All Programs-->click Microsoft SQL Server 2008 R2-->click Configuration Tools --> click Reporting Services Configuration Manager.
To verify the SQL server reporting service installation in  windows server 2012, Just serach for Reporting Services Configuration Manager in Search column.
If  Reporting Services Configuration Manager is not found run the SQL setup and proceed with installation of Reporting services Configuration Manager. Else, open the Reporting service configuration manager and start working with the connectivity verification.
Make sure the connectivity of Reporting Services with site database
Click, Reporting services Configuration Manager
Provide SQL server name and instance name to connect.

Once you connected, Make sure the Report server mode is Native and and reporting service is up and running , else start the reporting service.

Make sure the database Name and service account that connects the Database .

Specify the virtual Directory  and configure a URL to access the Report server . If you have created any SSL certificate for authentication, mention it in SSL certificate column , else proceed with default.
Configure a URL to acess report Manager , So that You can use this URL in future to add folders or to create custom SQL reports by accessing Report Manager .

Once the verification and configuration from SQL Server Reporting service done, proceed with the installation of Reporting Service point configuration Manager role.

Installation of Reporting Service Point
 
To manage report reporting site role must be installed. The reporting services point copies report folders and reports to SQL Server Reporting Services and it applies the security policy for the reports and folders, and sets the configuration settings in Reporting Services.The reporting services point is a site system role that must be configured on a server with Microsoft SQL Server Reporting Services installed and running .
Installation of Reporting Service Point
  1. Run SCCM site role installation Wizard
  2. Skip the Proxy tab, if you don’t have proxy environment
  3. Select the Reporting Services point role to install


Mention the site database server and database name, run the verification wizard and check for successful verification.
Specify the folder to create on the site system server reports that will contain the SCCM 2012 reports.
Select reporting server instance name, if the instance name is not available, then the SQL server reporting service is not running/installed.
Specify the user name that have read access to configuration manager database.

Click Next

After the successful installation wizard , verify the site server logs
Related logs found under \\SCCMServer\CCM\ Logs
srsrpMSI.log
srsrpsetup.log  

srsrpsetup.log  
Check for the below successful log entry
Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\srsrp.msi SRSRPINSTALLDIR="C:\Program Files\SMS_SRSRP" SRSRPLANGPACKFLAGS=0
srsrp.msi exited with return code: 0 ,Installation was successful.
srsrpMSI.log
Check for below log entry in srsrpMSI.log
Windows Installer reconfigured the product. Product Name: ConfigMgr Reporting Services Point. Product Version: 5.00.7804.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
After the successful installation , verify the reporting tab in configuration Manager console. The report manager and report server url can be seen .click on the Report Manager link and make sure the folders you have created is found and it has all the inbuilt SCCM reports found in consle.

Click the folder and view the report .
Thanks Guys!! I will continue with creation of custom report in next post.


Translate

Total Pageviews

Blog Archive

Followers

Linkedin

Popular Posts