In previous post,we saw how to get list of referenced task sequence packages used in Task Sequence which are incomplete.

In this report,we see how to get list of Distribution Points who do not have these referenced packages used in Task Sequence so you know all these sites which do not have package may fail during the OSD Policy check.

Count  : Distribution Points who do not have these packages used in Task Sequence

select sitecode,COUNT(distinct packageID) as [Not Distributed] from v_PackageStatusDetailSumm PSD
where PSD.Targeted=’0′ and PSd.PackageID in (select ReferencePackageID from v_TaskSequenceReferencesInfo
where PackageID =@TS1)
group by psd.SiteCode
order by psd.sitecode

what Task Sequence Reference packages missing from Which DP :

select PSD.PackageID,PSD.Name,psd.SiteCode,PSD.SiteName,PSD.SummaryDate  from v_PackageStatusDetailSumm PSD
where PSD.Targeted=’0′ and PSd.PackageID in (select ReferencePackageID from v_TaskSequenceReferencesInfo
where PackageID =@TS1)
Group by PSD.PackageID,PSD.Name,psd.SiteCode,PSD.SiteName,PSD.SummaryDate
order by SiteCode

Prompt for TS1 :

select PackageID,Name from v_TaskSequencePackage

Fix it before you advertise any Task Sequence to Computers .

Another Interesting report which will help you to identify if there are any packages used in Task Sequence are not available on Distribution Points.

If the Reference packages used in Task Sequence not available on DP,your Task sequence will fail and then u come back to fix the issues so lets be proactive .

SCCM 2012 presents nice view with compliance level for the reference packages used in Task Sequence.

select
pkg.Name as [Package Name],
Case pkg.PackageType
When 0 Then ‘Software Distribution Package’
When 3 Then ‘Driver Package’
When 4 Then ‘Task Sequence Package’
When 5 Then ‘software Update Package’
When 6 Then ‘Device Settings Package’
When 7 Then ‘Virtual Package’
When 257 Then ‘Image Package’
When 258 Then ‘Boot Image Package’
When 259 Then ‘OS Install Package’
Else ‘ ‘
END AS ‘Package Type’,
pkg.PackageID,
SUBSTRING(dp.ServerNALPath, CHARINDEX(‘\\’, dp.ServerNALPath) + 2, CHARINDEX(‘”]’, dp.ServerNALPath) – CHARINDEX(‘\\’, dp.ServerNALPath) – 3 ) AS [Server Name],
dp.SiteCode,
dp.LastRefreshTime,
stat.SourceVersion,
stat.LastCopied,
stat.SummaryDate,
stat.InstallStatus,
case when dp.IsPeerDP=1 then ‘*’ else ” end as BranchDP
from v_Package pkg
join v_DistributionPoint dp on pkg.PackageID=dp.PackageID
join v_PackageStatusDistPointsSumm stat on dp.ServerNALPath=stat.ServerNALPath
                                             and dp.PackageID=stat.PackageID
where stat.State!=0 and pkg.PackageID in (select ReferencePackageID from v_TaskSequenceReferencesInfo
where PackageID =@TS1)

Prompt for TS:

select PackageID,Name from v_TaskSequencePackage

You can create n number of Prompts with above Query if you want to look for multiple task sequences.

Note: Please replace the quotes used in this report as they converted to Fancy by Blog.

Attached MOF file Status of Task sequence which you can import directly into SCCM

Thought of sharing nice post on Task sequence replication issue to child site by Frank Rojas.

Symptoms :

When creating a new Task Sequence or updating an existing Task Sequence on a parent primary site in System Center Configuration Manager 2007, the Task Sequence may not replicate down to child primary sites. Packages and other Task Sequences replicate to the child primary site without issue.

Examining the logs associated with site replication (despool.log, replmgr.log, sched.log, sender.log) on both the parent and child primary sites does not reveal any errors. However examining the distmgr.log on the child primary site reveals the following errors:

Processing incoming file <ConfigMgr_Install_Directory>\inboxes\distmgr.box\INCOMING\<Random>.PKG. SMS_DISTRIBUTION_MANAGER
Adding package <Task_Sequence_ID> to the active package array. SMS_DISTRIBUTION_MANAGER
Adding these contents to the package <Task_Sequence_ID> version <x>. SMS_DISTRIBUTION_MANAGER
Updated replicated package info for package <Task_Sequence_ID> SMS_DISTRIBUTION_MANAGER
Failed to insert SMS Program ID <y> because the referenced program <Software_Package_ID>-<Software_Program_Name> is not present in the PkgPrograms table. Will try later. SMS_DISTRIBUTION_MANAGER
Cannot update the package program for package <Task_Sequence_ID> in the package source, error = 40 SMS_DISTRIBUTION_MANAGER
Removing package <Task_Sequence_ID> from the active package array. SMS_DISTRIBUTION_MANAGER

Cause

This issue is caused by a software package specified in the Task Sequence not replicating down to the child primary site. Any other Task Sequence that also has the problematic software package will also not replicate to child primary sites. However any Task Sequence that does not have the problematic software package will replicate to child primary sites without issues.

The problematic software package will be contained in the distmgr.log in the following line:

Failed to insert SMS Program ID <y> because the referenced program <Software_Package_ID>-<Software_Program_Name> is not present in the PkgPrograms table. Will try later.

Use the package ID and package name to identify the problematic software package.

Please note that not replicating to the child primary site means that information about the software package has not been replicated to the child primary site. It does not mean that the software package has not been copied to the child primary site’s Distribution Point.

There could be several reasons why the software package has not replicated to the child primary site, but usually the cause is that the software package has a bad property in it such as invalid path to its source files.

Read Complete post on http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2012/06/29/a-system-center-configuration-manager-2007-task-sequence-does-not-replicate-to-a-child-site.aspx

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

After fixing SQL server Issue with the required patches , I have got installed configMgr 2012 RC2 on my lab after fixing the issue with SQL server 2008 R2 SP1 with CU4.

This Guide assumes that you have Domain Controller with DNS,DHCP(Optional) and Member server with server 2008 R2 Operating system.

Please go through the TechNet guide to more about configuration Manager 2012 http://technet.microsoft.com/en-us/library/gg682140.aspx
I will not go through the configuration of IIS,BITS etc which are needed as prerequisites for configmgr 2012 .for all these configurations,
please take a look at windows-noob.com for step by step http://www.windows-noob.com/forums/index.php?/topic/4045-sccm-2012-guides/
start the installation of SQL server 2008 R2 or SQL server 2008 on member server (which is ConfigMgr server) .

Supported versions of SQL Server 2008 for ConfigMgr 2012 RC2 are:

SQL Server 2008 SP2 Standard and Enterprise CU7
SQL Server 2008 R2 SP1 and CU4
SQL Server Express 2008 R2 and CU4
If you are running SQL 2008 SP2, install CU7 from http://support.microsoft.com/kb/2617148.
If you are running SQL Server 2008 R2 SP1, use CU4 from http://support.microsoft.com/kb/2633146.

You can use the command lines to install SQL server 2008 including SQL server 2008 R2 SP1 and cumulative update 4 from http://www.ronnipedersen.com/2012/01/installing-sql-server-2008-r2-for-configmgr-2012/ (The current supported configuration of SQL Server for System Center 2012 Configuration Manager, is Microsoft SQL Server 2008 R2 with Service Pack 1 and Cumulative Update 4.)

Once you are done with it ,start the installation of ConfigMgr 2012 RC2 from your downloaded media http://eskonr.com/2012/01/configmgr-2012-rc2-released/(http://care.dlservice.microsoft.com/dl/download/3/4/C/34C7656A-F89E-473C-8CE0-21DA5DB0717C/configmgr_2012_RC2_ENU_7703.exe)

The required prerequisites files are downloaded prior and placed in shared folder.

Download prerequisites files for ConfigMgr 2012 RC2 http://eskonr.com/2012/01/configuration-managerconfigmgr-2012-rc2-prerequisites-download/

Use Prereq Checker setup file before you start the installation of configuration manager 2012

K:\Kit\SCCM Kit\SCCM 2012\ConfigMgr_2012_RC2_ENU_7703\SMSSETUP\BIN\X64>prereqchk.exe /ADMINUI

After installing all the prereq files including IIS,BITS,Schema extension,RDC and dotnet 4.0 Full.

For administering and configuring configMgr 2012 ,please look Windows-noob.com

http://www.windows-noob.com/forums/index.php?/topic/4045-sccm-2012-guides/

Additional Resources

• Getting Started with System Center 2012 Configuration Manager
• Introduction to Software Updates in Configuration Manager
• Configuring Software Updates in Configuration Manager
• What’s New in Configuration Manager

Recently have a requirement to uninstall all old adobe versions and install the new on.Looking for something which can be done Via but i found the below method is simple that can remove all the older applications and instal the new one(which can be done Via TS by adding two TS actions one with removal of old adobe versions and other for installation of New adobe).

Thought of sharing with you here how to remove different versions of applications at one go. Thanks to john Marcum for providing me the command line.

Here is the simple script that checks if the application is in use or not ,if app is opened ,it will terminate and start the uninstallation .

On Error Resume Next

 Dim WshShell

Set objHOST = CreateObject(“WScript.Shell”)

 strComputer = “.”

Set objWMIService = GetObject(“winmgmts:” _

    & “{impersonationLevel=impersonate}!\\” & strComputer & “\root\cimv2″)

Set colProcessList = objWMIService.ExecQuery _

    (“Select * from Win32_Process Where Name = ‘acroRd32.exe’”)

For Each objProcess in colProcessList

    objProcess.Terminate()

    Exit For

Next

 Set WshShell= CreateObject(“Wscript.Shell”)

WshShell.Run “msiexec /x {AC76BA86-7AD7-1033-7B44-A94000000001} /qn /norestart”,0,true

WshShell.Run “msiexec /x {AC76BA86-7AD7-FFFF-7B44-AA0000000002} /qn /norestart”,0,true

WshShell.Run “msiexec /x {AC76BA86-7AD7-FFFF-7B45-AA0000000002} /qn /norestart”,0,true

If you have multiple versions with different product ID for removal,add all the product ID’s at the end of the above code you know what i mean.

are you looking for smsts.log file while running SCCM OSD Task sequence. smsts.log file will move on to different places when OS is deploying depending on the progress of the build and the architecture of the OS:.it cont sit in one place

Below lists the location of smsts.log while deploying the OS*:

–>Windows PE before HDD format: x:\windows\temp\smstslog\smsts.log

–>Windows PE after HDD format: x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

->After Windows OS deployed but before SCCM agent installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

–>Both Windows OS(x86) and SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.log

–>Both Windows OS(x64) and SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log

–>After Task Sequence has finished running: c:\windows\system32\ccm\logs\smsts.log

–>After Task Sequence has finished running (x64): c:\windows\sysWOW64\ccm\logs\smsts.log

Now you should be able to find the smsts.log file depends on the status of your task sequence .

check out this blog here how to get the smsts.log when the TS fails in WinPE mode by pressing F8 http://eskonr.com/2009/12/how-to-view-the-smsts-log-and-other-log-files-when-pe-boot-fails-in-running-the-task-sequence/

Also take a look at the other sccm log files catagory type avilable here on http://blogs.msdn.com/lxchen/archive/2009/04/03/a-list-of-sccm-log-files.aspx.

Though the original post is avilable in windows-noob , having utilised the original task seqeunce, there are slight modifications done to carryout this task which are simple to upgrade WinXP to win7.

To use the existing Task sequence in 64 Bit OS , you will have to create additional packages like USMT and Micrisoft runscanstate pacakges which are used to in exisitng TS.

1. Create a New package“USMT x64 Only” which will point to source directory c:\program files\WAIK\tools\USMT\amd64. Do not create any program for this. MAke it avialble on to DP.

2.Open notepad ,paste the below code and name it as like runscanstate-offlinewindirx64.bat

@set USMT_WORKING_DIR=%~2%\USMTbits\amd64

“%~2\USMTbits\amd64\scanstate.exe” “%~1″ /c /o /hardlink /efs:hardlink /nocompress /offlinewindir:c:\windows /v:5 /l:%~2\windows\TEMP\SMSTSLog\scanstate.log /progress:%~2\windows\TEMP\SMSTSLog\scanstateprogress.log /i:%~2\USMTbits\amd64\miguser.xml /i:%~2\USMTbits\amd64\migapp.xml

Now Create package called “runscanstate-offlinewindirx64″  with program command line “runscanstate-offlinewindirx64.bat” with default avilable options.Make it avialable to DP also.

It assumes that ,u have already created another USMT package which will point to USMT folder (x86,amd64) in c:\program files\WAIK\tools\USMT.

once the above packages are ready , you can import the avilable Task Sequence . Edit the TS to ensure the correct packages are referenced like USMTx64 only,USMT Both version( USMT folder) and scanstate package.

You will also need to make some command line changes in xcopy x64 usmt to usmtbits\amd64 step since i have used the default TS from noob and it tries to copy all the DP pakcages to usmtbits folder so i modified the commands like below as it works fine for me.

The command prompt which i use looks like xcopy %_SMSTSC01000D0%* %systemdrive%\USMTbits\amd64 /herciy Where C01000D0 is package ID of  USMT x64 only.

and another task xcopy runscanstate.bat to usmtbits command looks like xcopy %_SMSTSC0100047%* %systemdrive%\USMTbits /herciy where C0100047 is package ID of runscanstate-offlinewindirx64.

Rest of the process is same,you need to Advertise the above tasksequence to the respective collection and do a WINPE to carryout the task.

Task Sequence is given below with snap shot:

Just want to show you how you can enable Language bar at welcome screen in windows 7 at the left corner topside.

Log into your windows 7 computer 1) Go to control panel ,click on Region and Language shown below with screen shots.

Once you have done the all above changes ,Log off the computer. Next time,when you login ,you should be able to see Language bar on the left side top corner to select which Language.

This is quite simple to create a bootable ISO image to capture winXP or Win7.On the technician computer ,install WAIK tool Downlaod it from here .

1.On technician system launch ‘Windows PE Tools Command Prompt’ from ‘Microsoft Windows AIK’ on the Programs Menu. The entire CD build process is performed in this CMD window.

2.To begin building a Windows PE CD type: copype.cmd amd64 c:\winpe_x64

3.Now mount the Windows PE boot image as a folder on your machine so that it may be edited by typing the following: imagex /mountrw c:\Winpe_x64\winpe.wim 1 c:\Winpe_x64\mount

4.To copy servicing tools into the mounted PE image, type:
xcopy “C:\Program Files\Windows AIK\Tools\Servicing” c:\winpe_x64\mount\Windows /s

xcopy “C:\Program Files\Windows AIK\Tools\amd64″ c:\winpe_x64\mount\Windows /s /Y

5.To commit the changes made to Windows PE, type: imagex /unmount c:\winpe_x64\mount /commit

6.Copy the updated WIM to the ISO folder for creation:
copy c:\winpe_x64\winpe.wim c:\winpe_x64\ISO\sources\boot.wim /Y

7.Create your ISO image:
oscdimg -n -bc:\winpe_x64\etfsboot.com c:\winpe_x64\ISO c:\winpe_x64\winpe_x64.iso

Using your preferred CD creation software burn the disk image c:\winpe_x86\winpe_x86.iso to CD or CD-RW.