Packages referenced by a specific task sequence that are Missing

So you have many task sequences but when you setup a DP you need to know if that DP is ready for that Task sequence. There are reports for Packages on a DP, Packages for a Task Sequence but here is a report that will tell you what packages are missing from the DP for the specific task sequence.

The current draw back is that this report doesn't check to makes sure the package is already installed, just deployed so I will update that soon. But here you go. Hope this helps with some deployments.



---------------------
TaskSequenceID = Task Sequence ID
ID = Distribution point ID

-----------------------------------------
SELECT ps.Name AS Name
, ps.SourceVersion
, ps.SourceDate
, ps.SourceSize
, ps.SourceCompressedSize
, ps.PackageID
FROM
(
SELECT DISTINCT v_TaskSequenceReferencesInfo.ReferencePackageID AS PackageID
FROM v_TaskSequenceReferencesInfo
WHERE v_TaskSequenceReferencesInfo.PackageID=@TaskSequenceID
) RefPkgs
JOIN v_PackageStatusRootSummarizer ps ON ps.PackageID = RefPkgs.PackageID
where RefPkgs.PackageID not in (SELECT v_Package.PackageID
FROM v_Package
INNER JOIN v_DistributionPoint ON v_Package.PackageID = v_DistributionPoint.PackageID
WHERE v_DistributionPoint.ServerNALPath LIKE '%' + @ID + '%')
ORDER BY ps.Name

Auto Discovery via Script

Ever wanted clients to auto-assign but you didn't know how to do it.
Well there are several ways to do this. You could create an export of all the boundarys, so with a script so the client can determine where it needs to be. Otherwise you can do this:

----------- Reassign.vbs -------------------
Set smsclient = CreateObject("Microsoft.SMS.Client")
smsClient.ReAssignSite
------------------------------------------------------------

Example:
Multi-Tier hiearchy. Imaging done at the central site. Computer is assigned during imaging to the Central Site.
At the end of the process run the script and it should auto discovery it's site code based on the boundaries. Obviously if the client stays at the Central site then you have a boundary or other problem that needs to be addressed.

Here is a link to my website that I made several years back. I it is one the slipped my mind until recently.Site Code Assignment

Forefront Endpoint Protection Update 1 Updates tool

Have you been using Forefront Endpoint protection 2010. Hopefully you have found the time to update to the lastest release, Update 1.

What is critical to this update is the new update tool that allows you to really automate the download and push to the DPs. Before you had to do this manually, created a script or use another 3rd party script.


http://www.microsoft.com/download/en/details.aspx?id=26613

This tool should be copied to your Bin folder on machine performing the updates or referenced on the command line to run the program.

If you choose to create your own Deployment Management name and package name then you need to follow the switches for the application

SoftwareUpdateAutomation.exe” /AssignmentName FEP2010SignatureUpdates /PackageName FEP2010Signature

If you choose to use the defaults provided by the program then you simply need to run the .exe and sit back and watch. In the programsData folder there should be a log file name softwareupdateautomation.log. In here you can watch the program check the Deployment Management / Package and then download the files and update the DPs as necessary.

I recommend that you check your Deployment settings and set the program to use Binary Replication so you don't push all the files over and over again.