anes

Hi All, im have been doing some vb-scripting of sccm for a while and came across an interesting issue. According to MS http://msdn.microsof...y/cc143262.aspx one must create both the collection as well as the corresponding SMS_CollectToSubcollect object: ' Create the collection. Set newCollection = connection.Get("SMS_Collection").SpawnInstance_ newCollection.Comment = newCollectionComment newCollection.Name = newCollectionName newCollection.OwnedByThisSite = ownedByThisSite ' Save the new collection and the collection path for later. Set collectionPath = newCollection.Put_ ' Define to what collection the new collection is subordinate. ' IMPORTANT: If you do not specify the relationship, the new collection will not be visible in the console. Set newSubCollectToSubCollect = connection.Get("SMS_CollectToSubCollect").SpawnInstance_ newSubCollectToSubCollect.parentCollectionID = existingParentCollectionID newSubCollectToSubCollect.subCollectionID = CStr(collectionPath.Keys("CollectionID")) ' Save the subcollection information. newSubCollectToSubCollect.Put_ Accidentally it comes to an error (general failure) in the line "newSubCollectToSubCollect.Put_" Because of that collection is not shown in the console and I had to adjust the DB directly in order to get it shown. I have a feeling, that it happens because the creation process has not been completed yet when the second Put_ call comes. And the questions 1. Have your ever seen such a behaviour? 2. Would the change to AsyncPut_ resolve the problem? Thanks in advance.

Hi Peter, OK Hmmm What machine (where the action starts) do you mean? 1. SCCM client 2. SCCM site server or 3. machine where the SCCM console runs (if the download action was started from within that console)

Hi all, we observe an interesting effect with MS-updates if the site server and the software update point are installed on different machines. The updates' definitions are synchronized via SUP. However the updates themselves (e.g. cab-files) get downloaded by the site server directly - not via SUP! The SCCM version is 2007 R3. Has someone seen that already?

Hi all, it is not very clear to me, how the update SP2->R3 functions when there are many site servers. As an example: Srv_1: Win2k8R2 + MS SQL 2008 R2 (Site DB Server) Srv_2: Win2k8R2 + SCCM 2007 SP2 (Site Server + MP + DP) Srv_3: Win2k8-32bit + SCCM 2007 SP2 (RP) Srv_4: Win2k8R2 + SCCM 2007 SP2 (SUP) All four server build a single SCCM site. The second one was installed using SP2-DVD, all others from the site server. Do the site systems get automagically updated during the site server update? Or should they be updated somehow independently on the site server? Thanks in advance!