Friday 14 November 2014

Deployment Monitoring Tool in SCCM 2012 Toolkit

Deployment Monitoring Tool in SCCM 2012 Toolkit


Deployment Monitor Tool (DeploymentMonitoringTool.exe) is new addition to SCCM  2012 Toolkit. This Tool is a graphical user interface designed to assist in troubleshooting applications, updates and baseline deployments.







 The use of this tools comes with below features.
1.        Actions
2.        Client Properties
3.        Deployments
4.        All Updates






Deployment Monitoring Tool MUST be run as administrator.

Through actions menu you can perform the following task
(a) Connect to A remote Computer, 
(b) Import and Export XML files of a system for further troubleshooting
 (c) Review the log files depending upon which TAB are selected. For Example if it is  Application and Baseline Deployments Tab –> PolicyAgent.log:, Update Deployments –> updatesDeployment.log and All Updates Tab –> WindowsUpdate.log:


Ø  Client Properties
Client Properties tab will help us to get all the client details. The following information is very helpful at the time of troubleshooting. Client Logs Directory, ccmexec service Status,  Service Window (maintenance window) status, Proxy MP, Resident MP details, WSUS Locations, Update Sources, Last Policy refresh Cycle,Assigned MP, Site Code, Client Approved status and certificate information.



Ø  Deployments
Deployments tab will help us to list down the details of each targeted deployments.
 This will provide us more details of the deployments like Name, Deadline, State,Type and ID.
For example, in the following pic, you can see the deployed application is OPTIONAL, state of deployment is APP_CI_ASSIGNMENT_EVALUATION, Deployment ID and Deployment Type is Application. However, if you look at other two deployments, you can see that one is Software Update and other one is mandatory application deployment with a deadline.
We will get in depth characteristics of selected deployment in the bottom of the tool.


 Information which can be fetched are as under. These details are very very helpful at the time of troubleshooting.

1.        AssignmentAction,
2.        DisableMomAlerts,NotifyUser,
3.        SuppressReboot,
4.        OverrideServiceWindows,
5.        RaiseMomAlertOnFailure,
6.        StartTime, StartTime,
7.        Target,
8.        RebootOutsideOfServiceWindows,
9.        UserUIExperience, 
10.     DeploymentType,


We can retrive in-depth details about selected deployment at the bottom (each and every details that you’ve specified at the time of creation of new application). For example – Properties (as mentioned above), Policy, Evaluation, Content, Enforcement, Reporting and Requirement Violations.


Ø  All Updates
All updates tab will provide the details about all the required updates along with their status.
Article ID, Bulletin, Status, Title, Unique ID, Scan Time, Source Version and Source Unique ID





Thursday 6 November 2014

Managing workgroup clients in SCCM 2012

Managing workgroup clients in SCCM 2012
The Server Locator Point is no more a separate site system role in SCCM 2012. It's functionality is merged into the Management Point.
To install CM12 client on workgroup machines: 
  1. Make sure that the Management Point is published on DNS or WINS
  1. Make sure Management Point FQDN can be resolved from the client machine
  1. For the client installation on Workgroup machines use the CCMSetup.exe  with local Administrator previledge
CCMSetup.exe and its supporting files are located on the System Center 2012 Configuration Manager site server in the Client folder of the System Center 2012 Configuration Manager installation folder. This folder is shared to the network as <Site Server Name>\SMS_<Site Code>\Client.

At the command prompt, the CCMSetup.exe command uses the following format:
CCMSetup.exe [Ccmsetup properties] [client.msi setup properties]

For example, CCMSetup.exe /mp:SMSMP01 /logon SMSSITECODE=S01 FSP=SMSFSP01 which performs the following actions:

Specifies the management point named SMSMP01 to request a list of distribution points to download the client installation source files.
Specifies that installation should stop if a version of the System Center 2012 Configuration Manager or Configuration Manager 2007 client already exists on the computer.
Instructs client.msi to assign the client to the site code S01.
Instructs client.msi to use the fallback status point named SMSFP01. 

    4. In a scenario where we haven't published Management Point to Active Directory but want to manage domain clients with SCCM 2012, you can use Client push installation method with additional properties for client.msi (make sure 
Management Point is published on DNS or WINS and Management Point FQDN can be resolved from the client machine)


           SMSSITECODE=XYZ SMSMP=SCCM2012.domain.com FSP=SMSFSP01 DNSSUFFIX=domain.com