Month: September 2015
Working around with: Connect-SPOService : Current site is not a tenant administration site.
For the “Current site is not a tenant administration site” error message, which may look like following:
Connect-SPOService : Current site is not a tenant administration site.
At line:1 char:1
+ Connect-SPOService -Url https://mysite.sharepoint.com -Credential $credentials
+ CategoryInfo : NotSpecified: (:) [Connect-SPOService], ServerException
+ FullyQualifiedErrorId : Microsoft.SharePoint.Client.ServerException,Microsoft.Online.SharePoint.PowerShell.Con
You get this error because you’re not entering the URL for your “Sharepoint Online Administration Center” site… Which is typically your normal sharepoint online URL, but then with a
-admin after it, such as:
https://mysite-admin.sharepoint.com (assuming that your sharepoint online site is https://mysite.sharepoint.com). Therefore, then whole Powershell script would be:
Connect-SPOService -Url https://mysite-admin.sharepoint.com -credential firstname.lastname@example.org
Encourage Author, Please share on Twitter!! – Just one Click Tribute!
NOTE: The -admin site is setup automatically. You don’t have to do anything. Just type in your sitename and then add the -admin.sharepoint.com to the end and you’ll be prompted to log in.
Configure Windows PowerShell to Connect with O356
Configuring Widnows PoserShell to be used with O365 is few steps process. To successfully run the
Connect-MsolService PowerShell command, you need to:
- Find out what bitness your operating system is (x86 / 32-bit OR x64 / 64-bit). See Microsoft’s “Is my PC running the 32-bit or 64-bit version of Windows?” article for help.
- If necessary, install the appropriate bitness version of PowerShell 3.0
Windows6.0is Windows Vista and
Windows6.1is Windows 7
Note 2: If you get a message of “The update is not applicable to your computer.” during the install then either you downloaded the wrong version of you already have it installed
- Install the appropriate bitness version of the Microsoft Online Services Sign-In Assistant for IT Professionals
- Install the appropriate bitness version of the Windows Azure Active Directory Module for Windows PowerShell
Note: If you get an error of “In order to install Windows Azure Active Directory Module for Windows PowerShell, you must have Microsoft Online Services Sign-In Assistant version 7.0 or greater installed on this computer.” and a resulting failed install, install the Microsoft Online Services Sign-In Assistant for IT Professionals BETA (you shouldn’t need to uninstall the normal version but I would recommend it).
- Run the appropriate bitness version of PowerShell
- Run the
Import-Module MSOnlinePowerShell command
- Finally, run the
Note: When I say “the appropriate bitness version” I mean to use 64-bit if available.
Once gone through above steps seuccessfully, Run the cmdlet Get-Module and you should see list of all imported modules along with MsOnline module. As shown below:
Install Project Template in Visual Studio 2012 for Sharepoint 2013 Apps / Add-Ons
Download following components to get start with Sharepoint apps development.
Microsoft Exchange Web Services:
Click on the following link to download VS2012 project template to get start with the development of Sharepoint 2013 / O365 version.
Microsoft Identity Extensions
Workflow Manager Client 1.0
Microsoft Workflow Manger Tools
Working around with the error: An error occurred whilst trying to load some required components, Please ensure the following prerequisite components are installed.
Microsoft Web Developer Tools
Microsoft Exchange Web Services”
To get this error solved, Uninstall Microsoft Exchange Web Services from Control Panel, if its already installed. And navigate to the location of EwsManagedApi32.msi. In my case, its at: c:\Users\Zia\Download> In the command prompt, run
c:\Download> EwsManagedApi32.msi addlocal=”ExchangeWebServicesApi_Feature,ExchangeWebServicesApi_Gac”
It will initiate the installation wizard and I hope this will solve your problem.