This is Continuation to previous post package archival process.up on the query results,I would not delete the packages from console directly rather i delete them from its assigned Distribution points and move them to Archive folder and let be there for sometime until for sometime incase if it is required.

If you have large number of packages,you may find difficult in moving the packages by identifying where they reside (if you have subfolders).If you have less packages <10,you may use the report to know the root path of the package  and then right click on the package Move to archive folder by appending Retired to the existing package name to know package is retired.

If you have multiple packages,moving one by one is not easy thus you require something like script or tools.

Moving package using script may require to get the Source folder ContainerID number of  the packages(Folder of the package)  and Destination Folder ContainerID(Archival folder ID).

Here is the SQL query for the list of moving packages to know their Source Folder ContanerID.

From the package clean up report,if you get multiple packages,just place them in IN condition separated by comma (,).

I have packageID cen00004 which i need to move to archive folder with containerID=4 from SQL query below

select  B.ContainerNodeID,B.NAME,A.InstanceKey from dbo.FolderMembers a,.dbo.Folders b where
a.ContainerNodeID=b.ContainerNodeID and b.Name like ‘%archive%’

Replace the folder name if you have other one.

Now we have list of packages with their source ContainerNodeID(which is nothing  but the package FolderID).

Create a VB script with below syntax with input of all package IDs separated by commas with their source folder and destination folder.

Note : Please replace quotes (‘”) as they are replaced by fancy.

Option Explicit
‘On error resume next

Dim strSMSServer, strSMSSiteCode, strPackageIDs
Dim intSourceFolder, intDestFolder, intObjectType
Dim loc, objSMS
Dim objFolder
Dim arrPackageIDs
Dim retval

strSMSServer   = "SCCM server Name"
strSMSSiteCode = "SiteCode"
strPackageIDs  = inputbox("Please input packageIDs separated by commas","List of packages to be moved")

intSourceFolder =inputbox("Please input Source folder ContainerID number", "Source ContainerID")  ‘This ID is what you see in above SQL query to move all packages from the same folder test =1.
intDestFolder   =4 ‘Destination Folder for Archived packages :In this case,My archive package folder is 4.

intObjectType   = 2  ’2=Package for type of object .This scripts works only for standard software distribution packages.

Set loc         = CreateObject("WbemScripting.SWbemLocator")
Set objSMS      = loc.ConnectServer(strSMSServer, "root\SMS\site_" & strSMSSiteCode)

Set objFolder = objSMS.Get("SMS_ObjectContainerItem")
arrPackageIDs = Split(strPackageIDs, ",")

retval = objFolder.MoveMembers(arrPackageIDs, intSourceFolder , intDestFolder , intObjectType)
If Err.Number <> 0 Then
    msgbox Err.Description
End If

MSGBOX "Script is completed"

You may get multiple packages with different source Folders.So you will have to run the script to move bulk packages from each source folder to Destination at one go.

It is better than moving one by one package each time.

Hope it helps!

Problem : Someone has Created package/Package’s (bulk) and distributed to sites/DP’s and these packages are in large size(more than 1GB).

You get notification from network Team or other teams about bandwidth issues.You may have to identify what packages are in process of sending to DPs and should also check how much % leftover to take further actions.(Stop sending the packages now and initiate it later sometime during night). You can also Use Senderanalyzer http://eskonr.com/2012/09/troubleshooting-sccm-configmgr-packages/ tool but sometimes packageID will be blank.

There are couple of logs and inbox folders to verify this.

Lets look at logs file first and then go with inbox folders to stop the sending files.

From sender.log :

when you create packages and send to child sites,package will be decompressed into .PCK and send which you can see from sender.log something like below :

Attempt to write 1048576 bytes to \\inhydcmS01.eskonr.com\SMS_SITE\2000OKA1.PCK at position 285944832

Wrote 1048576 bytes to \\inhydcms01.com\SMS_SITE\2000OKA1.PCK at position 285944832

Where KA1(2000OKA1.PCK) is sitecode from which the file is being generated and sending.

  2000O(2000OKA1.PCK) is the random generated number.

with the help of PCK file name,we can find what is the package ID from schedule.log.

Open Schedule.log on the server and search with PCK file name (2000OKA1) .You get something like below :

Send Request 2000OKA1 JobID: 00000018   DestSite: HY1   FinalSite:      State:  Pending   Status:            Action:    None   Total size:   3259244k   Remaining:   3259244k   Heartbeat: 21:41   Start: 12:00   Finish:   12:00   Retry:         SWD PkgID: ESK00006   SWD Pkg Version:   1

With this ,you can take necessary action whether you want to stop sending the package or continue it.

If you want to terminate /stop the files which are being transferred /Queue ,you can simply delete the job from schedule.box and its corresponding send request files ( this is not recommended way of doing it).

More about Understanding Site to Site Communication in SMS/SCCM ,you can refer steve rachui’s blog http://blogs.msdn.com/b/steverac/archive/2010/07/16/understanding-site-to-site-communication-in-sms-sccm.aspx

If you have any issues with distribution of any packages to child sites or if you are in multi-tier hierarchy,You get face issues with packages not replicating to child sites due to several reasons and they will be retrying n (specific) number of times until they get right version of PCK file.

Preload is Our Friend to fix Package replication issues in better way. To know more about Preload Tool  and its usage http://blogs.technet.com/b/configurationmgr/archive/2009/05/07/configmgr-2007-the-preload-package-tool-preloadpkgonsite-exe-explained.aspx

How do you copy the PCK files ? Via Network Share ? sending them Via disk if you have large number of packages (this may happen when building new site) or different method ?

I use Robocopy oftenly if there are any Big Packages(more than 1GB or even less you can use) to copy even if there are any network breakage/Restart, it keeps retry.

Here is the syntax used to copy the PCK file.

robocopy sourcename Destination [Filename /Z

Ex: robocopy \\CM07\f$\smspkg  G:\smspkg\ Cen00C01.pck /z

/Z : copy files in restartable mode

To know more about Robocopy ,use Robocopy /?

Download Robocopy from here

Today I was looking at Packages to see how many packages are created without any distribution Points added. This might help you in identifying whether these packages are really needed to be in SCCM or

archive them. This below report will help you in achieving this.

select PackageID,Name,Version,SourceDate from v_Package where PackageID not in (select packageid from v_PackageStatusDistPointsSumm)

Note : Some packages might use just command line (script based) and they do not have any distribution Points . Double Verify them before you take any action)

Create New SCCM collection and paste the below query into it.

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 inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.Caption like "Microsoft Windows 7%" and SMS_G_System_COMPUTER_SYSTEM.SystemType = "x64-based PC"

Also need report :look at here http://myitforum.com/cs2/blogs/skissinger/archive/2009/06/23/32bit-vs-64bit-report.aspx

Computers that are running on virtual(Virtual PC or VMware etc) will have an entry in win32_computersystem with attribute model in WMI.

You can create a collection to using table called SMS_G_System_COMPUTER_SYSTEM.

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
inner join SMS_G_System_COMPUTER_SYSTEM on
SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId
where SMS_G_System_COMPUTER_SYSTEM.Model like "%Virtual%"

To list all physical computers ,create another collection using operator not in from above collection like below:

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.ResourceId not in (select SMS_R_SYSTEM.ResourceID from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.Model like "%Virtual%")

Hope it helps.

Wishing you all a merry time lighting up your Christmas Tree and A Happy New Year 2011.
Ciao you all in New Year 2011

The Microsoft Enterprise Desktop Virtualization v2 Beta Refresh is now available for download on the Microsoft Connect site. The updated software provides fixes to customer reported issues and new features including Workspace packager updates which add additional options for customizing the MED-V computer names.

NOTE:  The MED-V_HostAgent_setup.exe replaces the MED-V client install MSI and the MED-V_WorkspacePackager_setup.exe replaces the MED-V console install MSI.   This change simplifies the install and deployment of these components as they now detect install the correct architecture in a single install.  All of the command line options provided for the MSI’s in the previous installs are still supported for these installers.”

The Guest Agent MSI no longer has to be installed by the administrator on the Windows XP image. The Guest Agent is now installed automatically as part of first time setup. For more information see the MED-V Release Candidate Release Notes.

Please read the release notes for important information about upgrading and the rename of the MED-V Installers.

 Release Candidate Release Notes 

 https://connect.microsoft.com/medv/content/content.aspx?ContentID=23311

Download Release Candidate software  :

http://connect.microsoft.com/medv/Downloads/DownloadDetails.aspx?DownloadID=32936

If your boss ask to get list of laptops which are managed by SMS or SCCM.what do you do and how do you get that. Right click on computer and go to resource explorer to identify the computer is Laptop or Desktop ?

You can identify if the computer is Laptop or Desktop based on its chassis Types.

Below are listed the Chassis types available to create SCCM collection or reports.

For Laptops Chassis Types : 8 , 9, 10, 11, 12, 14, 18, 21

For Desktop Chassis Type : 3, 4, 5, 6, 7, 15, 16

For server Chassis  Type: 23

Below is the collection to list all the computers which are laptops which fall in above Chassis type.

You can also replace the values with Desktop computers or servers also you can use joins to club these with AD groups for deploying the applications based on this.

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 inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes in ( "8", "9", "10", "11", "12", "14", "18", "21" )

Here are some sample reports/queries available which you can make use of it

http://myitforum.com/cs2/blogs/snorman/archive/2007/09/18/count-of-chassis-types-by-collection.aspx

How to Identify the computers which has What version of BITS(Background intelligence Transfer service) installed onto it.

Background Intelligent Transfer Service (BITS) transfers files (downloads or uploads) between a client and server and provides progress information related to the transfers. You can also download files from a peer and it is Needed in

• Asynchronously transfer files in the foreground or background.
• Preserve the responsiveness of other network applications.
• Automatically resume file transfers after network disconnects and computer restarts.

To determine the version of BITS on the client computer,check the version of QMgr.dll. To find the version number of the DLL:

• Locate QMgr.dll in %windir%\System32.
• Right-click QMgr.dll and click Properties.
• Click the Version tab.

The following table lists the versions of BITS and their corresponding QMgr.dll file version numbers.

To get these details by SCCM client into Database for creation of collection or reports ,first you will have to do some changes to site settings for Software inventory Client Agent.

From site management—>client Agent—>software inventory client Agent Properties—>GO to Inventory collection Tab and click on start Burst to specify the File name which gives the File version for BITS.

Provide the name of the file as Qmgr.dll  and click on set for providing the location path where to search this file from.

click on Variable or Path and Type %windir%\System32 and unselect Subdirectories(you don’t want to search all the subdirectories for this file really). Clck ok and Uncheck Exclude Files in Windows Directory since we are looking for File which is from Windows Directory which should be included. click Ok to finish the configuration.

On the next policy interval,client should start receiving the new changes which you made for this agent and start collecting the DLL file details and sent to Site server.

Below is the collection Query to determine the BITS versions on the target computer.

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 inner join SMS_G_System_SoftwareFile on
SMS_G_System_SoftwareFile.ResourceId = SMS_R_System.ResourceId where
SMS_G_System_SoftwareFile.FileName = "qmgr.dll" and SMS_G_System_SoftwareFile.FileVersion > "7.%"