{"id":72,"date":"2013-10-15T02:00:55","date_gmt":"2013-10-15T02:00:55","guid":{"rendered":"http:\/\/www.torontohelpdesk.ca\/blog\/?p=72"},"modified":"2013-10-15T02:00:55","modified_gmt":"2013-10-15T02:00:55","slug":"sbs-2011-migration-moving-the-ssl-over","status":"publish","type":"post","link":"https:\/\/www.torontohelpdesk.ca\/blog\/sbs-2011-migration-moving-the-ssl-over\/","title":{"rendered":"SBS 2011 Migration &#8211; Moving the SSL over"},"content":{"rendered":"<p>Migrated SBS 2008 to SBS 2011 and I needed to move the SSL over to the new server (granted it&#8217;s expiring in a couple of months).<\/p>\n<p><a href=\"http:\/\/technet.microsoft.com\/en-us\/library\/gg563798.aspx\" target=\"_blank\">http:\/\/technet.microsoft.com\/en-us\/library\/gg563798.aspx<\/a><\/p>\n<h3>Move certificates<\/h3>\n<div>\n<p><strong>Self-issued certificates<\/strong><\/p>\n<p>Migrating self-issued certificates is not supported. Users must transfer the Certificate Distribution Package in the new server to removable media, and then they must re-install the self-issued certificates on the remote computers that are not joined to the domain.<\/p>\n<p><strong>Trusted certificates<\/strong><\/p>\n<p>If you purchased a trusted certificate, and it is available to export, you can move the certificate to Windows SBS\u00a02011 Standard. To move a certificate, use the following procedures to export it from the Source Server, import it to the Destination Server, and then run the Add a Trusted Certificate Wizard to connect the certificate to Remote Web Access.<\/p>\n<h4>To export a trusted certificate from the Source Server<\/h4>\n<div>\n<ol>\n<li>On the Source Server, click <strong>Start<\/strong>, click <strong>Run<\/strong>, type <strong>mmc.exe<\/strong>, and then press ENTER.<\/li>\n<li>On the console, click <strong>File<\/strong>, and then click <strong>Add\/Remove Snap-in<\/strong>.<\/li>\n<li>Click <strong>Add<\/strong>, choose <strong>Certificates<\/strong> from the list, click <strong>Add<\/strong>, and then click <strong>OK<\/strong>.<\/li>\n<li>In the pop-up window that appears, click <strong>Computer Account<\/strong>, click <strong>Finish<\/strong>, and then click <strong>OK<\/strong>.<\/li>\n<li>Expand <strong>Certificates<\/strong>, expand <strong>Personal<\/strong>, and then click <strong>Certificates<\/strong>.<\/li>\n<li>Right-click the certificate that is issued to your website (for example: remote.contoso.com), click <strong>All Tasks<\/strong>, and then click <strong>Export<\/strong>.\n<div>\n<table>\n<tbody>\n<tr>\n<th align=\"left\"><img decoding=\"async\" id=\"note\" title=\"note\" alt=\"note\" src=\"http:\/\/i.technet.microsoft.com\/areas\/global\/content\/clear.gif\" \/>Note<\/th>\n<\/tr>\n<tr>\n<td>There may be multiple certificates with the same name. Ensure that you choose a certificate that has a valid expiration date and that was issued by a trusted authority. If you are not sure which certificate to use, open Internet Information Services (IIS), determine which certificate IIS is using on the Source Server, and then choose the same certificate.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<\/div>\n<\/li>\n<li>In the Certificate Export Wizard, click <strong>Next<\/strong>.<\/li>\n<li>Ensure <strong>Yes, export the private key<\/strong> is selected, and then click <strong>Next<\/strong>.<\/li>\n<li>Ensure <strong>Include all certificates in the certificate path if possible<\/strong> and <strong>Export all extended properties<\/strong> are selected, and then click <strong>Next<\/strong>. Do not select <strong>Delete the private key if the export is successful<\/strong>.<\/li>\n<li>Type a password to protect the certificate file, and then click <strong>Next<\/strong>.<\/li>\n<li>Choose a location to save the .pfx file (for example, <strong>C:\\trustedcert.pfx<\/strong>), and then click <strong>Next<\/strong>.<\/li>\n<li>Finish the wizard.<\/li>\n<\/ol>\n<\/div>\n<h4>To import the trusted certificate to the Destination Server<\/h4>\n<div>\n<ol>\n<li>Move the <strong>trustedcert.pfx<\/strong> file to the Destination Server by using the network or a USB flash drive.<\/li>\n<li>On the Destination Server, click <strong>Start<\/strong>, type <strong>mmc.exe<\/strong>, and then press ENTER.<\/li>\n<li>On the console, click <strong>File<\/strong>, and then click <strong>Add\/Remove Snap-in<\/strong>.<\/li>\n<li>Choose <strong>Certificates<\/strong> from the list, and then click <strong>Add<\/strong>.<\/li>\n<li>In the pop-up window that appears, select <strong>Computer Account<\/strong>, click <strong>Finish<\/strong>, and then click <strong>OK<\/strong>.<\/li>\n<li>Expand <strong>Certificates<\/strong>, expand <strong>Personal<\/strong>, and then click <strong>Certificates<\/strong>.<\/li>\n<li>Right-click <strong>Certificates<\/strong>, click <strong>All Tasks<\/strong>, and then click <strong>Import<\/strong>.<\/li>\n<li>On the Certificate Import Wizard <strong>Welcome<\/strong> page, click <strong>Next<\/strong>.<\/li>\n<li>Browse to the location of the saved .pfx file, and then click <strong>Next<\/strong>.<\/li>\n<li>Type the password that you typed in the Export procedure, ensure that <strong>Mark this key as exportable<\/strong> and <strong>Include all extended properties<\/strong> are selected, and then click <strong>Next<\/strong>.<\/li>\n<li>Ensure that the certificate is imported to the <strong>Personal<\/strong> folder, and then click <strong>Next<\/strong>.<\/li>\n<li>Finish the wizard.<\/li>\n<\/ol>\n<\/div>\n<p>To ensure that the Destination Server is using the newly imported certificate, run the Add a Trusted Certificate Wizard:<\/p>\n<h4>To run the Add a Trusted Certificate Wizard<\/h4>\n<div>\n<ol>\n<li>Open the Windows SBS\u00a02011 Standard Console.<\/li>\n<li>On the navigation bar, click the <strong>Network<\/strong> tab, and then click <strong>Connectivity<\/strong>.<\/li>\n<li>In the task pane, click <strong>Add a trusted certificate<\/strong>.<\/li>\n<li>On the <strong>Welcome<\/strong> page, read the information, and then click <strong>Next<\/strong>.<\/li>\n<li>On the <strong>Get the certificate<\/strong> page, click <strong>I want to use a certificate that is already installed on the server<\/strong>, and then click <strong>Next<\/strong>.<\/li>\n<li>On the <strong>Choose an installed certificate<\/strong> page, click the certificate that you just imported, and then click <strong>Next<\/strong>.\n<div>\n<table>\n<tbody>\n<tr>\n<th align=\"left\"><img decoding=\"async\" id=\"note\" title=\"note\" alt=\"note\" src=\"http:\/\/i.technet.microsoft.com\/areas\/global\/content\/clear.gif\" \/>Note<\/th>\n<\/tr>\n<tr>\n<td>If you cannot find the certificate that you just imported in the previous step, double-check whether the Internet address that is configured on the Destination Server is exactly the same as the one on the Source Server.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<\/div>\n<\/li>\n<li>When the wizard finishes, click <strong>Finish<\/strong>.<\/li>\n<li>We recommend that you upgrade to a\u00a02048-bit certificate if you were using a 1024-bit certificate.<\/li>\n<\/ol>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Migrated SBS 2008 to SBS 2011 and I needed to move the SSL over to the new server (granted it&#8217;s expiring in a couple of months). http:\/\/technet.microsoft.com\/en-us\/library\/gg563798.aspx Move certificates Self-issued certificates Migrating self-issued certificates is not supported. Users must transfer <a class=\"more-link\" href=\"https:\/\/www.torontohelpdesk.ca\/blog\/sbs-2011-migration-moving-the-ssl-over\/\">Continue reading <span class=\"screen-reader-text\">  SBS 2011 Migration &#8211; Moving the SSL over<\/span><span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18,24,25],"tags":[26,78,77,76],"class_list":["post-72","post","type-post","status-publish","format-standard","hentry","category-sbs-2008","category-sbs-2011","category-ssl","tag-moving-certificate","tag-sbs-2008","tag-sbs-2011","tag-ssl"],"_links":{"self":[{"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts\/72","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/comments?post=72"}],"version-history":[{"count":2,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts\/72\/revisions"}],"predecessor-version":[{"id":79,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts\/72\/revisions\/79"}],"wp:attachment":[{"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/media?parent=72"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/categories?post=72"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/tags?post=72"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}