IP address Range collection

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.IPAddresses >= "192.168.1.1" and SMS_R_System.IPAddresses <= "192.168.1.50"

How can I check which SQL Server instance my SCVMM installation is using?

Q: How can I check which SQL Server instance my SCVMM installation is using?

A: The easiest way to check which SQL Server instance your SCVMM installation is using is to look at the registry on the SCVMM server:

1. Start the registry editor (regedit.exe).
2. Move to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\Sql.
3. Look at the InstanceName and DatabaseName values for the SQL Server instance and database name. The ConnectionString value shows the complete combination.
4. Close the registry editor.

Nice Posts

Nice post on different things to try, http://sccmbrokeit.blogspot.com/2013/10/sccm-2012-client-troubleshooting.html 

http://www.adaptiva.com/onesite/

http://blogs.msdn.com/b/scstr/archive/2012/05/31/configuration_2d00_manager_2d00_2012_2d00_sizing_2d00_considerations.aspx

configwise

if the reports struck , you can delete the dash board and re-scan the same

SCM

Security compliance manager helps to create 2012 server scan template in SCCM 2012

SQL Learning for SCCM Engineers

http://msdn.microsoft.com/en-us/library/ms191517(SQL.105).aspx

http://www.codinghorror.com/blog/2007/10/a-visual-explanation-of-sql-joins.html

http://docs.oracle.com/cd/B28359_01/server.111/b28286/queries006.htm

TO fix the SMS client GUID issue

How to fix the SMS client GUID issue

1.If the client status unknown in the SMS console after installing the SMS client (make sure that CCM setup.log shows the succeeded message)

2.Use the psexec tool to login to the machine locally

Usage of the tool

Psexec \\IPadress of the machine (space) cmd

Make sure that open client id manager startup.log in the client system to observer the changes

Patch of the client id manager startup.log would be c:\windows\system32\ccm\logs\

Below are the commands you should execute in the PSEXEC tool

a)      net stop ccmexec

b)      del "%windir%\Smscfg.ini"

c)       net start ccmexec

now open “client id manager startup.log “ in client system and observe the message

Once you identify that you fixed the client guid , open the sql and check the system status after few minits .

Use below query to check the same.

SELECT     Name0 AS [Machine Name], User_Name0 AS [User Name],AD_site_name0 as [AD site code] ,creation_date0 as [AD discoverd date],

                      CASE Active0 WHEN '0' THEN 'InActive' WHEN '1' THEN 'Active' ELSE 'Unknown' END AS [Active Client],

                      CASE Client0 WHEN '0' THEN 'No' WHEN '1' THEN 'Yes' ELSE 'Unknown' END AS [Client Status],

                      CASE obsolete0 WHEN '0' THEN 'No' WHEN '1' THEN 'Yes' ELSE 'Unknown' END AS [Obsolete Client], DATEDIFF(D,V_GS_WORKSTATION_STATUS.LASTHWSCAN,GETDATE()) AS [HW SCAN DIFFERENCE]

FROM         v_R_System  LEFT JOIN V_GS_WORKSTATION_STATUS ON V_R_SYSTEM.RESOURCEID = V_GS_WORKSTATION_STATUS.RESOURCEID

WHERE     (Name0 IN (

'Systemanem'))