31 December 2019

I have migrated my blog to a WordPress site, please check the new site at https://paddymaddy.com

02 December 2010

ALL Collections WQL and collection ID and Names in a Site

SELECT     TOP (100) PERCENT dbo.v_Collection.Name, dbo.v_Collection.CollectionID, dbo.v_CollectionRuleQuery.RuleName, dbo.v_CollectionRuleQuery.QueryID,
                      dbo.v_CollectionRuleQuery.LimitToCollectionID, dbo.v_CollectionRuleQuery.QueryExpression
FROM         dbo.v_Collection INNER JOIN
                      dbo.v_CollectionRuleQuery ON dbo.v_Collection.CollectionID = dbo.v_CollectionRuleQuery.CollectionID
ORDER BY dbo.v_Collection.Name, dbo.v_Collection.CollectionID

30 November 2010

SMS 2003 Sourceforge Tools And Utilities

SMS/SCCM Peer2Peer AddOn
SMSTorrent is a Peer2Peer AddOn for SMS2003/SCCM2007 Clients. SMS/SCCM Clients are able to share the local Package cache with other Clients using the BitTorrent filesharing protocol.
http://sourceforge.net/projects/smstorrent
SMS Site Settings tweak
SMSSettings provides a GUI to modify SMS2003 (Microsoft System Management Server 2003) Site Settings which are not accessible over the normal SMS Admin Interface.
http://sourceforge.net/projects/smssettings
Screen Lock
This Tool does lock the Screen, Mouse and Keyboard for a specified time.
http://sourceforge.net/projects/screenlock
SMS Client Center
Troubleshoot and manage SMS 2003 advanced clients
http://sourceforge.net/projects/smsclictr
SMS 2003 Offline Hardware Inventory
Capture SMS2003 Hardware Inventory on Systems without Network connectivity or Systems without an SMS Agent installed. This Tool creates a DDR (DataDiscoveryRecord) and an IDMIF File for each scanned system.
http://sourceforge.net/projects/smshwinv
Secure Autologon
Enable Windows Autologon without a cleartext password in the Registry. The password will be stored by the Local Security Authority (LSA).
http://sourceforge.net/projects/autologon
SMS2003 Object Backup
Backup and restore a definable set of SMS 2003 Objects (Packages, Programs, Advertisements, Collections...). SMSObjBackup can also be used for Site Migration (Objects can be moved to another SMS Primary Site Server)
http://sourceforge.net/projects/smsobjbackup
SMS 2003 Adv.Client local policy import
A command line tool to assign local software distribution policies to an SMS 2003 Advanced Client. The Software will be installed independent of collection memberships.
http://sourceforge.net/projects/smspolimp
SMS CloneDP
Manage the assigned Software Packages of a Microsoft SMS (SystemManagementServer) 2003 DistributionPoint
http://sourceforge.net/projects/smsclonedp
SMS 2003 Software Request Web Form
SMS 2003 Software Request Web Form with a simple Workflow (mail/web based).
http://sourceforge.net/projects/smsswreq
SMS Collection Commander
Initiate SMS 2003 advanced client actions on a collection: Ping, WakeUp, HW/SW Inventory, ReRun Advertisements, Show logged on user, Download/Refresh Policy, Repair SMS Agents, Import Clients to the Collection...
http://sourceforge.net/projects/smscollctr
SMS OSD Program Import
SMSOSDXML extends the SMS 2003 Admin Console to import OSD Program-Settings based on a XML File. SMS OSD automatically creates such XML Files (SMSDeploy.xml) for each OSD Program created in the Admin Console.
http://sourceforge.net/projects/smsosdxml
SMS Package Dependency Viewer
Show "Microsoft System Management Server 2003" Software Package dependencies in a TreeView.
http://sourceforge.net/projects/smsdepview

04 November 2010

WMI delete

To delete a class

You can delete a class in the current namespace with Delete Class on the Windows Management Instrumentation Tester dialog box.

Open the Windows Management Instrumentation Tester dialog box.
In the Windows Management Instrumentation (WMI) Tester dialog box, click Connect.
In the Namespace box, type the path to the namespace that you want to connect to.
Example?
- To connect to the namespace where the Win32 provider classes reside, type:
  root\cimv2
Click Connect.
Click Delete Class.
In the Get Class Name dialog box, type the name of the class you want to delete, and then click OK.
A dialog box is displayed to warn you that the class might have derived classes or instances. This dialog box is displayed even if there are no derived classes or instances.
If you are sure you want to delete the class, click Yes to delete the class.

Notes

Performing this task on the local computer does not require you to have administrative credentials. Therefore, as a security best practice, consider performing this task as a user without administrative credentials.
Performing this task on a remote computer requires that you are a member of the Administrators group on the remote computer, or that you have been delegated the appropriate authority.
To open the Windows Management Instrumentation Tester dialog box, click Start, click Run, and then type WBEMTest.exe.

20 October 2010

Client Site code

19 October 2010

Use Full SQL Tables / Views

UseFull SQL Tables/ Views	Description / Use
v_Add_Remove_Programs
v_Advertisement
v_AdvertisementInfo
v_ClientCollectionMembers
v_Collection
v_Collection
v_ConfigurationItems
v_DistributionPoint
v_DistributionPointGroup
v_GS_ADD_REMOVE_PROGRAMS
v_GS_ADD_REMOVE_PROGRAMS_64
v_GS_COMPUTER_SYSTEM
v_GS_DISK
v_GS_Memory_Details0
v_GS_OPERATING_SYSTEM
v_GS_PATCHSTATE
v_GS_SERVICE
v_GS_SoftwareProduct
v_GS_SYSTEM
v_GS_WORKSTATION_STATUS
v_GS_X86_PC_MEMORY
v_OS_Details
v_Package
v_PackageStatus
v_Program
v_Query
v_R_System
v_R_User
v_R_UserGroup
v_RA_System_IPAddresses
v_RA_System_IPSubnets
v_RA_System_IPXAddresses
v_RA_System_MACAddresses
v_RA_System_SMSAssignedSites
v_RA_System_SMSInstalledSites
v_RA_System_SystemContainerName
v_RA_System_SystemGroupName
v_RA_System_SystemOUName
v_RA_System_SystemRoles
v_Report
v_Site
v_SiteBoundary_ADSite
v_SiteBoundary_IPSubnet
v_StateNames
v_UpdateBundles
v_UpdateListStatus_Live
v_UpdatePrograms

Download these next path ::

vnext
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ffca869c-4a83-434e-acc9-8b2388c0c7f7&displaylang=en&hash=AsfGo9XDkf9sIbtk88J1avBWmhXUWCuAjSQj1%2fsZM8VWG9dUPmqIq8n7VvOTw8xKAUCheBh89IzMW23MsS5aCA

scom r2
http://download.microsoft.com/download/E/2/9/E29F1A2F-78B0-4B11-9517-435A2627A72F/OPSMGR2007R2EVAL.exe

service manager
http://download.microsoft.com/download/8/5/2/8529ED85-8D64-4662-A337-2DCA431C495B/SCSM_RETAIL.exe

Data Protection Manager

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=cba30567-6ef0-4450-93f8-e433897cb093&displaylang=en&hash=S%2flpPNEVndZjpiujZaCC95kn7ehGeZtOLb%2blWlPPZslSlU3mjHyQXFym%2bnRtExHr0cG3eGeGlmGrsaaDapy%2bjw%3d%3d

Opalis

http://download.microsoft.com/download/D/F/C/DFC9F061-65A9-44C0-9012-450A7B8697CC/Opalis_180_Day_Evaluation.exe

16 October 2010

SCCM R3 Provides

The following features are new to Configuration Manager 2007 R3.

Power Management: Provides a set of tools that enable the site administrator to configure standard Windows power settings across computers and monitor power consumption and computer activity.
Operating System Deployment Improvements: Provides pre-staging of boot images and Windows Imaging Format (.wim) files on new computers that enables the administrator to apply a task sequence to the device that can use the pre-staged media.
Dynamic Collection Evaluation: Enables you to rapidly evaluate a collection membership by adding only newly discovered resources.
Active Directory Delta Discovery: Performs an intermediate discovery cycle that adds only new resources to the Configuration Manager 2007 database.
Simplified Resource Management: Enables you to search for and add resources to a specified collection.
Desired Configuration Management: Enables you to create a collection of compliant or noncompliant computers in desired configuration management.
Higher Number of Supported Clients Per Hierarchy: Configuration Manager 2007 R3 supports up to 300,000 clients per hierarchy when it uses the default settings for all Configuration Manager 2007 features. This increase in supported clients is the result of improvements to the Active Directory synchronization and Collection Evaluation processes

15 October 2010

Test post

14 October 2010

V.Next: Configuration Manager and Systems Management Server

Configuration Manager and Systems Management Server

You can find the labs all on the TechNet Virtual Lab page here.
Don’t forget, tomorrow the Community Evaluation Program for ConfigMgr v.Next starts. More information on that is here.

R3 is RELEASED !!!!!!

http://blogs.technet.com/b/systemcenter/archive/2010/10/14/system-center-configuration-manager-2007-r3-unleashed.aspx

Epo tutorials & documentation.

Below link has Epo tutorials & documentation.

https://community.mcafee.com/community/business/epo?view=documents

13 October 2010

Windows 2008 IIS Common Issue on MP : Make sure you need to meet this settings on your windows 2008 server

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

11 October 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

06 October 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.

05 October 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