from the site settings / title, description and icon

if you choose “use the new SharePoint user interface,  and don't ask me again”

but you changed your mind and said “oh no no i want to go back to v3 visual style", what do i do now ? “

solution:

open power shell

$myweb = $GetSPWeb https://localhost/sites/department1

$myweb.uiversionconfigurationenabled = $true

$myweb.update()

goto site settings now and you will find the visual upgrade option shown

any misconfiguration of the file will lead to

1- instability of file icons

2- document cannot be opened normally by office products

by misconfiguration here i mean  : (the following list is not exclusive)

1- duplicate of any icon file definition . i have to lines that define pdf . the 2 lines are clones, however the search results cannot deal with it. so we have to trim one line

so make sure before compiling any bill of quantity/material that our products are supported on i64

as you can see, the confusion comes from the need for both versions (2.111.7.0  comes with Oracle Client ) and (2.111.7.20 comes with ODAC.NET ) if we only have 1 machine. so we need to install both packages : Oracle Client 11g and ODAC.NET for client

2- i can now start a job manually (force it to start now) instead of waiting to next schedule :) check the “Run now” button in the image

if you are using SQL authentication as opposed to windows authentication, developer dashboard will not work since it might compromise some passwords. this has been decided when building the dashboard

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

# Start SharePoint 2010 Services

"Starting SharePoint Server 2010"

"SPTimerV4","WebAnalyticsService","SPWriterV4","DCLoadBalancer14","DCLauncher14","SPUserCodeV4","SPTraceV4","SPAdminV4","OSearch14","SPSearch4" | ForEach-Object {

    $servicePrior = get-service $_

    "$_  : " + $servicePrior.status 

Start-Service $_

    $serviceAfter = get-service $_

    "$_ : " + $serviceAfter.status }

" SharePoint Server 2010 is Up and running"

Shutdown SharePoint Server 2010
--------------------------------------------
# Stop SharePoint Services
"Stopping SharePoint 2010"
"SPTimerV4","DCLoadBalancer14","DCLauncher14","SPWriterV4","SPUserCodeV4","SPTraceV4","SPAdminV4","WebAnalyticsService" ,"OSearch14","SPSearch4" | ForEach-Object {
    $servicePrior = get-service $_
    "$_ is " + $servicePrior.status
    Stop-Service $_ -Force
    $serviceAfter = get-service $_
    "$_ : " + $serviceAfter.status }
"SharePoint 2010 is Shutdown"

pros :

1- separate web.config

2- separate SLA (like access channels, zones, etc...)

3- separate management for IIS (since IIS can see the wep application level)

cons :

1- different socket (IP:Port) even if we have to use host headers. it is a separate socket

2- aloooooot of overhead for managing diff web apps

3- not scalable (when we reach a large number of tenants we cannot provision each one as a web app) as compared to site collections

4- share same web.config

5- some IIS features (example bit rate throttling) will only be configured per web app

1- save those files on local servers (file server or sharepoint)

2- store them on a media host service like silverlight.live.com

so basically the 2nd option will save your storage cost and bandwidth cost. you dont have to design around your bandiwdth limitation anymore and you hopefully you dont have to ask for a bigger SAN.

get 10 GB free now on https://silverlight.live.com/

if you are getting access denied when you access "Configure Service Accounts" for instance

or trying to create a new instance of a service application by navigating to manage serive applications page , but the new button is inactive and the properties button is inactive too.

if you are sure you have enough permission , then please run IE in an elevated admin mode :) everything lightens up :)