Compare and query creation handy tool

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 

Read More

Configuration Manager 2012 client Architecture Data Flow

Configuration Manager 2012 client Architecture Data Flow

Configuration Manager client Architecture for Deadline Data flow

Configuration Manager client Architecture for Activation Data Flow

Read More

Application Deployment Troubleshooting in Depth

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.

Read More

Installing and Configuring SCCM 2012 SP2 Reporting Service Point

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.

Read More

Setting up Maintenance Window in SCCM 2012

Maintenance windows is nothing but a time frame set by administrative users to carry out the operational activities related to configuration Manager on members of a device collection. The reason for setting up maintenance window is to avoid the delay in productivity of the organization due to configuration manager operational task such as installing updates, application, packages, rebooting machines etc.

Maintenance windows are configured for a collection with a start and end date with accurate timing. It is also possible to set a recurrence pattern. Each maintenance window must have duration of less than 24 hours. By default, Machine reboot caused by a deployment are not allowed outside of a maintenance window, but you can override the default in the settings for each deployment. You can also set the deployment to run in maintenance window but the download action to run outside of the maintenance window.

The following Configuration Manager operations support maintenance windows:

• Software deployments
• Software update deployments
• Compliance settings deployment and evaluation
• Operating system deployments
• Task sequence deployments

If we set two maintenance windows and if both the time overlaps, then configuration Manager will assume it as single window encompassing the time period covered by both maintenance windows.

How to set up maintenance window?

Create a collection, for the group of machine you are intended to create specific maintenance window time frame.

Once collection Created, right click the collection > Properties

In maintenance window tab, click the yellow label as highlighted in below figure.

Mention the name, date, time frame and apply this schedule as per your needs like Deployment, Task sequence, software updates etc.

Hope this Helps!! Thanks for reading. If you have any questions, please post it below.

Read More

Discovery Process in Configuration Manager 2012 SP2

Discovery Process in Configuration Manager

Hope you have seen my previous post on Installing configuration Manager 2012 console. So after installing configuration manager, it’s recommended to discover Active directory resource. The Computer and user resource that are planned to manage through Configuration manager is discovered using Configuration Manager 2012 Discovery method. Once the discovery is run, a discovery data record (DDR) for each discovered object are created and stored in the Configuration Manager database. Once discovery successful, it puts information about the resource in a file that is referred to as a discovery data record (DDR). DDRs are in turn processed by site servers and entered into the Configuration Manager database, where they are then replicated by database-replication with all sites. Active Directory Forest Discovery is a new discovery method that can discover subnets and Active Directory sites, and can add them as boundaries for your hierarchy.

There are six different discovery methods available to discover Active directory resource.

Active Directory Forest Discovery 

This discovery method is used to discover Active Directory sites and subnets, and then create Configuration Manager Boundaries for each site and subnet from the forests that you have configured for discovery. When Active Directory Forest Discovery identifies a supernet that is assigned to an Active Directory site, Configuration Manager converts the supernet into an IP address range boundary.. 

Active Directory System Discovery 

This discovery method is used to discover system from the specified locations in Active Directory Domain Services. Active Directory System Discovery Account or the computer account of the site server is used to run this discovery

Active Directory User Discovery

This discovery Discovers user accounts from the specified locations in Active Directory Domain Services. Active Directory System Discovery Account or the computer account of the site server is used to run this discovery 

Active Directory Group Discovery

This discovery Discovers local, global, and universal security groups, the membership within these groups, and the membership within distribution groups from the specified locations in Active directory Domain Services. Distribution groups are not discovered as group resources. Active Directory System Discovery Account or the computer account of the site server is used to run this discovery

Heartbeat Discovery

Used by active Configuration Manager Clients to update their discovery records in the database. This discovery is enabled by default. Computer account of the agent is used to run this discovery. Heartbeat Discovery can force discovery of a computer as a new resource record, or can repopulate the database record of a computer that was deleted from the database. 

Network Discovery 

This discovery Searches your network infrastructure for network devices that have an IP address. This can discover devices that might not be found by other discovery methods. This includes printers, routers, and bridges.

How to Run Discovery?

Once you installed the Configuration Manager console,

Administration > Hierarchy Configuration > Discovery methods

Select Each Discovery and enable the status. For example,

Right click Active Directory Forest Discovery > properties

You will be seeing screenshot like below, check the option Enable Active directory forest and apply to run AS soon as possible.

Active Directory Group Discovery

Right click Active Directory Group Discovery > properties

You will be seeing screenshot like below, check the option Enable Active directory group discovery and select the specific group that you want to discover. 

Specify the Name of the group to be discovered and browse the respective Active directory group you are interested to discover.

Similar to Group discovery, you can perform user Discovery by enabling and selecting Active directory User Discovery in configuration Manager 2012 Sp2.

Active Directory System Discovery

Right click Active Directory OU Discovery > properties

You will be seeing screenshot like below, check the option Enable Active directory System discovery and select the specific container that you want to discover. 

Once you selected the container, clicks apply and run the discovery immediately.

Logs to very Discover status

ADforestDisc.log – The log file that logs information about forest discovery

adsgdis.log - The log file that logs information about group discovery

adsysdis.log - The log file that logs information about system discovery

adusrdis.log - The log file that logs information about user discovery

These site server Logs available in site server from where you are performing discovery, and the path should be %Program Files%\Microsoft Configuration Manager\Logs.

Read More

Step By Step SCCM 2012 Installation - Installation of Endpoint Protection

Home

The main intension to built System Center 2012 Endpoint Protection on Configuration Manager is to create a single infrastructure for deploying and managing endpoint protection. In previous version (SCCM 2007)System center Endpoint protection was not associated with sytem center configuration manager product. Some of the features that we achived by associating SCEP with configuration manager are mentioned below

1. Central administration for deploying and configuring the Endpoint Protection client.
2. Default antimalware policies can be deployed to groups of computers.
3. Security roles for managing antimalware polices can be managed/controlled
4. Security settings like Windows Firewall changes can be deployed to group of computers
5. Scan and status reports can be genrated easily by configuration manager
6. The endpoint protection client can be updated by monthly patch cycle using SCCM endpoint definition updates
7. Security roles for managing antimalware polices can be managed/controlled
8. Notification can be set via configuration manager for malware compliance computers
9. Scan and status reports can be genrated easily by configuration manager

How to setup and deploy System center Endpoint Protection?

The SCCM 2012 site role responsible for setting up Endpoint protection feature is Endpoint Protection Point . This role should be installed and configured in Central administration site or standalone primary site . In addition to this, Software update point should be configured to deliver definition updates if you want to use Configuration Manager Software updates to deliver definition and engine updates. With this entire prerequisite create client antimalware policy to manage Endpoint protection settings.

Deploying system center Endpoint protection has few steps as mentioned below

1. Install Endpoint Protection point SCCM site role

2. Create custom client policy for Endpoint protection

3. Create custom antimalware client policy

4. Sync the Software update to deliver updates

Read More

Step By Step SCCM 2012 Installation - Part 1: Installation of Endpoint Protection Point configuration Manager Site role

Installation of Endpoint Protection Point configuration Manager Site role

Select Add new site role

Mention the server Name, where you want to install EP role, this should be installed in standalone primary site or Central administration site.

Ignore this check box and hit Next , if you are not synchronising information from the internet .

Select The role , Endpoint Protection Point

Click OK,

Accept the license

Select Baisc Membership (it will send low level information to microsoft if found any errors)

Click Next and Finish.

We are done with Endpoint protection point role installation.

EPsetup.log – Log to verify the Endpoint protection setup installation. If installation succeeds ,you should be able to see log entry like “lnstallation was successful”

Thank you guys! Let me continue Part 2 and in my Next Post Creation of new Custom device  and antimalware settings for Endpoint Protection.

For Part 2 of the process click here

Read More

Step By Step SCCM 2012 Installation - Part 2: Creation of new custom device settings for Endpoint Protection

Home

Hi Guys, Hope you have gone through the part 1, Installation of Endpoint Protection Point configuration Manager Site role. 

Right click Client setting > Create new custom device settings

Select Endpoint Protection and click ok

Now ,open the properties of newly created client setting.

Select Endpoint protection tab and customise as below .

Click OK

we successfully created new client setting for Endpoint protection.

Now Deploy the newly created client setting to the collection ,where we are going to push system center endpoint protection .

Once you deployed , you should be able to see System center endpoint protection in client machine part of the deployed collection .

Of Part 3 of the process click here

Read More