Managed installs/labelling strategy (help needed)
We've been running fairly well with our win 7 deployment using the following strategy
scripted install of machine, after machine is joined to domain and named all business standard software is deployed via managed installs. However, I'm now running into a couple hurdles which I'll try to describe here
using example of adobeX
Our labelling setup, I previously had software deploying to all machines that do not have AdobeX. This worked OK, but if I patch adobe and it goes to 11 or some other version, the label will recatch it again and re-deploy the older version.
to fix this, I target my labels in the following way
machine smart label - M_*Installs* Requires Adobe Reader
- is win7
- is x64
- doesn't have 'Adobe Reader' (which catches any version, we handle the rest via patching)
- is on the domain (due to we don't want installs pushing to machines before the deploy process is finished)
the effect is, once a machine is inventoried after the deploy, this label no longer applies. Which is great, patching can go to any version and the software never gets redeployed.
However now I have the following situation
we have x64 machines here and they require 2 versions of java, both 64bit and 32bit
I can't find a way to target a machine with a label to show that it needs 32bit version of java. The smart labels only allow 4 fields as well.
This is going to be the same for anything which requires double installs (flash player for x64 and x86 browsers)
How are other people doing this?
scripted install of machine, after machine is joined to domain and named all business standard software is deployed via managed installs. However, I'm now running into a couple hurdles which I'll try to describe here
using example of adobeX
Our labelling setup, I previously had software deploying to all machines that do not have AdobeX. This worked OK, but if I patch adobe and it goes to 11 or some other version, the label will recatch it again and re-deploy the older version.
to fix this, I target my labels in the following way
machine smart label - M_*Installs* Requires Adobe Reader
- is win7
- is x64
- doesn't have 'Adobe Reader' (which catches any version, we handle the rest via patching)
- is on the domain (due to we don't want installs pushing to machines before the deploy process is finished)
the effect is, once a machine is inventoried after the deploy, this label no longer applies. Which is great, patching can go to any version and the software never gets redeployed.
However now I have the following situation
we have x64 machines here and they require 2 versions of java, both 64bit and 32bit
I can't find a way to target a machine with a label to show that it needs 32bit version of java. The smart labels only allow 4 fields as well.
This is going to be the same for anything which requires double installs (flash player for x64 and x86 browsers)
How are other people doing this?
0 Comments
[ + ] Show comments
Answers (12)
Please log in to answer
Posted by:
steelc
12 years ago
The smart label form only shows four fields, but once it is created you can edit the SQL code in label management. I'm not sure if that helps or not.
Posted by:
dogfish182
12 years ago
actually that does help a bit, I was staring at deployments for faar too long today and it didn't occur to me. Thanks.
Still would like to hear how others address these issues though, I find the smart label builder thing a bit strange, I can edit the SQL code (and do) but that's annoying and not very quick either. 10 fields that you can consistantly go back and use the builder to edit would just make so much sense.
Still would like to hear how others address these issues though, I find the smart label builder thing a bit strange, I can edit the SQL code (and do) but that's annoying and not very quick either. 10 fields that you can consistantly go back and use the builder to edit would just make so much sense.
Posted by:
ronco
12 years ago
dogfish,
You also have the ability to create nested labels. For instance, you could create a Smart Label containing the first four criteria you need. Then create a second Smart Label, making its' first criteria Label Names contains <the prior label>, and adding whatever add'l criteria you need. You'll want to make sure that the Label Order always keeps the initial label "in front of" the second one. r2
You also have the ability to create nested labels. For instance, you could create a Smart Label containing the first four criteria you need. Then create a second Smart Label, making its' first criteria Label Names contains <the prior label>, and adding whatever add'l criteria you need. You'll want to make sure that the Label Order always keeps the initial label "in front of" the second one. r2
Posted by:
darkhawktman
12 years ago
Here is how I'm getting around the whole issue of updating software and making sure that the managed install doesn't redeploy. Here is how I'm deploying Adobe Reader X version 10.1.1
First I created a new software item. In the Custom Inventory Rule I put this information in:
RegistryValueGreaterThan(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1033-7B44-AA1000000001}, DisplayVersion, 10.1) AND RegistryValueLessThan(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1033-7B44-AA1000000001}, DisplayVersion, 11)
So if I have a machine that is set to get adobe reader the kbox checks the above registry key to see which version of reader is installed. If the version number is greater than 10.1 and is less than 11 then it won't install reader. This way you don't have to monkey around with smart labels or nested labels.
First I created a new software item. In the Custom Inventory Rule I put this information in:
RegistryValueGreaterThan(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1033-7B44-AA1000000001}, DisplayVersion, 10.1) AND RegistryValueLessThan(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1033-7B44-AA1000000001}, DisplayVersion, 11)
So if I have a machine that is set to get adobe reader the kbox checks the above registry key to see which version of reader is installed. If the version number is greater than 10.1 and is less than 11 then it won't install reader. This way you don't have to monkey around with smart labels or nested labels.
Posted by:
ronco
12 years ago
darkhawktman,
Excellent! A Custom Inventory Rule is a great choice when dealing with sub-version numbers. r2
Excellent! A Custom Inventory Rule is a great choice when dealing with sub-version numbers. r2
Posted by:
dude
12 years ago
These are all great working suggestions!
OR...the folks at Kace could make our lives easier and allow us to simply enter more than 4 criteria when creating Smart Labels.
*winks*
OR...the folks at Kace could make our lives easier and allow us to simply enter more than 4 criteria when creating Smart Labels.
*winks*
Posted by:
ronco
12 years ago
dude,
Hey, you're preaching to the choir here, mate! [;)] I'm a trainer, not a developer. r2
Hey, you're preaching to the choir here, mate! [;)] I'm a trainer, not a developer. r2
Posted by:
cblake
12 years ago
Believe us Dude- we're on your side there. The issue at hand is the limitation of the browser; the character limit on URL's binds us and the SQL is passed to the URL on creation and testing. Nested labels is a workaround; although editing the SQL directly is best. Nested labels can lead to mistakes, misues, and bad timing causing things to misfire. It's certainly a valid workaround if you aren't comfortable with some SQL-fu, but be prepared to be patient if you're using that method, and I'd highly recommend some serial number scheme on your labels so you can make sure that your nesting "master" only gets exactly what you want. Adding a serial number scheme or something like that to them gives you less room for error because you have to be more explicit to include them.
AFAIK engineering is working on more query options as well, but go vote it up at http://kace.uservoice.com/forums/82699-k1000
AFAIK engineering is working on more query options as well, but go vote it up at http://kace.uservoice.com/forums/82699-k1000
Posted by:
dogfish182
12 years ago
thanks for the responses all, I"m going to test a couple of options this week and will update. I think we are going to go the route of editing the SQL to get what we want.
Posted by:
Tylerh
12 years ago
Any update on how Inception labels (Nested labels) work for you or anyone for that matter?
I am running into the same problems and want to know if I need to learn some SQL or not.
I am running into the same problems and want to know if I need to learn some SQL or not.
Posted by:
dogfish182
12 years ago
I don't (and won't) use nested labels. Because if you're using that for managed installs, then you are checking if 'machine is labelled with label X' and you've created them, then the machine won't actually use that 2nd label until its second inventory. Because on the first time it isn't a member of 'label x' so it will only be the second inventory when that criteria is satisfied and it gets the second label.
When we do deployments I want the machine to deploy from the k2000, then install and then immediately run a checkin and push everything it's supposed to, right away. I tend to copy/paste from other labels and just 'learn sql' like that. I don't have time to really look and understand it, but I can copy/paste things well enough. More than 4 fields would be useful but apparently browser restrictions :(
we get quite good at using 4 fields to get what we want as well now....
When we do deployments I want the machine to deploy from the k2000, then install and then immediately run a checkin and push everything it's supposed to, right away. I tend to copy/paste from other labels and just 'learn sql' like that. I don't have time to really look and understand it, but I can copy/paste things well enough. More than 4 fields would be useful but apparently browser restrictions :(
we get quite good at using 4 fields to get what we want as well now....
Posted by:
darkhawktman
12 years ago
ORIGINAL: dogfish182
I don't (and won't) use nested labels. Because if you're using that for managed installs, then you are checking if 'machine is labelled with label X' and you've created them, then the machine won't actually use that 2nd label until its second inventory. Because on the first time it isn't a member of 'label x' so it will only be the second inventory when that criteria is satisfied and it gets the second label.
When we do deployments I want the machine to deploy from the k2000, then install and then immediately run a checkin and push everything it's supposed to, right away. I tend to copy/paste from other labels and just 'learn sql' like that. I don't have time to really look and understand it, but I can copy/paste things well enough. More than 4 fields would be useful but apparently browser restrictions :(
we get quite good at using 4 fields to get what we want as well now....
Are you Ordering your Smart Labels? I have a few instances where I'm using nested labels for various things and if you order your labels properly you don't need to inventory multiple times to apply all of the labels.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.