1. In web.config of the web application add the following lines under configuration/system.web section

• <browserCaps>
  <result type=”System.Web.Mobile.MobileCapabilities, System.Web.Mobile, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”/>
  <filter>isMobileDevice=false</filter>
  </browserCaps>

2. Modify the compat.browser of the web application found under C:\inetpub\wwwroot\wss\VirtualDirectories\<webapp>\App_Browsers

• Code to change for each user agent 
  • <capability name=”isMobileDevice” value=”false” />

3.

Disable-SPFeature -Identity MobilityRedirect -Url https://yoursite 

Note: None of the above method really block any user from directly accessing the mobile view of the site by simply appending ?mobile=1 in the URL

# To completely block the access we need to do the following:

# Install IIS URL rewriter module.

# add the below lines in your web.config of web application, just under the defaultdocuments tag

<rewrite>
            <rules>
                <rule name="test" patternSyntax="Wildcard" stopProcessing="true">
                    <match url="*" />
                    <conditions trackAllCaptures="true">
                        <add input="{QUERY_STRING}" pattern="*mobile=1" />
                    </conditions>
                    <action type="Redirect" url="{R:1}" appendQueryString="false" logRewrittenUrl="true" redirectType="Found" />
                </rule>
            </rules>
        </rewrite>
        <defaultDocument enabled="false">
            <files>
                <remove value="default.aspx" />
            </files>

# same can be configured through GUI of URL rewriter as well

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

<?xml version="1.0" encoding="UTF-8"?>

<OpenSearchDescription xmlns="https://a9.com/-/spec/opensearch/1.1/" xmlns:ms-ose="https://schemas.microsoft.com/opensearchext/2009/">

<ms-ose:MaximumResultCount>500</ms-ose:MaximumResultCount>

<ShortName>Spinifex SharePoint</ShortName>

<Description>Search the Spinifex SharePoint Search Center</Description>

<Url type="application/rss+xml" template="<SP URL>/_layouts/15/srchrss.aspx?k={searchTerms}&amp;count={count?}&amp;start={startIndex?}"/>

<Url type="text/html" template="https://<SP URL>/_layouts/15/osssearchresults.aspx?k={searchTerms}&amp;start={startIndex?}"/>

<ms-ose:locationProperties>

<ms-ose:property name="TreatLinkAsEnclosure">-1</ms-ose:property>

</ms-ose:locationProperties>

<ms-ose:ResultsProcessing format="application/rss+xml">

<ms-ose:LinkIsFilePath>-1</ms-ose:LinkIsFilePath>

</ms-ose:ResultsProcessing>

</OpenSearchDescription>

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

# Copy it in a notepad and save it as .osdx file, double click and it will ask you to add.

# The highlighted attribute is the extended parameters available to bypass the default limit of opensearch 1.1. that allows only 100 results to be returned

# You can find more details about the OpenSearch description file at https://msdn.microsoft.com/en-us/library/windows/desktop/dd940453%28v=vs.85%29.aspx#fed_search_page_size 

1. Install SMTP role on one of the Servers in the domain which has access to internet, since we need to connect to smtp.office365.com this is must.

2. Configuring SMTP service so that it can talk to office365 smtp

Open --> IIS 6.0 Manager --> right click on SMTP --> properties

2.1 First we will configure the Access, we don’t have much to configure in this. Check authentication is set to anonymous

2.2 Next click on connection button and you can select which servers can connect to this virtual server, by default it is set to accept all. If you need you can modify as per your orgs security policies

2.3 Next click on relay, here you can select which computer can relay through this SMTP. If you need that any computer / server can relay through this, select all except the list below option

2.4 Next click on Messages tab, here we don’t have to change anything except if you need to change the badmail directory i.e. where SMTP store any email that it fails to deliver due to one or the other reason.

2.5 Next click on delivery tab  à outbound security, here chose basic authentication and provide a username and password, remember this user should have a valid exchange online mailbox. Also make sure you check TLS encryption here

2.6 Next click on outbound connections, here we can specify the port as 25 or 587 and leave rest as it is

2.7 Next click on Advanced , here you can provide FQDN name of your domain and smart host which should be set to smtp.office365.com

This completes our SMTP level configuration

3. Testing the connection

3.1 Install telnet client on the server : Server manager à add feature à check Telnet client

3.2 Open cmd prompt and run the following

telnet localhost 25:

helo

mail from:<office365 email address>

rcpt to:<to address>

data

subject:test mail

test email

.

Quit

4. Configuring SharePoint server 

4.1 CA --> system settings --> outgoing email settings 

Make sure that from address have permissions to send email through your exchange online else you will see bad email in your badmail directory on the SMTP Server with the following message in it 

1. 1. Diagnostic-Code: smtp; 550 5.7.1 Client does not have permissions to send as this sender

       To test the outgoing email settings just set any alert on one of the document libraries or any list for any user with a valid email address

       

       

Following script uploads the userphotos in bulk to your AD, assumption is that photos are saved in file system as <SAMAccountname>.<extension>

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

$path = "C:\Users\administrator.CORP\Desktop\photo"

$x = Get-ChildItem $PATH

$x.VersionInfo.filename
foreach ($item in Get-ChildItem $path)
{
$photopath = $item.versioninfo.filename
$photo = [byte[]](get-content $photopath -Encoding byte)
$temp = $photopath.lastindexof(".")
$temp1 = $photopath.LastIndexOf("\")
$temp2 = $temp-$temp1
$user = $photopath.substring($temp1+1,$temp2-1)
$user
Set-ADUser $user -Replace @{thumbnailPhoto=$photo}

}

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

$url = Read-Host "Enter URL" 

do{
$listname = Read-Host "Enter List Name"
$web = get-spweb $url 
$list = $web.lists[$listname]
$files = $list.rootfolder.files

#---------------------------- Delete Forms ----------------------

$form1 = $list.RootFolder.files | ?{$_.url -match "dispform.aspx"}

$form2 = $list.RootFolder.files | ?{$_.url -match "editform.aspx"}

$form3 = $list.RootFolder.files | ?{$_.url -match "newform.aspx"}

$form2.delete()
$form1.delete()
$form3.delete()

$list.update()

# --------------------------recreating --------------------------------

$editformurl = $list.RootFolder.ServerRelativeUrl + "/editform.aspx"
$dispformurl = $list.RootFolder.ServerRelativeUrl + "/Dispform.aspx"
$newformurl = $list.RootFolder.ServerRelativeUrl + "/NewForm.aspx"

$dispform = $files.add($dispformurl, [Microsoft.SharePoint.SPTemplateFileType]::FormPage)
$editform = $files.add($editformurl, [Microsoft.SharePoint.SPTemplateFileType]::FormPage)
$newform = $files.add($newformurl, [Microsoft.SharePoint.SPTemplateFileType]::FormPage)

$wpm = $editform.GetLimitedWebPartManager([System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared)
$wpm2 = $dispform.GetLimitedWebPartManager([System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared)
$wpm3 = $newform.GetLimitedWebPartManager([System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared)

$lfw1 = new-object ([Microsoft.SharePoint.WebPartPages.ListFormwebpart])
$lfw2 = new-object ([Microsoft.SharePoint.WebPartPages.ListFormwebpart])
$lfw3 = new-object ([Microsoft.SharePoint.WebPartPages.ListFormwebpart])

$ilist1 = [Microsoft.SharePoint.WebPartPages.IListWebPart]($lfw1)
$ilist2 = [Microsoft.SharePoint.WebPartPages.IListWebPart]($lfw2)
$ilist3 = [Microsoft.SharePoint.WebPartPages.IListWebPart]($lfw3)

$ilist1.ListId = $list.id
$ilist1.PageType = [Microsoft.SharePoint.PAGETYPE]::PAGE_EDITFORM;

$ilist2.ListId = $list.id
$ilist2.PageType = [Microsoft.SharePoint.PAGETYPE]::PAGE_DISPLAYFORM;

$ilist3.ListId = $list.id
$ilist3.PageType = [Microsoft.SharePoint.PAGETYPE]::PAGE_NEWFORM;

$wpm.AddWebPart($lfw1, "Main", 1)
$wpm2.AddWebPart($lfw2, "Main", 1) 
$wpm3.AddWebPart($lfw3, "Main", 1)


$list.DefaultDisplayFormUrl = $dispformurl
$list.DefaultEditFormUrl = $editformurl 
$list.DefaultNewFormUrl = $newformurl

$list.update()
}
while ($TRUE)
# # ===================

=====

Edit item options are missing in the ribbon and in the drop down of the items in a list

Cause:

=====

Issue is due to PermMask field schema has missing "RenderXMLUsingPattern", it can be at the site level, web level or list level

Resolution:

=====

Run the following script, it run through all the webs, including rootweb and lists and fixes the schema

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

$site = get-spsite <URL of the site collection>

function checkxml($field)

{

  if($field.SchemaXml.Contains("RenderXMLUsingPattern"))
  {
  
    return $TRUE
  }
  else 
  {
   return $FALSE
  }
  
}

function fixxml($field)

{

   [xml]$schema = $field.SchemaXml

   $att = $schema.createattribute("RenderXMLUsingPattern")

   $att.value = "TRUE"

   $schema.field.attributes.append($att)

   $field.schemaxml = $schema.innerxml

   $field.update()

}

$web = $site.RootWeb

if(checkxml($web.Fields.GetFieldByInternalName("PermMask")))

{

  write-host "Field at Root Level is fine" 
  
}

else

{

  fixxml($web.Fields.GetFieldByInternalName("PermMask"))
  $web.update()
  
}  
      

foreach ($webs in $site.AllWebs)

{

try { $fieldw = $webs.fields.getfieldbyinternalname("PermMask") }
catch [System.Exception] { write-host "Field not found in :"  $webs.url }

  if(checkxml($fieldw))
  
   {
  
     write-host "No broken field found at :" $web.url
      
   }
  
  else
   {
  
    write-host "Broken Field found at :" $web.url 
    fixxml($fieldw)
    $web.update()
   
   }
  
  for($i = $webs.lists.count - 1; $i -ge 0; $i--) 
  {
  $list = $webs.lists[$i]
  try{ $fieldl =  $list.fields.getfieldbyinternalname("PermMask")  }
  catch [System.Exception] { write-host "Permmask field not found in :" $list.title } 
 
    if(checkxml($fieldl))
  
       {
  
         write-host "No broken field found at :" $list.title
      
       }
  
  
    else
       {
  
         write-host "Broken Field found at :" $list.title
         fixxml($fieldl)
         
        }
  
 
  }   
  
}  

In search results when we click on an item it takes us to an incorrect displayform URL. For example in an working scenario when we click on an item in search results it takes us to <url of the list>/dispform.aspx?id=<***>, but in case where there are multiple display form created for a list search results always picks only one display form to crawl.

Cause:

This is kind of by design behavior where the gatherer process renders through the available display forms in the list and picks only the form which is on the top of the order.

Resolution:

As of now it’s not possible to index all the display forms of the list but to index the desired display form following can be done.

1. Run the following to get the exact order in which gatherer will see the display forms

            $web = get-spweb <>

            $list = $web.lists[“<list title>”]

            foreach($form in $list.forms)

             {

                if($form.Type -eq "PAGE_DISPLAYFORM")

                 {

     
                      $form.id, $form.url

                }

            }

2. In our case we got the following

Maps.aspx

Home.aspx

Dispform.aspx

3. We needed that home.aspx  should be picked up in the index and not maps.aspx.

4.  So two workarounds were there first : delete maps.aspx Second: just recreate maps.aspx using SharePoint designer.

5. Either of two changes the order and subsequent reset and full crawl starts giving the desired results

Enabling enterprise features on SharePoint 2010 or upgrading from Standard license to Enterprise license fails on multiple server farm with the following error in GUI

An error occurred while enabling Enterprise features. Refer to the event logs on your server machines for more details. For more information on how to fix this error, refer to help.

Click OK to return to the SharePoint Central Administration Operations page."

Same time following concurrency exception is logged in eventlogs

 An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was
thrown.  Additional exception
information: An update conflict has occurred, and you must re-try this action

 Cause:

 Every time we try to enable or upgrade to enterprise license in Multiple Server SP 2010 farm, it creates a one time job of each of the Server which kicks off psconfig simultaneously on all of the Server due to which we keep on getting the concurrency exception and feature activation never completes

 Resolution

1. First we need to make sure that all the Server should be in “no action required” status to avoid other objects upgrading when the SharePoint Server upgrade job triggers psconfig

       2. First to make sure that the psconfig doesn’t start on all the Servers simultaneously we disable the timer service on all the Servers in the farm except the Server hosting Central Admin.

       3. Try to enable enterprise features, it will fail but check event logs we should see a success for psconfig along MSInstaller logs for successful installation of Infopath, visio and other Services.

       4. Now one by one run “Psconfig.exe –cmd services –install –cmd installfeatures” on all the Servers

       5. Make sure we get success for psconfig and MSinstaller logs on all the Server after psconfig command completes

       6. On Server hosting central admin run powershell cmdlet  “set-spfarmconfig –installedproductrefresh”

       7.Now we should see enterprise features enabled in Central admin

1. 
   Once
   done start the full crawl and we should be in good state.