What is the difference between checkin and update?
Update = Updates the current branch you have it installed in
Check in = you can put it into a different branch for testing, such as evaluation instead of overwriting your current branch.
Consider doing pilot group.
An option is to check in the full product for new machines, so they would pilot it. You can also checkin the patch 7 into evaluation and have a subset of you devices update virusscan code from eval
If it was me, I would check in Patch 7 to the Evaluation Branch. In our environment, I use Policy Assignment rules along with Tags to deploy the patch out to only systems I want to test with.
We use a TAG called "Test Patch 7".
Create an agent policy that pulls the patches from the Evaluation branch.
Create a Policy Assignment rule that uses that modified agent policy and also use the TAG called "Test Pacth 7".
When we assign this tag to a system, it will get that modified agent policy which tells it to pull the patch from the Evaluation branch.
Thank you to all the helpful comments, i noticed next to management/report extensions there is only update, is it safe to do this prior to checking in the new branch?
It's extremely unlikely that checking in an updated extension will cause issues, unless perhaps you're running a version of the software that the extension specifically doesn't support (which is, from I've seen, very rare). I'd suggest checking in the extension updates before deploying the software to any endpoints.
When an extension check-in fails, it fails big time. If it can't roll back, better be sure you have a good backup. Extensions are pieces of software that run on your ePO application server so it is an all or nothing thing that affects you database structure.
It is one of the riskiest thing you can do in ePO.
Thanks both, so recommendations before 'updating' these extensions is a snapshot of the virtual machine and a database backup?
Logically I'm thinking I would need to upgrade the extensions first and then checkin the new branch of VSE, is this correct?
As far as a plan goes:
1. Backup EPO database / Snapshot EPO VM
2. Update extensions via EPO
3. Check in new branch of VSE
4. Manually deploy this to selected machines to test
Let me know your thoughts
Sounds like a good plan to me.
Disabling master repository pull tasks is also a best practice.