SMS Collections

• Backlog of .psd file in coll_out.box [25/01/07]
• Can I recover the standard SMS Collections as I've accidentally deleted them? [4/10/00]
• Can you Build Groups in SMS? [22/5/03]
• Collection Created by WMI Script is Invisible to Console [11/8/03]
• Collection Evaluator Errors [4/10/00]
• Collection not updating [25/1/01]
• Collections and Subcollections [30/5/02]
• Creating a Collection for Laptops [14/11/05]
• Creating a Collection from a text file [4/10/00]
• Displaying the Collection ID in the SMS Administrator console [4/10/99]
• Importing Machines into a Collection [21/10/03]
• Is there a way to create a collection based on a list of users rather than systems using Makecoll? [11/11/00]
• Is there an Easy way to Change the Refresh Interval for Several Collections? [12/10/04]
• Moving/Copying Collections [14/10/00]
• Organising collections [7/10/00]
• 'Padlocks' appearing on my Collections [4/10/00]
• Recovered NetWare server no longer appears in collections [14/11/00]
• Refreshing Collection Information on a Child Site [07/09/04]
• Removing a large number of machines from the SMS database [4/11/99]
• Removing Locks on Collections and Adverts at a Child Site [29/7/03]
• SMS says Collection already exists when trying to create a new Collection [22/1/01]
• What happens when I delete a client from a Collection? [19/1/01]

Backlog of .psd file in coll_out.box

Can I recover the standard SMS Collections as I've accidentally deleted them?

1. It is used in the 1.2 -> 2 conversion process.
    
2. It can be used to check the integrity of an SMS 2.0 database. It recreates all SP's, Triggers etc. and will restore the default Collections as part of this process.

Can you Build Groups in SMS?

Contributed By: Hans Schefske [MVP SMS]
So you want to delegate control of your SMS clients to certain administrators? Collections is the way to go as detailed in this article…  [Go to article]
 

Collection Created by WMI Script is Invisible to Console

Contributed By: Cliff Hobbs [MVP SMS]
If you’re creating a Collection via a WMI script but then wondering why you can’t ‘see’ the newly created Collection in the MMC then here’s why courtesy of Michael Niehaus…  [Go to article]
 

Collection Evaluator Errors

"Microsoft SQL Server reported SQL message 208, severity 16: Invalid object name '_RES_COLL_DG000036'"

This problem has been cured for some people by applying SP2.

Check the 'sms\inboxes\colleval.box' directory for files on the server generating the messages. You can open up the file with Notepad and check to see if it matches the Collection ID mentioned in the error messages. I've seen this before and it was kind of like an orphaned Collection, the Collection Evaluator does not know it doesn't exist anymore and tries to process it, but SQL cannot find the correct tables for the Collection ID listed. I've fixed this before by just deleting the file in the 'colleval.box'. If you have a hierarchical site, you should check all the 'colleval.box' directories in your site.

The other alternative is to delete the Collection object within the SMS database with a SQL statement by using SQL Query Analyser to connect to your SMS database. Then use the following SQL syntax:

select * from collections

This will display all the collections in the database. The offending collection will be in the format of:

Collectionid = 10
SiteID = sgs00005
Collection = test

run
delete from collections where collectionid = 10
 

Collection not updating

I have created two Collections, Office 2000 and Office 2000 SR1. I sent out the update to Office 2000 via SMS. The Advertisement status says that 162 people have received it, 143 have started it and successfully installed the program. However, when I do an update Collection I may pick up one or two of the computers into the SR1 collection. It has been over a week now and I don't seem to be making any real significant gains in my SR1 collection.

The Query I've setup is supposed to look at the software inventory update of Microsoft-Office2000-Winword.exe 9.0.3822. In other words when it sees the update of that version of 'Winword.exe' it will then consider the computer to be upgraded to SR-1. When I remote control to someone's computer I find that the user has SR-1 on the help screen, but the software is not being updated to the new version. So from what I can see SMS is doing its job but for some reason the version number is not being updated. I really don't know why. Any ideas on a better query that I could write, that was the only way I could think of. Strange cause some people get updated right away and other don't at all?

The Software Inventory must be run AFTER the software is updated for the new data to be placed in the database. Check the frequency of your Software Inventory as until you do a new inventory to pick up the new information SMS won't update the Collection.
 

Collections and Subcollections

Contributed By: Cliff Hobbs [MVP SMS]
So you're confused over how Collections and Subcollections work. Let's try to explain the difference and how they work...  [Go to article]
 

Creating a Collection for Laptops

Creating a Collection from a text file

You can use the BackOffice Resource Kit 4.5 utility 'MakeColl.exe' to create a Collection from a text file. The text file can contain NetBIOS computer names or IP addresses.

You can also create your Collection in Excel or other applications, save them as text files and then use 'MakeColl.exe' to create the Collection in SMS.
 

Displaying the Collection ID in the SMS Administrator console

Contributed By: Cliff Hobbs [MVP SMS]
If you run SMS Administrator with a commandline like the one below:
"\SMSADMIN\bin\i386\sms.msc /SMS:NodeInfo=1"

you'll get an extra tab called 'Node information' - this will give you (among other things) the Collection or Package IDs.

• If you use the above command line, the 'Node information' tab appears as the last tab.
• If you use the 'NodeInfo=2" command line, the 'Node information' tab appears as the first tab.

Importing Machines into a Collection

Contributed By: Paul Thomsen [MS]
Wondering if there’s a way to import machines into a Collection? Here’s one way…  [Go to article]
 

Is there a way to create a collection based on a list of users rather than systems using Makecoll?

Yes - use the 'UserColl' tool available from 1E at:

http://www.1e.com/Downloads/FreeTools/Index.aspx?optionselected=SMS%20Tools

This tool was created by changing the 'MakeColl' source code which is in the Platform SDK which is available from:

http://www.microsoft.com/smserver/downloads/20/tools/sdk.asp

Here is a list of sample tools in the Platform SDK:

MOF Examples: Two examples of MOF files that can be used to create Packages and/or Programs

VB Examples:

• AssetWiz - The Asset Information Wizard demonstrates how to extend SMS Client Inventory via the SMS SDK. Basically it's a 'User Info' gathering tool that extends Hardware Inventory via the WMI method as opposed to writing a MIF.
   
• CollTree - The CollTree sample allows Collection hierarchies to be edited by a very simple Drag and Drop system. CollTree first connects to a provider via the information collected when the Connect button is clicked. CollTree then creates, modifies, and deletes instances of SMS_CollectToSubCollect when collections are dragged and dropped above and below other collections.
   
• ProgEdit - This tool allows the user to Create, Modify, and Delete instances of SMS_Program and attach them to an instance of SMS_Package. So you can create Programs for Packages via the GUI interface.
   
• SiteCtrl - Provides an example of how to programatically edit the values in the Site Control file. Not one for testing on your production servers :-)
   
• StatTray - Creates an icon in the System tray which changes according to the status of the SMS Site at which the tool is pointing.

VC++ Programs:

• CustMsg - Demonstrates how to generate a custom Status Message
   
• InvList - Queries a site server for various Inventory items (command Line)
   
• MakeCap - Makes a system available to SMS as a CAP (command line)
   
• MakeColl - Creates collections of system resources based on input from a text list of systems (command line).
   
• MakeDDR - Demonstrates the functions used to generate a DDR (command line)
   
• MakeDist - Similar to MakeCAP - but makes a DP! (command line)
   
• MakeDPG - Creates Distribution Point Groups from the command line
   
• PackList - Queries and lists Packages and programs (command line)
   
• SiteBoun - Imports/Exports site boundaries to/from a text file (command Line)
   
• StatMsg - Generates custom Status Messages (command line)

Other Examples:

• Collmembers - DHTML example that lets the user view members of the default collections
   
• DiscData - VBS example that displays discovery data for a given system
   
• InvChart - Excel example that creates a spreadsheet of inventory statistics

Is there an Easy way to Change the Refresh Interval for Several Collections?

Moving/Copying Collections

Is there any quick and easy method of moving Collections, or copying a Collection to another location? I created a list of Collections based on physical location, all under the Collections root. Since then, I have a preference to create these Collections underneath a subcollection from the root collections option.

Currently, I have:

Collections

- [Location1]
- [Location2]
- [Location3]

I would prefer to have:

Collections

+ [Locations]

- [Location1]
- [Location2]
- [Location3]

making it possible to minimise Collections that aren't being used, and clean up the console for admin work. I could export each existing Collection, and re-import them, but I have created quite a few, and if there is an easier way, I would be interested to hear it. (I fully expect to have to export/import however!)

Although I could be wrong, you may want to try this. Create your '[Locations]' Collection, and then right click and go to 'New | Link to Collection'. You can then choose '[Location1]' and click 'OK'.  It will create a subcollection under '[Locations]' for '[Location1]'.

From what I understand when this was discussed before, this actually creates the subcollection - it doesn't create a 'pointer'/ link to the old Collection, which I originally thought was the case.  If this is true, then you should be able to delete your original collection and keep the newly 'moved' one.
 

Organising collections

Does anyone have any suggestions for the best way to organise Collections? We're just starting out with Software Distribution and already we can't see the wood for the trees. I've heard that creating several layers of sub-collections slows things down to a virtual standstill - does anyone have any experience of this?

Make as many Collections as you like. Just keep in mind that all Collections are passed down to all child sites, however Service Pack 2 greatly reduces the bandwidth utilised in this procedure. Also I would recommend you change the 'update interval' for all Collections from the default '1' or '2' hours to every '1 day'.

Depending on the needs of the company you're at, you could have Collections for all sorts of things. I've had main collections like 'Subnets', 'Operating Systems', 'Packages' which are just empty collections. Then underneath the 'Subnet' Collection for example, I'd have a subcollection for each and every subnet that is in the company. The 'Operating Systems' subcollections would be self-explanatory, and the 'Packages' Collection would have a subcollection for each package that is available for sending to clients. I advertise to the subcollection 'Lotus Notes 4.6.2' and then when I want someone to receive that package, I put them in that collection (or put another collection in that subcollection). This way, if I want to make broad sweeping changes to the package, I only have to advertise it to that one subcollection and everyone that I put into it gets the package.

You can document existing collections, packages, adverts, etc using the 'Site Properties Manager' (SMSSPMAN.EXE) from the BackOffice Resource Kit.
 

'Padlocks' appearing on my Collections

Contributed By: Cliff Hobbs [MVP SMS]
That's the way it is supposed to work. All standard Collections and all other Collections defined at the Central site are 'owned' by the Central site and can only be modified via the Central site, hence the 'locks' on the child Primary site. Any Collections created on the Central site 'flow down' the SMS hierarchy, so if you create a Collection on a child site and then create a Collection on the Parent/Central site with the same name, the Collection on the Child site gets overwritten with the one from the Parent/Central.
 

Recovered NetWare server no longer appears in collections

Stop and start the 'Collection Evaluator' service.
 

Refreshing Collection Information on a Child Site

Removing a large number of machines from the SMS database

Is there an easy way to delete a large number of machines from the SMS database without having to do them individually?

Yes - use the 'Delete Special' option. First create a Query/Collection that contains the machines/resources you want to delete from the SMS database. Once the Collection contains all of the machines/resources you want to delete, right-click on that Collection and select 'Delete Special'. Click 'Yes' to confirm the deletion. The machines/resources in the Collection are deleted from that Collection and from the SMS database - use this with care..!!
 

Removing Locks on Collections and Adverts at a Child Site

Contributed By: Cliff Hobbs [MVP SMS]
If you need to remove the locks on a Collection/ Advert on a Child site then these VBScripts from Dennis Abbott will do the trick…  [Go to article]
 

SMS says Collection already exists when trying to create a new Collection

The Collection could have been created without getting tied to the invisible 'COLLROOT' Collection, making it effectively invisible. You can remove it using the WBEM SMS interface, but you have to find the right one to delete. This script will list them all:

"Set l = CreateObject("WbemScripting.SWbemLocator")
Set c = l.ConnectServer("YOURSERVER","root\sms\site_XXX")

set rs = c.ExecQuery("select * from SMS_Collection")
for each r in rs
   WScript.Echo r.CollectionID, r.Name
next"

To delete it, you'll need to use 'WBEMTEST' (connect to the Site, query for the discovered Collection, then delete the instance). I certainly wouldn't recommend deleting it from SQL directly, as you'll leave other 'garbage' laying around.
 

What happens when I delete a client from a Collection?

When you remove a Client from a Collection are they removed from the SMS database? I have removed one of my machines from a test Collection and I can no longer find it in my 'All Systems' Collection or Query seemingly. Can anyone give me an explanation of the process that takes place when you do this?

When you delete a machine from a Collection it is deleted from the SMS database. It will resync itself on the next Hardware or Software inventory cycle.

There are differences between the 'Delete' and 'Delete Special' tasks in the MMC:

• Right clicking on a 'resource' and choosing 'Delete' will delete the resource from the SMS database
   
• Right clicking on a 'Collection' and choosing 'Delete Special' will delete all objects in the Collection from the SMS database.

To restore the entry:

If the Client software has been installed but the information reflected by the resource entry in the MMC remains incomplete or inaccurate, you can correct it by deleting the existing resource entry and copy the 'SMSDISC.DDR' file from the target client workstation's '%WINDIR%\sms\sms\core\data' directory to the Site Servers '\sms\inboxes\ddm.box' directory.

Wait a few minutes then, in the MMC, highlight the 'All Systems' Collection, right click and select 'All Tasks | Update Collection Membership'. This usually places a small hour glass over the 'Collection' icon. Right click again and select 'Refresh'. A valid resource entry should now appear.

As far as Queries go, if the query is a Direct Membership query you need to go into the 'Collection membership rules' and remove it from there. For Query based Collections, it is in the Collection because it meets the rules set in the Query so it cannot be removed until it no longer meets those requirements.
 

© FAQShop.com 2003 - 2008