<div>
How are your subnets setup? &nbsp;We have 10 sites to target specific sites, I use the subnet for that particular site, for example 10.1.1.xx 
 
We could also use computer name for the site as our computer names are setup as sitecode-compcode-assetnumber, again this will depend on how your computernames are setup in the first place. 
 
Subnets are usually the best method if your network has been designed in this manner, for instance, 10.1.1-10 maybe at one site than we may have four different offices broken up into 10.1.1.1-2, 10.1.1.3-5 etc.. allowing us to deploy to only those offices. 
 
Hope that made sense, write back if you need clarification. 
 
Cheers
</div>

<div>
I have subnet setup for each office. So that is not an issuee. I have some questions that are raised to me about deploying 2k7 compatibility on all the offices. can you please look at time and tell me the right solution to these comments. 
 
Is the requirement of All x86 Windows XP l a minimum requirement (ie if XP SP2 etc will this still run ?) 
1) &nbsp; &nbsp; &nbsp; Set a Maximum Allowed Time ( which will allow other packages to install a bit quicker even if this one fails) 
 
2) &nbsp; &nbsp; &nbsp; Use of the condition Whether or not a user is logged on&nbsp; &nbsp; 
 
&nbsp; 
 
Also future enhancements to all packages should include the use of dynamic collections so we can target reimaged machines ect 
 
I understand the need to deploy it across the whole company, just questioning the deployment method. 
 
Starting at one small office then increasing the size of the rollout as it rolls through would give some measure of protection if there are issues. 
 
&nbsp;Also it looks like you are going to assign this only once. 
 
Are you planning a follow-up assignment to catch those that fail? 
 
In fact there is nothing in the CR that would suggest checking on the success of the roll out 
 
 
These are the comments not sure how to answer them. 
 

</div>

<div>
Sorry for the delay 
 
If Microsoft specifies that an update is for all Windows XP Systems than it includes all Windows XP including SP1, SP2 and now SP3. 
Set a maximum allowed time isn't really required, the install will start, if it fails it will fail and then go to the next advertisement, however since this is usually a one off anyway, I assume you're associating it to computers not users, than it will run once for the machine and it's done. 
Use of the conditon whether or not a user is logged out, although it's preferable that the user isn't logged in, it never works out that way, so I don't usually flag this, however what I normally do is in the advertisement, schedule it to install after a user has logged on, which basically makes it run immediately after there logon. 
 
Having dynamic collections is definately a positive thing, what I tend to do is make my query for example with subnet 10.1.1 and also if a program does not exist in Add/Remove Programs I than schedule the collection to update at least once a day, which will basically remove computers that have installed the product. 
 
With regards to testing, I have a test collection made up of a number staff at different locations, with different responsiblities, around 20 users, this includes receptionists, personal assistants, helpdesk, normal staff, they are basically my testers, although I usually test this in a Proof of Concept lab, I find that it's best to test in the live environment on a limited scale first before deploying across the enter companies wan. 
 
&quot;Also it looks like you are going to assign this only once.&quot; As I mentioned by creating the dynamic collection, it will only install on systems that haven't got the software. 
 
&quot;Are you planning a follow-up assignment to catch those that fail?&quot; 
Well yes you can, but in general as long as 95% of the machines update, I consider it a successful deployment, the remaining 5% usually have other problems either they don't have Office 2003 or maybe there SMS Client isn't working. &nbsp;You can usually gather this information from your reports or queries, in fact after your rolled out the software you should be able to view your custom collection to see who hasn't installed the product yet. 
 
Anyway sorry if I rambled on a bit, hope that helps. 
 
Cheers 
 
 

</div>

<div>
Your response is great I really appreciate your support. 
One more help I need is to create a new dynamic collection which I will link or limited to collection : Workstation Bankok. and many other collections that are already prebuilt and are already limited to All Windows workstation or Professional System. 
 
How can I create a new query that will only collect computers with Microsoft office 2003? If possible can you actually to create just one and I should be able to make more and link them to other Workstation collections that are there. 
Thanks you for your help. 
&nbsp; 

</div>

<div>
Unforunately no, you'll need to edit the collection query, otherwise your collection won't be dynamic. &nbsp;For instance having Workstation Bankok query and Microsoft Office 2003 query would provide you two different queries 
The Bankok Query would pull in all your Bankok Clients 
The Microsoft 2003 Query would pull in all Systems with Microsoft Office 2003. 
 
So here's my method. 
 
Under Queries create a new query, name it: !Windows XP with Office 2003 
NB: The !&quot;exclamation mark&quot; just places the query at the top of the list, but isn't required. 
 
Under Properties click &quot;Edit Query Statement&quot; button 
Click &quot;Show Query Language&quot; button 
 
Paste the attached code snippet below into the query. 
Click &quot;Show Query Design&quot; button to see what this does. 
 
As you can see I've created a query against: 
Systems where the Operating System and Name is &quot;LIKE&quot; %Workstation 5.1% &quot;AND&quot; these systems have an IP Address &quot;LIKE&quot; 10.1.%.%&quot; AND these systems have under Add/Remove Programs &quot;Microsoft Office Professional Edition 2003&quot; 
 
You should be able to run this query to view the systems that fall under this query. 
 
Now when you want to setup &nbsp;a new collection for say Bankok which lets say has a subnet of 10.2... 
Create your new Collection name it &quot;Microsoft Office 2007 Compatibility Pack&quot; 
NB: Do not add machines to this collection, it's basically just to keep your Collections tidy. 
Create a new SubCollection name it Bankok 
Select Membership rules 
Click &quot;Query Membership Properties&quot; button - to create a new query 
Type&quot; Bankok Windows XP Systems with Office 2003&quot; or something similar 
Click &quot;Import Query Statement&quot; button 
NB: If you named the Query with ! it should be at the top of the list otherwise, scroll down until you find the query you just created. 
Click OK 
Click &quot;Edit Query Statement&quot; button 
Click &quot;Show Query Language&quot; button 
Now change 10.1.%.% to 10.2.%.% (assuming 10.2 was Bankok subnet) 
Click Apply - OK 
Make sure &quot;Update this collection on a schedule&quot; is checked, change the schedule as required. 
 
Create a new Collection under &quot;Microsoft Office 2007 Compatibility Pack&quot; named xyz and do the next site etc.. 
 
Hope that made sense. 
 
Cheers 

<pre><code class="code-1 nolinks" id="code-122336">select distinct SMS_R_System.Name, SMS_G_System_NETWORK_ADAPTER_CONFIGURATION.IPAddress from SMS_R_System inner join SMS_G_System_NETWORK_ADAPTER_CONFIGURATION on SMS_G_System_NETWORK_ADAPTER_CONFIGURATION.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like &quot;%Workstation 5.1%&quot; and SMS_G_System_NETWORK_ADAPTER_CONFIGURATION.IPAddress like &quot;10.1.%.%&quot; and SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = &quot;Microsoft Office Professional Edition 2003&quot;
</code></pre>
</div>

<div>
I have done the query part and it went well. &nbsp;Thank you so much sir. I really salute you. 
I just have a one more question when you choose the operating system and name is &quot;&nbsp;Like %workstation 5.1% &quot;&nbsp; 
%workstation 5.1% what does it mean? is windows XP refered to as workstation 5.1? 
sorry for my ignorance. 
Thanks, 

</div>

<div>
Mr. Matrixnz is the best and he assisted / supported me in my quest to fullest ability. 
Thank you again for a wonderful job done.
</div>

<div>
Hi! Can you help me . They want some change to be done to the collection and its subcollection. Here is what they want: 
 
So this is how it should be setup, 
Your top level collection Global Collection  MS 2K7 Compatibility Pack&nbsp;should have the following member ship rules. 
Have Windows XP as the Operating System 
Have Office 2003 Installed and not have the Compatibility Pack Installed. 
 
Your child collections memberships should be 
IP Address subnet of the office you are rolling out to 
The membership be limited to the parent collection Global Collection  MS 2K7 Compatibility Pack 
&nbsp; 
Can assist in redesigning the Global collection and the sub collection. 
&nbsp; 
Thanks, 

</div>

<div>
Hi smartmanwin 
 
Quite sound reasoning but very difficult query, although it may seem like you could simple have the collection 
LIKE &quot;%Workstation 5.1%&quot; and 
EQUAL &quot;Microsoft Office Professional Edition 2003&quot; and 
NOT EQUAL TO &quot;Compatibility Pack for the 2007 Office system&quot; 
unfortunately it doesn't work because NOT EQUAL TO basically looks at each &quot;Display Name&quot; and compares this against the name &quot;Compatibility Pack for 2007 Office system&quot; so when it comes across &quot;Adobe Reader&quot; for example it compares the names and than includes the machine inside the collection. &nbsp;Ahh I hope that makes sense. 
 
Anyway there is a way but as I mention it's a difficult query, basically what we do is query against another query within the same query by using &quot;not in&quot; &nbsp;So if you look at the attach code snippet below, that's basically the query you need to use for the top level collection. &nbsp;Here's what it does. 
 
This is the standard information each collection includes when you click on a collection 
-------------------------------------------------------------------------------------------------------------------------------------------------- 
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 
-------------------------------------------------------------------------------------------------------------------------------------------------- 
 
This is where it gets the attributes above from 
-------------------------------------------------------------------------------------------------------------------------------------------------- 
from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId 
-------------------------------------------------------------------------------------------------------------------------------------------------- 
 
This is our first part of the query where we want to only query Windows XP Systems with Microsoft Office Professional Edition 2003. 
-------------------------------------------------------------------------------------------------------------------------------------------------- 
where SMS_R_System.OperatingSystemNameandVersion like &quot;%Workstation 5.1%&quot; and SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = &quot;Microsoft Office Professional Edition 2003&quot; 
-------------------------------------------------------------------------------------------------------------------------------------------------- 
 
This is the second part of the query where we actually check to see that the computer isn't found within this sub query where the Operating System is Windows XP and Compatibility Pack for the 2007 Office system is installed. 
-------------------------------------------------------------------------------------------------------------------------------------------------- 
and SMS_G_System_SYSTEM.Name not in (select SMS_G_System_SYSTEM.Name from &nbsp;SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like &quot;%Workstation 5.1%&quot; and &nbsp;SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = &quot;Compatibility Pack for the 2007 Office system&quot;) 
-------------------------------------------------------------------------------------------------------------------------------------------------- 
 

<pre><code class="code-1 nolinks" id="code-124859">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 inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like &quot;%Workstation 5.1%&quot; and SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = &quot;Microsoft Office Professional Edition 2003&quot; and SMS_G_System_SYSTEM.Name not in (select SMS_G_System_SYSTEM.Name from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like &quot;%Workstation 5.1%&quot; and SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = &quot;Compatibility Pack for the 2007 Office system&quot;)
</code></pre>
</div>

<div>
Oh and the subcollection would just be the following (see attach code snippet) and limited against the collection above. 
 
Cheers 

<pre><code class="code-1 nolinks" id="code-124864">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_NETWORK_ADAPTER_CONFIGURATION on SMS_G_System_NETWORK_ADAPTER_CONFIGURATION.ResourceID = SMS_R_System.ResourceId where SMS_G_System_NETWORK_ADAPTER_CONFIGURATION.IPAddress like &quot;10.1.%.%&quot;
</code></pre>
</div>

<div>
<div class="content wysiwyg-content">
Hi! I would like some help on SMS collection creation. I am trying to deploy a package MS 2007 compatibity pack. to all regional offices. Basically I want to target the computer that have Office 2003 installed. But in each region and office. The regions are Asia, Europe and middleeast. and each region is again divided to respective offices. 
 
I want to do a stage deployment but I am not sure how to start it with the collections. 
 
Thanks, 
</div>
</div>

Hi! I would like some help on SMS collection creation. I am trying to deploy a package MS 2007 compatibity pack. to all regional offices. Basically I want to target the computer that have Office 2003 installed. But in each region and office. The regions are Asia, Europe and middleeast. and each region is again divided to respective offices. 

I want to do a stage deployment but I am not sure how to start it with the collections. 

Thanks, 

Creating a Collection and subcollection on SMS

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.