mitchell1981 Posted October 11, 2023 Posted October 11, 2023 Hi All, Just a quick question about the correct way to handle an updated version of an application. For example, I want to update all workstations to the latest version of Cloud Drive Mapper. Until now I've always just created a completely new application and put the version number in the details. Should I actually be using a single application and putting new versions into 'Deployment Types'? Thanks.
Norphy Posted October 11, 2023 Posted October 11, 2023 I'd say that ConfigMgr is flexible enough to say that if you find a method of managing something that works for you, do it like that. That said... I would personally not use a single Application and put in different deployment types for new versions of the app. I can see that being a headache. I've always used Deployment Types to deploy the same version of the app with different options; for example with something like NetSupport I'd have one Deployment Type for computers which need the Teacher Console and another for ones which just need the agent. I would continue what you're doing with creating new Applications for new versions of a piece of software and make sure you use Supersedence rules to make sure that you always deploy the current version.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now