All about SCCM Learning

Wednesday, October 13, 2010

Last hardware inventory 14 days

---------------------------------------------
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.Name not in (select SMS_R_System.Name from SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on SMS_G_System_WORKSTATION_STATUS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_WORKSTATION_STATUS.LastHardwareScan >= DateAdd(dd,-14,GetDate()) )
-----------------------

Collections: query to check for obsolete clients

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 obsolete = 1

Monday, October 11, 2010

You must know these collections as handy : Collections End to End

1.Client all system collection

2.Non client systems

3.Inactive systems

4.Obsolete system

5.Duplicate client Yes or No

6. Last hardware inventory 14 days

7.Last software inventory 14 days

8.Last Data discovery cycle.

9. XYZ package, XYZ Advertisement success systems’ collection

10. XYZ package, XYZ Advertisement Failed systems’ collection

11.XYZ subnet collection system

12.Add XYZ system’s to a collection of Existing

13. All SMS server system collection

14. All windows server, workstation,DP,BDP collection

15. All system’s with AD site based

16. Collection limiting to sub collection, linking

17.System’s are in “A” collection But not in “B” Collection & Vice versa

18. In collection “XYZ” Software installed system

19. In collection “XYZ” File inventory(s\w inventory based) installed system

20. In collection “XYZ” file specific method(H\w inventory based) system

21.XYZ patch Installed & Not Installed system

22. All windows update Agent version 7.6 below

23.XYZ user/group collection

Wednesday, October 6, 2010

“The network path was not found" error on Win XP sp3”

The problem
You are unable to connect to any network resource (network shares, printer, etc) on a Windows XP machine, from a Win XP client.
A solution (there could be several causes)

On the target machine (the one you're trying to connect to) open up Services, under Administrative Tools in the Start Menu.
Scroll down to the Computer Browser service.
If it is Disabled or set to Manual, set it to Automatic.
Then start it. It may stop immediately again, but this is OK.
At this point try to connect to the target machine.

If it still doesn't work, you can try the following:

open up Network Connections, under Control Panel.
Right click on your network adapter and click on Properties.
Click on Internet Protocol (TCP/IP), then click on Properties.
Click on Advanced, and click on the WINS tab.
Even if it is set to Default, set the radio button to Enable NetBIOS over TCP/IP.
Press OK on each screen until everything's closed.
Go back to the client machine and try again.
You should be able to connect!

If it still doesn't work:

Go back to the Services window and find the service named Routing and Remote Access.
Double-click on it, set it to Manual, and stop it.
Close Services and try to connect from your client machine again.

Tuesday, October 5, 2010

WSUS Wiki and troubleshooting WSUS

Read here on the WSUS Team Blog a nice article about troubleshooting WSUS. It references the site http://www.wsuswiki.com/.

This site was created to provide a place for the WSUS community to share information about WSUS, including troubleshooting steps and best practices. The advantages that this site provides over public news groups include:

Content on this site is edited and kept up-to-date. News group postings can get out of date, can contain incorrect information, and are often not corrected.
It is easier for readers to find information on this site than in the news group.
This site captures minor contribution from many users and both aggregates and persists them over time. This body of work grows and gets better over time whereas newsgroups just grow.
It is fun to edit pages and improve on contributions of others. You can not really do that with news groups.

It also references several troubleshooting tips for successful configuration of WSUS.

Check it out.

SQL Reporting Services: SRS

SQL Reporting services have some benefits over the current reporting solution:

Provide best in class reporting capability by integrating SQL Reporting Services, with the leading change and configuration management product: SCCM 2007
Enable Ad-hoc reporting - Make it easy for both SCCM administrators, and non administrators to find the information they need to make the right decisions for their business
Support alternative databases as the reporting database, such as a replicated or backup database
Allow custom report creation via a report authoring wizard.
Enable report browsing and viewing via the SRS Report Viewer.
Take advantage of rendering in all supported SRS formats, report caching, and subscriptions.

This article will explain setting up SRS with Configuration Manager based on SQL 2008. I’ve taken most of the steps from this article (many thanks to Michael Wiles). I’ve added some screenshots and applied it to SQL 2008, while the original article discusses SQL 2005. If you need more background info on SRS check out that link.

Install and configure SQL Reporting Services in SQL 2008

Be sure to check Reporting Services as part of your SQL installation

At step 21 of this part of this guide the setup provides you with three choices:

Native mode default configuration
SharePoint mode default configuration
Unconfigured Reporting Services installation

You should select Unconfigured Reporting Services installation at this point.

After the installation finishes you should configure SRS for the use with Configuration Manager 2007.

1. In the start menu select Microsoft SQL Server 2008 / Configuration Tools, then click Reporting Services Configuration Manager.

2. In the Reporting Services Configuration Connection select the Server Name and the Report Server Instance, then select Connect.

3. In the Report Server Status verify that the Service Status is set to Running. If it is not, click Start, and then click Apply.

4. Select Web Service URL and make sure you specify the name you want to call the virtual directory created by Reporting Services (or use the default ReportServer). Optionally you can select the IP-address you want to use, the port and SSL setting. When done click Apply.

5. Select Database, select Create a new report server database in the Report Server Database Configuration Wizard and click Next

6. Select the Database Server Name and Authentication Type that matches your SQL server and credentials.

7. Supply the Database Name and Language. Be sure to select Native Mode for Report Server Mode. Click Next.

8. Select the proper credentials from the drop list for Authentication Type

9. In the Summary screen review your settings and Click Next.

10. Review your database in the Report Server Database screen.

11. Select Report Manager URL and make sure you specify the name you want to call the virtual directory created by Reporting Services (or use the default Reports). Optionally you can select the IP-address you want to use, the port and SSL setting. When done click Apply.

12. Email settings are not mandatory to setup, but can be configured appropiately if necessary.

13. Execution Account is necessary to configure if you will be running unattended reports. Optionally apply credentials and Click Apply.

20. Click Exit to close Reporting Services Configuration Manager.

Configure Configuration Manager 2007

SQL Reporting Services need the configuration of a Reporting Services Point role.

1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code>-<site name> / Site Settings / Site Systems.

2. In this guide I will add the reporting services point site role to the existing site system. Right-click the site system name, and click New Roles. On the General page of the New Site Role Wizard, configure the general settings for this site system, then click Next.

3. On the System Role Selection page of the wizard, select Reporting Services point (don’t select Reporting Point by mistake, which is the traditional reporting functionality), then click Next.

5. On the Reporting Services Point page, specify the folder that will be created on the report server to contain the SQL Reporting Services reports used in Configuration Manager and then click Next.

6. Review the information shown on the Summary page, then click Next.

7. Click Close to exit the wizard.

8. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Reporting / Reporting Services, and expand the node.

9. Right-click the reporting services point server you want to configure, then click Properties.

10. On the Data Source Settings tab of the Report Server Properties dialog box, specify the Configuration Manager 2007 database server and database name (not the one create earlier for reporting!) to be used as the data source for SQL Reporting Services reports. Click the test button to verify that you have correct data entered.

11. On the Data Source Authentication tab of the Report Server Properties dialog box, specify the credentials used to access reports on the report server. I’ve use Windows Integrated Security here.

12. On the Data Source Security tab of the Report Server Properties dialog box, specify permissions for the users who have access to the data source specified in the Data Source Settings tab.

13. On the Security tab of the Report Server Properties dialog box, specify the users who have access to the selected report server.

14. Click OK to close the Report Server Properties dialog box.

Import standard reports in Reporting Services

The last step in configuring SRS for Configuration Manager 2007 is to convert the standard reports to Reporting Services reports.

1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Reporting / Reporting Services

2. Right-click the Reporting Services server that the standard reports will be copied to, then click Copy Reports to Reporting Services.

3. On the Data Source Settings page of the Copy Reports Wizard, specify the Configuration Manager 2007 database server and database name from which to copy the reports. Click Next.

4. On the Data Source Authentication page of the Copy Reports Wizard, choose the authentication method required to run the copied reports on the reporting point server. Click Next.

5. On the Select Reports page of the Copy Reports Wizard, select the reports you want to copy to the reporting services point. Select Overwrite existing reports if you want to overwrite any reports that already exist on the reporting services point. Click Next.

6. On the Security page of the Copy Reports Wizard, specify which users can access the copied reports and the roles they must belong to. For more information about the options on this page, see Report Server Properties: Security Tab. Click Next