Eswar Koneti's Blog

we see lot of file extensions from inbox folders while replicating information to Child sites .what really these files do and  what information do they carry ?

This post is basically talks about what  type of files generated during site-Site Replication. Sometimes I wonder that the file Type is when working with replication issues and see if it requires any attention.

It might help you in understanding about replications files types.

To know more about how Site-Site Replications works in SCCM 2007,Read http://blogs.technet.com/b/configurationmgr/archive/2011/08/29/site-to-site-data-replication-flow-in-sms-2003-and-configmgr-2007-explained.aspx

Also look at this post to know about SCCM Components that helps you in replication issues http://eskonr.com/2012/09/sccm-2007-components-threads-use-site-site-replication/

To know more about Site-to-site SCCM / Configmgr Package Replication http://blogs.msdn.com/b/steverac/archive/2010/07/16/understanding-site-to-site-communication-in-sms-sccm.aspx

Note : This content is taken from Configmgr2007 Site-site replication document from Technet blogs. To know more about Replication look at here http://blogs.technet.com/cfs-file.ashx/__key/CommunityServer-Components-PostAttachments/00-03-34-44-65/ConfigMgr2007Site2SiteReplication.doc

If you are in Large #SCCM / #Configmgr 2007 Environment with multiple site dispersed geographically and you try to distribute the packages to site .So what happens next ?

Do you keep looking at logs(sender.log) to troubleshoot whether my site is sending any data to child or not ? If so How long would you look at the log ?

Our Friend (Dan) has developed Simple application that would read in and construe the sender.log and display all the details in a nice readable format.

You would require to enter the Parent Site server name (to list all the packages which are sending) and Sitecode.

Let say You have Central(CEN) and Primary(P01—Child of CEN) and Secondary (S01—Child of P01) and you created package in Central site and distributed to P01 and S01 site.

You now need to track what is going on at S01 Site.For this provide detials about P01 site name and site code,it gives all information to which site the information is sending.

Here is snap from Andrew Blog How it looks like.

Download the Application from Here

Where should I Run this application ? To run this application,you must have access to SCCM and you can run this app from any member server or workstation(ensure you have good network speed from the machine to connected server as it connects to the server and read the sender.log).

For full Details about the Application,visit Dans Blog : http://www.danrichings.com/?p=90

For Any Questions /Feedback ,Please get in Touch with Dan at this Blog.

Thanks to Dan for developing such a nice application.

In my Recent post,I posted how to enable .net framework feature in windows 7 http://eskonr.com/2012/04/enable-net-framework-3-5-1-feature-in-windows-7/ but need to enable sub functions in it they are Windows communication foundation features.

If you try to add these two features in additions to .net framework using DISM,it doesn’t work and you will get error :50 in execmgr.log due to missing elements required for  HTTP Activation.

I tried enabling these features using command line manually with : Dism.exe /online /Enable-Feature /FeatureName:NetFx3 /FeatureName:WCF-HTTP-Activation /FeatureName:WCF-NonHTTP-Activation

It failed with error code 50 saying  The operation completed but WCF-HTTP-Activation feature was not enabled. Ensure that the following parent feature(s) are enabled first. If they are already enabled, refer to the log file for further diagnostics.
IIS-NetFxExtensibility, IIS-ApplicationDevelopment, IIS-WebServer, IIS-WebServer Role, IIS-RequestFiltering, IIS-Security, WAS-ProcessModel, WAS-WindowsActivationService, WAS-NetFxEnvironment, WAS-ConfigurationAPI

This needs other components to enable like IIS and Windows process activation etc.

Create a batch script with the following command and advertise onto collection.

Dism.exe /online /Enable-Feature /FeatureName:IIS-WebServerRole /FeatureName:IIS-WebServerRole /FeatureName:IIS-WebServer /FeatureName:IIS-ApplicationDevelopment /FeatureName:IIS-Security /FeatureName:IIS-RequestFiltering /FeatureName:IIS-NetFxExtensibility /FeatureName:WAS-WindowsActivationService /FeatureName:WAS-ProcessModel /FeatureName:WAS-NetFxEnvironment /FeatureName:WAS-ConfigurationAPI /FeatureName:NetFx3 /FeatureName:WCF-HTTP-Activation /FeatureName:WCF-NonHTTP-Activation

Hope it helps.

In ConfigMgr 2007, we now have several different types of packages, which can make it difficult to find a specific package which is referenced by a task sequence.  Here are a couple of tips to help resolve package references:

1. If you select your task sequence in the Admin UI and select the "References" tab on the preview pane you will get a list of all packages that the task sequence references (including the type and version fields which can be used to find them).
2. You can use the "Packages referenced by a specific task sequence" report to get the status of all packages referenced by a task sequence.  As a general rule, you should check this before you advertise the task sequence to ensure that all of the packages are properly replicated to accessible distribution points.

However, dynamic package references are not included in the list of references, so you will need to check the status of these packages manually before advertising the task sequence.  Dynamic package references which might be required by a task sequence include:

Packages / Programs that are installed using the "Install multiple applications" option.

1. Drivers in Driver Packages that are needed by the "Auto Apply Driver" task sequence step.
2. Software Updates in Software Update Deployment packages that are needed by the "Install Software Update" task sequence step.

Reference Via http://blogs.technet.com/b/inside_osd/archive/2008/02/08/tips-for-resolving-package-references.aspx

Enabling the .Net framework feature in windows 7 can be done using manually but if you want to do this on all clients ,how do you manage it ? Script Based using OCsetup ? or enabling this feature in Image ? or PowerShell script ?

I go with DISM (Deployment Image Servicing and Management)tool to enable this feature.

Download and install WAIK to get DISM tool http://www.microsoft.com/download/en/details.aspx?id=10333

Deployment Image Servicing and Management (DISM) is a command-line tool used to service Windows® images offline before deployment. You can use it to install, uninstall, configure, and update Windows features, packages, drivers, and international settings. Subsets of the DISM servicing commands are also available for servicing a running operating system

Create a folder with standard naming procedure and place DISM.EXE (for 64 Bit and 32 Bit) ,share folder would be better.

Go to sccm and create new package using the above source location as data Source

Create program with command line : Dism.exe /online /Enable-Feature /FeatureName:NetFx3

Get list of available features from windows 7 machine using DISM tool with command prompt : Dism /online /Get-Features (run the cmd prompt with admin account)

Create Advertisement and move it onto collection you needed.

You know what next to do with this …Monitoring the deployment status and fix the issues

There are cases where computer might needs to be deleted from SCCM Database when the OS up gradation happens(new name applied to host machines) and old name should be removed else it will automatically be removed as per the site maintenance settings.

Here is VB script that remove computer from SCCM Database based asking for machine name.

Note :I would love to test this on Lab before taking this to production.

You would be prompted for SCCM Site server name(where SQL server installed) and site code for the Site server.

ON ERROR RESUME NEXT

strServer=InputBox("Enter Site Server Nmae",,"win-cm2k7")

strSiteCode=InputBox("Enter Site Code",,"P01")

strComputer = InputBox("Enter Machine Name To Delete",,"System name")

Set locator = CreateObject( "WbemScripting.SWbemLocator" )

Set WbemServices1 = locator.ConnectServer( strServer,"root\SMS\site_" & strSiteCode
 
ResID = getResID(strComputer, WbemServices1)

If ResID = Empty Then

MsgBox "Unable To Determine The ResourceId For " & strComputer & " Exiting Application"

Wscript.Quit

Else 

MsgBox "The ResourceId For " & strComputer & " On " & strServer & " Is " & ResID

End If

 
Set sResource = WbemServices1.Get("SMS_R_System=’" & ResID & "’")

sResource.Delete_
 

If Err = 0 Then

MsgBox strComputer & " Has Been Removed From " & strSiteCode

Else

MsgBox "Unable To Locate " & strComputer & " On " & strServer

End If  

Set sResource = Nothing

Function GetResID(strComputer, oWbem)

strQry = "Select ResourceID from SMS_R_System where Name=" & "’" & strComputer & "’"

Set objEnumerator = oWbem.ExecQuery(strQry)

If Err <> 0 Then

GetResID = 0

Exit Function

End If

 
For Each objInstance in objEnumerator

For Each oProp in objInstance.Properties_

GetResID = oProp.Value

Next

Next

Set objEnumerator = Nothing

End Function

Via http://eskonr.com/trainings-webcasts/sccm-2007/

Configuration Manager SP1 and R2 Overview (Level 300) Level 300

Deploying and Upgrading to ConfigMgr (Part 1 of 2) Level 300

Deploying and Upgrading to ConfigMgr (Part 2 of 2) Level 300

Deploying Operating Systems with ConfigMgr (Part 1 of 2) Level 300 – With John Baker

Deploying Operating Systems with ConfigMgr (Part 2 of 2) Level 300 – With John Baker

Deploying Operating Systems with ConfigMgr (Part 1 of 2) Level 300 – With Keith Combs

Deploying Operating Systems with ConfigMgr (Part 2 of 2) Level 300 – With Keith Combs

Deploying Operating Systems with ConfigMgr 2007 Level 300 – With Ravi Kiran Chintalapudi

Deploying ConfigMgr 2007 Level 200

Deploying ConfigMgr 2007 Clients Level 300

Desired Configuration Management in ConfigMgr 2007 Level 300

Introduction to ConfigMgr 2007 Level 200

Lite Touch Installation Using Microsoft Deployment Toolkit Level 200

New License Options for ConfigMgr 2007 Level 100

New Tools to Streamline the Imaging and Deployment Process in Windows Server 2008 Level 300

Optimizing Desktop Management with ConfigMgr and Microsoft Soft Grid Application Virtualization Level 300

Overview of ConfigMgr 2007 Level 300

Software Distribution with ConfigMgr Level 300

Microsoft Deployment Toolkit – Zero Touch Screencast

SCUP – Installation Video

SCUP – Finding, Managing & Importing Catalogs

An Introduction to Microsoft Deployment Toolkit Tools (Level 200) Level 200

Software Update Management with ConfigMgr Level 300

ConfigMgr: The Datacenter Level 300

Zero Touch Installation Using Microsoft Deployment Toolkit and ConfigMgr 2007 Level 200

Via http://eskonr.com/trainings-webcasts/sccm-2007/

What’s coming in ConfigMgr

ConfigMgr – Prerequisites Before Installation

Using Configuration Manager 2007 to Perform Your Most Common and Critical Desktop Management Tasks

Installing SQL Server on a Server other than the ConfigMgr Primary

Installing SQL 2005 SP2 Local to the ConfigMgr Primary Server

In-Place Upgrade of SMS 2003 SP3 with the ITMU to ConfigMgr Mixed Mode

Configuring PKI and Installing ConfigMgr in Native Mode

How to Properly Upgrade from ConfigMgr Base to SP1

First Steps After ConfigMgr Installation

Deploying and Configuring a Secondary Site

How to Deploy the ConfigMgr Client to Target Machines

How to Remove the ConfigMgr Client

Deploying System Center Configuration Manager (SCCM) 2007

Deploying Windows 7 Operating System Images Using System Center Configuration Manager 2007

Determining Client Health in Configuration Manager 2007 R2

Generating Asset Intelligence Data with Configuration Manager 2007

Implementing Branch Distribution Points in System Center Configuration Manager (SCCM) 2007

Implementing Desired Configuration Management in System Center Configuration Manager (SCCM) 2007

Implementing Maintenance Windows for Software Distribution in System Center Configuration Manager (SCCM) 2007

Integrating Application Virtualization into Configuration Manager 2007 R2

Integrating SQL Server Reporting Services into Configuration Manager 2007 R2

Introduction to System Center Configuration Manager (SCCM) 2007

Managing Custom Application Updates using Systems Center Configuration Manager (SCCM) 2007

Managing Microsoft Updates with System Center Configuration Manager (SCCM) 2007

Upgrading SMS 2003 SP2 to System Center Configuration Manager (SCCM) 2007

Upgrading System Center Configuration Manager 2007 to Service Pack 1

Configuring Configuration Manager 2007 Security including PKI TechNet

When SCCM client is installed on computers and get assigned to site correctly,you will have schedule ID’s for each agent that runs on the client.  You can use the below codes to kick off different agents on the client. There are several scripts out there that will allow you to to do this. One of the most used is the SendSched.vbs file from the SMS 2003 Toolkit2. The toolkit can be downloaded from this link.

Hardware Inventory Collection Task {00000000-0000-0000-0000-000000000001}

Software Inventory Collection Task {00000000-0000-0000-0000-000000000002}

Heartbeat Discovery Cycle {00000000-0000-0000-0000-000000000003}

Software Inventory File Collection Task {00000000-0000-0000-0000-000000000010}

Request Machine Policy Assignments {00000000-0000-0000-0000-000000000021}

Evaluate Machine Policy Assignments {00000000-0000-0000-0000-000000000022}

Refresh Default MP Task {00000000-0000-0000-0000-000000000023}

Refresh Location Services Task {00000000-0000-0000-0000-000000000024}

Location Services Cleanup Task {00000000-0000-0000-0000-000000000025}

Software Metering Report Cycle {00000000-0000-0000-0000-000000000031}

Source Update Manage Update Cycle {00000000-0000-0000-0000-000000000032}

Policy Agent Cleanup Cycle {00000000-0000-0000-0000-000000000040}

Request Machine Policy Assignments {00000000-0000-0000-0000-000000000042}

Certificate Maintenance Cycle {00000000-0000-0000-0000-000000000051}

Peer Distribution Point Status Task {00000000-0000-0000-0000-000000000061}

Peer Distribution Point Provisioning Status Task {00000000-0000-0000-0000-000000000062}

Compliance Interval Enforcement {00000000-0000-0000-0000-000000000071}

Software Updates Agent Assignment Evaluation Cycle {00000000-0000-0000-0000-000000000108}

Send Unsent State Messages {00000000-0000-0000-0000-000000000111}

State Message Manager Task {00000000-0000-0000-0000-000000000112}

Force Update Scan {00000000-0000-0000-0000-000000000113}

AMT Provision Cycle {00000000-0000-0000-0000-000000000120}

Hope it helps.

 Usually when applications are installed,they wont repot to site server with installed software and its details why because the value that should report to site server is not picked by sms agent by default and you should edit SMS_DEF.MOF file which you find it from your site server installed drive,inbox folder,clifiles,hinv .

Below is the group to make TRUE from FALSE to get the requirement information. You dont have to compile this mof file on clients as they get it by its next policy cycle.

Monitor the MOF Changes from site server logs (dataldr.log)

  SMS_Report     (FALSE),
  SMS_Group_Name (“Installed Software”),
  SMS_Namespace  (TRUE),
  SMS_Class_ID   (“MICROSOFT|INSTALLED_SOFTWARE|1.0″) ] as TRUE from ur SMS_DEF.MOF file

SELECT A.ARPDisplayName0, A.InstallDate0, A.InstalledLocation0, A.InstallSource0
FROM v_GS_INSTALLED_SOFTWARE A, v_GS_COMPUTER_SYSTEM B
WHERE A.ResourceID = B.ResourceID
AND B.Name0 = @computer
AND A.InstallDate0 >= DATEADD(day, -7, CURRENT_TIMESTAMP)
ORDER BY A.InstallDate0, A.ARPDisplayName0

Prompt for Computer:

select Name0 from v_GS_SYSTEM