I wasn't sure whether to ask this for Inventory of Deploy, but here goes.
We use collections in Inventory for collecting clients with old versions of software. For example, Skype.
Application version lower than $(AppVerSkype)
There are schedules in Deploy to automatically deploy the latest version to these collections with the heartbeat option.
Now we also use a 3 day package update approval window.
This causes the following when a new package is released:
- Skype package is updated, but not yet approved by us
- Version variable gets updated in Inventory
- Clients with the previous version are being placed in the 'Old' collection
- Deploy schedules kicks off, but is still deploying the previous version because the newest is not yet approved
While this behaviour makes sense, it's still rather annoying. I could alter the collections, adding some static version, or disregard the built-in variables and use my own. The problem is that this creates a lot of extra work that I want to avoid.
Anyone else have any idea how I would go about this?
Please sign in to leave a comment.