New Post: New application branch deployment best practises

Sorry if the title is inappropriate, I did my best and find no better way.
Here is the scenario
Application version 11 is deployed in the enterprise. Everytime a new update (.msp) is released it is published in Wsus Package Publisher and it supersedes all previous ones.
Application version 12 is released while Application 11 is still maintained and it will get new updates.
The enterprise cannot migrate to Application 12 entirely because it doesn't support the legacy windows xp.
So the idea is the following:

• all new computers will migrate to Application 12
• legacy xp computers will get the .msp update for version 11
  

Currently the windows 7 and 8 computers have application 11 and its last update approved.
Which is the best way to achieve the goal ?
I suppose it is better create a new Product name for Application 12 and change the approval for application 11 removing all computers which are not windows xp.

Any suggestions ?

Thanks
Filippo

P.S.
Any reference to Adobe Reader Dc is purely casual.