{"id":12111,"date":"2011-11-12T00:01:00","date_gmt":"2011-11-12T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2011\/11\/12\/use-powershell-to-edit-sharepoint-profiles\/"},"modified":"2011-11-12T00:01:00","modified_gmt":"2011-11-12T00:01:00","slug":"use-powershell-to-edit-sharepoint-profiles","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/use-powershell-to-edit-sharepoint-profiles\/","title":{"rendered":"Use PowerShell to Edit SharePoint Profiles"},"content":{"rendered":"

Summary:<\/strong> Microsoft Premier Field Engineer Chris Weaver shows how to use Windows PowerShell to edit SharePoint profiles.<\/span><\/span><\/p>\n<\/p>\n

Microsoft Scripting Guy Ed Wilson here. It is Guest Blogger Weekend. To start the weekend, we have Chris Weaver. The <\/span>Scripting Wife<\/span><\/a> and I recently met Chris <\/span>in real life (IRL)<\/span><\/a> at Geek Ready, a conference at which I was speaking. What can I say? Chris is cool! Here is his biography.<\/span><\/span> <\/span><\/p>\n<\/p>\n

<\/span> <\/p>\n

\"Photo<\/a><\/span><\/p>\n

I have been working at Microsoft since late 2008. During that time I have been an engineer within CSS, a SharePoint 2010 TAP, and most recently a dedicated premier field engineer working with several of our Premier customers to support their SharePoint infrastructure. I have been using Windows PowerShell for the last two years to simplify the administration and troubleshooting of SharePoint for my customers. I very recently started <\/span>my own blog<\/span><\/a>, which will look at issues with SharePoint and its supporting infrastructure. <\/span><\/span><\/p>\n

I enjoy camping with my family and kite surfing in my spare time (yeah, right, who has any of that?).<\/span> <\/span><\/b><\/span><\/p>\n

Note<\/span><\/b>   The script for today’s blog article appears on the <\/span>Scripting Guys Script Repository<\/span><\/a>. <\/span><\/span><\/p>\n

 <\/span><\/p>\n

I am working with a customer to automate the installation and configuration of SharePoint Server 2010 using Windows PowerShell.<\/span><\/p>\n

I would like to show you one of the functions that we are using to configure profiles after we have completed an import. The customer is highly regulated and has users that cannot communicate in any form with other users, so when it was discovered that profiles by default would send email for several different reasons, we had to reverse it.<\/span><\/p>\n

We will be editing the profile property called SPS-MailOptIn<\/b>. In the GUI, it is represented by three check boxes. <\/span>First, you want to load the following assembly so that we can work with the profiles:<\/span><\/p>\n

Add-Type -Path “c:\\program files\\common files\\microsoft shared\\web server extensions\\14\\isapi\\microsoft.office.server.dll”<\/span><\/p>\n

And don’t forget to ensure that the SharePoint snap-in is loaded because we will want to use commands from it. You can use the following lines to verify or load that info. This snap-in is installed on all SharePoint installations and automatically loaded, if using the SharePoint 2010 Management Shell:<\/span><\/p>\n

$PSSnapIn = Get-PSSnapin | where {$_.Name -like “*sharepoint*”}<\/span><\/p>\n

 <\/span><\/p>\n

if(!($PSSnapIn.Name -like “*sharepoint*”))<\/span><\/p>\n

{<\/span><\/p>\n

Add-PSSnapin Microsoft.SharePoint.PowerShell<\/span><\/p>\n

}<\/span><\/p>\n

Then we need to load the UserProfileManager<\/b>, and I do so with the following code. To be able to manage this, the account running the script will need to be a User Profile Service Application Administrator with at least Manage Profile permissions:<\/span><\/p>\n

$Site = Get-SPSite -Limit 1    #Get Site for Service context<\/span><\/p>\n

$ServiceContext = Get-SPServiceContext($Site)<\/span><\/p>\n

$ProfileManager = new-object Microsoft.Office.Server.UserProfiles.UserProfileManager($ServiceContext)<\/span><\/p>\n

$Profiles = $ProfileManager.GetEnumerator()    #Load all profiles into array<\/span><\/p>\n

Using Get-SPSite<\/b> has two advantages. The first advantage is that I do not have to worry about disposing of the object because Windows PowerShell will do that for me. The second advantage is that by using the switch -Limit<\/b> set to 1<\/b>, I get one site to connect to and don’t have to worry about personalizing it to the farm before running the script.<\/span><\/p>\n

Then I throw everything into a For <\/b>loop, iterate through all the profiles, and get the property using the following:<\/span><\/p>\n

$OriginalValue = $Profile[“SPS-EmailOptin”].Value<\/span><\/p>\n

After I get the value, I save it to a text file to ensure that I have it in the future, if needed. Then, as I had mentioned, only some users are regulated, so we compare the profiles name to a list of regulated users, and if not in the list, we proceed to change the value with the following line:<\/span><\/p>\n

$Profile[“SPS-EmailOptin”].Value = $EmailOptInValue<\/span><\/p>\n

The variable $EmailOptInValue<\/b> represents three integers. Each number can be 0 or 1. 0 means the box is checked, and 1 means it is not. As an example, the variable could be loaded with the 101 or 010:<\/span><\/p>\n