<h2>Reconciliation running for hours on Microsoft Publisher</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Description</h3><section><ul style="list-style-position: inside;"><li>Reconciliation running for hours on Microsoft Publisher</li></ul></section></div><div ><h3 >Release or Environment</h3><section><ul style="list-style-position: inside;"><li>All</li></ul></section></div><div ><h3 >Resolution</h3><section><ul style="list-style-position: inside;"><li>Check if there are any active <strong>Visual Studio</strong> entitlements.<br /><br /></li><li><strong>Visual Studio</strong> software model is a <strong>suite</strong> model which has more than 400 components and downgrades.<br /><br /></li><li>This lets the Reconciliation takes hours together to process and fail during the execution.<br /><br /></li><li>To improve performance customers may need to do following as the best practices<br /><br /> <ul style="list-style-position: inside;"><li>Add user/device allocations to your Visual Studio entitlements.<br /><br /></li><li>Add software install conditions on your Visual Studio software models.<br /><br /></li><li>Run reconciliation.<br /><br /></li></ul> </li><li>User/device allocations for Visual Studio entitlements can speed up the Reconciliation and having Install conditions on software models can improve the performance as mentioned above.<br /><br /></li><li>If the data related to user/device allocations is not available, the only options to address the issues are,<br /> <ul style="list-style-position: inside;"><li>Customers will either have to remove the Visual Studio entitlements and add them later when the allocations data is available. To achieve this, customers can mark the Entitlements as "<strong>Retired</strong>" and can update them back to "<strong>In use</strong>" once they have the allocation data.<br /><br /></li><li>Else, they will have to check with <strong>Microsoft</strong> for subscribed users so that they can create allocations.</li></ul> </li></ul></section></div></article></div>