|
Can I extract SMS query data into other programs? |
|
Yes - If you are using version 1.2 of the MMC, you can use the 'Export List...' menu item (available by right-clicking on an item in the MMC), you can save information in the following file formats:
The link Where can I get version 1.2 of the MMC from provides details on where to obtain version 1.2 of the MMC. In addition to the above, the BackOffice Resource Kit 4.5 provides the "SMSExtract.xlt" and "SMSExtract.xls" files which you can use to extract SMS query results into Excel spreadsheets where you can manipulate them. There is also an Access version ("SMSExtract.mdb") included in the Resource Kit. If these don't do what you want, check
out http://www.i405.com/sms/
which contains a better version of the Excel spreadsheet or check out Web
Reports for SMS from Computing
Edge's (a link to the Computing Edge's website can be found from the
Third
Party Tools and Utilities page) |
Copying a Query |
|
Is there a way to make a copy of a
Query? If
I were to build a Query for each software product I want to inventory, and I just
need to change the criteria for each package, how can I go about copying a Query
rather that building 50 individual ones? Couple of options:
|
Creating a Query based on a Custom SMS_DEF.MOF |
|
I've created and tested a new SMS_DEF.MOF. Now I want to make a Query with the new fields, but I can't find it. Written in the 'ServicePacks.dos' is the following: The class that the client component version data is available from is SMS_G_System_SMS_CLIENT in the root\SMS\site_<sitecode> namespace. When you create a new query in the MMC, under
'Criteria' you get the
'General' window, with
'Simple
Value' displayed, and alongside the 'WHERE:' field is
the 'Select'
button. Click 'Select' to get the
'ATTRIBUTE CLASS' dropdown list. |
Creating a Subselect Query |
|
I'm trying to make a Query based on a Collection that seems like it should be pretty simple. All members of 'Collection X' which are not a member of 'Collection Y' should be members of 'Collection Z'. This is known as a "subselect" query. The following is an overview from Ian Turek and Dave Yarborough.
Contributed
By: Ian Turek select whatever where .resourceID is not in (collection selecting .resourceID
Contributed
By: Dave Yarborough 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_SYSTEM on SMS_G_System_SYSTEM.ResourceID =
SMS_R_System.ResourceId where SMS_G_System_SYSTEM.Name not in (select
SMS_R_System.Name from SMS_R_System inner join SMS_G_System_SoftwareFile on
SMS_G_System_SoftwareFile.ResourceID = SMS_R_System.ResourceId where
SMS_G_System_SoftwareFile.FileName ="navw32.exe") |
Defining a Site in a Query/Collection |
|
I'd like to know how you are managing your
Secondary Site systems in their Parent database? The obvious way is to set a
Query based on subnet boundaries that define the Secondary. The problem comes
when you get a traveller into the Secondary such that the machine's properties
end up with multiple IP addresses as they move around an enterprise into
different SMS sites. So a Query that defines the Site will return not only those systems that were installed at - and never left - that site, but ALSO return visitors TO the site who happen to have picked up the visited site's subnet. This results in a Collection for site 'AAA' where you end up with clients from 'AAA' but also client systems with Site 'BBB'. This same confusion also extends to using Queries based upon the SMS "installed" Site (for example the Site code where the Client got installed from originally - a single value only, but not necessarily where the Client lives today!); and, SMS "assigned" site (i.e.: any and all "Sites" that travelling computers may ever have joined at some point in time - could be many values here). What's the best method to develop a Collection based upon the machines that *currently* and really, really belong to that site? Using Travelling Mode is what causes the creation of
multiple Site information as well as multiple IP addresses for the Client record
(from DHCP assigning different addresses at the different visited locations), so
I have seen many instances of a Client record with 3 or 4 different SMS
"Assigned" sites and an equal amount of different IP addresses in the
record.
|
Getting the Remote Tools and Resource Explorer options to Display in Query Results |
|
Contributed
By: Cliff Hobbs [MVP SMS] |
How do I Query for a Certain Piece of Software on my Network? |
|
I am trying to find a certain piece of software on our network unsuccessfully. How can I do a report (Query), on every software company and executable? Also what is the best way to learn queries? This following query will show you all known software products by company: select distinct SMS_G_System_SoftwareProduct.CompanyName, SMS_G_System_SoftwareProduct.ProductName from SMS_R_System inner join SMS_G_System_SoftwareProduct on SMS_G_System_SoftwareProduct.ResourceID = SMS_R_System.ResourceId order by SMS_G_System_SoftwareProduct.CompanyName, SMS_G_System_SoftwareProduct.ProductName As for learning about queries enable the SMS
Provider log, run an adhoc query or predefined through the MMC. Then go
back to the SMS Provider log to see what commands the MMC issued against the
database to see the query you just built in the Admin UI. That's a pretty
easy way to get the exact syntax for any query you could possibly want to right
without being a SQL or SMS WMI guru. |
How to do a NOT Query |
|
How do I do a query where I want to find machines that are NOT in another query? Details of how to this can be found in the following article which can be accessed at http://www.myitforum.com/articles/1/view.asp?id=179 but is reproduced here in case it becomes unavailable in the future. You have to create two queries, the first one will give you a list of everyone who has the software, the second will return a list of everyone who does not have the software. The second will rely on the WQL that comprises the first. Create the first query like this:
Now you have designed the query that finds systems with the software. You will use this query in your subselected query to find systems that do not have this software. Now to Create the Subselected Query:
Now you have a query that uses the results of another query (the subselected values) to create it's own result set. Simply put this query says "Show me all the systems that aren't in this list". The WQL for the second query might look something like this:
|
How to Inventory Internet Explorer |
|
How do I to create a query to get the different versions of Internet Explorer?
Contributed By: Cliff Hobbs [MVP SMS] Remember that by default Software Inventory only
inventories EXE files. To add DLL files, go to 'Client Agents
| Software
Inventory Client Agent' and click the 'Inventory Collection' tab
then the Gold asterisk (*). Enter the file type(s) you want to add. The next
time software inventory runs, the new information will be collected. Bear in
mind that inventorying all DLLs on a machine may increase the size of the SMS
database considerably (depending on the number of clients). |
Is the SMS 2.0 Database Schema Published Anywhere? |
|
Contributed By: Cliff Hobbs [MVP SMS] and "Hermes" |
Is there a Way to Query for Failed Client Installations? |
|
Contributed By:
Wally Mead [MS] |
Laptop Query |
|
Contributed By: Cliff Hobbs [MVP SMS] |
Producing a Query of Which Packages are Installed on Which Machines |
|
From the microsoft.public.sms.admin
newsgroup |
Query Analyzer Tips |
|
Contributed
By: Cliff Hobbs [MVP SMS] |
Query in Collection Membership Rule May Fail |
|
Contributed
By: Cliff Hobbs [MVP SMS] |
Querying the State of a Registry Key |
|
Contributed
By: Cliff Hobbs [MVP SMS] |
Quick Snapshot of Applications and Their Descriptions |
|
Contributed
By: Cliff Hobbs [MVP SMS] |
Running some of the Pre-defined Queries in the Admin Console return no results |
|
When I run some of the pre-defined queries in the Admin console they come back empty.
Contributed
By: Cliff Hobbs [MVP SMS] |
Systems Not Appearing in Default Queries |
|
I use the "All NT 4.0
Workstations" default query. As it turns out quite a few systems don't show up in that query.
Upon further investigation, I looked at the query "All Systems" and
there they were. What was missing was their Site Code and OS description. Their
IP's were within the sitecode boundaries. The "Operating System Name" description
was blank. Any ideas why this is happening to some systems? Which log would I
look at that may point to why it is not getting a site code?
Something similar happened at our site, except I thought
that the site code data was there - just not the operating system, etc. When this happened to
me, it was due to there being no hardware inventory in the database - only discovery data. I
found that the WBEM software needed to be re-installed on many of my PCs before
the hardware inventories could be properly collected. |
Using NULL in Queries |
|
Contributed
By: Cliff Hobbs [MVP SMS] |
Using Wildcards in SMS Queries |
|
Contributed
By: Cliff Hobbs [MVP SMS] |
What are the Version Numbers for Office XP? |
|
Contributed
By: Cliff Hobbs [MVP SMS] |
| © FAQShop.com 2003 - 2008 |
|
|