{"id":84,"date":"2011-10-07T11:48:00","date_gmt":"2011-10-07T11:48:00","guid":{"rendered":"\/post\/2011\/10\/07\/Error-1603-installing-Exchange-2010-RollUps.aspx"},"modified":"2011-10-07T11:48:00","modified_gmt":"2011-10-07T11:48:00","slug":"error-1603-installing-exchange-2010-rollups","status":"publish","type":"post","link":"https:\/\/www.vatland.no\/index.php\/error-1603-installing-exchange-2010-rollups\/","title":{"rendered":"Error 1603 installing Exchange 2010 RollUp&#8217;s"},"content":{"rendered":"<p>Getting error installing Rollup 5 for Exchange 2010 Sp1. Error 1603. According to msi log file it is ServiceControl.ps1 that is causing the error. Solution was to set execution policy to RemoteSigned and also run the &#8220;ServiceControl.ps1 AfterPatch&#8221; script from the Exchange 2010 Bin folder&nbsp;. Also remember to start Powershell as administrator.<\/p>\n<p>set-executionpolicy -executionpolicy RemoteSigned<\/p>\n<p>.\\servicecontrol.ps1 AfterPatch<\/p>\n<p>After this the install turned out OK.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Getting error installing Rollup 5 for Exchange 2010 Sp1. Error 1603. According to msi log file it is ServiceControl.ps1 that is causing the error. Solution was to set execution policy to RemoteSigned and also run the &#8220;ServiceControl.ps1 AfterPatch&#8221; script from the Exchange 2010 Bin folder&nbsp;. Also remember to start Powershell as administrator. set-executionpolicy -executionpolicy RemoteSigned &hellip; <a href=\"https:\/\/www.vatland.no\/index.php\/error-1603-installing-exchange-2010-rollups\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Error 1603 installing Exchange 2010 RollUp&#8217;s<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[5],"tags":[],"class_list":["post-84","post","type-post","status-publish","format-standard","hentry","category-exchange"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":false,"jetpack-related-posts":[{"id":790,"url":"https:\/\/www.vatland.no\/index.php\/upgrade-to-skype-for-business-failed-error-1603\/","url_meta":{"origin":84,"position":0},"title":"Upgrade to Skype for Business failed. Error 1603","author":"Atle","date":"October 20, 2018","format":false,"excerpt":"Have done several upgrades from Lync 2013 to Skype for Business 2015, so this last one should be no different, but faith had other plans. Installed topology builder on a new computer and prepared the upgrade process. But when a bit into the upgrade it failed. Error: Error returned while\u2026","rel":"","context":"In &quot;Lync&quot;","block_context":{"text":"Lync","link":"https:\/\/www.vatland.no\/index.php\/category\/lync\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2018\/10\/Capture5.jpg?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2018\/10\/Capture5.jpg?resize=350%2C200 1x, https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2018\/10\/Capture5.jpg?resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2018\/10\/Capture5.jpg?resize=700%2C400 2x"},"classes":[]},{"id":61,"url":"https:\/\/www.vatland.no\/index.php\/exchange-2013-ecp-iis-error\/","url_meta":{"origin":84,"position":1},"title":"Exchange 2013 ecp iis error","author":"Atle","date":"October 17, 2012","format":false,"excerpt":"After installing Exchange 2013 I\u00a0got this \"Server Error in '\/ecp' Application\" when entering \"Exchange Admin Center\" web page. \"Could not load type 'Microsoft.Exchange.Managment.Security.AdfsFederationAuthModule'\" Solution: Exchange 2013 did not install the \"Windows Identity Foundation 3.5\" automatically. So all there is to it, add\u00a0this feature. \u00a0\u00a0","rel":"","context":"In &quot;Exchange&quot;","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"","src":"\/image.axd?picture=2012%2f10%2fecp_error_e2013.JPG","width":350,"height":200,"srcset":"\/image.axd?picture=2012%2f10%2fecp_error_e2013.JPG 1x, \/image.axd?picture=2012%2f10%2fecp_error_e2013.JPG 1.5x"},"classes":[]},{"id":467,"url":"https:\/\/www.vatland.no\/index.php\/exchange-2010-mapiexceptionnetworkerror\/","url_meta":{"origin":84,"position":2},"title":"Exchange 2010 : MapiExceptionNetworkError","author":"Atle","date":"May 23, 2015","format":false,"excerpt":"One of our Exchange 2010 servers had its mailboxdatabases dismounted sometime during the night. When we tried to mount them we got a strange error message : \"MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)\" As we usually do with issued like this on Exchange is to\u2026","rel":"","context":"In &quot;Exchange&quot;","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"exchange","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2014\/09\/exchange.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":39,"url":"https:\/\/www.vatland.no\/index.php\/exchange-2010-sp3-upgrade-rpcproxyoutlook-anywhere-error\/","url_meta":{"origin":84,"position":3},"title":"Exchange 2010 SP3 upgrade RpcProxy\/Outlook Anywhere error.","author":"Atle","date":"May 31, 2013","format":false,"excerpt":"After upgrading from Exchange 2010 sp2 to Exchange 2010 sp3 Outlook Anywhere stopped working. Solution is to replace a corrupt web.config in the RpcProxy Virtual Directory. https:\/\/www.vatland.no\/page\/Exchange-2010-SP3-RpcProxy-webconfig-OutlookAnywhere.aspx Atle","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":80,"url":"https:\/\/www.vatland.no\/index.php\/scom-2007-r2-error-importing-exchange-2010-mp\/","url_meta":{"origin":84,"position":4},"title":"SCOM 2007 R2 , Error importing Exchange 2010 MP.","author":"Atle","date":"November 14, 2011","format":false,"excerpt":"\"Import incomplete\" !!!! Does it sound familiar? I've tried and I\u00a0tried. I tried servereal CU's (from 1 to 5) . Upgraded all the other MP's resulting in only one thing : \"Import incomplete\". It turned out that all I had to do was to increase the size of OperationManager database\u2026","rel":"","context":"In &quot;SCOM 2007&quot;","block_context":{"text":"SCOM 2007","link":"https:\/\/www.vatland.no\/index.php\/category\/scom-2007\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":96,"url":"https:\/\/www.vatland.no\/index.php\/smtp-unreliable-links\/","url_meta":{"origin":84,"position":5},"title":"SMTP unreliable links","author":"Atle","date":"July 30, 2011","format":false,"excerpt":"Had a problem with large emails between exchange 2010 servers. Got the smtp error 421.4.4.2 . I solved this by increasing the MaxProtocolError and ConnectionTimeout on the receiving connector. Use the powershell set-receiveconnector . In this senario we are talking about a 1mb sat link.","rel":"","context":"In &quot;Exchange&quot;","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/84","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/comments?post=84"}],"version-history":[{"count":0,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/84\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/media?parent=84"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/categories?post=84"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/tags?post=84"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}