<div>
<div class="content wysiwyg-content">
When I deploy a new version of a software package, I add it to the <i>same</i> gpo, and declare which old packages are replaced by this one, so windows installer knows that it's an update, not an additional package.<br />
<br />
How long should the old versions remain in the gpo?<br />
Must it stay until no machine has it installed any more?<br />
When happens if it's removed earlier?<br />
What happens if the msi-files are removed earlier, how long are they needed?
</div>
</div>


When I deploy a new version of a software package, I add it to the same gpo, and declare which old packages are replaced by this one, so windows installer knows that it's an update, not an additional package.

How long should the old versions remain in the gpo?
Must it stay until no machine has it installed any more?
When happens if it's removed earlier?
What happens if the msi-files are removed earlier, how long are they needed?

When to remove old software packages from gpo distribution?

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.