SELECT
   COUNT(distinct ResourceID) as [Count],
   IP_Subnets0 as Subnet
FROM
   dbo.v_RA_System_IPSubnets
WHERE
   IP_Subnets0 NOT IN (SELECT IPSubnet FROM
dbo.v_SiteRoamingBoundary_IPSubnet)
GROUP BY
   IP_Subnets0
ORDER BY
   IP_Subnets0

I started listing down comparative differences between SMS 2003, SCCM 2007 and SCCM 2012 and with the help of Wei King to finish off the list, here is what we came up with Via http://www.myitforum.com/myITToolbar/frame-click.asp?url=http://mymomexperience.blogspot.com/2011/04/comparing-sms2003-sccm-2007-and-sccm.html

There are many tools like SMS /SCCM or scripting to get list of applications installed on computers(you dont use SMS/SCCM only for this kind of information :) ) but what if the clients are not reported back to site server for some other reason and there could lot of applications installed on computers then you will start troubleshooting the clients why it doesnt report.

 Use the below simple VB script to get list of applications installed on target computers with its installed date and product ID as well.

Collect list of computers that you are looking for and pipe all the computer names into computers.txt file.

create a notepad file and name it as applications.vbs and paste the following query into it.

Output will be piped into status.csv file on the same location where the VBscript runs from.

On Error Resume Next
Set fso=CreateObject(“scripting.filesystemobject”)
Set objinputfile=fso.OpenTextFile(“computers.txt“,1,true)
Set objoutputfile=fso.OpenTextFile(“status.csv“,2,true)
Do While objinputfile.AtEndOfLine <> True
strcomputer=objinputfile.ReadLine
 Set objWMIService = GetObject(“winmgmts:\\” & strComputer)
 If Err.Number <> 0 Then
  objoutputfile.WriteLine( strcomputer & ” ” & Err.Description)
  Err.Clear
  Else
                              Set colItems = objWMIService.ExecQuery(“SELECT * FROM Win32_Product”,,48)
objoutputfile.WriteLine (“computer name:” & strcomputer)
For Each objItem in colItems
   objoutputfile.WriteLine(“Name: ” & objItem.Name  & ” , ” & “ProductID: ” & objItem.ProductID & “,” &”Installed On:” & objItem.InstallDate )

Next
End if
Loop
msgbox(“done”)

PS:Both the computers file and VB script should be in same folder location.

Having issues with hardware inventory in running on the machines ,there are several tools that does this job like Right click tools ,SMS collection commander from  Zander and can use batch script given below.

1.Cretea a folder called Temp in C drive.

2.Crete a new notepad file ,add list of computers that you want to kick the hinv on and save it as Computerlist.txt in c:\Temp folder.

3.Open a notepad and paste the below code and save it as filename.bat .

@echo off
REM It kickoffs the hinv on to the list of machines provided
WMIC /node:@c:\temp\Computerlist.txt /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000001}”

4.double click the filename.bat file and it should trigger the hinv on the list of machines that you have proivded in the notepad list.

since the above script is created  to trigger hardware inventory action,You will have all the Actions ID given below for each.

• • Hardware Inventory – 00000000-0000-0000-0000-000000000001
  • Software Inventory – 00000000-0000-0000-0000-000000000002
  • Data Discovery – 00000000-0000-0000-0000-000000000003
  • Machine Policy Assignment Request – 00000000-0000-0000-0000-000000000021
  • Machine Policy Evaluation – 00000000-0000-0000-0000-000000000022
  • Refresh Default Management Point – 00000000-0000-0000-0000-000000000023
  • Refresh Location (AD site or Subnet) – 00000000-0000-0000-0000-000000000024
  • Software Metering Usage Reporting – 00000000-0000-0000-0000-000000000031
  • Source list Update Cycle – 00000000-0000-0000-0000-000000000032
  • Refresh proxy management point – 00000000-0000-0000-0000-000000000037
  • Cleanup policy – 00000000-0000-0000-0000-000000000040
  • Validate assignments – 00000000-0000-0000-0000-000000000042
  • Certificate Maintenance – 00000000-0000-0000-0000-000000000051
  • Branch DP Scheduled Maintenance – 00000000-0000-0000-0000-000000000061
  • Branch DP Provisioning Status Reporting – 00000000-0000-0000-0000-000000000062
  • Software Update Deployment – 00000000-0000-0000-0000-000000000108
  • State Message Upload – 00000000-0000-0000-0000-000000000111
  • State Message Cache Cleanup – 00000000-0000-0000-0000-000000000112
  • Software Update Scan – 00000000-0000-0000-0000-000000000113
  • Software Update Deployment Re-eval – 00000000-0000-0000-0000-000000000114
  • OOBS Discovery – 00000000-0000-0000-0000-000000000120

You can see all the above actions item IDs from WMI. From Run command,type wbemtest and use the name space as ‘root\CCM\Policy\Machine‘. It list all the classes (Dynamic or Static from WMI Repository).

 Hope it Helps !

select Distinct
CS.Name0,
SER.Displayname0,
SER.Started0,
SER.StartMode0,
SER.State0
from
dbo.v_GS_COMPUTER_SYSTEM CS,
dbo.v_GS_SERVICE SER,
dbo.v_FullCollectionMembership FCM
where
CS.ResourceId = SER.ResourceID
and CS.ResourceId = FCM.ResourceID
and SER.displayname0 like ‘%firewall%’
and (SER.State0 != ‘Running’ or Isnull(SER.State0,”)=”)
and FCM.CollectionID = ‘SMS00001′

Below are some of the ports which are required to be open for proper communication.

Port Requirements:

–>SMS site server to Active Directory

–>  SMS 2003 Advanced Client to Active Directory

In an Active Directory environment, the Advanced client makes a Lightweight Directory Access Protocol (LDAP) query to the global catalog server to find a management point that matches the client’s IP address. The following ports are required in Active Directory to allow the client to contact the global catalog server.

–> Port 389 UDP (User Datagram Protocol) LDAP Ping

–> Port 389 TCP LDAP

–> Port 636 TCP LDAP (SSL Connection)

-> Port 3268 TCP (explicit connection to Global Catalog)

–> Port 3269 TCP (explicit SSL connection to Global Catalog)

–> SMS 2003 Advanced Client to Management Point or to distribution point

–> Port 80 Hypertext Transfer Protocol (HTTP)

–> Port 139 Client sessions (for non BITS-enabled DPs)

–> Port 445 Server Message Block (for non BITS-enabled DPs)

–> SMS Remote Control UDP

When you use NetBIOS over TCP/IP for SMS Remote Control, the following ports are used:

–> Port 137 Name resolution

–> Port 138 Messaging

–> Port 139 Client sessions