<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>B2b on Matt Thornton</title>
    <link>https://matt-thornton.net/tags/b2b/</link>
    <description>Recent content in B2b on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 21 Nov 2017 15:15:40 +0000</lastBuildDate><atom:link href="https://matt-thornton.net/tags/b2b/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>psconfig v2v or b2b?</title>
      <link>https://matt-thornton.net/tech/sharepoint/psconfig-v2v-b2b/</link>
      <pubDate>Tue, 21 Nov 2017 15:15:40 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/sharepoint/psconfig-v2v-b2b/</guid>
      
        <description>&lt;p&gt;Yesterday I posted about a &lt;a href=&#34;https://www.matt-thornton.net/tech/sharepoint/sharepoint-passphrase-recovery&#34;&gt;quick hack to reset the farm passphrase&lt;/a&gt;. Part of this was using the psconfig cli to perform an in-place upgrade of SharePoint.&lt;/p&gt;
&lt;p&gt;Part of this was the command:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;psconfig.exe -cmd upgrade -inplace v2v -passphrase &amp;quot;passphrase&amp;quot; -wait&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;At the time, all seemed to Ok&amp;hellip; but today have noticed that the Manage Database Upgrade Status in Central Admin was showing that some databases had been left behind - “Database is in compatibility range and should be upgraded”. And the output from&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>