Shaun Cassells at MyITForum.com

SMS 2003 SP3 Review / Analysis (pre install) Part 1

I have been asked to a review of SP3 for SMS 2003.  Specific focus on AssetMetrix

I will be doing a run down on what I’ve discovered doing research on the web and through testing.

This is part 1 (the research)

Topics:

1. SMS 2003 SP3
2. Webcasts
3. What's New in SMS 2003 Service Pack 3
4. Upgrade Check list
5. AssetMetrix Help and Support Articles
6. MMS 2007
7. KB’s for SMS SP3
8. Hotfixes
9. Notes

SMS 2003 SP3: http://www.microsoft.com/technet/sms/2003/downloads/servicepacks/sp3.mspx

Webcast: Wally Meads webcast What's New in Systems Management Server 2003 SP3  (Level 200)

• http://myitforum.com/cs2/blogs/cstauffer/archive/2007/06/20/recorded-technet-webcast-what-s-new-in-systems-management-server-2003-sp3-level-200.aspx
• Thanks Chris Stauffer
• http://www.microsoft.com/events/EventDetails.aspx?CMTYSvcSource=MSCOMMedia&Params=%7eCMTYDataSvcParams%5e%7earg+Name%3d%22ID%22+Value%3d%221032341248%22%2f%5e%7earg+Name%3d%22ProviderID%22+Value%3d%22A6B43178-497C-4225-BA42-DF595171F04C%22%2f%5e%7earg+Name%3d%22lang%22+Value%3d%22en%22%2f%5e%7earg+Name%3d%22cr%22+Value%3d%22US%22%2f%5e%7esParams%5e%7e%2fsParams%5e%7e%2fCMTYDataSvcParams%5e
• On demand webcast

What's New in SMS 2003 Service Pack 3

http://www.microsoft.com/technet/prodtechnol/sms/sms2003/whatsnew/e6410303-095e-448c-9d34-3919153480ef.mspx?mfr=true

• Asset Intelligence
• This add on extension of SMS 2003 enhances the ability to track software licenses, upgrade readiness, and more
• Windows Vista support
• A description of the Windows Vista™ Editions supported by SMS 2003 SP3
• 64 bit processor support
• Information regarding the extension of 64 bit support
• Accurate file size inventory above 2GB
• File sizes greater than 2GB are now reported accurately
• Hotfixes incorporated into SMS 2003 Service Pack 3
• A list of hotfixes that have been included in the SP3 upgrade

Upgrade Check list : http://download.microsoft.com/download/d/a/a/daab93e2-a526-4100-a5d0-7bfe65776a24/SMS%202003%20SP3%20Upgrade%20Checklist.htm

AssetMetrix Help and Support Articles – (these seem to be pre SP3 integration)

• http://support.microsoft.com/ph/12531
• AssetMetrix 'Quick Start' and the Email-AssetAgent Reference guide is available at the Download Center
• AssetMetrix LAN, Disk and Linux-AssetAgent Reference guide is available at the Download Center
• AssetMetrix AssetAgent Advanced Features Reference guide is available at the Download Center
• AssetMetrix Asset Data Elements and Asset Management Reference guide is available at the Download Center
• AssetMetrix Using ServicePages on a PC Reference guide is available at the Download Center
• AssetMetrix Technical Overview and Troubleshooting Reference guide is available at the Download Center
• AssetMetrix Using the License Ledger Reference guide is available at the Download Center
• AssetMetrix Using the Unauthorized Software Feature Reference guide is available at the Download Center

MMS 2007

• SY02 - SMS 2003 SP3 – Asset Intelligence
• Speaker(s): Quincy Milton; Michael Nappi
• This session covers the incorporation of the AssetMetrix acquisition as it is integrated into SMS 2003 SP3. Starting from an overview of SMS 2003 SP3 the session will look at the steps needed to prepare for and deploy the service pack; the session will then drill into the Asset Management solutions enabled by this update. The session will close with a look at the related Asset Management features which will be included in SCCM 2007 and beyond.

KB’s for SMS SP3

• Resource Explorer does not display processor data for client computers that run hardware inventory after you upgrade the primary site server to SMS 2003 Service Pack 3
• http://support.microsoft.com/kb/937634

• Some ITMU-specific reports contain no data after you upgrade to SMS 2003 Service Pack 3
• http://support.microsoft.com/kb/937098

• Asset Management reports in Systems Management Server 2003 Service Pack 3 contain information about obsolete computers
• http://support.microsoft.com/kb/936739

• Error message when you try to install Systems Management Server 2003 Service Pack 3 on a computer that is running Windows Vista: "Not enough storage is available to process this command "Error message when you try to install Systems Management Server 2003 Service Pack 3 on a computer that is running Windows Vista: "Not enough storage is available to process this command"
• http://support.microsoft.com/kb/936044

• You cannot use the software inventory method to collect files from a mobile device after you install Microsoft Systems Management Server 2003 Service Pack 3
• Install PREVIOUS to SP3 implementation
• http://support.microsoft.com/kb/934206

• SMS 2003 Setup does not verify whether the 325804 hotfix is installed when you install a secondary site by using advanced security
• http://support.microsoft.com/kb/886033

Hotfixes:

934206 – Mobile Device management

937882 – AssettMetrix update

Notes

• Related to ITMU pre v3 - I found a note regarding the need to install SP3, then reapply ITMU v3
• MP install fails because a service could not be deleted – reboot resolved.
• HW inventory may be inconsistent until all clients are upgraded to SP3 (data is there, but not visible)
• SMS_Def.mof will need to be extended for AssetMetrix and SP3
• Check with Sherry Kramer for updates (on www.myitforum.com)
• Install 934206 before installing SP3 to prevent device feature pack issues

SMS 2003 SP2 post fixes (Pre-SP3)

Note: this is the list pre SP3 release 

Note: This is not an official SMS hotfix list.  One size does not fit all and your mileage may vary.  So please review this list for applicability to your particular SMS environment.  

Topics covered:

ITMU scanning performance:
Windows 2003 issues that impact SMS:
Windows 2000 issues that impact SMS:
SQL 2005 issues that impact SMS: 

Hotfixes Incorporated Into SMS 2003 Service Pack 3

ITMU scanning performance:

924148: Systems Management Server 2003 client computers experience slow performance when you run the Inventory Tool for Microsoft Updates (ITMU)
http://support.microsoft.com/?id=924148
Brief: ITMU scans can cause high CPU utilization and slow response on clients.  

932494: When you use Automatic Updates to scan for updates or to apply updates to applications that use Windows Installer, you experience issues that involve the Svchost.exe process
http://support.microsoft.com/?id=932494
Brief: High Svchost.exe CPU utilization and application errors during patch scans.

There are two fixes (916089 now superseded) for ITMU scan performance issues:
916089 (Replaced by 927891) When you run Windows Update to scan for updates that use Windows Installer, including Office updates, CPU utilization may reach 100 percent for prolonged periods
http://support.microsoft.com/default.aspx?scid=kb;EN-US;916089
Brief: A new version of Microsoft Windows Installer: 3.1 v2 (3.1.4000.2435)

927891 (Replaces 916089) You receive an access violation when you try to install an update from Windows Update after you apply hotfix package 916089  Note that 927891 was re-released 2-20-07
Brief: A newer version of Microsoft Windows Installer: 3.1 v2 (3.1.4000.4003)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;927891

926464: A new version of the Windows Update offline scan file is available
http://support.microsoft.com/Default.aspx?id=926464
Brief: A new ITMU version (ITMUv3) is required to use this new wsusscn2.cab catalog.  ITMUv3 includes fixes to remediate previously identified performance issues and will be required by March 2007 when the current wsusscan.cab will be retired.
A good overview of ITMU changes by SMS MVP Greg Ramsey at: http://myitforum.com/cs2/blogs/gramsey/archive/2006/10/12/ITMU-Update-_2D00_-November-2006.aspx

918914: The ddm.box inbox folder is queued with many DDRs, and the SMS database is not updated with newly created objects in Systems Management Server 2003. http://support.microsoft.com/?id=918914
Brief: SMS fails to process DDRs and a backlog of DDRs results in SMS\inboxes\auth\ddm.box. This problem occurs if the Windows Management Instrumentation (WMI) property on the SMS client contains two or more site codes.

915198: You may receive inaccurate reports when you run SMS hardware inventory reports on the parent site server http://support.microsoft.com/default.aspx?scid=kb;EN-US;915198
Brief: SMS_DESPOOLER and SMS_REPLICATION_MANAGER process files in alphabetical rather than chronological order, causing possible inaccurate reports.

916523:  If an SMS 2003 site database is larger than 2 GB, the database size is reported incorrectly in the SMS Administrator Console http://support.microsoft.com/default.aspx?scid=kb;EN-US;916523
Brief: If the size of the SMS database and the corresponding transaction logs exceeds 2 gigabytes (GB), the SMS Admin console reports their size incorrectly.

920108: The Manage Site Accounts tool does not add or modify Client Push accounts in Systems Management Server 2003 SP2 http://support.microsoft.com/default.aspx?scid=kb;EN-US;920108
Brief: After adding a new Client Push account via MSAC, it is not displayed in the Accounts tab of the Client Push Installation Properties.

917435:  Errors are logged in the sender.log file and the sched.log file on Systems Management Server 2003 http://support.microsoft.com/default.aspx?scid=kb;EN-US;917435
Brief: The SMS Scheduler component deletes instruction files (.I??) that are older than 25 hours, which causes invalid send request errors in sender and scheduler logs

919094: Error message when you try to import the Sms2003sp2_ad_schema.ldf file in Systems Management Server 2003 Service Pack 2: "Add error on line 21"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;919094
Brief: The command syntax that is documented in the Sms2003sp2_ad_schema.ldf file is incorrect and returns an error.

921463   Active Directory System Group Discovery may update the time stamp for SMS clients that no longer update their DNS records on a computer that is running SMS 2003 with Service Pack 2  http://support.microsoft.com/default.aspx?scid=kb;EN-US;921463
Brief: Delete Aged Discovery Data task may not remove aged clients.

Windows 2003 issues that impact SMS:
924779: The Family attribute of the Win32_Processor WMI class returns incorrect values for some processors that run on a Windows Server 2003-based computer
http://support.microsoft.com/default.aspx?scid=kb;EN-US;924779
Brief: Some 64bit AMD processors may be incorrectly identified in WMI.  SMS hardware inventory will collect this incorrect data.

906317 (897667): The SMS_EXECUTIVE service of Systems Management Server 2003 may unexpectedly stop during the service startup.
http://support.microsoft.com/Default.aspx?id=906317
Brief: This is a COM+ roll-up fix (KB 897667) that addresses an issue in ODBC that frequently causes SMS server components to crash during startup.

906570: A custom program that uses the RegConnectRegistry function can no longer access the registry of a remote computer in Windows Server 2003 with Service Pack 1 or in an x64-based version of Windows Server 2003
Brief: This problem occurs after you upgrade a site server or site system to Windows Server 2003 SP1 and that server attempts to connect to the registry on a Windows Server 2003 RTM or Windows 2000 machine.
http://support.microsoft.com/?id=906570

913441: The list of extension files that the IisWebService.ListExtensionFiles method returns may be incomplete in IIS 6.0  http://support.microsoft.com/default.aspx?scid=kb;EN-US;913441
Brief: Errors during MP setup caused by the removal of a previous management point installation which did not correctly clean up all the Web service extension file names in the Metabase.xml file.  For more details see: http://support.microsoft.com/default.aspx?scid=kb;[LN];918324
 
913666:   An SMS 2003 server locator point on a Windows Server 2003 Service Pack 1 (SP1)-based computer stops functioning.   http://support.microsoft.com/default.aspx?scid=kb;EN-US;913666
Brief: The SLP stops functioning because DCOM Local Launch permissions for the Internet Guest account are removed after upgrading to Win2003 sp1.

Windows 2000 issues that impact SMS:

905792: Every 30 minutes, the Svchost.exe CPU utilization increases on a Systems Management Server 2003 Advanced Client computer that is running Windows 2000
http://support.microsoft.com/?id=905792
Brief: By default, the Windows Management Instrumentation (WMI) repository backup occurs every 30 minutes on Win2000 clients.  This can be changed via the registry to back up less frequently.

SQL 2005 issues that impact SMS:

923116 Error message after you install the Systems Management Server 2003 site database on Microsoft SQL Server 2005: "Message ID : 619"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;923116
Brief: You may receive an error message when installing SMS 2003 on SQL server 2005 without the following hotfix:

925335 FIX: Error message when you use a label after a Transact-SQL query in SQL Server 2005: "Incorrect syntax near 'X'"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;925335

Hotfixes Incorporated Into SMS 2003 Service Pack 3

Background Intelligent Transfer Service for Windows (BITS 2.5)

SMS 2003 error / exit code 65534

SMS 2003 when it attempts program execution and results in exit code: 65534

Definition: This exit code means insufficient rights by SMS to execute program or scripts in package source directory.

Fix:

• change the program
• Environment tab
• Run Mode
• Run with administrative rights checked
• Update the Distribution Points
• Verify the DPs have updated in the System Status >> Package Status logs
• Update the target PCs machine policy
• Alternatively delete the folder
• \\<CompName>\admin$\system32\CCM\Cache\<PackageID>.<PackageVersion>.System
• Execute the program (remotely)
• Client Interaction applications
• SMS Client Spy
• http://sourceforge.net/projects/smsclictr
• SMS View
• www.smsview.com
• SMS Send
• http://www.myitforum.com/articles/8/print_view.asp?id=7099
• Or Create a new / modify advertisement

SMS 2003 Reroot orphaned collections

'Author Shaun Cassells
'Shaun dot cassells at gmail dot com
'3-19-2007

' This script creates an association in v_CollectToSubCollect table.
' Inputs required
' Server Name
' Server Site Code
' Parent Collection Name
' Collections to query to be made sub collections of parent
' Go or no go.  Should be value of "Y" if you want it to go

'For command line input
if Wscript.Arguments.Count = "4" Then
 SMSServer = WScript.Arguments(0)
 SiteCode = WScript.Arguments(1)
 ParentCollection = WScript.Arguments(2)
 SubCollection = WScript.Arguments(3)
ElseIf WScript.Arguments.Count = "5" Then
 SMSServer = WScript.Arguments(0)
 SiteCode = WScript.Arguments(1)
 ParentCollection = WScript.Arguments(2)
 SubCollection = WScript.Arguments(3)
 bDoIT = WScript.Arguments(4)
Else
 Wscript.ECHO "*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*"
 Wscript.ECHO "please Add the following 4 or 5 inputs"
 Wscript.Echo "Note: following utility will only create a root if one does not exist."
 Wscript.Echo "       Will not change one if one already exists"
 Wscript.Echo "*SMS Server"
 Wscript.Echo "*SMS SiteCode"
 Wscript.Echo "*Parent Collection Name"
 Wscript.Echo "*Sub Collection Query"
 Wscript.Echo "    Ex.  '01[0-9][0-9]2007' - will return all Jan 2007 collections"
 Wscript.Echo "*Last input:  either blank.  or a 'Y' to actually reroot collection"
 Wscript.ECHO "*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*"
 WSCRIPT.QUIT
End If

Set SMSContext = CreateObject("WbemScripting.SWbemNamedValueSet")
 'Create the context qualifer object
        'Add the standard SMS context qualifiers to the context object
        SMSContext.Add "LocaleID", "MS\1033"
        Set WshNetwork = WScript.CreateObject("WScript.Network")
        SMSContext.Add "MachineName", WshNetwork.ComputerName
        SMSContext.Add "ApplicationName", "script DPAddAll"
       
'Connect WMI
Set objLocator = CreateObject("WbemScripting.SWbemLocator")
Set objWMIService = objLocator.ConnectServer(SMSServer, "root\SMS\site_" & SiteCode)
objWMIService.Security_.ImpersonationLevel = 3          ' impersonationLevel = Impersonate

'Connect SQL
Set cn = CreateObject("ADODB.Connection")
Set cmd = CreateObject("ADODB.Command")
constring = "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=SMS_" & SiteCode & ";Data Source="& SMSServer
cn.ConnectionString = constring
cn.Open
Set cmd.ActiveConnection = cn
cmd.Prepared = True
cmd.CommandText = "SELECT DISTINCT CollectionID, Name FROM dbo.v_Collection where Name = '" & ParentCollection & "'"
Set rs = cmd.Execute
Do Until rs.EOF
 wscript.echo "Root Package ID " & rs(0) & " " & rs(1)
 cmd.CommandText = "SELECT DISTINCT CollectionID, Name FROM dbo.v_Collection where Name like '%" & SubCollection & "%'"
 Set rSub = cmd.Execute
 Do Until rSub.EOF

  cmd.CommandText = "SELECT DISTINCT ParentCollectionID, SubCollectionID FROM dbo.v_CollectToSubCollect where parentCollectionID  = '" & rs(0) & "' and subCollectionID = '" & rSub(0) & "'"
  Set rExistSub = cmd.Execute
  If not rExistSub.EOF Then
   'Eventually need to add in code to get SMS_CollectionToSubCollection value if it already exists
   'If it does exist and doesn't match change the parent value to match
   'Didn't find this as nessecary during outtage March of 2007
   'Do Until rExistSub.EOF
    'wscript.echo "*   Sub Collection ID's " & rSub(0) & " " & rSub(1)   
    'wscript.echo "   *   Parent Collection Exists " & rExistSub(0) & " " & rExistSub(1)
   ' rExistSub.movenext()
   'Loop
  Else
   wscript.echo "*   Sub Collection ID's " & rSub(0) & " " & rSub(1)
   Set instCollToSubColl = objWMIService.Get("SMS_CollectToSubCollect").SpawnInstance_
   instCollToSubColl.parentCollectionID = rs(0)
   instCollToSubColl.subCollectionID = rSub(0)
   If bDoIT = "Y" Then
    instCollToSubColl.Put_
   End If
  End If
  rSub.movenext()
 Loop

 'test = InputBox("Type 'DIE'","Kill script?","DIE")
 'If test = "DIE" Then Wscript.Quit
        rs.MoveNext
Loop

cn.close
Set cn = Nothing
Set cmd = Nothing
Set objLocator = Nothing
Set objWMIService = Nothing
Set instCollToSubColl = Nothing
Set SiteCode = nothing
Set SMSServer = nothing