Best way to use both Managed installs and Patching functions of K1000
Hi all,
I have been recently testing the Patching functions of the K1000 and I feel like I have a grasp of how it works. I would like to start using the patching functions to keep things like Adobe Flash, Firefox, and Adobe Reader up to date without having to manually create updated deployments for this software.
My question is how do you keep Managed installs and Patches from overwriting each other? For example, I am have been testing with WinSCP. Here's a rundown of how everything was set up:
Managed Install: WinSCP 5.5.5
I don't my setup is completely right at the moment. Any advice on how to modify my setup?
I have been recently testing the Patching functions of the K1000 and I feel like I have a grasp of how it works. I would like to start using the patching functions to keep things like Adobe Flash, Firefox, and Adobe Reader up to date without having to manually create updated deployments for this software.
My question is how do you keep Managed installs and Patches from overwriting each other? For example, I am have been testing with WinSCP. Here's a rundown of how everything was set up:
Managed Install: WinSCP 5.5.5
- Deployed to a Manual Label called "Deploy Winscp"
- Deployed to a Smart Label that searches for any computer with WinSCP in the software title
Latest version for WinSCP in the patches section is WinSCP 5.7.5
My test computer with WinSCP 5.5.5 would be updated through the Patching function to WinSCP 5.7.5 but then later, the Managed Install would install the old WinSCP 5.5.5. The Patch and Managed installed would keep fighting itself until the patch function stopped after 5 tries.
I don't my setup is completely right at the moment. Any advice on how to modify my setup?
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
rockhead44
9 years ago
The easiest way would be to modify the smart label your Managed Install uses to identify machines that contain WinSCP but whose software version is below WinSCP 5.5.5 to avoid that issue. That way machines at or above 5.5.5 will not be in that smart label.
Why are 2 labels tied to the Managed Install?