While most of the configuration of managed accounts will likely take place in Central Administration, at some point you may need (or simply prefer) to change the password via PowerShell. Personally, I ran into the need, as my farm account password had been changed and the Central Administration site would not run.

I used the following PowerShell script to change the Managed Account password.

$ver = $host | select version
if ($ver.Version.Major -gt 1)  {$Host.Runspace.ThreadOptions = ReuseThread"}
Add-PsSnapin Microsoft.SharePoint.PowerShell
Set-location $home

$inManagedAcct = Read-Host 'Service Account'

$managedAcct = Get-SPManagedAccount $inManagedAcct

$inPass = Read-Host 'Enter Password' -AsSecureString
$inPassConfirm = Read-Host'Confirm Password' -AsSecureString

Set-SPManagedAccount -Identity $managedAcct -NewPassword $inPass -ConfirmPassword $inPassConfirm -SetNewPassword

Click here to download the PS1 file. You may need to remove the first few lines that load the SharePoint PowerShell snap-in, if you intend to run the script from the “SharePoint 2010 Management Shell” console.

Original Posting

One such feature is the “Share” menu, with the option to “Save to SharePoint”. The following screenshot is from the MS Word 2010 Menu after creating a brand new file… complete with Recent Locations.

May not seem like much, but try living without it after you’ve had it for quite some time.

True, we’ve had “My SharePoint Sites” within the “Save File” screen in previous versions. But its never quite worked as expected… you had to explicitly be a “Member” of the site (not through an AD group), the profile import had to be working just right, after you were made a “Member” of the site it may not have shown up on your list until the following day, and a slew of other things. You could also say that we had “My Network Places”, but that required a certain level of proactivity that often times you just don’t have.

Nothing in Office 2010 was my idea… but to whoever's idea this feature was; Thanks for keeping my experience in mind.

Original Blog Post

This event will be from 8:00 am – 6:00 pm at Norris Conference Center, 803 Town & Country Lane, Houston, TX 77024.  713-590-0950.  We will provide a continental breakfast, break refreshments and hot lunch.  Parking is free in the parking garage (adjacent to Norris and Studio Movie Grill) in the 3rd level and above.  Enter Norris on the third level from the south end of the parking garage.

About SharePoint Saturday:  Whether you are a IT professional, professional, business owner, manager or enthusiast, SharePoint Saturday is an educational, informative & lively day filled with sessions from respected SharePoint professionals & MVPs, covering a wide variety of SharePoint-orientated topics. SharePoint Saturday is FREE, open to the public and is your local chance to immerse yourself in SharePoint!

Seats are limited so, register today! http://www.sharepointsaturday.org/houston/default.aspx

Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator.

Correlation ID:[SomeCorrelationID]

This is not an uncommon error, its also not very descriptive. But just a little digging around in the ULS logs using the Correlation ID should quickly reveal the problem. Which (when external lists are involved) usually has something to do with security; like specifying that the Data Source Connection use the users identity when not all users have access to the back-end system. But that was not the case here; I configured it to Connect with an Impersonated Windows Identity, set up and configured a Secure Store Target Application, and triple-checked that I specified the correct Target Application ID. But the error persisted, and the logs simply stated:

The Microsoft Secure Store Service application Secure Store Service failed to retrieve credentials. The error returned was 'Target application not found (application id: AWContactAdmins).'

It turns out the Application ID I specified was right. But the Secure Store Service App under which I created it was not associated with the SharePoint Web Application where I built my External List.

The fix: I had more than one Secured Store Application Configured, one of which was already associated with the Web Application hosting my external list. So I just re-created the Target Application under the corresponding secured store.

Go to http://blog.rafelo.com/2010/03/bcs-external-list-error-unable-to.html for more information and to view the original post.

Cross Post from: http://blog.rafelo.com/2010/03/bcs-business-connectivity-services-team.html

Check out my latest blog posting with a step by step how-to video on the subject. 

Additional information from TechNet at: Plan automatic password change (SharePoint Foundation)