{"id":2743,"date":"2005-10-19T14:36:00","date_gmt":"2005-10-19T14:36:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/heaths\/2005\/10\/19\/arpsystemcomponent-and-sequencing\/"},"modified":"2005-10-19T14:36:00","modified_gmt":"2005-10-19T14:36:00","slug":"arpsystemcomponent-and-sequencing","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/setup\/arpsystemcomponent-and-sequencing\/","title":{"rendered":"ARPSYSTEMCOMPONENT and Sequencing"},"content":{"rendered":"<p><a href=\"http:\/\/msdn.microsoft.com\/library\/en-us\/msi\/setup\/sequencing_patches.asp\">Sequencing<\/a> Windows Installer <a href=\"http:\/\/blogs.msdn.com\/heaths\/archive\/2005\/09\/01\/459561.aspx\">patches<\/a> is typically straight forward but when the original product install or a previous, non-superseded patch defines <a href=\"http:\/\/msdn.microsoft.com\/library\/en-us\/msi\/setup\/arpsystemcomponent.asp\"><code>ARPSYSTEMCOMPONENT<\/code><\/a> as 1 in the <a href=\"http:\/\/msdn.microsoft.com\/library\/en-us\/msi\/setup\/property_table.asp\">Property table<\/a> a custom supersedence plan is necessary to support writing Add\/Remove Program registry keys correctly with patch supersedence and sequencing in mind.<\/p>\n<ol>\n<li><a href=\"http:\/\/blogs.msdn.com\/heaths\/archive\/2005\/08\/05\/448198.aspx\">The Dangers of ARPSYSTEMCOMPONENT<\/a><br \/>Using the <code>ARPSYSTEMCOMPONENT<\/code> Windows Installer property can leave your Add\/Remove Program entries behind.\n<\/li>\n<li><a href=\"http:\/\/blogs.msdn.com\/heaths\/archive\/2005\/08\/16\/452395.aspx\">A Reason for ARPSYSTEMCOMPONENT<\/a><br \/>Reasons for setting <code>ARPSYSTEMCOMPONENT<\/code> to 1 despite the dangers.\n<\/li>\n<li><a href=\"http:\/\/blogs.msdn.com\/heaths\/archive\/2005\/08\/26\/456915.aspx\">Working with ARPSYSTEMCOMPONENT<\/a><br \/>How to work around the issues with ARP when defining <code>ARPSYSTEMCOMPONENT=1<\/code>.\n<\/li>\n<li><a href=\"http:\/\/blogs.msdn.com\/heaths\/archive\/2005\/08\/29\/457477.aspx\">Supporting our Lifecycle Policy with ARPSYSTEMCOMPONENT<\/a><br \/>How to support N and N-1 with the workaround for defining <code>ARPSYSTEMCOMPONENT=1<\/code>.\n<\/li>\n<li><a href=\"http:\/\/blogs.msdn.com\/heaths\/archive\/2005\/10\/19\/482761.aspx\">A Better Way of Working with ARPSYSTEMCOMPONENT<\/a><br \/>How to support custom supersedence when you have to manage patch-specific registry keys manually without using a lot of custom code.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Sequencing Windows Installer patches is typically straight forward but when the original product install or a previous, non-superseded patch defines ARPSYSTEMCOMPONENT as 1 in the Property table a custom supersedence plan is necessary to support writing Add\/Remove Program registry keys correctly with patch supersedence and sequencing in mind. The Dangers of ARPSYSTEMCOMPONENTUsing the ARPSYSTEMCOMPONENT Windows [&hellip;]<\/p>\n","protected":false},"author":389,"featured_media":3843,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[5,20,28],"class_list":["post-2743","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-arpsystemcomponent","tag-installation","tag-pages"],"acf":[],"blog_post_summary":"<p>Sequencing Windows Installer patches is typically straight forward but when the original product install or a previous, non-superseded patch defines ARPSYSTEMCOMPONENT as 1 in the Property table a custom supersedence plan is necessary to support writing Add\/Remove Program registry keys correctly with patch supersedence and sequencing in mind. The Dangers of ARPSYSTEMCOMPONENTUsing the ARPSYSTEMCOMPONENT Windows [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts\/2743","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/users\/389"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/comments?post=2743"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts\/2743\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/media\/3843"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/media?parent=2743"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/categories?post=2743"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/tags?post=2743"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}