Blog Archives

SharePoint Online – Storage Metrics – Monitor storage usage in your Site Collection

Hey Everyone!!!

Today i will talk about Storage Metrics in your SharePoint Site Collection!!!

Everyone knows what is the main feature on SharePoint that you could interact with and Structure of SharePoint Site Collections! right!? Site Content and Struct (/_layouts/sitemanager.aspx)!!!

Site Content and Structure page, give you a great overview about all your Site Collection structure. This feature, available since Microsoft Office SharePoint Server 2007, give the capability to navigate dynamically on your site collection hierarchy, it is familiar to Windows Explorer in fact. You can see the site collection hierarchy in the navigation pane as a tree view on the left of the Site Content and Structure page.

But, if you need know more details about storage, probably don’t help you as you expect, so in this case you case access to Storage Metrics (/_layouts/storman.aspx).

 

Storage Metrics underneath Site Collection Administration, access to your all sub-sites and libraries in SharePoint Online ( also available for SharePoint 2010, SharePoint 2013 and SharePoint 2016) and give you the information about how much storage they are consuming.

It is great!!! Because Storage Metrics allows you to drill down to each site, library and even folder to show a very granular report on your storage consumption, this is very important if you need migrate a large lists or even you are planning an migration between SharePoint Versions without any 3rd Party tool.

Take a Look:

 

 

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

Advertisements

SharePoint 2016 – Create Service Accounts using PowerShell script

Hey Everyone!!!

Today i will show you how can you create SharePoint 2016 Service Accounts using PowerShell script following the Best Practices.

The script not only create all the accounts but also create the respectives OU (Organizational Unit):

  • SharePoint Accounts
  • SQL Accounts

Service Accounts:

 Name  Description  Local Rights  Domain Rights
SP_Farm The server farm account is used to perform the following tasks:
-Configure and manage the server farm.
-Act as the application pool identity for the SharePoint Central Administration Web site.
-Run the Microsoft SharePoint Foundation Workflow Timer Service.
SecurityAdmin and DB_Creator rights on the SQL Instance Domain User
SP_Admin The server farm account is used to perform the following tasks:
-Setup
-SharePoint Products Configuration Wizard
Local Administrator on all the SharePoint Servers. SecurityAdmin and DB_Creator rights on the SQL Instance Domain User
SP_Pool The Pool account is used to run the Web Application Pools None Domain User
SP_Services The Services Account is used to run the Service Application Pool None Domain User
SP_Crawl The Default Content Access Account for the Search Service Application None Domain User
SP_Search Service Account to run the SharePoint Search “Windows Service” None Domain User
SP_UserProfiles The User Profile Synchronization Account None Domain User
SP_MySitePool Used for the My Sites Web Application None Domain User
SP_CacheSuperUser Object Cache Service Account. The goals of the object cache are to reduce the load on the computer on which SQL Server is running, and to improve request latency and throughput. These user account must be properly configured to ensure that the object cache works correctly. None.
SharePoint: Must be an account that has Full Control access to the Web application.
Domain User
SP_CacheSuperReader Object Cache Service Account. The goals of the object cache are to reduce the load on the computer on which SQL Server is running, and to improve request latency and throughput. These user account must be properly configured to ensure that the object cache works correctly. None.
SharePoint: Must be an account that has Full Read access to the Web application
Domain User
WF_Service WorkFlow Manager Service Account Local Administrator and SysAdmin rights on the SQL instance. Domain User
SP_MySitePool Used for the My Sites Web Application None Domain User
SP_VisioUser Visio Unattended ID None Domain User
SP_ExcelUser Excel Unattended ID None Domain User
SP_PerfPointUser Performance Point Unattended ID None Domain User
SQL_Admin SQL Admin on the SQL Server. Used to Install the SQL Server. Local Administrator on the SQL Server Domain User
SQL_Services It is the service account for the following SQL Server services: MSSQLSERVER SQLSERVERAGENT None Domain User


Script:

 

$mydom = (get-addomain).distinguishedname 
$password = "pass@word1" | ConvertTo-SecureString -AsPlainText -Force 

$ouNameSP = "SharePoint Accounts"
$oudnSP = "OU=$ounameSP,$mydom" 

$ouNameSQL = "SQL Accounts" 
$oudnSQL = "OU=$ounameSQL,$mydom" 

#----------------------------> Organizational Unit <---------------------------- 

New-ADOrganizationalUnit -Name $OUNameSP -Path $mydom 
Write-Host "OU $OUNameSP Created" -foregroundcolor green 

New-ADOrganizationalUnit -Name $OUNameSQL -Path $mydom 
Write-Host "OU $OUNameSQL Created" -foregroundcolor green 

#-----------------------------> SharePoint 2016 <-------------------------------

$usersArraySP = @("SP_Farm","SP_Admin","SP_Pool","SP_Services","SP_Crawl","SP_Search",
                  "SP_UserProfiles","SP_PortalSuperReader","SP_CacheSuperUser","SP_VisioUser",
                  "SP_PerfPointUser","WF_Service","SP_MySitePool","SP_PortalSuperUser")

foreach ($usp in $usersArraySP) {
        New-ADUser -Name $usp -DisplayName $usp -SamAccountName $usp -AccountPassword $password 
        -ChangePasswordAtLogon $false -PassThru -PasswordNeverExpires $true -Path $oudnSP 
        Write-Host "$usp Created" -foregroundcolor green
 }

#----------------------------------> SQL <--------------------------------------
$usersArraySQL = @("SQL_Admin","SQL_Service")

foreach ($usql in $usersArraySQL) {
       New-ADUser -Name $usql -DisplayName $usql -SamAccountName $usql -AccountPassword $password 
       -ChangePasswordAtLogon $false -PassThru -PasswordNeverExpires $true -Path $oudnSQL
       Write-Host "$usql Created" -foregroundcolor green
 }

 

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

SharePoint – Export all solutions wsp using PowerShell script

Hey Everyone,

Today i will post a script very helpful when you are on Migration steps and you need export all wsp solutions.

 

$dirName = "C:WSP"
if (!(Test-Path -path $dirName))
{
New-Item $dirName -type directory
}
Write-Host Exporting solutions to $dirName
foreach ($solution in Get-SPSolution)
{
    $id = $Solution.SolutionID
    $title = $Solution.Name
    $filename = $Solution.SolutionFile.Name
    Write-Host "Exporting ‘$title’ to …$filename" -nonewline
    try {
        $solution.SolutionFile.SaveAs("$dirName$filename")
        Write-Host " – done" -foreground green
    }
    catch
    {
        Write-Host " – error : $_" -foreground red
    }
}

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

SharePoint 2016 – Essential Migration Steps and Considerations

Hey Everyone!

Today i will talk about SharePoint Migrations, a complex process that requires an extra efforts depending the version of SharePoint.

Why should I upgrade or migrate to SharePoint 2016?!

1.SharePoint Farm of company is old! If it’s SP2003, SP2007 or SP2010, Microsoft do not give more support and updates for that versions, so you can’t expect more features our updates for your infrastructure.

SharePoint Product Lifecycle

Products Released  End Date of Support
 SharePoint Portal Server 2001  11/07/2006
 SharePoint Portal Server 2003  14/04/2009
 SharePoint Server 2007  09/10/2012
 SharePoint Server 2010 13/10/2015
 SharePoint Server 2013 04/10/2018

 

2.SharePoint 2016, it’s more stable and fast than the other version even is a version more close to the cloud, all the innovation and experience hosting SharePoint Online brought that knowledge and innovation to SharePoint 2016, also that, new version use MinRoles a significant improvement in terms of infrastructure.

3.FIM is no more a component of SharePoint, it was replaced by Microsoft Identity Manager (MIM).

4.Data Loss Prevention is now part of SharePoint.  You can now identify, monitor for, and protect sensitive data across SharePoint 2016, SharePoint Online, and One Drive for Business using SharePoint 2016.

5.Hybrid Solutions between SharePoint 2016 and Office 365,  now you can easily integrate with Office 365 using SharePoint 2016. Taking the advantage of Cloud Hybrid Search, Delve, Hybrid Sites, Groups, Profile Redirection and more running SharePoint in hybrid mode.

6.Durable Links,move files wherever you like and your link remains valid. It may seem like a small thing but to end users this is a big deal.

7.Cloud Hybrid Search in the cloud you can display all of your results from O365 and on-prem will be listed happily together, by relevancy, and it’s all encrypted by the crawler.

There are many other new features offered by SharePoint 2016 you can read more about in this link.

Which approach should I take, to upgrade or migrate?!

 Version  Upgrade Approach  Migration Approach
SharePoint 2001  Upgrade through each version of SharePoint.
Requires new SharePoint
Farms for each Upgrade, until the latest version is met.
 Manually copy or use a 3rd Party tool to migrate the core document and asset content into a new structure defined within a new SharePoint 2016 Farm.
SharePoint 2003 Upgrade through each version of SharePoint.
Requires new SharePoint Farms for each Upgrade, until the latest version is met.
 Manually copy or use a 3rd Party tool to migrate the core document and asset content into a new structure defined within a new SharePoint 2016.
SharePoint 2007  Upgrade through each version of SharePoint.
Requires new SharePoint Farms for each Upgrade, until the latest version is met.Utilize Database Attach method.
 Manually copy or use a 3rd Party tool to migrate content into a new structure defined within a new SharePoint 2016 Farm.
SharePoint 2010  Upgrade through each version of SharePoint.
Requires new SharePoint Farms for each Upgrade, until the latest version is met.
Utilize Database Attach method.
 Manually copy or use a 3rd Party tool to migrate content into a new structure defined within a new SharePoint 2016 Farm.
SharePoint 2013 Upgrade through each version of SharePoint.
Requires new SharePoint Farms for each Upgrade, until the latest version is met.
 Manually copy or use a 3rd Party tool to migrate the core document and asset content into a new structure defined within a new SharePoint 2016 Farm.

 

What questions should I ask before upgrading or migrating?

It’s important understand what is the main processes and data that you what migrate for your new version of SharePoint, this will be essential to define the process and success of the operation. Ask questions about the current solution and success criteria you can define the scope of the migration or upgrade, this type of process not is fast but is really importance is be precision.

Are you now ready to migrate or upgrade?

The  success of  migration or upgrade is planning, then some more planning, and organizational buy in. Moving to SharePoint 2016 will deliver better security, collaboration, content management, mobility, compliance and cloud connectivity features. But the migration or upgrade warrants a much more care and attention to detail in planning, you need to lay out every step needed to get there and  engage all the stakeholders in your organization in all aspects of the selected process.

New and improved features in SharePoint Server 2016
Create the SharePoint Server 2016 farm for a database attach upgrade

 

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|