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