Showing posts with label PowerShell. Show all posts
Showing posts with label PowerShell. Show all posts

Friday, November 18, 2022

powershell scripts for sharepoint migration or powershell script for sharepoint online migration:

powershell scripts for sharepoint migration or powershell script for sharepoint online migration:



Most Commonly the below are the scripts used in any of the migration from Sharepoint On-premise to SharePoint Online.

The scripts may vary depends on the Enviornment and Requirement but the most common are as below.

Intial Migration Automation Scripts:

1.User Mapping

Post Migration scripts:

  1. Add QA members to Group
  2. Comparison Scripts
  3. convert classic to Modern site
  4. Custom Banner Adding
  5. Deploy site design
  6. Disable custom scripting
  7. Import sharegate connection
  8. Invoke site design
  9. Make site read only
  10. Set Sensitivity lables SPO
  11. Set Site clasifycation
  12. unhide site title in default page
  13. Delta Automation Script:This is Last script to user for Incremental Migration.



I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Monday, August 7, 2017

The specified module 'Microsoft.Online.SharePoint.PowerShell' was not loaded

The specified module 'Microsoft.Online.SharePoint.PowerShell' was not loaded
 
This is a Common Issue Every SharePoint administrator face once in a while executing the PowerShell scripts by Management shell.


Issue: When the SharePoint Online Management Shell Opens it immediately displays the following error message prior to type anything.


Error message:
Import-Module: The specified module 'Microsoft.Online.SharePoint.PowerShell' was not loaded because no valid module file was found in any module directory.


solution: Please follow the steps below to resolve the issue.


  1. Make sure you run the SharePoint Online Management shell as an Administrator.
    Or
  2. remove and re-install both the x86 and x64 management shells
I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Friday, September 4, 2015

SharePoint 2010 Management Shell does not load with Windows Power Shell 3.0



SharePoint 2010 Management Shell does not load with Windows Power Shell 3.0

Issue: After you install Microsoft SharePoint Server 2010 and Windows Power Shell 3.0 on a server, you receive one or both of the following error messages when you start SharePoint 2010 Management Shell:

Error message 1:The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.

Error message 2:Microsoft SharePoint is not supported with version 4.0.30319.17929 of the Microsoft .Net Runtime.

Workaround: please follow the work around mentioned below.
To work around this issue, change the Target field value for SharePoint 2010 Management Shell. To do this, follow these steps:
1.   Click Start, and then right-click SharePoint 2010 Management Shell.
2.   Click Properties.
3.   Click the Shortcut tab in the SharePoint 2010 Management Shell Properties window.
4.   Input the following value in the Target field:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -Version 2.0 -NoExit " & ' C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ' "

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Tuesday, July 7, 2015

Farm configuration Restores in Sharepoint 2013.



Farm configuration Restores in Sharepoint 2013.

You can use Windows Power Shell to restore a farm’s configuration.

To restore a farm's configuration by using Windows Power Shell 

1.    Verify that you have the following memberships:
o    securityadmin fixed server role on the SQL Server instance.
o    db_owner fixed database role on all databases that are to be updated.
o    Administrators group on the server on which you are running the Windows PowerShell cmdlets.
An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.

2.    On the Start menu, click All Programs .
3.    Click Microsoft SharePoint 2013 Products.
4.    Click SharePoint 2013 Management Shell.
5.    At the Windows Power Shell command prompt, type the following command:
Restore-SPFarm -Directory <RestoreShare> -RestoreMethod Overwrite -ConfigurationOnly

<RestoreShare> is network location where the backup file is stored
 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Monday, June 29, 2015

Resetting of pass phrase by power shell



Resetting of pass phrase by power shell

This is a common issue that most of the administrators face once in there work. In this article I am providing the steps how to reset the new pass phrase if we lost the old one.

Open Power Shell and execute the following script. Enter the new pass phrase when prompted:

 



 Confirm the Pass phrase










Click Yes



I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Adding a content DB in SharePoint 2013



Adding a content DB in SharePoint 2013

You can add a content database to a SharePoint 2013 farm by using the SharePoint Central Administration website or Windows Power Shell

You can use the procedures that are described in this article to create a new content database and attach it to a web application. If you are using Windows authentication to connect to SQL Server, the user account must also be a member the SQL Server dbcreator fixed server role on the SQL Server instance where the database will be created. If you are using SQL authentication to connect to SQL Server, the SQL authentication account that you specify when you create the content database must have dbcreator permission on the SQL Server instance where the database will be created.

To add a content database to a web application by using Central Administration 

1.    Verify that the user account that is performing this operation is a member of the Farm Administrators SharePoint group.
2.    Start SharePoint 2013 Central Administration.
o    For Windows Server 2008 R2:
§  Click Start, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Central Administration.
o    For Windows Server 2012:
§  On the Start screen, click SharePoint 2013 Central Administration.
If SharePoint 2013 Central Administration is not on the Start screen:
§  Right-click Computer, click All apps, and then click SharePoint 2013 Central Administration.
3.    On the SharePoint Central Administration website, click Application Management.
4.    In the Databases section, click Manage content databases.
5.    On the Manage Content Databases page, click Add a content database.
6.    On the Add Content Database page:
1.    Specify a web application for the new database.
2.    Specify a database server to host the new database.
3.    Specify the authentication method that the new database will use and supply an account name and password, if they are necessary.
ImportantImportant:
The account name and password must already exist as a SQL Server login.
4.    Specify the name of the failover database server, if one exists.
5.    Specify the number of top-level sites that can be created before a warning is issued. By default, this is 2,000.
6.    Specify the total number of top-level sites that can be created in the database. By default, this is 5,000.
7.    Click OK.

To add a content database to a web application by using Windows Power Shell 

1.    Verify that you have the following memberships:
o    securityadmin fixed server role on the SQL Server instance.
o    db_owner fixed database role on all databases that are to be updated.
o    Administrators group on the server on which you are running the Windows PowerShell cmdlets.
An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 Products cmdlets.
NoteNote:
If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about Windows PowerShell permissions, see Add-SPShellAdmin

2.    On the Start menu, click All Programs.
3.    Click Microsoft SharePoint 2013 Products.
4.    Click SharePoint 2013 Management Shell.
5.    At the Windows PowerShell command prompt, type the following command:
New-SPContentDatabase -Name <ContentDbName> -WebApplication <WebApplicationName>
Where:
o    <ContentDbName> is the name of the content database to create.
o    <WebApplicationName> is the name of the web application to which the new database is attached.

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

ShareThis

X