This is a scenario I've ran into more when testing application deployments rather than in production but I'm still looking for clarification.
Background:
I have a mix of both x86 and x64 installations of Office 2010. I would like to update some of these to Office 2013. Because I don't know what bitness of Office might be on a particular machine I've:
1. Created an application deployment for Office 2013
2. Created two different deployment types for each bitness
3. Created global conditions to check for the bitness of the installed Office 2010 suite and set those as requirements for the deployment types for the respective bitness of Office 2013.
Since I've created two different deployment types and set their content to be only the files for their respective bitness the client evaluates the requirements at deployment time and only downloads/installs the content needed to upgrade that bitness of Office 2010.
This works fine in most cases. The "problem" I've run into is that on a test clients where I test both the x86 and x64 upgrades if I test the x86 upgrade first the content for the x86 version is downloaded and installed no problem. However when I uninstall Office 2013 x86 and install Office 2010 x64 to test the x64 upgrade the deployment continues to use the cached content for the x86 deployment type. It doesn't re-evaluate the requirement for the Office bitness and download the x64 deployment type content even after running an Application Deployment policy cycle.
Is this expected behavior? In production this is unlikely to ever be an issue but I'd like to know if the client should be re-evaluating the requirements after an Application Deployment Policy refresh and downloading the content for the correct bitness after realizing it doesn't have the correct content anymore.
Or do I have to clear the cache in order for the client to download the correct content?