Upgrade windows 2003 32 bit DC to windows 2008 64 bit DC

Adding Windows Serve 2008 R2 AD DS in Existing Windows Server 2003 32 bit forest

Prepare Windows Server 2008 R2 64 bit
1. Install windows Server 2008 R2 from the installation DVD [ http://www.petri.co.il/how-to-install-windows-server-2008-step-by-step.htm ]
2. Give a Static IP address to the server.
3. Configure the Preferred DNS server as the Windows server 2003 DC.
4. Install the updates from the following site. http://windowsupdate.microsoft.com/. This should install the needed SP2 and post hot fixes.
5. Join the Machine to the Domain as a Member Server. Reboot the Server.

Installing Pre-Requisites
Make sure that .NET Framework 3.5 SP1 is installed.

Preparing Windows Server 2003 Forest for Windows Server 2008 R2 DC
Prepare the Forest
1. Log-on to the Windows 2003 DC Schema Master with the Enterprise Admins, Schema Admins, and Domain Admins groups privileges to prepare the Forest for Windows Server 2008 R2 DC.
2. Insert the Windows Server 2008 R2 DVD into the DVD drive.
3. Run Command Prompt as Administrator.
4. Run the following command from the DVD.
a. D:\support\adprep\adprep /forestprep [ Note: If it is Windows Server 2008, it will be D:\sources\adprep\adprep /forestprep ]
5. If you have multiple Windows Server 2003 DC’s, let the replication finish or use replmon to manually replicate the Domain Controllers before preparing the Domain for Windows Server 2008 R2 DC.

Prepare the Domain
1. Log-on to the Infrastructure master with Domain Admin privileges.
2. Insert the Windows Server 2008 R2 DVD into the DVD drive.
3. Run command prompt as Administrator.
4. Run the following command from the DVD.
a. D:\support\adprep\adprep /domainprep [ Note: If it is Windows Server 2008, it will be D:\sources\adprep\adprep /Domainprep ]
5. If you have multiple Windows Server 2003 DC’s, let the replication finish or use replmon to manually replicate the Domain Controllers before preparing the Domain for Windows Server 2008 R2 DC.
Note: For other Deployment scenarios please follow this link. http://technet.microsoft.com/en-us/library/cc771433(WS.10).aspx

Adding Windows Server 2008 R2 as an Additional Domain Controller.
1. Open Server Manager. Click Start, point to Administrative Tools, and then click Server Manager.

2. In Roles Summary, click Add Roles.

3. If necessary, review the information on the Before You Begin page, and then click Next.

4. On the Select Server Roles page, click the Active Directory Domain Services check box, and then click Next.

5. If necessary, review the information on the Active Directory Domain Services page, and then click Next.

6. On the Confirm Installation Selections page, click Install.

7. On the Installation Results page, click Close this wizard and launch the Active Directory Domain Services Installation Wizard (dcpromo.exe).

8. On the Welcome to the Active Directory Domain Services Installation Wizard page, click Next.

9. On the Operating System Compatibility page, review the warning about the default security settings for Windows Server 2008 R2 domain controllers, and then click Next.

10. On the Choose a Deployment Configuration page, click Existing forest, click Add a domain controller to an existing domain, and then click Next.

11. On the Network Credentials page, type the name of any existing domain in the forest where you plan to install the additional domain controller. Under Specify the account credentials to use to perform the installation, click My current logged on credentials and then click Set. In the Windows Security dialog box, provide the user name and password for an account that can install the additional domain controller. To install an additional domain controller, you must be a member of the Enterprise Admins group or the Domain Admins group. When you are finished providing credentials, click Next.

12. On the Select a Domain page, select the domain of the new domain controller, and then click Next.

13. On the Select a Site page, select a site from the list or select the option to install the domain controller in the site that corresponds to its IP address, and then click Next.

14. On the Additional Domain Controller Options page, make the following selections, and then click Next:
1. DNS server: This option is selected by default so that your domain controller can function as a Domain Name System (DNS) server. If you do not want the domain controller to be a DNS server, clear this option.

15. If you selected Use advanced mode installation on the Welcome page, the Source Domain Controller page appears. Click Let the wizard choose an appropriate domain controller or click Use this specific domain controller to specify a domain controller that you want to provide as a source for replication to create the new domain controller, and then click Next.

16. On the Location for Database, Log Files, and SYSVOL page, type or browse to the volume and folder locations for the database file, the directory service log files, and the system volume (SYSVOL) files, and then click Next.
Windows Server Backup backs up the directory service by volume. For backup and recovery efficiency, store these files on separate volumes that do not contain applications or other nondirectory files.

17. On the Directory Services Restore Mode Administrator Password page, type and confirm the restore mode password, and then click Next. This password must be used to start AD DS in Directory Service Restore Mode (DSRM) for tasks that must be performed offline.

18. On the Summary page, review your selections. Click Back to change any selections, if necessary.
To save the settings that you have selected to an answer file that you can use to automate subsequent AD DS operations, click Export settings. Type the name for your answer file, and then click Save.
When you are sure that your selections are accurate, click Next to install AD DS.

19. On the Completing the Active Directory Domain Services Installation Wizard page, click Finish.

20. You can either select the Reboot on completion check box to have the server restart automatically or you can restart the server to complete the AD DS installation when you are prompted to do so.

Note:- Once the replication is done between the 2003 DC and 2008 DC, you can either change their Static IP addresses or change the DHCP settings for preferred DNS servers, to point it to the new 2008 DC. The same above steps can be taken to add another Additional 2008 DC.

---------------------------------------------------------------------------------------

Alternate Access Mapping error

Issue:- Not able to change any settings in AAM
Error:-
Unexpected end of file while parsing Name has occurred. Line 29, position 13. at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseQName(Boolean isQName, Int32 startOffset, Int32& colonPos)
at System.Xml.XmlTextReaderImpl.ParseElement()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.LoadXml(String xml)
at Microsoft.SharePoint.Administration.SPAlternateUrlCollection.HasMissingUrl(String xml)
at Microsoft.SharePoint.Administration.SPContentDatabase.UpdateAlternateAccessMapping(SPAlternateUrlCollection collection)
at Microsoft.SharePoint.Administration.SPAlternateUrlCollection.UpdateAlternateAccessMappingInContent()
at Microsoft.SharePoint.Administration.SPAlternateUrlCollection.Update()
at Microsoft.SharePoint.ApplicationPages.EditOutboundUrlsPage.BtnSave_Click(Object sender, EventArgs e)
at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

This above error comes after installing April Cumulative pack for SharePoint 2007

This is the extract from the article http://support.microsoft.com/kb/973410 , which is included in the August cumulative update http://support.microsoft.com/kb/974982

"You have a Web application that has more than five incoming URLs. You cannot change Alternate Access Mappings (AAM) settings after you install the 2007 Microsoft Office system cumulative update that was released in April 2008"

There is one more article which has the same issue of editing URL's for more than 5 zone entrie, but does not have the parsing error. Still in this article there is no resolution given by MS. http://support.microsoft.com/kb/2000628

Change Secondary Schema to IE7 for SharePoint Designer 2007

Error:- "In Internet Explorer 6.0 the tag "" is not permitted.

In SharePoint Designer 2007, we need to change the Secondary Schema to IE7 so that certain tags would render without any errors.

On the machine where SharePoint Designer 2007 is installed:
1. Browse to %SystemDrive%\Program Files\Common Files\Microsoft Shared\OFFICE12\SCHEMAS\HTML
2. Copy the IE6_0.XSD and then rename the copied file to IE7_0.XSD
3. Open the IE7_0.XSD file using Notepad or Visual Studio and edit the following lines:
<-- xsd:schema color="#ff0000" targetnamespace="'http://schemas.microsoft.com/intellisense/<--font" version="1.0"><--xsd:schema color="#ff0000" targetnamespace="'http://schemas.microsoft.com/intellisense/<-- xsd:schema version="1.0" targetNamespace='http://schemas.microsoft.com/intellisense/ie7' elementFormDefault='qualified' xmlns='http://schemas.microsoft.com/intellisense/ie7' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:vs='http://schemas.microsoft.com/Visual-Studio-Intellisense' xmlns:fp='http://schemas.microsoft.com/FrontPageScripting'
vs:clientom="ie6_0dom.tlb"
vs:ishtmlschema="true"
vs:isserverschema="false"
vs:htmlflavor="4.0"
vs:MultipleScriptLanguages="true"
vs:cssschema="CSS 2.1"
vs:SuccinctFriendlyName="Internet Explorer 7">
Note: the DOM reference for client side IntelliSense (vs:clientom=”ie6_0dom.tlb) remains the same.
Save and close the file.

Next, open your registry and browse to:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Common\Schemas\] Note: This is on 32bit version machines

If you are using Windows Server 2008, 64bit machine
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\Common\Schemas

Create a new key and name it ie7_0.xsd and then create the following string values:
Value Name:- Abbrev Name
Value Data:- IE7
Value Name:- File
Value Data:- html\\ie7_0.xsd
Value Name:- Friendly Name
Value Data:- Internet Explorer 7.0
Value Name:- URI
Value Data:- http://schemas.microsoft.com/intellisense/ie7

Now, restart SharePoint Designer 2007 and click on Tools > Page Editor Options… In the Secondary Schema drop down select Internet Explorer 7.0. Click OK.

SharePoint 2010 Security Options

Note:- This is subject to change as this is not the Final release

The new options in 2010 we can see are in General Security and Information Policy
In General Security we have new options like,
1. Configure Managed Accounts. :- The service accounts used in SP 2010 are registered or we can register them manually before using the Account for a service.

When you Edit or Add a User account, you will get below options.

2. Configure password Change settings. :- In SP 2010 we have an option to change/reset service account passwords either Manual or Automatic selection. In either ways SharePoint will send notification email to User or Group of Users as configured in this setting.

3. Manage WebPart Security. :- This is quite Self Explanatory.
4. Configure Secure Token Service. :- Not exactly sure about this token service, but surely its related to other Applications and FARM’s who can use this (.svc) URL as endpoints for communication between them.

5. Manage Trust. :- It gives a message “There are no Trusted Identity Providers defined.”

----------------------------------------------------------------------------------

New Features in SharePoint 2010

Note:- These are subject to change as this is Beta Version.
There would be many others which I have missed, but these are the ones which are visible easily.

1. Database failover options, dependant on SQL mirroring.
2. Search, people, BDC, Excel Services all working as individual entities providing robust and
easy to maintain environment.
3. Access Database Integration at server level.
4. Fast Search Server.
5. Lotus Notes Connector for Crawling data.
6. New Connection options for importing User Profiles from different directories other than AD.
7. In-Built Monitoring and Health check on servers.
8. Enhanced options of Site Usage Reports, trimming reports and storing them directly to a library. Web Analytics Report.
9. Direct Edit option using SharePoint Designer 2010 only. Out of the box workflows can also be
edited.
10. New Site Templates [ bugs, projects, charity, Enterprise Wiki ]
11. Enhanced RSS Feed options. Tagging Options.
12. Major My Site template changes. Combination of facebook and newsgator features.
13. Granular Backup and Restore options for site collections and Individual Lists.
14. Recover data from unattached content databases.
15. GUI mode to integrate SQL Reporting services.
16. PowerShell Scripting and Management Console available.
17.Silverlight webpart and few more.
18.External Content Type options
19.Connection to any external application of another FARM which has service app .svc extension (not sure what is this as I am not into developing)

Enterprise Search 2010 SharePoint

Testing out of the box Enterprise Search 2010

Note:- This is subject to change as this is not from the final release.
1. Wildcard (*) is supported.

2. The “Notes” section in PPT files is also indexed. It is not so in MOSS 2007

3. “AND”, “OR”, “NOT” are taken as Boolean operators. “and”, “or”, “not” are taken as normal words

4. Query without the brackets [windows near services] will give results where only these 3 words exist in the file.

5. Double Quotes [ “ ” ] work.

6. ‘+’ ‘-‘ are not taken as Boolean operators in 2010 when used with phrases.

7. Query without the Brackets [ windows –author:greg ]. Here the string is taken as an operator. This will show all files with “windows” in it but not the one whose author is “Greg”.

8. Query without the Brackets [ windows author:greg ]. Here the string is taken as an operator. This will show all files with “windows” in it but only the one whose author is “Greg” and not other files.

9. [ title:xxx ] [ -title:xxx ] works as expected.

10. [ auther:greg title:tech ed ] will show 1 file.

11. [ auther:greg -title:tech ed ] will show 0 file. “No results matching your search were found”

12. [ 1/4 ] [ “1/4” ] both work as it works in Longitdue. Same set of results.

13. [ windows AND ( sharepoint OR services) ] works the same way in both.

In 2010 Search Results page. On the left hand side below options are given.

When we Edit the Search Results page. The following webparts are shown.

Sharepoint 14 Installation [ Beta Version ]

Fresh Installation of SharePoint 2010 [ SP 14 Beta Version ]

Fortunately I got a hand on the Beta Version of SharePoint 2010 (SP14). I have included only those screenshots which are different from MOSS 2007 installation. other steps and configuration are the same as MOSS 2007 installation.

Running the Setup of Beta Version.

Pre-Requisites Check. Lot of softwares to be installed. It needs Internet connection enabled on the server.

During PSConfig, this is the new window we get related to "Passphrase Password"
Once PsConfig finishes Successfully and the Services are started, SQL Databases are created as below.

RegEdit Screenshot

Features of SharePoint 2010

New features Sneak Preview of SharePoint 2010
Though the features and look and feel of the new product is farely good, I will not be surprised to find double the bugs in that product as SharePoint 2007.

Upgrade and Central Administration is quiet a relief to look at but then again it depands on how smoothly it works on large enterprises where already a lot of customization is done. Microsoft has still not released anything on SharePoint 2010 Basic installation or upgradation path from that type of installation. Will have to wait and watch......

Capture Site Collection deleted immediately

Even though SharePoint 2007 has a wonderful feature of Recycle Bin, its disadvantage is that it does not capture Site Collections Deleted. If we have to restore the deleted Site Collection, get it from the backup and if no backup, forget the site and re-create again.

I hope that archiving of a Site Collection feature is introduced in SharePoint 2010, but in the mean time, we can still use an open source tool, easy to deploy on the SharePoint FARM given by CodePlex.

This tool will capture the deleted site collection immediately and send a mail to the Site Administrators with the name of the person who deleted the site. Also allowing you to restore the site if needed immediately.

Microsoft IT Site Delete Capture LE 1.0

Event ID 5586, Cannot generate SSPI context

You get "Cannot connect to Configuration database" while accessing Central Administration or any SharePoint sites.

In Event Viewer we get the below error on the SharePoint server.

Event Type: ErrorEvent Source: Windows SharePoint Services 3Event Category:
Database Event ID: 5586
Date: 7/13/2009
Time: 12:36:31 AM
User: N/A
Computer: COMPUTERNAME
Description:Unknown SQL Exception 0 occured. Additional error information from SQL Server is included below. Cannot generate SSPI context.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

While trying to connect using connect.udl file, it gives the same error "Cannot generate SSPI Context"

On the SQL 2005 Server we get the below error.

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 17836
Date: 6/25/2009
Time: 11:51:45 PM
User: N/A
Computer: COMPUTERNAME
Description:
Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT:IP of SP Server]

Quick Resolution:- Reboot the SQL Server 2005

Error Troubleshooting:-
How to troubleshoot the "Cannot generate SSPI context" error message
http://support.microsoft.com/kb/811889

This is related to some SPN configurations gone incorrect on the SQL server.

Resolution:-
Logon to the server using Domain Admin rights.
Download Setspn.exe from Microsoft site to set the SPN's for the SQL server.

At command prompt go to the location where setspn.exe was installed.
C:\Program files\support tools>setspn -L MyDomain\MyUserName
Registered ServicePrincipleNames for CN=MyUserName Service Account, OU=Service Accounts, DC=MyDomain,DC=com: mssqlsvc/MyServer1.MyDomain.com:MyPort mssqlsvc/MyServer2.MyDomain.com:MyPort mssqlsvc/MyServer3.MyDomain.com:MyPort

If you are getting the error (Cannot generate SSPI context), you will not find the SQL server name in the list displayed by the command.

To Register your SQL server type the following command.
setspn -A MSSQLSvc/MyServer.MyDomain.com:1433 MyAccount

Note:- MyServer will be the SQL server name to which you are not able to connect.

Again run the setspn -L MyDomain\MyUserName command, you should find your SQL servers FQDN registered.

Checklist before Planning System requirements for Deploying Sharepoint

Questionnaire

=> Access SharePoint sites from Internet (Y/N) If Yes,
No. of Current users who will be accessing SharePoint sites.
No. of Users projected to Access SharePoint sites by next 5 yrs.

=> No. of Current users who will be accessing SharePoint sites. (Intranet)
=> No. of Users projected to Access SharePoint sites by next 5 yrs. (Intranet)

=> Data to be uploaded on the SharePoint sites (in GB/TB)
=> Data to be uploaded on the SharePoint sites (in GB/TB) in next 5 years

=> No. Of Geographical Site locations

=> Requirement of Incoming Email Libraries (Y/N)
=> Requirement of Search Functionality (Y/N)

=> Search Usage (Heavy/Average)
Heavy - Using Customised/Enhanced Search/Federated Search
Heavy - Support for searching external data stores.
Average - Out of the box Search Functionality

=> Use of InfoPath Services and Excel Services (Y/N)
=> Usage of MySites (Y/N)
=> Usage of Business Data Catalog (Y/N)

=> Sites Redundancy/Failover Requirements?
=> Plan to Customize SharePoint Sites (Y/N)

=> Support for Multiple Language (Y/N)

=> Recovery Server Hardware and then restore sites on Production site.

Note: Some questions may not relate exactly to the hardware, but it will depand on performance suggesting to add more WFE servers to the FARM or no

Glitch after installing Service Pack 2 on MOSS

As usuall Microsoft has done it again and I am not surprised. There is no single patch or Service Pack released by Microsoft which is uncontroversial. Even after Service Pack 2 release of MOSS, it makes sure that they keep getting calls to PSS support.

When you install the 2007 Microsoft Office servers Service Pack 2, the product expiration date is activated incorrectly
http://support.microsoft.com/kb/971620

Link to download WSS 3.0 SP2
http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en

Link to download SP2 for MOSS 2007
http://www.microsoft.com/downloads/details.aspx?FamilyID=b7816d90-5fc6-4347-89b0-a80deb27a082&displaylang=en

Read more information on SP2
http://technet.microsoft.com/hi-in/office/sharepointserver/bb735839(en-us).aspx

Cannot perform this operation. The file is no longer checked out or has been deleted.

Issue:- You get the error while you check-in a file in SharePoint library.

Resolution:-
1. Site Actions -> Site Settings

2. Go to "Site content types" click on the "Document" content type.

3. The status for the Title column should be "Optional" and not "Hidden".

On MOSS server Contents Site & SSP are using same web application & search is broken

Issue:
In case we use single web application for Content & SSP in MOSS (Microsoft Office SharePoint Server 2007) & search breaks at some point.
We create a new SSP by creating another web application.
Now if we try to change associations to use the newly created SSP,
We are not able to do that because the content site is also a Shared Services "Administration Host"

Resolution:
Last good full farm backup when search was working, if we don't have it

Workaround:
1. As usual start with all possible backups (A full farm backup may fail due to this bad ssp)
2. Backup content databse attached to content site
3. Detach it from existing web application & attach to new web application
(stsadm -o restore may not work)
4. From Central admin>Application Management>Delete Site Collection
5. Delete /ssp/admin site collection
6. IISReset
7. Go to Shared Services Administration & change associations
8. Make new ssp Default
9. Delete old ssp without removing databases
(if we keep old ssp search on new ssp may not work)
10. Run full crawl of content sources & check search after it completes

Note:
We lose old ssp configurations for example Audiences
In case of major issues revert back to last good backup
NOT recommended on Production Servers

Uninstall Microsoft##SSEE (Windows Internal Database Engine which comes with WSS3.0)

Backup all the SQL databases for the Microsoft##SSEE SQL instance
or Copy or rename folder 'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\ [Uninstall does not remove the folder though :-)]
Run the command below to uninstall that instance:
msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe

Enable this Form to be filled out by using a browser - checkbox is grayed out while publishing an InfoPath Form

Issue:- "Enable this Form to be filled out by using a browser" checkbox is grayed out while publishing an InfoPath Form.

Even if we try to forcefully Activate the Enterprise Site Collection Feature using stsadm, it does not resolve the issue.

By default when you Browse to the main Site Collection -> View All Site Contents. You should be able to see "Form Templates" by default if the Site Collection "Feature Office SharePoint Server Enterprise Site Features" is Activated.

If the Form Templates is not visible even if "Office SharePoint Server Enterprise Site Features" is Activated then follow the below steps

Resolution:-

1. Open the Main Site Collection in SharePoint Designer.

2. Select the root URL and Right Click -> NEW -> SharePoint Content -> Select Document Library -> Select Form Library -> Under options type the name as "FormServerTemplates". Click on OK.

3. The Library will be created. Right click on "FormServerTemplates" -> Select Properties -> On settings Tab change the name to "Form Templates" and uncheck the option "Use a template for new documents"

4. Click OK. Now you will see the "Form Templates" on the view all site content page.

5. Deactivate and Activate "Office SharePoint Server Enterprise Site Features" once again and now You should be able to publish the InfoPath form with "Enable this Form to be filled out by using a browser" checkbox Enabled.

How to identify the template used to create a site..

hi Friends

I use to wonder in case solution (WSP files) when deployed on the server globally

If the solution are available the sites are also made using those solution . Now I had a Question in my mind that how could I find which templates are bening applied on the site .In case site are moved i.e server is backup is restored over a new server , Creation on new configuration database , Solution are removed etc

At last we end up in getting message

"Page not found' or "Internet Explorer could complete this request " or " Unkown Error"

I created a Aspx file usign the code snipet given below

Code Snippet [ before every tag, '--' is added, you need to remove the hyphens]

==========================================================

<--script type="text/javascript" <--%@ Assembly Name="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>
<--%@ Page Language="C#" MasterPageFile="~/_layouts/application.master" Inherits="Microsoft.SharePoint.WebControls.LayoutsPageBase" %>
<--%@ Import Namespace="Microsoft.SharePoint" %>

<--script runat="server">
protected override void OnLoad(EventArgs e){
SPSecurity.RunWithElevatedPrivileges(delegate()
{
using (SPWeb thisWeb = this.Web)
{
lblWebTempalte.Text = thisWeb.WebTemplate;
lblWebTemplateID.Text = thisWeb.WebTemplateId.ToString();
}
});
}
<--/script>
<--asp:Content ID="Main" runat="server" contentplaceholderid="PlaceHolderMain" >

Web Template: <--asp:Label ID="lblWebTempalte" runat="server" />

Web Template ID: <--asp:Label ID="lblWebTemplateID" runat="server" />
<--/asp:Content>

<--asp:Content ID="PageTitle" runat="server" contentplaceholderid="PlaceHolderPageTitle" >
Site Template Information
<--/asp:Content>

<--asp:Content ID="PageTitleInTitleArea" runat="server" contentplaceholderid="PlaceHolderPageTitleInTitleArea" >
Site Template Information
<--/asp:Content>

<--/script>
===========================================================

Web Template: ----->Web Template ID:

============= ================

ABSENCE ----> Absencevacationschedule ----> 75811

PROJMULTI ---->Budgetingtrackingmultipleprojects ----> 75819

BT ----> Bugdatabase ----> 75801

CALLCENTER ---->Callcenter ---->75812

PROJCHANGE ---->Changerequest ----> 75818

COMPROC ---->Complianceprocesssupport ---->75813

DR ---->Documentlibraryreview ---->75803

EVENTPLAN ----> Eventplanning ---->75814

EXREPORTS ---->expensereimbursementapproval ----> 75815

HELPDESK ---->HELPDESK ---->75816

IT ---->InventoryTracking ---->75804

ITTEAM ---->ITTeamWorkspace ---->75817

JRIM ---->JobRequisition ---->75805

KB ---->KnowledgeBase ---->75806

LL ---->LendingLibrary ---->75807

PATM ---->PhysicalAssetTracking ---->75808

PROJSING ---->ProjectTrackingWorkspace ----> 75820

RER ---->RoomEquipmentReservations ---->75809

ST ---->SalesLeadPipeline ---->75810

List of Out of the box MOSS 2007 Template ID Information

========================================================

NAme ---->Web Template: ----> Web Template ID:

============= ================

GLOBAL ---->Global template" ----> 0

STS ---->Team Site,Blank Site,Document Workspace ----> 1

MPS ---->Basic Meeting Workspace ----> 2

MPS ---->Blank Meeting Workspace ---->2

MPS ---->Decision Meeting Workspace ---->2

MPS ---->Social Meeting Workspace 2

MPS ---->Multipage Meeting Workspace 2

CENTRALADMIN ---->Central Admin Site ----> 3

WIKI ---->Wiki Site ---->4

BDR ---->Document Center ----> 7

BLOG ---->Blog ---->9

SPS ---->SharePoint Portal Server Site ---->20

SPSPERS ---->SharePoint Portal Server Personal Space ---->21

SPSMSITE ---->Personalization Site ---->22

SPSTOC ---->Contents area Template ----> 30

SPSTOPIC ---->Topic area template ---->31

SPSNEWS ---->News area template ---->32

SPSNHOME ---->News Home template ---->33

SPSSITES ---->Site Directory area template ----> 34

SPSCOMMU ---->Community area template ---->36

SPSREPORTCENTER ----> Report Center Site" ---->38

CMSPUBLISHING ---->Publishing and Team Collaboration Site ----> 39

OSRV ----> Shared Services Administration Site ----> 40

SPSPORTAL ---->Corporate Intranet Site ---->47

SRCHCEN ---->Search Center ---->50

PROFILES ---->Profiles ----> 51

BLANKINTERNETCONTAINER ---->Internet Presence Web Site ---->52

BLANKINTERNET ---->Publishing Site ---->53

BLANKINTERNET ---->Press Releases Site ---->53

BLANKINTERNET ---->Publishing Site ---->53

SPSMSITEHOST ----> My Site Host ---->54

SRCHCENTERLITE ----> Search Center Lite ---->90

PWA ---->Project Web Access Site ----> 6221

PWS ----> Project Workspace ---->6215

OFFILE ----> Records Repository ----> 1483

OFFILE---->Records Repository ---->14483

To find out how many Solutions are deployed on the server we can achieve by

Central administration > operation> solution management

We would be finding the List of WSP file or Cab files installed

To find the solution from the Configuration database to you configuration database (Eg Wss_config)

Go to the databases open the table Dbo.objects .you would be finding the List of Solution in inside the tables

Note:- Above Steps would be senario Specfic .before doing any step Its advisable to take a full farm back and Sql back up to be on safe side

Full farm Backup (GUI)

hi Friends
Recently I faced a issue related to Full farm backup .When I use to take a Full farm backup we use to get error
"object (database name) failed in event OnBackup. for more information, see the error log located in the backup directory. sqlException: BACKUP DATABASE is terminating abnormally.

Digging more in to the issue we came accross many settings. but the one thats solved the problem was a registry entry
We added the registry key “SessTimeout” at the location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters.
We gave the value as 360 for SessTimeout

Here is the article you can check
http://support.microsoft.com/default.aspx?scid=kb;EN-US;102981

Schedule Automatic WSS3.0 Backups

Back up a farm by using the Stsadm command-line tool (Windows SharePoint Services 3.0)
http://technet.microsoft.com/en-us/library/cc288541.aspx

Back up a farm by using SQL Server Tools (Windows SharePoint Services 3.0)
http://technet.microsoft.com/en-us/library/cc288402.aspx

How to schedule a database backup operation by using SQL Server Management Studio in SQL Server 2005
http://support.microsoft.com/?kbid=930615

Restore a farm after a configuration database problem (Windows SharePoint Services)
http://technet.microsoft.com/en-us/library/cc512814.aspx

MOSS/WSS3.0 DISASTER RECOVERY STEPS

From File system backup following:
1.C:\inetpub\wwwroot
2.C:\windows\assembly
3.C:\windows\system32\drivers\etc\hosts file
4.C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\
5.C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\
6.C:\Program Files\Microsoft Office Servers\12.0 (Not Applicable in WSS3.0)
(If you are using any custom locations instead of above default locations please backup them.)

From Registry Editor backup following:
1. 1.HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure
2.HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0

Back Up IIS Metabase (IIS 6.0) using following steps:
To create a non-portable backup (password not required)
1.
In IIS Manager, right-click the local computer, click All Tasks, and click Backup/Restore Configuration.
2.
Click Create Backup.
3.
In the Configuration backup name box, type a name for the backup file.
4.
Click OK, and then click Close.
The IIS metabase is created in the systemroot\system32\inetsrv\MetaBack folder.

Back up Central Administration Configured Settings:
1. In Central Administration,
2. Here is the following links that need to be documented(screenshot) to have a
backup of your configuration

a. Operations
i. Outgoing e-mail settings
ii. Incoming e-mail settings
iii. Approve/reject distribution groups
iv. Master site directory settings
v. Alternate access mappings
vi. Solution Management
vii. Services on Server (for each server)

b. Application Management
i. Define managed paths
ii. Web Application outgoing e-mail settings
iii. Web application general settings
iv. Content Databases
v. Web Application list
vi. Records center
vii. Manage form templates
viii. Configure InfoPath Forms Services
ix. Manage data connection files
x. Manage the Web service proxy
xi. Create or configure this farm’s shared services
xii. Grant or configure shared services between farms
xiii. Configure session state
xiv. Security for Web Part pages
xv. Self-service site management
xvi. User permissions for Web application
xvii. Policy for Web application
xviii. Authentication providers
xix. Manage Search service
xx. Workflow settings

c. Shared Services Administration (Not Applicable in WSS3.0)
i. In each SSP, document the following
1. User profiles and properties
2. Profile services policies
3. My Site settings
4. Trusted My Site host locations
5. Published links to Office client applications
6. Personalization site links
7. Personalization services permissions
8. Search settings
9. Search usage reports
10. Edit Excel Services settings
11. Trusted file locations
12. Trusted data connection libraries
13. Trusted data providers
14. User-defined function assemblies
15. Audiences
16. Usage Reporting
17. Import application definition
18. View applications
19. View entities
20. Business Data Catalog permissions
21. Edit profile page template

3. Next we will need to have you take a backup using the Central Administration site
a. In the Operations tab, click on Perform a Backup
b. Check the box next to Farm, click on Continue to Backup Options
c. Be sure that Full is selected
d. Enter in a share for the backup to be placed in that folder
i. Note: The MOSS service account needs full control for the Share, as well as
the NTFS permissions.
e. Click OK
i. It will take a few minutes before the backup is started.

Full Farm Backup using command prompt:
stsadm -o backup -directory -backupmethod full

To backup individual site collections:
Open a command prompt
Cd “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN”
stsadm -o backup -url -filename -overwrite

Backup all SharePoint Databases from SQL Server Management Studio:
1. Configuration database (Configuration database name can be found from Central admin>Operations>Topology and Services>Servers in Farm)
2. Content Databases (We can find the association of the web application and Content database from Central administration>Application Management>Content Database>On right hand side we need to select drop down list>change web application & we need to select a web application for which the Content database will be listed below.)
3. WSS_Search Database (WSS Search database name can be found from Central admin>Operations>Topology and Services>Services on server>Click on Windows SharePoint Services Search>Search Database>Database Name)
4. Shared Services DB Databases (Not Applicable in WSS3.0)
5. Shared Services SEARCH Databases (Not Applicable in WSS3.0)
6. Any other databases related to Product integrated with SharePoint (For example: SQL Reporting Services, Project Server etc)

4.Disconnecting from existing Configuration Database & creating a new Configuration Database:
This will cause loss of following:
1. Central admin configured settings (Need to be reentered from screenshots taken earlier)
2. Any solutions deployed in farm (Need to read & redeploy)
3. 3rd party web parts or templates (Need to reinstall)
4. Integration with other products (Need to reconfigure)

5. After the backup finishes successfully, run SharePoint Products and Technologies Configuration from each server(one at a time)
a. Click next; click Yes
b. Select Disconnect from this server farm; click Next

6. Creating a new configuration database;
run the SharePoint Products and
Technologies Configuration from the server that will be hosting Central
Administration.
a. Click Next; Click Yes
b. Select No, I want to create a new server farm
c. Type in Database server
d. Make sure the Database name is unique(This will be the name of your
configuration database)
e. Enter in your username and password
f. Click next
g. Specify a port(optional)
h. Click Next; Click Next

7. Connect other servers up to the farm; run SharePoint Products and Technologies Configuration from the other servers one at a time
a. Click Next; click Yes
b. Make sure Yes, I want to connect to an existing server farm is selected; click
Next
c. Enter in the database server name; Click Retrieve Database Names
d. Select the database that you just created for Database name
e. Type in the password for the service account
f. Click Next 3 times

8. Start the services in the Central Administration -> Operations -> Services on server
a. Start the services that were documented in the previous steps for each server
b. Make sure the services are in the Started status, not Starting

9. Restoring from backup; Central Administration -> Operations -> Restore from backup
a. Specify the location of the backup; click OK
b. Select the backup that was taken in the previous steps; Click Continue the
Restore Process
c. Check the box next to Farm; Click Continue the Restore Process
d. Select New Configuration
i. NOTE: DO NOT USE SAME CONFIGURATION
e. Complete the forms with the correct information about database names/servers
and service account usernames/passwords
f. Click OK
i. The Restore process will take a few minutes to start.

10. If above restore Operation does not work try one of following:

A. For catastrophic restore
stsadm -o restore -directory -restoremethod

B. For site collection restore
stsadm -o restore -url -filename [-hostheaderwebapplicationurl] -overwrite

C. Create new web application & use stsadm -o addcontentdb to attach original content database
stsadm.exe -o addcontentdb -url -databaseserver -databasename

Restoring On the same server:
Since Configuration Database is same & all the files are in place, most of the sites work without problem.
If New Configuration Database is created on same server then follow instructions below

Restoring On new server:
1.Since we need to create a new configuation database & all required files are not present, We need to copy the contents of backed up folders partially or fully to the new server.
2.We also need to redeploy the lost settings mentioned in step 4 above,
3.SSL certificates needs to be assigned again.
4.Host/CNAME records in DNS needs to be updated to point to new Server.