#Name of your SQL Server Alias
$AliasName = "SP13_PROD_SQL"

# Actual SQL Server Name
$SQLServerName = "G1VSP13-SQLC001" 

#These are the two Registry locations for the SQL Alias 
$x86 = "HKLM:\Software\Microsoft\MSSQLServer\Client\ConnectTo"
$x64 = "HKLM:\Software\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo"

#if the ConnectTo key doesn't exists, create it.
if ((test-path -path $x86) -ne $True)
{
    New-Item $x86
}

if ((test-path -path $x64) -ne $True)
{
    New-Item $x64
}

#Define SQL Alias 
$TCPAliasName = ("DBMSSOCN," + $SQLServerName)

#Create TCP/IP Aliases
New-ItemProperty -Path $x86 -Name $AliasName -PropertyType String -Value $TCPAliasName
New-ItemProperty -Path $x64 -Name $AliasName -PropertyType String -Value $TCPAliasName

• C:\Windows\System32\cliconfg.exe
• C:\Windows\SysWOW64\cliconfg.exe

• Farm(s) Topology - List of servers and roles, physical and logical architecture diagrams for production, Staging and Development Environment (if applicable)
• Server Infrastructure (Physical/Virtual), Storage, CPU-RAM-Network configurations
• List of Service Accounts (Setup account, Farm account, search crawler account, etc) and passwords
• Maintenance windows schedule - Patching, patch Level? OS versions?
• Incoming/Outgoing E-mail configurations. SMTP configuration details
• IIS Level customizations (compression, URL rewrite, redirects, etc.)
• Backup, Disaster recovery in place. Tools used (SCDPM, Comvault, etc). Backup frequency.
• Database server details. SQL Alias? Redundancy - Clustering in place? Mirroring? Always ON?
• Monitoring setup for server/application Health, SCOM, etc
• Load Balancing/Publishing details (ISA? TMG? CISCO Ace? or any other Hardware load balancer, F5 Big IP?)
• Third party software (Nintex, Layer2, Control Point, etc installed in the environment
• Licensing details for SharePoint and any 3rd party software. Volume/MSDN Licenses for DEV/TEST? Premier support with vendors such as Microsoft?
• Profile Import/My site setup - Schedules, directory services/sources List
• Last but not least - Contact person/teams for all dependent teams such as Network, DBA teams, System Admins, Backup, AD, Server Hardware, Security, Exchange server, etc.

• User Base - Total No. of users, region, locations, internal vs. external, site usage in last one Month?
• How external users access SharePoint? Published Intranet? users member of AD? VPN connections?
• Custom authentication provider in use (E.g. FBA, AD LDS, ADFS, Live)? Kerberos ?
• Web applications/CA is SSL enabled? certificate details, providers.
• Any SharePoint specific Antivirus on SP Servers? E.g. Forefront antivirus for SharePoint? Third party anti-virus solutions such as McAFee?
• Are there any exclusive site for end-user training materials, FAQs, KB, etc?Any self service sites?
• Access Rights Policies? - Any custom permission levels created (E.g. contributor without delete)

• List of web Applications, site collections with owner contacts
• List of customizations/custom solutions and its documentation
• Additional Language Packs installed.
• CA Specific custom settings - Recycle bin, Max File Upload size, Storage quotas, etc
• Integration points (Interfaces) with LOB and other applications/ Software (SQL server reporting services?)
• List of SharePoint and other related application databases
• How Branding is applied, Whats being done? (feature staplers/custom site definitions/Themes/Custom CSS, Master pages, etc)
• List of SharePoint Sites that are most critical to business?
• Typical SharePoint Usages in the Org. (Collaboration, Knowledge Management, Enterprise content Management, Document management, Dashboards, etc. )
• Repository for configuration files, Implementation/Build guides, Known error database (KEDB) , Incident Logs, RCA (root cause analysis), (CSV, SVN, TFS, etc.)

• Team Structure - Team Members, Roles supporting existing SharePoint environment.
• System in place for Incident/Request/Change management? 
• How end user requests are routed to the team? Provide the complete request life cycle.
• Existing SLA and priorities for incident management. 
• Governance Policies in place. E.g. site creations, content responsibility, support limits, etc 
• Support statistics (Tickets received last month, open/close, etc)
• Scheduled Reports to the business owners? E.g. Monthly reports for usage.
• Remote Sharing/ User Interaction methods (Web ex, etc).
• Communication plan for any planned/unplanned outages - Key stakeholder list

Add-PSSnapin Microsoft.SharePoint.Powershell -ErrorAction SilentlyContinue

#Custom PowerShell Function to Export All Lists and Libraries from a SharePoint site
Function Export-AllLists($WebURL, $ExportPath)
{
   #Get the source web
   $web = Get-SPWeb $WebURL

   #Check the Local Folder export Lists

   #Get all lists - Exclude System lists
   $ListCollection = $web.lists | Where-Object  { ($_.hidden -eq $false) -and ($_.IsSiteAssetsLibrary -eq $false) -and ($_.Author.LoginName -ne "SHAREPOINT\system") }

   #Iterate through each list and export
   foreach($list in $ListCollection)
    {
        Write-host "Exporting: " $list.Title
        #Remove : from List title - As we can't name a file with : symbol
        $ListTitle = $list.Title.Replace(":","")
        Export-SPWeb $WebURL -ItemUrl "/$($list.RootFolder.Url)" -IncludeUserSecurity -IncludeVersions All -path ($ExportPath + $ListTitle+ ".cmp") -nologfile
    } 
}

#Custom PowerShell Function to Export All Lists and Libraries from a SharePoint site
Function Import-AllLists($WebURL, $ImportPath)
{
   #Get the Target web
   $web = Get-SPWeb $WebURL

   #Check the Local Folder export Lists

   #Get all File Backups to Import
   $FilesCollection = Get-ChildItem $ImportPath

   #Iterate through each file and import
   foreach($File in $FilesCollection)
    {
        Write-host "Importing: " $File.Name
        Import-SPWeb $webURL -path $ImportPath$File -includeusersecurity -UpdateVersions Overwrite -nologfile
    } 
}

#Call the function to export
Export-AllLists "http://sales.crescent.com/" "D:\Backup\"
#To import, Use:
#Import-AllLists "http://marketing.crescent.com/" "D:\Backup\"

Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

function Get-WebPage([string]$url,[System.Net.NetworkCredential]$cred=$null) 
{ 
    $WebClient = new-object net.webclient 
    if($cred -eq $null) 
    { 
        $cred = [System.Net.CredentialCache]::DefaultCredentials; 
    } 
    $WebClient.credentials = $cred; 
    return $WebClient.DownloadString($url); 
} # end Function 

# Make sure the account has enough permission to read sites
#$cred = [System.Net.CredentialCache]::DefaultCredentials; 
#Change these values accordingly
#$cred = new-object System.Net.NetworkCredential("USER ID","PASSWORD","DOMAIN")

#Get All Web Applications and iterate through
$WebAppsColl = Get-SPWebApplication -IncludeCentralAdministration

foreach($WebApp in $WebAppsColl)
{
    #Get All site collections and iterate through
    $SitesColl = $WebApp.Sites

    foreach ($Site in $SitesColl) 
    {
	Write-Host "Warming up Site collection:"  $Site.URL
	$html = Get-WebPage -url $Site.URL  -cred $cred 
    }

#Change these URL's if you need any other Site/URL for warmup
#$html = Get-WebPage -url "http://northwind.crescent.com/SitePages/Home.aspx" -cred $cred 

• Lets keep a log for warmed up sites, 
• Warm-up all Host-named site collections - Lets create a proxy to hit on the SAME web front end rather going to load balancer - We can't edit HOST file for each HNSC, isn't it?

start-transcript -path C:\Scripts\$(get-date -format 'ddMMyyyy').txt -append

Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue  

function Get-WebPage([string]$url)
{   
    $bypassonlocal = $false
    $proxyuri = "http://" + $env:COMPUTERNAME
    $proxy = New-Object system.Net.WebProxy($proxyuri, $bypassonlocal)
    $wc = new-object net.webclient
    $wc.credentials = [System.Net.CredentialCache]::DefaultCredentials
    $wc.proxy = $proxy
    $pageContents = $wc.DownloadString($url)
    #write-host $wc.ResponseHeaders.Get("WFE")
    $wc.Dispose()
    return $pageContents
}

#Central Administration
write-host "Warming up Central Administration..."
$WebApps = Get-SPWebApplication -IncludeCentralAdministration
Get-SPWebApplication -IncludeCentralAdministration | ? {$_.IsAdministrationWebApplication -eq $true} | % { $Req = Get-WebPage $_.url }
write-host "`nCentral Administration Warmed up!"

# Warm up Host Name Site Collections (HNSC)
	Write-Host "Warming up Host Name Site Collections (HNSC)...`n"
	$hnsc = Get-SPSite -Limit All |? {$_.HostHeaderIsSiteName -eq $true} | Select Url
	foreach ($sc in $hnsc) {
        write-host "Processing HNSC: "$sc.Url
		$Req = Get-WebPage $sc.url  
	}

# Clean Temporary Files
	Remove-item "$env:systemroot\system32\config\systemprofile\appdata\local\microsoft\Windows\temporary internet files\content.ie5\*.*" -Recurse -ErrorAction SilentlyContinue
	Remove-item "$env:systemroot\syswow64\config\systemprofile\appdata\local\microsoft\Windows\temporary internet files\content.ie5\*.*" -Recurse -ErrorAction SilentlyContinue

stop-transcript

1. Using IIS HTTP Response header and Fiddler Tool
2. Placing a specific image file in each WFE denoting its whereabouts and linking it to SharePoint

Method 1: Using HTTP Response Header

1. Go to your Web Front End server, Open IIS, Choose your SharePoint web application from Sites tree view. Open "HTTP Response Headers" widget
2. From the Right pane of the widget, Click on "Add" link, Give a name and value. Here, I gave "WFE" as name and "WFE01" as my web front end name. Click "OK"to save your changes. Repeat this step of setting HTTP response header in IIS for all of the web front end servers of your SharePoint farm!
   
3. Now, from the client side, run Fiddler tool. From the Fiddler tool , Go to "Inspectors" tab and then "Header"section. You can get the custom HTTP response header we've created with its corresponding value.
   
   

Method 2: WFE Specific Image 

 

• Go to Server Manager >> Choose "System Configuration" from Tools menu. (Shortcut: MSCONFIG)
• Under Tools tab, Select "Change UAC Settings" and click on "Launch" button

• Drag the slider down to "Never Notify" and click "OK".

• Open Windows Registry Editor (shortcut: regedit)
• Navigate to the following registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
• In the Right Pane, locate the "EnableLUA" DWORD value. Double click and set its Value "0" (zero)
• Exit Registry Editor and then restart your Server.

Set-ItemProperty -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System" -Name "EnableLUA" -Value "0"
Shutdown -r -t 0 

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

#Output Report File
$currentLocation = (Get-Location).Path
$outputReport = $currentLocation + "\" + "SharePointUsers.csv" 
#Write CSV File Header

#Array to hold user data
$UserDataCollection = @() 

#Get All Web Applications and iterate through
$WebAppsColl = Get-SPWebApplication 
#To Get all Users from specific web application, Use: $WeAppsColl = Get-SPWebApplication "web-app-url"
#and remove line #12

foreach($WebApp in $WebAppsColl)
{
    Write-host "Scanning Web Application:"$WebApp.Name
    #Get All site collections and iterate through
    $SitesColl = $WebApp.Sites
    #To Get all Users from site collection, Use: $SitesColl = Get-SPSite "site-collection-url"
    #and remove lines between #11 to #20 and Line #55 "}"
    #get all users from site collection PowerShell
    foreach ($Site in $SitesColl) 
    {
        Write-host "Scanning Site Collection:"$Site.URL
        #Get All Webs and iterate through
        $WebsColl = $Site.AllWebs
        #To Get all Users from aq site, Use: $WebsColl = Get-SPWeb "web-url"
         #and remove lines between #11 to #28 and Lines #53, #54, #55 "}"

            foreach ($web in $WebsColl) 
            {
                Write-host "Scanning Web:"$Web.URL
                #Get All Users of the Web
                $UsersColl = $web.AllUsers  #get all users programmatically 
                    #list all users 
                    foreach ($user in $UsersColl) 
                    {
                           if($User.IsDomainGroup -eq $false) 
                            {
                                $UserData = New-Object PSObject

                                $UserData | Add-Member -type NoteProperty -name "UserLogin" -value $user.UserLogin.ToString()
                                $UserData | Add-Member -type NoteProperty -name "DisplayName" -value $user.displayName.ToString()
                                $UserData | Add-Member -type NoteProperty -name "E-mailID" -value $user.Email.ToString()

                                $UserDataCollection += $UserData
                            }
                    }
            $Web.dispose()
            }
         $site.dispose()
        }
    }    
    #Remove duplicates
    $UserDataCollection = $UserDataCollection | sort-object -Property  {$_.UserLogin } -Unique 

    #Remove duplicates and export all users to excel
    $UserDataCollection | Export-Csv -LiteralPath $OutputReport -NoTypeInformation

    Write-host "Total Number of Unique Users found:"$UserDataCollection.Length

Alternate approach to rename SharePoint database:

#Create new Content Database
New-SPContentDatabase -Name SharePoint_AdminContent -WebApplication http://centraladmin:2013

# Get SharePoint database IDs for old and new DBs for central admin site
Get-SPWebApplication –Identity http://centraladmin:2013 | Get-SPContentDatabase | SELECT ID, Name, WebApplication | Format-List

#Note down the IDs of Original Database and New Database. 
# In my case, Old database id: c87506a9-b87d-40b8-9582-aac9ee89c8f8.  
# New Database id: 8f35dc3b-56ab-45df-a1cf-459b60aa7454

# Move central admin sites to from old Database to new SharePoint content database
Get-SPSite –ContentDatabase c633c573-966d-4362-a1f8-430fba561f11 | Move-SPSite –DestinationDatabase 8f35dc3b-56ab-45df-a1cf-459b60aa7454

#You must do an IISReset!

# Now, You can Remove OLD SharePoint admin content database using Old database ID - actually deletes the database on the SQL Server.
 Remove-SPContentDatabase -identity c633c573-966d-4362-a1f8-430fba561f11 

(New-Object System.Net.Sockets.TCPClient("SQL-Server-Name",1433)).Connected 

1. Open Central administration.
2. Go Security >> Click on Configure Managed Accounts.
3. Click the Register Managed Account link to create a new managed account.
4. Enter the account’s AD username in domain\username format. Specify the account's password.
5. Optionally, You can enable the automatic password reset.
6. Click "OK" to to create managed account in SharePoint 2013.
   

$cred = Get-Credential
New-SPManagedAccount –Credential $cred

Add-PSSnapin microsoft.sharepoint.powershell -ea SilentlyContinue

#Define a common password for all service accounts
$password = "Password1"
$securePassword = ConvertTo-SecureString -String $password -AsPlainText -Force

#List of Service accounts
$ServiceAccounts = "SP-Farm","SP_Services","SP_Search","SP_UserProfile"

   ForEach ($Account in $ServiceAccounts) 
   {
    #Get the account in Domain\UserName format
    $userName = $env:USERDOMAIN + "\" + $Account
    #Set the Credentials
    $cred = New-Object System.Management.Automation.PSCredential -ArgumentList $username, $securePassword
    #Create Managed Account
    New-SPManagedAccount -Credential $cred
    }

Troubleshooting: 

1.     Generating new password
2.     Set account password to new value
3.     Use existing password - This option lets us updating the account password in SharePoint, if it is changed in Active Directory(or somewhere!)

Set-SPManagedAccount –Identity domain\user -AutoGeneratePassword $true

$ManagedAccount = Read-Host "Enter the Managed account in Domain\User Format:"

#$ManagedAccount = Get-SPManagedAccount -Identity “sharepoint\sa-spcontent”
#Get new Password for the managed account
$Password = Read-Host "Enter new password for managed account" –AsSecureString

#Change the password for the managed account
Set-SPManagedAccount -Identity $ManagedAccount -NewPassword $Password

$ManagedAccount = Read-Host "Enter the Managed account in Domain\User Format:"

#Get new Password for the managed account
$Password = Read-Host "Enter new password for managed account" –AsSecureString

#Change the password for the managed account
Set-SPManagedAccount -Identity $ManagedAccount -ExistingPassword $Password -UseExistingPassword $true

• Go to Central Administration >> Select Application Management  >> Configure quotas and locks
• Choose the site collection you want to set on Read-only mode and select the option “Read-Only". Choose farm administrator controlled or site collection administrator controlled options accordingly.
• Enter the lock information and click "Ok"

Set-SPSite -Identity "Site-Collection-URL" -LockState "ReadOnly"

Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue

#Get all Site Collections
$SitesColl = Get-SPSite -limit All

#Loop through all site collections
ForEach($Site in $SitesColl)
{
  Set-SPSite -Identity $site.Url -LockState "ReadOnly"
  #You can also use: Set-SPSiteAdministration -LockState "ReadOnly" -Identity $Site.URL
}

Set-SPSite -Identity "Site-Collection-URL" -LockState "Unlock"

How to Create a New Managed Account in SharePoint 2010/2013:

1. Go to Central Administration, Click Security >> Click on Configure Managed Accounts.
2. Click the Register Managed Account link to create a new managed account.
3. Enter the Service account's AD user name in domain\username format. Specify the account's password.
4. If you want SharePoint to automatically change this account’s password on a regular schedule, check the "Enable Automatic Password Change" check box and specify when to change password in accordance to the password expiry policy of your AD.
5. Check the "Start Notifying By E-mail" check box and specify the number of days before the password change you want to be notified.
6. Specify the schedule for your password change. You can change the password weekly or monthly.
   You should set changes to occur during scheduled downtime or during light usage, because the password changes will cause momentary service interruptions as application pools are restarted.
7. Click OK to save the new managed account.

• Create New Managed Account in SharePoint 2013 Using Powershell

• Central Administration >> Security 
• Under the General Security section, click Configure service accounts. 

1. Select Security from the SharePoint Central Administration page.
2. On the Security page select Configure managed accounts under General Security.
3. The Managed Accounts page will list all Managed Accounts registered in SharePoint.

1. To edit an existing managed account using Central Administration, follow these steps:
2. Click Security and then select Configure Managed Accounts.
3. The list of existing managed accounts is displayed. To make changes to the account, Click the edit icon for the managed account.
4. Click OK to save your changes.

1. Click Security and then select Configure Managed Accounts.
2. Click the delete icon for the managed account you want to remove.
3. In the Remove Managed Account page, confirm the correct account is selected and click OK.

Remove-spmanagedaccount "Crescent\SP_Farm" 

Add-PSSnapin Microsoft.SharePoint.PowerShell

#Import data from CSV file
$UserData = Import-CSV -path "C:\Accounts.csv"

#Iterate through each Row in the CSV
foreach ($Row in $UserData)
 {
    write-host "Processing user:" $row.Email

    #Site collection URL
    $siteURL ="https://intranet.crescent.com"
    $site = Get-SPSite $siteURL

    foreach($web in $site.AllWebs)
     {
        #Get All Users
        $UserColl = Get-SPUser -web $web.Url

        foreach ($User in $UserColl)
        {
            #Get values from CSV File
            $OldUserID= $Row.OldUserID.Trim()
            $NewUserID =$Row.NewUserID.Trim()
            $Email = $Row.Email.Trim()

            #Search for Old User Accounts
            if($User.UserLogin.Contains($OldUserID))
             {
                #Update the User E-mail
                Set-SPUser -Identity $User.UserLogin -Email $Email -Web $web.URL

                $NewUser = $User.UserLogin.replace($OldUserID, $NewUserID)

                #Migrate user from Old account to new account - migrate users to new domain
                Move-SPUser -Identity $User -NewAlias $NewUser -IgnoreSID -confirm:$false
                write-host "User Migrated: $($User.userlogin) at site $($web.Url)"
             }        

        } 
    }
}

• Settings >> Site Settings
• Click the "Site permissions" link under "Users and permissions" section
• Now, from the ribbon, Click on “Access Request Settings” button. You'll be prompted with the access request Settings popup window.

• Click on "Allow access request" option to enable access request and enter the E-mail address of the user who will receive access requests from that site.

Add-PSSnapin Microsoft.SharePoint.Powershell

#Set the site URL variable accordingly!
$SiteURL = "https://intranet.crescent.com"

$site = Get-SPSite $SiteURL

    ForEach ($web in $site.AllWebs | where { $_.Permissions.Inherited -eq $false})
          {
                #sharepoint 2013 access request settings powershell
                $web.RequestAccessEmail="Support@Crescent.com"
                write-host Updated Access request settings for $web.Title, at: $web.URL 
         }

• Report for SharePoint Access Request Email Configurations 
• Configure Access Requests in SharePoint 2010/2007
• Change All SharePoint Site's Access Request Emails with PowerShell
   

1. SP_Setup - SharePoint Setup account
2. SP_Farm    - SharePoint Farm account
3. SP_Pool    - The account is used to run the Web Application Pools
4. SP_Services - The Services Account is used to run the Service Applications
5. SP_Crawl - The Default Content Access Account for the Search Service Application
6. SP_UserProfile - The User Profile Import and Synchronization Account
7. SP_SuperUser - Cache account for Web application super User account
8. SP_SuperReader - Cache account for Web application super reader account
9. SQL_Admin - SQL Admin on the SQL Server. Used to Install the SQL Server.
10. SQL_Services - Service account to run SQL Server services

Import-Module ActiveDirectory -ErrorAction SilentlyContinue

#Set configurations
$AccountPassword = "Password1"
#Convert to Secure string 
$Password = ConvertTo-SecureString -AsPlainText $AccountPassword -Force

$Domain = "YourDomain.com"
#Specify the OU
$AccountPath= "ou=SharePoint,DC=YourDomain,DC=com"

#Create SharePoint Accounts
$Account="SP_Setup" 
New-ADUser -SamAccountName $Account -name $Account -UserPrincipalName $Account@$domain -Accountpassword $Password -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description="Account Used to install SharePoint"}

$Account="SP_Farm" 
New-ADUser -SamAccountName $Account -name $Account -UserPrincipalName $Account@$domain -Accountpassword $Password -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description="SharePoint Farm Account."}

$Account="SP_Pool" 
New-ADUser -SamAccountName $Account -name $Account -UserPrincipalName $Account@$domain -Accountpassword $Password -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description="SharePoint Web Application Pools Account"}

$Account="SP_Services" 
New-ADUser -SamAccountName $Account -name $Account -UserPrincipalName $Account@$domain -Accountpassword $Password -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description="Account to run the Service Applications"}

$Account="SP_Crawl" 
New-ADUser -SamAccountName $Account -name $Account -UserPrincipalName $Account@$domain -Accountpassword $Password -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description="Content Access Account for the Search Service Application"}

$Account="SP_UserProfile" 
New-ADUser -SamAccountName $Account -name $Account -UserPrincipalName $Account@$domain -Accountpassword $Password -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description="User Profile Import and Synchronization Account"}

$Account="SP_SuperUser" 
New-ADUser -SamAccountName $Account -name $Account -UserPrincipalName $Account@$domain -Accountpassword $Password -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description="Web application super User account"}

$Account="SP_SuperReader" 
New-ADUser -SamAccountName $Account -name $Account -UserPrincipalName $Account@$domain -Accountpassword $Password -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description=" Web application super reader account"}

$Account="SQL_Admin" 
New-ADUser -SamAccountName $Account -name $Account -UserPrincipalName $Account@$domain -Accountpassword $Password -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description="SQL Server Admin Account"}

$Account="SQL_Services" 
New-ADUser -SamAccountName $Account -name $Account -UserPrincipalName $Account@$domain -Accountpassword $Password -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description="Account to run SQL Server services"}

Import-Module ActiveDirectory -ErrorAction SilentlyContinue

#Set configurations
$Domain = "YourDomain.com"
#Specify the OU
$AccountPath= "ou=SharePoint,DC=YourDomain,DC=com"

# Import the CSV File
$ServiceAccounts = Import-Csv D:\SharePoint\ServiceAccounts.csv

Foreach ($ServiceAccount in $ServiceAccounts) 
 {   
    write-host "Creating Account:"$ServiceAccount.Account
    write-host "Creating Account:"$ServiceAccount.password

    #Convert to password to Secure string 
    $AccountPassword = ConvertTo-SecureString -AsPlainText $ServiceAccount.Password -Force

    $UPN = "$($ServiceAccount.Account)@$($domain)"

    #Create SharePoint Service Accounts from CSV
    New-ADUser -SamAccountName $ServiceAccount.Account -name $ServiceAccount.Account -UserPrincipalName $UPN -Accountpassword $AccountPassword -Enabled $true -PasswordNeverExpires $true -path $AccountPath -OtherAttributes @{Description=$ServiceAccount.Description}
 }