change service accounts and service account passwords in SharePoint Server 2007 and in Windows SharePoint Services 3.0

We have a requirement to change the passwords for service accounts in SharePoint Server 2007 and in Windows SharePoint Services 3.0, succeeded in Dev box (SharePoint Server 2007 Multi Form Environment). still need to implement in Prod.

follow these steps.

Note If the SQL Server service uses a domain account, and the password for that domain account is either expired or invalid, make sure that you update the password for the domain account before you perform this procedure.

1. Update the password for the account that is used by the Central Administration application pool. To do this, follow these steps:
   1. On all servers in the server farm, open a command prompt, type the following line, and then press ENTER:
      cd %commonprogramfiles%\Microsoft Shared\Web server extensions\12\Bin
   2. On the server that hosts the Central Administration Web site, type the following line at the command prompt, and then press ENTER:
      stsadm -o updatefarmcredentials -userlogin DomainName\UserName -password NewPassword
   3. On all other servers in the server farm, type the following line at the command prompt, and then press ENTER:
      stsadm -o updatefarmcredentials -userlogin DomainName\UserName -password NewPassword -local
   4. Restart Microsoft Internet Information Services (IIS) 6.0. To do this, type the following line at the command prompt, and then press ENTER:
      iisreset /noforce
2. Verify that the Administration Application Pool Credential Deployment job definition is no longer displayed on the Timer Job Definitions page of SharePoint 3.0 Central Administration. To do this, follow these steps:
   1. Open SharePoint 3.0 Central Administration, click Operations, and then click Timer job definitions under Global Configuration.
   2. Verify that the Administration Application Pool Credential Deployment job definition is no longer displayed in the list.
      
      Note If the Administration Application Pool Credential Deployment job definition is displayed in the list, wait until it disappears from the list.
3. Update the password for the application pool account that is used by Web applications on the server farm. To do this, type the following line at a command prompt on every server on the server farm, and then press ENTER:
   stsadm -o updateaccountpassword -userlogin DomainName\UserName -password NewPassword -noadmin
4. Update the password for the account that is used to run the Windows SharePoint Services Help Search service. To do this, type the following line at a command prompt on every server on the server farm, and then press ENTER:
   stsadm.exe -o spsearch -farmserviceaccount DomainName\UserName -farmservicepassword NewPassword
5. Update the password for the default content access account that is used by the Windows SharePoint Services Help Search service. To do this, type the following line at a command prompt on every server on the server farm, and then press ENTER:
   stsadm.exe -o spsearch -farmcontentaccessaccount DomainName\UserName -farmcontentaccesspassword NewPassword
6. If you are running SharePoint Server 2007, you must also follow these steps:
1. Update the password for the account that is used by every Shared Services Provider (SSP) on the server farm. To do this, type the following line at a command prompt on every server on the server farm, and then press ENTER:
   stsadm.exe -o editssp -title SharedServicesProviderName -ssplogin DomainName\UserName -ssppassword NewPassword
2. Update the password for the account that is used to run the Office SharePoint Server Search service. To do this, type the following line at the command prompt, and then press ENTER:
   stsadm.exe -o osearch -farmserviceaccount DomainName\UserName -farmservicepassword NewPassword
3. If the server farm is configured to use single sign-on, update the password for the account that is used by the Microsoft Single Sign-On Service. To do this, follow these steps:
   1. Click Operations in SharePoint 3.0 Central Administration, and then click Service accounts under Security Configuration.
   2. Under Windows service, click Single Sign-On Service.
   3. Under Configurable, specify the password, and then click OK.
4. Update the password for the default content access account that is used by the Office SharePoint Server Search service. To do this, follow these steps:
1. Open SharePoint 3.0 Central Administration, and then click the link to the SSP Web application under Shared Services Administration.
2. Under Search, click Search settings, and then click Default content access account.
3. Specify the password to use for the content access account, and then click OK.

Found this Useful KB article @

Thanks,
JK

Fixing a Pagelayout issue for the migrated site

Hi, Here in my case when i migrated a publishing site after a edit page action in home page and tried to save and exit edit i got stucked with a error message saying:
This page is not using a valid page layout.  To correct the problem, edit page settings and select a valid page layout."
so for this i used a stsadm command to fix this issue
stsadm -o gl-fixpublishingpagespagelayouturl -url http://yoursite/sitename -scope <WebApplication | Site | Web | Page> .... and so on. for my case i used only URL & SCOPE switches. for additional please check the STSADM.EXE -help gl-fixpublishingpagespagelayouturl.

Thanks
jk

To know Occupied size of individual site collection in SharePoint

Use STSADM.EXE
syntax:-
stsadm -o enumsites -url http://xxxxx/ >test.txt

Example:-
stsadm -o enumsites -url http://mysitecollection/ > test.txt

this will write all site collections occupied size in MB's into a text file.

so how it look like...

<Sites Count="1">
  <Site
    Url="http://url"
    Owner="A\user"
    SecondaryOwner="A\user2"
    ContentDatabase="WSS_Content_DB"
    StorageUsedMB="13756"
    StorageWarningMB="0"
    StorageMaxMB="0" /> </Sites>

check it.....

cheer
JK

How to Move a SharePoint site from one site collection to another

Here we got a requirement like moving a site collection from one division to another; the simple way to do is STSADM.EXE.
And steps are as follows:
Move Top Level Site to Sub Site
First, I had a top level site in it's own web application that needed to be a sub-site in another web application.  I've illustrated in the graphic below.  We had to move Site 1 from Site Collection 1 to Site Collection 2.

To export I used:

• stsadm.exe -o export -url http://Site1 -filename Site1.cab -versions 4

To import I used:

• stsadm.exe -o import -url http://SiteA/Site1 -filename Site1.cab

Notes

1. If http://SiteA/Site1 already exists when you do you import you may see an error telling you the templates don't match.  This means the export site was created using a different template to the one that exists in the new location.  To workaround this back up and delete http://SiteA/Site1 then run the import again.
2. Any content that hasn't been approved will not be exported by default.  I used the -versions 4 switch to export all major, minor and draft versions.  You might not need to do this.

Move Sub Site to Top Level Site
Next I needed to move a sub site in Site Collection 1 and move it into an empty Web Application 2.  In the figure below we had to move Site C from Site Collection 1 to Site Collection 2.

For the export I used:

• stsadm -o export -url http://SiteA/SiteC -filename SiteC.cab -versions 4

Because there was no site collection I created one with STSAdm without choosing a template.  Like this:

• stsadm.exe -o createsite -url http://SiteC -ownerlogin domain\administrator -owneremail administrator@domain.com -title Site C

That way you don't get any template clashes when you do your import:

• stsadm.exe -o import -url http://SiteC -filename SiteC.cab

Notes

1. An export should take all content with it.
2. Custom features that have been installed on the source server will need to be packaged up and installed on the target before the import will work.
3. It does matter which account you use for the export.  Strangely, if you don't have the right access the command runs successfully but the export file has got nothing in it.  The import doesn't fail either, but you can't find the site you thought you exported.   I've tried with an account that had local admin rights and was a site collection admin, but that isn't enough.  Always use the farm account.