So how to explain this as best as possible....
First off, I have seen this "issue" since ConfigMgr 2012 RTM and I have seen it continuously through the various upgrades done on the way to ConfigMgr 2012 R2. The environment consists of a single AD domain, one ConfigMgr Primary site with 30 DP's
and 1500 computers.
Application B is created and it should supersede application A. The application is present on all computers throughout the environment. The application is distributed to all DP's. The deployment of application A is targeted to a collection containing all computers. Then the deployment of application A is deleted. Application B is then configured to supersede application A with an uninstall of application A and the deployment type is replaced with the deployment type of application B. The option that Allows users to see older deployment types is not selected. Now application B is deployed to the same collection as application A was. The deployment settings are configured with a deadline date in the future (to match the corporate maintenance window - not a ConfigMgr maintenance window), but the application should be visible for users who want to upgrade before the deadline is reached. The option of automatically upgrading any superseded versions of the application is selected. The deployment is not created as a required deployment, but only available.
What happens after the above is done is a bit odd. If I compare a application deployment that is superseded, to the Software Updates that normally have the same psychological effect on users (for anyone in IT this is common knowledge to be: Postpone and don't bug me again until deadline has passed and then becomes a forced installation/update, for about 70% of the user mass) this is not the case. After about 24 hours about every single computer that is online has received the deployment of application B and has been successfully installed. I refuse to believe that close to a 100% of the users actually select the option to upgrade application B before the deadline has been passed.
I have checked the above and it looks like it does not honor the deadline given and finds out that when it can kick of the deployment, it does.
This also happens if I don't delete the deployment of application A and leave it deployed to the same collection as the superseding application B is deployed to.
Any ideas on why I'm seeing this behavior would be greatly appriciated.
/Tom Erik