######################## Start Variables ########################
######################## Varun's Script######################
$destination = "C:\\tools\\Folder"
$webUrl = "<Url of the specific site>"
$listUrl = "<Url of the specific list. This url is complete Url and NOT relative url>"
##############################################################

$web = Get-SPWeb -Identity $webUrl
$list = $web.GetList($listUrl)

function ProcessFolder {
    param($folderUrl)
    $folder = $web.GetFolder($folderUrl)
    foreach ($file in $folder.Files) {
        #Ensure destination directory
        $destinationfolder = $destination + "/" + $folder.Url 
        if (!(Test-Path -path $destinationfolder))
        {
            $dest = New-Item $destinationfolder -type directory 
        }
        #Download file
        $binary = $file.OpenBinary()
        $stream = New-Object System.IO.FileStream($destinationfolder + "/" + $file.Name), Create
        $writer = New-Object System.IO.BinaryWriter($stream)
        $writer.write($binary)
        $writer.Close()
        }
}

#Download root files
ProcessFolder($list.RootFolder.Url)
#Download files in folders
foreach ($folder in $list.Folders) {
    ProcessFolder($folder.Url)
}

As part of the logging they also log the name of the solution file in question. They have multiple Farm solutions and sandbox solutions.

As part of feature activated/Installed, I had to find the solution file name of which the feature was a part of.

The following code helped me do this:

public override void FeatureActivated(SPFeatureReceiverProperties properties)
        {
            SPSite site = (SPSite)properties.Feature.Parent;
            string solutionName = site.WebApplication.Farm.Solutions[properties.Feature.Definition.SolutionId].SolutionFile.DisplayName;
            //Log the namespace ToString the logging DB
        }

But sometimes even the profile sync is on, but SHarePoint 2010 can't update the accounts. In such a case one can - Powershell Command "Set-SPUser".

1) If the problem only appears with a single user, you can update a single account like so:

Set-SPUser -Identity ‘domain\Username’ –Web http://<URL To Site> –SyncFromAD


2) If all (or a lot) of the uesrs you can do it by the following:

Get-SPUser –Web http://<URL to Site> | Set-SPUser –SyncFromAD

The above will reset all users FOR THAT SPECIFIC URL; if you have additional site collections (i.e. Managed Paths), you have to run it on those URL's as well.

The cache is composed of these 2 folders:

• %APPDATA%\Microsoft\Web Server Extensions\Cache
• %USERPROFILE%\AppData\Local\Microsoft\WebsiteCache

In order to clear the cache, simply delete the files in these two folders.

I even created a batch file for doing this, which allows you to automate this function either as a scheduled job or manually by clicking on the batch file.

========Script Start below===================

cd “%APPDATA%\Microsoft\Web Server Extensions\Cache”

del *.web /S /Q “%APPDATA%\Microsoft\Web Server Extensions\Cache”

cd “%USERPROFILE%\AppData\Local\Microsoft\WebsiteCache\”

rmdir /S /Q “%USERPROFILE%\AppData\Local\Microsoft\WebsiteCache\.”

mkdir “%USERPROFILE%\AppData\Local\Microsoft\WebsiteCache”

dir “%APPDATA%\Microsoft\Web Server Extensions\Cache”
dir “%USERPROFILE%\AppData\Local\Microsoft\WebsiteCache”

========Script End========================

As the first step for troubleshooting, I asked them to try whether OOB  search works. And that also didnt return any results using the keywords - "ContentType:<NameofContentType>". What was happening.

I checked the central admin Managed property store and found that ContentType Managed property was mapped to the following Crawled properties (In this order)

• Mime Type
• Ows_ContentType
• Basic Text

On the search results page, I changed the xsl to spit out all the properties.

I used the below XSL:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:template match="/">
<xmp><xsl:copy-of select="*"/></xmp>
</xsl:template>
</xsl:stylesheet>

Surprisingly, the Content Type property was showing values like - Text/Html, Application.document, etc. This seemed like MimeType. Now I got it. The Content Type Managed property picks up one of the values from the list of mapped crawled properties and picks the one which comes first. In this case it is MimeType. 
So what you need would be wither changing the OOB property or create a custom managed property and doing a full crawl. Which I did and got the result.

In short in FAST 2010, OOB content Type property doesnt behave the same way as in enterprise search.

<Javascript code>

The javascript for copying to clip board is

    function copy_to_clipboard(text) 
    { 
        if(window.clipboardData) 
        { 
        window.clipboardData.setData('text',text); 
        } 
        else 
        { 
            var clipboarddiv=document.getElementById('divclipboardswf'); 
        if(clipboarddiv==null) 
        { 
           clipboarddiv=document.createElement('div'); 
               clipboarddiv.setAttribute("name", "divclipboardswf"); 
           clipboarddiv.setAttribute("id", "divclipboardswf"); 
           document.body.appendChild(clipboarddiv); 
        } 
            clipboarddiv.innerHTML='<embed src="clipboard.swf" FlashVars="clipboard='+ 
    encodeURIComponent(text)+'" width="0" height="0" type="application/x-shockwave-flash"></embed>'; 
        } 
        alert('The text is copied to your clipboard...'); 
        return false; 
    }

</Javascript code>

Thereafter you can register the javascript in the web part.

To achieve this we make use of the managed property : ContentClass.

Simply put the text - contentclass:"STS_Web" in the search box and hit enter. You will get the list of all the sites in your farm (Or web applications serviced by that search service application) But this doesnt return any root sites.

To get even root sites, just change the text to contentclass:"STS_Site" contentclass:"STS_Web"

In my case, I’ll restrict the URL to web application.

contentclass:"STS_Site" contentclass:"STS_Web" site:<Url of web application>

The SharePoint developer tools in Visual Studio 11 Developer Preview contain new designers and templates to facilitate SharePoint development, as well as new options for deploying and testing SharePoint sites. See the following descriptions to learn about these and other new features.

This topic contains the following sections.

• Create Lists and Content Types by Using New Designers
• Create Site Columns
• Create Silverlight Web Parts
• Publish SharePoint Solutions to Remote SharePoint Servers
• Test SharePoint Performance by Using Profiling Tools
• Create Sandboxed Visual Web Parts
• Improved Support for Sandboxed Solutions.
• Support for JavaScript Debugging and IntelliSense for JavaScript
• Streamlined SharePoint Project Templates

http://msdn.microsoft.com/en-us/library/ee290856%28VS.110%29.aspx

Recently one of my clients had a real complicated issue where his AD account would get locked out as soon as he tried to access the SharePoint portal

A couple of days back he reset his password and ever since then hsi account started getting locked. He was accessign the sharepoint site with the new password and was able to get into it. Leaving the site idle for 15 mins caused the account to lock out.

Clearly SharePoint couldn't lock the account. It seemed there was some resource/application which was hitting the proxy server with the wrong credentials. It seemed he had saved somewhere the credentials for some application.

But I couldn't find any sharepoint page/resource which had saved the credentials.

Strangely, during this time if he switched off the machine and tried accessing the site from some other site .. It worked fine. No account lockout. Which pointed to me that perhaps there was some client program which was causing this. I put in the fiddler trace and found that the SharePoint workspace was the culprit. The client had saved the credentials for the workspace and it was trying to sync every fifteen minutes and htting the proxy with the old passowrd. This caused it to lock the account.