<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  version="2.0">
  <channel>
    <title>SPNinja</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/spninja/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/spninja/feed.xml</link>
    <description />
    <lastBuildDate>Wed, 17 Apr 2019 03:51:49 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>Migrating users between O365 tenants</title>
      <link>https://docs.microsoft.com/archive/blogs/spninja/migrating-users-between-o365-tenants</link>
      <pubDate>Fri, 04 Jan 2013 14:23:00 GMT</pubDate>
      <dc:creator><![CDATA[SPNinja]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/spninja/2013/01/04/migrating-users-between-o365-tenants/</guid>
      <description><![CDATA[So, you have come across a situation where you have to migrate users between Office 365 tenants. Its...]]></description>
      <content:encoded><![CDATA[<p>So, you have come across a situation where you have to migrate users between Office 365 tenants. Its awfully painful and extremely tedious to recreate every single user... the good news is that O365 provides PowerShell modules that allow export users into a CSV file. We can then use the CSV to bulk import users into the new O365 tenant.</p>
<p>Here is a script to export users into a CSV :<code class="csharp">&nbsp;</code></p>
<pre class="scroll"><code class="csharp"> # Connect to MSO<br /> Connect-MsolService<br /> <br /> # Get all users<br /> $users = Get-MsolUser <br /> $users | <br /> Select-Object -property @{name="User Name";Expression={$_.UserPrincipalName}},<br /> @{name="First Name";Expression={$_.FirstName}},<br /> @{name="Last Name";Expression={$_.LastName}},<br /> @{name="Display Name";Expression={$_.DisplayName}},<br /> @{name="Job Title";Expression={$_.JobTitle}},<br /> @{name="Department";Expression={$_.Department}},<br /> @{name="Office Number";Expression={$_.Office}},<br /> @{name="Office Phone";Expression={$_.PhoneNumber}},<br /> @{name="Mobile Phone";Expression={$_.MobilePhone}},<br /> @{name="Fax";Expression={$_.Fax}},<br /> @{name="Address";Expression={$_.StreetAddress}},<br /> @{name="City";Expression={$_.City}},<br /> @{name="State or Province";Expression={$_.State}},<br /> @{name="Zip or Postal Code";Expression={$_.PostalCode}},<br /> @{name="Country or Region";Expression={$_.Country}} | <br /> Export-Csv c:\users.csv -NoTypeInformation</code></pre>
<p>&nbsp;</p>
<p>Now use the Bulk Import feature on the new tenant to import the CSV as follows:</p>
<ol>
<li>In the header, click <strong>Admin</strong>.</li>
<li>In the left pane, under <strong>Management</strong>, click <strong>Users</strong>.</li>
<li>On the <strong>Users</strong> page, click the arrow next to <strong>New</strong>, and then click <strong>Bulk add</strong>.</li>
<li>On the <strong>Select&nbsp;the above&nbsp;exported&nbsp;CSV file</strong> page and then click <strong>Next</strong>.</li>
<li>On the <strong>Verification results</strong> page, confirm that there are no errors in your CSV file and that the number of users to import is correct. To review errors in the log file, click <strong>View</strong>. If you have errors in your CSV file, click <strong>Back</strong>. Open your CSV file and make the corrections, and then perform step 4 again. Once your CSV file has passed verification, click <strong>Next</strong>.</li>
<li>On the <strong>Settings</strong> page, under <strong>Set sign-in status</strong>, select <strong>Allowed</strong> to allow users to sign in to Office&nbsp;365 and access licensed services, or <strong>Blocked</strong> to block users from signing in to Office&nbsp;365 and accessing licensed services. Under <strong>Set user location</strong>, select the users&rsquo; work location, and then click <strong>Next</strong>.</li>
<li>On the <strong>Assign licenses</strong> page, select the licenses that you want to assign to all of the users being imported, and then click <strong>Next</strong>.</li>
<li>On the <strong>Send results in email</strong> page, select <strong>Send email</strong> to send a user name and temporary password for the added users to yourself and/or recipients of your choice. Enter email addresses separated by semicolons (;), and then click <strong>Create</strong>.</li>
<li>On the <strong>Results</strong> page, a list of successfully imported users and their temporary passwords is displayed, as well as any errors that occurred during the import process. If a user was not imported, there will be a status message indicating the reason. If you chose not to send yourself this information by email, you can click <strong>View</strong> to open the log file, and then print or save the information.</li>
</ol>
<p>That's it!</p>
<p>&nbsp;</p>]]></content:encoded>
    </item>
    <item>
      <title>Running SharePoint 2010 Management Shell on Windows 8</title>
      <link>https://docs.microsoft.com/archive/blogs/spninja/running-sharepoint-2010-management-shell-on-windows-8</link>
      <pubDate>Fri, 21 Dec 2012 09:02:00 GMT</pubDate>
      <dc:creator><![CDATA[SPNinja]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/spninja/2012/12/21/running-sharepoint-2010-management-shell-on-windows-8/</guid>
      <description><![CDATA[So, you installed windows 8 pro and got SharePoint 2010 running as your dev environment. The first...]]></description>
      <content:encoded><![CDATA[<p>So, you installed windows 8 pro and got SharePoint 2010 running as your dev environment. The first thing you will notice is that you can no longer execute the SharePoint&nbsp;PowerShell commands. When you open the <strong>SharePoint 2010 Management Shell</strong>, you get the following error:</p>
<p><em><strong>"the local farm is not accessible. <span lang="en">Cmdlets with FeatureDependencyId are not registered"</span>.</strong></em></p>
<p>&nbsp;</p>
<p>Well, Windows 8 uses Windows Management Framework 3.0 which includes PowerShell 3.0 which in turn is based on .NET Framework 4.0.&nbsp;Since&nbsp;the SharePoint 2010 Management Shell uses .NET Framework 3.5, we cannot use PowerShell 3.0. Therefore, we have to force the&nbsp;shortcut to use PowerShell 2.0, by specifying the -Version command.</p>
<p>&nbsp;</p>
<p>Whew!</p>
<p>To make this work, change the target of the shortcut "SharePoint 2010 Management Shell"&nbsp;as follows:</p>
<p><strong>C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe -version 2 -NoExit <span class="str">" &amp; ' C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ' "</span></strong></p>
<p>&nbsp;</p>
<p>&nbsp;</p>]]></content:encoded>
    </item>
  </channel>
</rss>