NerdyHearn
Home
Blog

Contact
Mailing List

Software

Active Directory Products
Object Compare
Permission Compare

IPhone Products
Calls To Calendar
SMS To CSV
SMS To Gmail
Voicemail To Gmail

Sites
DocuTerminal
How Long For Me
My Music To Me
SaveMySerials
TypeCount

Blog
Twitter

NerdyHearn - Blog


<< Back To All Blogs

Up the creek without a paddle: Taking over a deserted SharePoint 2007 installation

Thursday, December 27th, 2012

I've been working on a client site for a few weeks and coming into the project they knew absolutely nothing about their current environment asides from the server name. This meant we didn't have the Farm admin password, and didn't have any current employees as farm or collection admins. To regain control of the environment I went through the following steps:

1. Reset the service account passwords by following the Microsoft KB article here

Once we re-gained farm login after resetting credentials, we had another interesting caveat. BUILTINAdministrators and the farm admin account had been removed from the Farm Admins group so we still couldn't access content on any site collections.

They had also changed their theme, so in central admin the menus to add users were not working. Our only option from this point was to add our accounts using stsadm.

For both steps below also pay attention to if the site is using SSL or not (you'll need to change http:// or https:// depending on the site collection)

2. Add users to the Farm Administrators group using STSADM:
stsadm -o adduser -url http://centraladminservername:port -userlogin DOMAINuser -useremail user@email.com -group "Farm Administrators" -username "DOMAINuser"

3. Set site collection ownership using STSADM:
You'll need to do this for each site collection you would like access to (My sites, Web Applications, etc)
stsadm -o siteowner -url http://site:port -ownerlogin DOMAINuser -secondarylogin DOMAINuser

Keep in mind that site collections can only have 2 owners, and resetting ownership may have adverse affects if the account you remove was being used as something other than an individual user.

Regainin' Tom Out.

Tags

SharePoint

Related Blogs

Web form to help audit permissions in SharePoint 2007/MOSS
Configuring ASP.NET (And SharePoint) to use SQL-based Sessions
Receiving "The specified file is not a valid spreadsheet or contains no data" when importing to Office 365
Using MOSS and WSS SharePoint Workflow to Resize Images in an Image Library
Resolving "Tracing Service lost trace events" in MOSS 2007

Comments

Currently no comments.

Add A Comment

Name:


URL:


Email Address: (not public, used to send notifications on further comments)


Comments:



Enter the text above, except for the 1st and last character:


NerdyHearn - Latest tech news relating to C#, ASP.NET, SharePoint, PHP, general development, and more. DocuTerminal - Online Filing Cabinet solution. Scan, search and archive your paper documents. SaveMySerials - Protect yourself from theft, fire, natural disasters and more by recording your serial numbers My Music To Me - Stream your subsonic music collection to your Sonos wireless system TypeCount - Count how often you type across different computers! Sipellect - Business-focused, IT-intelligent call center and online calling solutions