/build/static/layout/Breadcrumb_cap_w.png

Grouping managed installations

I've created managed installs for our basic software needed on all staff computers. I'm trying to find a way to create a label to be able to deploy all the software to a freshly imaged computer. I also have a need for a  basic group for all public computers.  I just need a point in the right direction and I can research more in-depth, kind of a geek that way. I've only been using KACE for about 6 months, but have been working with computers since the DOS and Win 3.11 days. I love automation and I know with KACE this should be possible, but I have not had enough experience with it to begin to tap its full resources. 

Thanks in advance,

Chris

Update: This is some of our basic installs. I'm looking to create a group to add newly imaged computers. I can then update individual software and add back to the group as needed when updates or modifications are needed. I'll need several groups like this Staff, Public User, and VPN clients possibly.


Asked 5 years ago 465 views
0 Comments   [ + ] Show comments

Answers (2)

Posted by: brucegoose03 5 years ago
5th Degree Black Belt
1

Yeah you can do a Custom Inventory Rule that pulls back the installed on date. 


ShellCommandDateReturn(cmd /q /c powershell.exe -command "gcim Win32_OperatingSystem | select InstallDate | format-table -HideTableHeaders")


It will look like this:

f7Pnnns2K620UlPCudnPOrwrnLvQjrz9IUCAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAIH5ICCgOx+Okm0kQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBBYlAK33HJLc+GFFzaXXXZZWzm3IHSHd1XOLTJeCRAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIDAzAgI6M6Ms7UQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQGEngrLPO6jlfCe9efvnlzZIlS3pOYyQBAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECAwPQICutPjaqkECBAgQIDANAqcfvrp07h0iyZAgAABAgQIECBAgAABAgQIECAwfwT8v7L5c6xsKQECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgsLIG7LKzdsTcECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIEpldABd3p9bV0AgQIECBAYAoFNttssylcmkURIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQGE1ABd3R3MxFgAABAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECCwSAUEdBfpgbfbBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECowkI6I7mZi4CBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAIFFKiCgu0gPvN0mQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAYTUBAdzQ3cxEgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECBAgQIAAAQIECCxSAQHdRXrg7TYBAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECBAgMBoAgK6o7mZiwABAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECBAgAABAgQIECBAYJEKCOgu0gNvtwkQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQIECAAAECBAgQ

Posted by: chucksteel 5 years ago
Red Belt
1

Why bother with just targeting new computers? The appliance won't re-install the applications unless they get removed from the client. I would recommend creating your labels for your machine groups and then apply those labels to the appropriate managed installs and the appropriate computers. When new versions are released, update the managed install to reference the new version of the software and the appliance will start deploying the new version to the clients.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ