SharePoint Development: SharePoint FAQS

how to take a backup of document library sharepoint + stsadm

how to change team site temp to some other template
sharepoint variations
How to restore from IIS backups
Where these IIS Backups generally stored?
Memory leaks in windows administration

Difference between WSS and MOSS?

WSS 3.0 offers all the standard site templates to build team sites, document workspaces, blank sites, blogs, wikis, and meeting workspaces.

You can also use WSS 3.0 to create people and group lists. You can integrate WSS 3.0 sites with Access 2007, Excel 2007, Outlook 2007, Word 2007 and PowerPoint 2007. You can create RSS feeds and set up alerts to notify you when content changes on a site. Version control, task notification and alerts all come with WSS 3.0

MOSS 2007 offers all of the features included in WSS 3.0.

In addition, MOSS 2007 offers business intelligence features that allow you to track key performance indicators and build BI dashboards into your team site. The dashboards can assemble and display business info using Excel spreadsheets, SQL, or integrate with line of business applications. Excel Services in MOSS go beyond simply displaying Excel spreadsheets, you can actually stream parts of a spreadsheet, showing or hiding various parts. Workflow can also be integrated into MOSS 2007 and WSS 3.0. And don’t get me started on slide libraries – a much needed and unique way to share and reuse slides that is available in MOSS 2007.

MOSS 2007 also offers My Sites, which are individual mini-sites that can be set up to show who in your company you’re connected to, what your tasks and skills are, your contact information, and more. When I worked at a consulting firm, we used our My Sites to let co-workers know what we did so that they knew whom to call on for a new project. We used the My Sites to ‘advertise’ ourselves.

One of our team members was given the task of putting together a team site for my group that summarized our My Sites and provided other links and resources. He had about one month to build the site, but a big project prevented him from doing it. He asked me to take his place at a presentation of the site to a larger group in the company, giving me two hours notice. Now, while I don’t recommend doing a site in two hours, I was able to do this in less than two hours – more of a tribute to how easy SharePoint is to use than to my skills.

The features that are included in WSS 3.0 are easy for anyone to use and set up. You can create your own team site, set up a blog in minutes, create wikis, use Word to post your blog entries, create slide libraries so that all your employees can find and reuse different slides from different presentations and lots more.

http://www.milesconsultingcorp.com/SharePoint-Portal-2007-Version-Comparison-between-MOSS2007-and-WSS3.aspx

Q) MOSS 2007 Prerequisites

Q) SQL Server Prerequisites. 2005? or 2000?
Hardware requirements

· Front-end Web server and application server computers: a dual-processor computer with processor clock speeds of 2.5-gigahertz (GHz) or higher and a minimum of 2 gigabytes (GB) of RAM.

· Back-end database server: a dual-processor computer with processor clock speeds of 2.0 GHz or higher and a minimum of 2 GB of RAM.

Software requirements Web and Application Server

· Microsoft Windows Server 2003 (Standard, Enterprise, Datacenter, or Web Edition) with Service Pack 1 (SP1)

· Microsoft .Net Framework 2.0

· Microsoft .Net Framework 3.0

· The Web server and application server computers must be configured as Web servers running Microsoft Internet Information Services (IIS) in IIS 6.0 worker process isolation mode.

· Each of the computers must be using the NTFS file system. Windows Server 2003 includes a conversion utility (Convert.exe) that you can use to convert an existing file allocation table (FAT) volume to NTFS without losing data.

Back-End Database Server

· The back-end database server computer must be running Microsoft SQL Server 2005 or Microsoft SQL Server 2000 with Service Pack 3 (SP3) or later. It is assumed that you have installed and configured the database program on the back-end server computer. You do not need to set up or create specific databases for Office SharePoint Server 2007. The Office SharePoint Server 2007 Setup program will create the necessary databases when you install and configure Office SharePoint Server 2007.

In addition to these requirements, if you are using SQL Server 2005, you need to configure surface area settings. Use the following procedure to do this.

Configure surface area settings in SQL Server 2005

1. Click Start, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration.

2. In the SQL Server Surface Area Configuration dialog box, click Surface Area Configuration for Services and Connections.

3. In the tree, open your instance of SQL Server, open Database Engine, and then click Remote Connections.

4. Click Local and Remote Connections, click Using both TCP/IP and named pipes, and then click OK.

Security account requirements

To install Office SharePoint Server 2007 in a server farm environment, at-least 2 accounts are required:

· A user account that you can use to install Office SharePoint Server 2007 and run the SharePoint Products and Technologies Configuration Wizard. This account must be:

· A domain user account.

· A member of the Administrators group on each of your front-end servers.

· A member of the SQL Server Logins, which grants login access to your SQL Server instance.

· A member of the SQL Server Database Creator server role, which grants permission to create and alter databases.

· A member of the SQL Server Security Administrators server role, which grants permission to manage server logins.

· A unique domain user account that you can specify as the Office SharePoint Server 2007 service account. This user account is used to access your SharePoint configuration database. It also acts as the application pool identity for the SharePoint Central Administration application pool and it is the account under which the Windows SharePoint Services Timer service runs. The SharePoint Products and Technologies Configuration Wizard adds this account to the SQL Server Logins, the SQL Server Database Creator server role, and the SQL Server Security Administrators server role. It is recommended that you follow the principle of least privilege and do not make this user account a member of any particular security group on your front-end servers or your back-end servers.

http://www.datasprings.com/resources/articles-information/overview-on-installing-sharepoint-2007

Q) How to remove sharepoint from a server?

Authentication methods SharePoint 2007?

What is kerboroes authenticaton mechanism?

SharePoint Supported IIS Authentication?

difference between basic and windows integrated authentication iis?

Can we use one form SSP in another Form?

how to restore a deleted site?

Indexing in SharePoint?

Difference between index server and Query Server?

Essentially, there are two main components of search, the indexing and the querying. The indexing is the process in which all documents and content are reviewed and many key items about the item (meta data) are stored. The querying is when a user wishes to search for an item. The user enters keywords or phrases and the query engine looks at the indexed content and returns items that match.

The indexing process is called “crawling” and the indexed content is called “crawled content”. The querying and the query results (search results) is the end-user experience of the MOSS Search capabilities. Usually in a MOSS farm, there is one server dedicated to perform the indexing and the querying, however, these functions may be split out onto two separate servers. For this series, the assumption is the same server provides both services to the farm.

What does WSP File contains? What is manifest.xml?

The Solutions File

Next, we look at the solution, which has an extension of “.wsp”. The solutions file contains everything needed to deploy your software. The solutions file is just a cab file, so we can open it by changing the extension from “.wsp” to “.cab” and then double-click on it.

Here’s an example of the content of a WSP file:

Manifest.xml

MyFeature\Feature.xml

ControlTemplates\MyFeatureForm.ascx

MyFeature.dll

Notice the Manifest.xml file at the beginning. A solution file may hold a variety of different files, but it always has a manifest.xml file. This manifest file list what is in the solutions file. Let’s examine the manifest.xml next.

Manifest.xml file and how it relates to the WSP file

The manifest.xml file specifies how the WSP file is put together. Here’s what the manifest.xml file for the above solutions file looks like:

</FeatureManifests>

<TemplateFiles>

<TemplateFile Location="ControlTemplates\MyFeatureForm.ascx"/>

</TemplateFiles>

</Assemblies>

</Solution>

This manifest tells us that this WSP has an Assembly (the dll), a user control (ascx), and a feature.xml file. There may be additonal files in the WSP. You can even embed a movie into the WSP. But unless the file is specified in the manifest, the installer will skip over it during installation.

The root element of the manifest is always <Solution>. The solution ID is a GUID that uniquely identifies your solution (the deployment package) to SharePoint. When you create a new package, you must always create a new GUID. The other elements specify what is in the WSP file and where to find them via the location attribute. The location is the most confusing part. When I first programmed SharePoint, I thought the location must either closely follow the 12 hive’s file structure or the location must be totally independent of the 12 hive. It turns out that both assumptions are false. The location does actually follow the 12 hives, but the root location will change according to the element type.

Let’s examine the element <FeatureManifest>, the location is based on root of the FEATURES at 12\TEMPLATE\FEATURES. If we deploy this WSP, the location tells it to look for the feature.xml file in MyFeature directory in the WSP file and deploy it to 12\TEMPLATE\FEATURES\MyFeature\feature.xml.

If we take a look at the element <TemplateFile> for the control “MyFeatureForm.ascx”, the location is based on the root of the TEMPLATE, which is at 12\TEMPLATE. If you examine 12\TEMPLATE in the hive, you’ll notice that there is already a CONTROLTEMPLATES and there is already a list of controls there. When we deploy, the manifest will tell the installer that the file MyFeatureForm.ascx is located in ControlTemplates directory in the WSP and that the MyFeatureForm.ascx should be deployed to 12\TEMPLATE\CONTROLTEMPLATES\MyFeatureForm.ascx.

Finally, the <Assembly> element specifies where the DLL is located. The root for this element is the web application bin file if you specify DeploymentTarget=”WebApplication”, and the GAC if you specify DeploymentTarget=”GlobalAssemblyCache”. Hopefully by now, you can guess how this works. In the above example, the <Assembly> element tells the installer to look in the root of the WSP file for the MyFeature.dll and deploy it to the GAC, which is typically located in C:\Windows\System32\Assembly on most systems.

The following is a small table listing the element and where the root of the location in the hive.

Manifest Element	Location’s Root
ApplicationResourceFile	12\Resources
Assembly	Web Application bin or GAC
FeatureManifest	12\TEMPLATE\FEATURES
ResourceFile	12\TEMPLATE\FEATURES
RootFile	12
SiteDefinitionManifest	12\TEMPLATE\SiteTemplates
TemplateFile	12\TEMPLATE
WebTempFile	12\TEMPLATE

If you understand the concept that each manifest element has a different root, you will be able to use this knowledge to deploy your web asset to any where you want within the hive. For example, suppose you want to group your user controls (ascx) under a folder. So instead of deploying your user control files to 12\TEMPLATE\CONTROLTEMPLATES, you want it to deploy to 12\TEMPLATE\CONTROLTEMPLATES\MyProject. You can change the location from

<TemplateFile Location="ControlTemplates\MyFeatureForm.ascx"/>

<TemplateFile Location="ControlTemplates\MyProject\MyFeatureForm.ascx"/>

Keep in mind that not all combination makes sense or is valid. Features are always limited to one layer deep. If you try to specify location=”MyProject\MyFeature\feature.xml” for a FeatureManifest element, you will get an error message that you cannot go beyond one level deep. In additon, specifying location=”Myproject\MyFeature.dll” doesn’t make sense either because you’ll end up with a subdirectory inside the GAC.

Generating the WSP using a DDF file

While the manifest determines what’s in the WSP file, you still have to create the WSP file itself. Technically, you can manually build the WSP file by hand, but you can use a diamond definition file to build it for you during a compile. A DDF is basically an instruction file for building WSP files. Let’s examine the DDF file used to build the WSP example. This DDF file is placed in the root of the project folder.

.OPTION EXPLICIT

; Specify the output filename

.Set CabinetNameTemplate="MyFeature.wsp"

; Specify where to create the WSP file

.Set DiskDirectoryTemplate="..\Deployment"

; Compress the solution package

.Set CompressionType=MSZIP

; You always have a manifest file

manifest.xml

; Assembly gets placed in the top level

bin\Release\MyFeature.dll

; Features placed in location specify in FeatureManifest

.Set DestinationDir="MyFeature"

12\TEMPLATE\FEATURES\MyFeature\feature.xml

; User control placed in location specified in TemplateFile

.SET DestinationDir="ControlTemplates"

12\TEMPLATE\ControlTemplates\MyFeatureForm.ascx

The first important line is “CabinetNameTemplate”, which specifies what the outfile file name is going to be. The entry “DiskDirectoryTemplate” may look a bit odd, but it tells the builder where to put the output file. In this case, we say “..\Deployment”. The path is relative to the project’s home directory, so this will generate a Deployment directory into the your Visual Studio’s solution file’s directory and put the WSP file there. The idea is when you compile, all of the WSP file for all projects in the solution will end up in the same deployment directory.

The rest of the DDF handles the adding of files to the WSP archive. You specify the file using a path relative to your project’s root. In the above example, the first file written is manifest.xml and it expects the file to be in the root of the project.

For the assembly, you recall the location for the Assembly in the manifest was location=”MyFeature.dll”. The manifest expects this file to be in the root of the WSP. In your Visual Studio, the path is bin\Release\MyFeature.dll, so the builder will grab the file from your bin directory and add it to the WSP’s root.

The next command is new to us, it said “.SET DestinationDir”. This is because the next item written is feature and the manifest expects it at “MyFeature\Feature.xml”. What we are doing is setting the write directory to “MyFeature” by setting the DestinationDir. Now all files will be written to the MyFeature directory, including the “12\TEMPLATE\FEATURES\MyFeature\feature.xml”.

Finally, we write the user control file. The TemplateFile location in our manifest specifies that it will be located at “ControlTemplates\MyFeatureForm.ascx”. We will use DestinationDir to set it to “ControlTemplates” and then write the user control, which is located in our project at “12\TEMPLATE\ControlTemplates\MyFeatureForm.ascx”.

The DDF file only define how the WSP is build. A utility call makecab does the actualy work. It reads the DDF file, copies the files in the DDF into the wsp. One way to have the files generated automatically is to add a script to the post compile event of your project.

cd "$(ProjectDir)"

MakeCab /f Package.ddf

Now when you compile your project, the event script will run and generate the WSP file.

Conclusion

With tools like WSPBuilder, you can now generate WSP file without fooling around DDF and Manifest files. However, it is still good to understand how the underlying mechanism works. I hope that you have found this article helpful.

iis site not created in one server out of 5 servers? What might be reason?

Timer Job might be got stuck up. That might be one reason.

Move site collections to a new database (split a content database)

Move site collections to a new database (split a content database) (Office SharePoint Server 2007)

Updated: 2009-05-14

Some site collections within a database that hosts multiple site collections are growing faster than expected, and you expect the database to approach its size limit quickly. You can split the database to move the growing site collections to another database or to another server.

Split a content database

You can use this procedure to split a content database that is associated with your site collections. When you split a content database, you are moving a site collection to a different database.

We recommend that you install the April Cumulative Update before you split content databases. This update fixes known issues with the Stsadm mergecontentdbs operation. For more information, see Deploy software updates for Office SharePoint Server 2007.

Before you use the Stsadm mergecontentdbs operation, make sure that there is free space available on the hard disk that is equal to at least three times the size of the source site collection. To determine the size of the site collection, refer to the StorageUsedMB attribute of the Stsadm enumsites operation in step 2 of the following procedure.

To complete the following procedure, you must be a member of both the Farm Administrators group and the Administrators group on the local computer. You must have Full Control permission for any site collection that needs to be moved. The account that you use to perform this procedure must be a member of the db_owner fixed database role in SQL Server.

Split a content database

1. At a command prompt on the drive where SharePoint Products and Technologies is installed, change to the following directory:

%COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin

2. Type the following command, and then press ENTER: Stsadm -o enumsites -url<URL> ><path/file name>.xml

where url is the address of the Web application that contains the site collection that you want to move, and path/file name is the name of the XML file that you want to create with the site collection data.

For more information, see Enumsites: Stsadm operation (Office SharePoint Server).

The previous step creates an XML file that contains all of the site collection URLs in the current database.

3. Open the XML file that you created in a text editing application. If there are any URLs for site collections that you do not want to move, be sure to delete them from the file. The only URLs that should remain in the XML file should be for the site collections that you want to move.

Note:

There is no need to change the site count or any of the other site collection information in the file. Only the URLs are relevant to this procedure.

4. Type the following command, and then press ENTER:Stsadm -o mergecontentdbs -url<URL>-sourcedatabasename<database name>-destinationdatabasename<database name>-operation 3 -filename<file name>

where url is the address of the Web application that contains the site collection that you want; sourcedatabasename is the name of the database that you want to move the site collection from; destinationdatabasename is the name of the database that you want to move the site collection to; operation 3 is the “Read from file” operation; and file name is the name of the file that contains the site collection URLs that you want to move.

For more information, see Mergecontentdbs: Stsadm operation (Office SharePoint Server).

5. Restart IIS by typing the following command, and then pressing ENTER:iisreset /noforce.

Move site collections between databases (SharePoint Server 2010)

http://technet.microsoft.com/en-us/library/cc825328.aspx

How to trouble shoot issues in Custom Timer Job?

check following in Cental Administration

1) Operations-->Timer Job definitions -->Find your Timer Job existed there or not

or Operations-->Timer Job Status(check Status/Progress/Started)

2) Go to Services -->Windows SharePoint Services Timer (restart this)

3). Check your account password if it is changed recently
4) Make sure the account running the SharePoint Timer service is the account which has the administrator Full Control permission over the site and the full permission over the content database.

You can use SharePoint Manager 2007 for monitoring the timer jobs status, schedule and the last run time. It’s very useful and time-saving rather than writing custom code to retrieve those values.

Reading the ULS Logs

The raw ULS logs can be difficult to navigate, and SharePoint provides no built-in viewer. To fill the gap and ease development and administration, free third-party tools exist like SPTraceView and WSS/MOSS Log File Reader (which plugs into Central Administration). Some utilities including SPTraceView will aggregate log data from more than one server in the farm.

Writing ULS Logs

What to write? The ULS logs are appropriate for recording any application lifecycle and diagnostic events not recorded elsewhere, including messages during feature installation, removal, activation, deactivation, startup, shutdown, and exceptions. Message types are identified through the Trace Severity property: Unassigned, Critical Event, Warning Event, Information Event, Exception, Assert, Unexpected, Monitorable, High, Medium, and Verbose.

To write Trace Logs you need a Trace Provider. MSDN provides a sample TraceProvider here. And that one was either adapted or copied into the Community Kit for SharePoint available here. I'm providing both, even though they're (virtually?) identical is that I would hope the CKS code will evolve and I don't expect that of the MSDN content.

Assuming the CKS version works for you (it's buried in the CKS.EWE subtree), you could build a wrapper like this for exception logging:

using System;

using System.Collections.Generic;

using System.Text;

using System.Diagnostics;

using CKS.Utilities.UlsLogs;

using System.Reflection;

namespace EliRobillard.SharePoint.Diagnostics

{

class ULS

{

/// <summary>

/// Log an error to the ULS log

/// </summary>

/// <param name="productName">The name of the application or project.</param>

/// <param name="errorMessage">The text of the error message.</param>

/// <param name="errorCategory">The category of the error, usually the feature or solution being implemented.</param>

public static void LogError(string productName, string errorMessage, string errorCategory)

{

TraceProvider.WriteTrace(0, TraceProvider.TraceSeverity.CriticalEvent, Guid.NewGuid(), Assembly.GetExecutingAssembly().FullName, productName, errorCategory, errorMessage);

}

Or just as simple (and without the overhead of reflection), just add your reference and call WriteTrace() directly. Look for the LogMessage methods inside the CKS.EWE.WikiDiscussion.CoordinateActions receiver, there are good examples of descriptive logging and those methods could be used in your own MyName.SharePoint.Utilities.Diagnostics project.

Change Default Index File Location

In a farm environment it will be usually a requirement to have the index file location on a separate drive and folder as opposed to the default location which is:

"C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications"

You can set this path for an SSP by using the UI through Central Administration. But to set the default path for Office SharePoint Server Search Service and for WSS Search Service you will have to set the location through STSADM command.

Office SharePoint Server Search Service is configured using OSEARCH command:

If its not clear then read here:
stsadm -o osearch -defaultindexlocation e:\Data\MOSS_Search_Index

(By default, the search index will be located at this path on this server. For index servers, you can specify a different path when you create an SSP.

Note:
Changing the index location will reset the index. To move an index with a reset, use the noreset parameter of the Spsearchsensitive or Osearchsensitive operation)

Windows SharePoint Services Search Service is configured using SPSEARCH command:

If its not clear then read here:
stsadm -o spsearch -indexlocation e:\Data\MOSS_Search_Index

(Configures the search server that has the location of where the index resides)

You can also set this path for already created SSP using EDITSSP command:

If its not clear then read here:

stsadm -o editssp -title Sharedservices1 -indexlocation e:\Data\MOSS_Search_Index

(Configures the search server that has the location of where the index resides. This parameter is used in conjunction with the osearch operation. )

References:

SPSEARCH: http://technet.microsoft.com/en-us/library/cc288507.aspx

OSEARCH: http://technet.microsoft.com/en-us/library/cc262920.aspx

EDITSSP: http://technet.microsoft.com/en-us/library/cc262727.aspx

Q) What is SPSearch and OSearch?

http://alliknw.blogspot.com/2008/10/search-service-stuck-at-stopping-or.html

Search service stuck at stopping or starting

>> Search service stuck at stopping or starting

Search as we know is one of the best features on MOSS, Office SharePoint has the best ability to index and search documents, file share’s, and other things as well, it stores the indexed documents in search databases and renders them whenever required.
Well that’s about how it works, but what will you do if your search service is central admin is shows the status as stopping or starting,If your search service is stuck even after you reboot the server this might be a problem,Look at the services console first and check if Windows SharePoint Search service is running and if the Office SharePoint servers search is running as wellThen check if they are running with the right service accounts.
This problem may arise the most when you have the two different accounts configured to run WSS and MOSSWhat should I do?Now you are at a stage where your search service is stuck it’s neither started not stopped. So when nothing works in SharePoint the command line works, let’s get our hero to work. First of all let’s get the search service stopped first.

We will stop the OSearch first and then the WSS search.

To stop the search server you will have to use the command line operation here is the command Stsadm –o osearch –action stop
Run iisreset / noforce

Similarly you will have to stop the wss search service
Stsadm –o spsearch –action stop

This will force stop the services, then we will un-provision the services before we actually start them, now if you are wondering what is provision service command used for it actually Starts or stops the SPService on the local computer or a custom service. To enumerate all the current running services with their service types in the farm, use the enumservices operationYou can know more from the link here http://technet.microsoft.com/en-us/library/cc288605.aspx

Before running the provision service you will have to run stsadm –o enum services command to get the service type and name.
So copy every thing between and Then run the commandstsadm -o provisionservice -action stop -servicetype Osearchsimilarly for sp search.
Then run the following command psconfig -cmd services -install, and install the services.
Then run psconfig -cmd secureresources
Then start spsearch and osearch from command lineStsadm –o spsearch –action start & stsadm –o osearch - action start

Q) How to change service accounts and service account passwords in SharePoint Server 2007 and in Windows SharePoint Services 3.0

To change the passwords for service accounts in SharePoint Server 2007 and in Windows SharePoint Services 3.0, 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:

a. 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

b. 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

c. 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

d. 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:

. Open SharePoint 3.0 Central Administration, click Operations, and then click Timer job definitions under Global Configuration.

a. 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:

. 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

a. 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

b. 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.

c. 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.

Sample script

The following script is an example of how you can use the previous procedure to create a batch file that automates password changes. Use the following syntax to run the script:

FileName.bat DomainName\UserName NewPassword

 @echo off

rem other app pools

echo *** Updating app pool passwords

"%commonprogramfiles%\Microsoft Shared\Web server extensions\12\BIN\Stsadm.exe" -o updateaccountpassword -userlogin %1 -password %2 -noadmin

rem central admin

echo *** Updating Central Admin password

"%commonprogramfiles%\Microsoft Shared\Web server extensions\12\BIN\Stsadm.exe" -o updatefarmcredentials -userlogin %1 -password %2

rem ssp - new

echo *** Updating ssp password for new installs

"%commonprogramfiles%\Microsoft Shared\Web server extensions\12\BIN\Stsadm.exe" -o editssp -title "SharedServices1" -ssplogin %1 -ssppassword %2

rem ssp - upgrade

echo *** Updating ssp password for upgraded installs

"%commonprogramfiles%\Microsoft Shared\Web server extensions\12\BIN\Stsadm.exe" -o editssp -title "Default Web Site" -ssplogin %1 -ssppassword %2

rem osearch

echo *** Updating osearch password

"%commonprogramfiles%\Microsoft Shared\Web server extensions\12\BIN\Stsadm.exe" -o osearch -farmserviceaccount %1 -farmservicepassword %2

echo *** MANUAL UPDATE NEEDED. To update the password, visit the SSP Web application page, click Search Settings, and then click Default Content Access Account.

rem spsearch

echo *** Updating spsearch password

"%commonprogramfiles%\Microsoft Shared\Web server extensions\12\BIN\Stsadm.exe" -o spsearch -farmserviceaccount %1 -farmservicepassword %2

echo *** Updating spsearch content access account

"%commonprogramfiles%\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o spsearch -farmcontentaccessaccount %1 -farmcontentaccesspassword %2

rem restarting IIS

echo *** Doing soft restart of IIS

iisreset /noforce

echo on

Modify the script to include the correct names of each SSP in the server farm. If the server farm is configured to use single sign-on, you must also use the sc config command.

Back to the top

How to update the SharePoint Server 2007 password when SharePoint Server 2007 is installed in a least-privileges configuration

Method 1: Start the SPAdmin service

Start the SPAdmin service on all computers in the farm before you update the password. Stop the service when the operation is complete.

Method 2: Add the database access account to the local administrators group

Add the database access account to the local administrators group of each computer in the farm that has an online search instance. Log on by using that account, and then update the password by using the stsadm command.

When this operation is complete, remove the database access account from the local administrators group of each computer.

http://support.microsoft.com/kb/934838

Q) what are the changes from backup and restore 2007 to 2010?

Content database idle size? Upto 200GB Ok.

http://www.hishamqaddomi.ca/spg/index.php?option=com_content&view=article&id=27:moss-limitations-list&catid=35:moss-administration&Itemid=66

http://technet.microsoft.com/en-us/library/cc262787.aspx - 2010 limits

http://technet.microsoft.com/en-us/library/cc262787(office.12).aspx -2007 limits

Q)What is small farm, medium farma and large farm

Q) how do you take a sharepoint site 2007 to 2010?

inplace backup

u have two database servers in SQL Server?

What these two datbases will be doing?

Active/ Passive

how many mananged path for the webapplication? Upto 20 is soft limit.

If it grows other than that, performance will reduce.

how do u take backups of your sharepoint sites?

serverupdate systemupdate

web.ensureuser

web.allowunsafeupdates

what are the ways to start a workflow?

what are the content sources?

what are the search scopes?

what is a application pool?

run with system.elevatedprivilazes..

what is a content type?

How to deploy workflows?

how to set a quota template for all your 10000 sharepoint sites?

what is a service application? can you give an example?

Initial deployment administrative and service accounts (SharePoint Server 2010)?

SQL Server service account

Setup user account

Server farm account or database access account

http://technet.microsoft.com/en-us/library/ee662513.aspx

What is a webapplication policy?

How to create page layouts?

http://www.hishamqaddomi.ca/spg/index.php?option=com_content&view=article&id=23:creating-your-own-page-layouts&catid=25:customizing-sps-2007&Itemid=64

What's in a SharePoint Managed Path?

I often hear and sense confusion about SharePoint managed paths. Managed paths are essentially 'mount points' for site collections. There are two types of managed paths - Explicit and Wildcard. What's the difference between an explicit managed path and a Wildcard managed path? By default, the root ‘/’ managed path is explicit, meaning only one site collection can be in it and it assumes the identity of the managed path. That's how you browse to http://webapp.fqdn.msft and get a Web page. A Web application without a site collection in the root managed path will return a 404 error when browsing to the root. You could always create another explicit managed path for multiple portal support in a Web application, i.e. http://webapp.fqdn.msft/HR. HR is a peer to '/'. Now, you can no longer have an HR sub-site in the root - you will get a security validation error because the URL space is already taken.

A Wildcard managed path is basically 180 degrees in the opposite direction. A Wildcard managed path can support hundreds or thousands of site collections, but they are appended to the managed path, like http://webapp.fqdn.msft/sites/team, with sites being the Wildcard managed path. It will always return a 404 error when browsing directly to a Wildcard managed path. But, you can create many Wildcard MPs like teams or projects. Wildcard managed paths are like a sorting mechanism for site collections.

Stsadm Commands list

http://www.wssdemo.com/Lists/stsadm/AllItems.aspx

Q)How to migrate SharePoint 2007 to SharePoint 2010

A 1)Thought it would be nice to put together a SHORT CHECK LIST of steps to go from 2007 to 2010 in no time. I will also add, that PowerShell is needed in this, but a powerful set of steps to do this FAST!

1.Backup your current 2007 Production Database

(no down time for end users of your 2007 environment this way!)

2.Restore the database to your new SQL Server database

3.Powershell command: Upgrade-SPContentDatabase

4.Powershell command: Mount-SPContentDatabase

And THAT’S IT! Those 2 basic powershell commands will get your restored content database to 2010 in no time flat. From there, you can run your visual upgrade, or run any export/import scripts to move your content to a whole new site collection. Hope that helps someone looking to get started with a migration! Personally I just don’t see the need (personally) to purchase any big migration tools that cost thousand of dollars… it doesn’t get any easier than that.

A 2) Inplace Upgrade

Database Management Concepts for Large and Growing Content Databases

http://blogs.technet.com/b/wbaer/archive/2007/05/08/database-management-concepts-for-large-and-growing-content-databases.aspx

SharePoint Development

Thursday, August 18, 2011

SharePoint FAQS

Change Default Index File Location

Search service stuck at stopping or starting

No comments:

Post a Comment