SharePoint 2010 Compatibility with Windows Server 2012

This is a bad? news for SharePointers out there which still has a good news inside as well ;). who’s going to deploy SharePoint 2010 on Windows Server 2012? Keep a note below.

The Bad News Is – As per Microsoft SharePoint Server 2010 does not compatible with Server 2012 platform and we have to wait till the SharePoint 2010 SP 2 released which will contain the patches and updates accordingly.

And here’s The Good News -Yes We have an workaround for this.

Though MS says that we have to wait till the SP 2 released, I cannot because somebody is waiting for the solution out there and there’s no excuse for it, couldn’t revert back my Server in to 2008 R2 as well. So started dig down in to a workaround and got finally SP 2010 on Server 2012 installed and configured nicely, Tons of thanks for the web community who Shares their experiences all over the world for others (I’m community a Lover…)

So, From the point of prerequisites preparation you will get below issues.

1. Prerequisites installer gives an incompatibility pop up (still you can go ahead by saying ‘Run Program without Help’)

clip_image001

2. Even Though you have got all prerequisites Installed either manually or through a script, SharePoint Server Installer still says ‘Windows Server Roles or Features required by this product are not Enabled’.

clip_image002

3. Let’s say you have passed all above barriers somehow. Still you get some other issues after installing and provisioning the farm.

3.1 Farm Configuration Wizard Fails

clip_image003

3.2 Local Farm Not Accessible via PowerShell. Again the compatibility issue.( "The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered")

clip_image004clip_image005

Let’s see how we can get this done and here are the workarounds you have.

Note : None of these workarounds are officially supported by Microsoft and still the best solution for now is to have SharePoint 2010 on Windows Server 2008 R2.

If you are Installing SharePoint server 2010 on SQL Server 2012, make sure you have the media which has SharePoint 2010 SP1 included. None SharePoint SP 1 doesn’t support SQL 2012.

Workaround 01 – Automated PowerShell installer Script (This will save hours for you)

Craig Luccier has done a great job here – http://gallery.technet.microsoft.com/sharepoint/SharePoint-2010-and-dee17600. This single PowerShell monster resolves all above issues. Basically –

  1. installs all of the Windows Server 8 beta Roles/Features necessary to run SharePoint 2010
  2. Change the default IIS 8 App Pool .NET Framework to v2.0
  3. Downloads and install the SharePoint 2010 Prerequisites
  4. The SP 2010 installer doesn’t work issues

Running this script before you Install SharePoint will do everything above so nothing to be done manually. Just go ahead and install SharePoint right after this.

Workaround 02 – Get everything manually prepared your self (Time consuming but interesting !)

I didn’t go through the above PowerShell script as I needed to know each and every points basically what we fix and where. So here are steps with detailed descriptions on the manual workaround which worked for me.

1.Installing Prerequisites

Download and install these packages

Microsoft Chart Controls for Microsoft .NET Framework 3.5

Microsoft Filter Pack 2.0 (Available in PrerequisiteInstallerFilesFilterPack as well)

Microsoft SQL Server 2008 Native Client

Microsoft SQL Server 2008 R2 ADOMD.NET

Microsoft Sync Framework 1.0

Enable Windows features and roles via Server manager. To do this, Direct to Server manager –> Manage –> Add roles and features and Select below roles.

clip_image006

Go Forward and select Windows identity Foundation 3.5 for .Net framework 3.5 under features. It’s good so you don’t have to download It anymore as Serer 2012 contains the feature out of the box.

clip_image007

Below List of services need to be selected under IIS Role.

clip_image008clip_image009clip_image010

clip_image011clip_image012

Go ahead and install them and that’s all from the Prerequisites side.

2. Installing SharePoint

Go and run the Setup.exe and you will get the issue no 2 I have mentioned above ‘Windows Server Roles or Features required by this product are not Enabled’. Don’t worry, one guy out there has done a great job. It’s all about just Downloading Hand.ServerManagerCmdEmul – Binaries from here and copy ServerManagerCmd file in to – C:\Windows\system32 in your SharePoint Server. Additionally from there you can get the Hand.ServerManagerCmdEmul – Sources project file as well.

Boom ! You wont see that error now. So Go ahead and get the product installed.

clip_image013

Once you complete the installation you will notified for product configuration wizard. Go ahead and get your farm configured. End of the wizard, again the next issue will pop up. Yes the issue number 3.1 which I have mentioned above, ‘Configuration failed’. This is because SharePoint 2010 needs .Net farmework 2.0 in IIS App Pools.

At this stage, all the app pools and sites has been created under IIS. Let’s go there and have a look. Yes they are !

But all are having .Net v4.0 and this has to be changed in to 2.0

clip_image014

Right click on each pool –> advanced settings –> and set the .Net version to 2.0 (ignore the .Net v4.5 and .Net v4.5 Classic) it should look like this once you done.

clip_image015

Now Run the Product Configuration Wizard again and it should complete successfully.

Here we go.. ! Your Central Admin loaded.

clip_image016

3. Fixing SharePoint Management Shell Issue

In order to make use of the powershell commands with sharePoint 2010 on Server 2010, we need to switch the powershell version back to version 2.

Note: This will not uninstall version 3, it will simply launch a new powershell instance that uses version 2.

Right click on SharePoint Management Shell –> Go to File Location –> Get the properties of the Shell Shortcut –>

replace the Existing Target value in to – C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe -version 2.0 -NoExit " & ‘ C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ‘ "

clip_image017

Let’s go and try now. Yeah Now the Shell back to Rock !!

clip_image018

Everything on it now.. Enjoy,

image

Advertisement

Where to create a New Sub Site in SharePoint 2013.

Create a New sub Site Option has been taken in to site Content in SharePoint 2013 New UI. previously it was on site actions. it took few minutes for me to find out at the very first experience of SP 2013 Preview.

Follow these steps to get a new site created.

  • Go to Site Contents from the Settings

clip_image001

  • Click ‘New Sub Site’ option on the bottom of the site Content Page

clip_image002

  • Provide the details for the New Site As you want. Title/URL/Permission Type etc..as usual

clip_image003

  • Give it a Moment. this Shouldn’t take long Winking smile

clip_image004

  • here you go !

clip_image005

SharePoint 2013 Editions and Feature Comparison

Found a useful SharePoint 2013 Edition Level feature comparison list from http://www.apps4rent.com

Feature SharePoint Foundation 2013 SharePoint Server Standard 2013 SharePoint Server Enterprise 2013

User Authentication and Authorization

User authentication in SharePoint 2013 is the process that verifies the identity of a user who requests access to a SharePoint web application. User authorization in SharePoint 2013 is the process that determines the users who can perform defined operations on a specified resource within a SharePoint web application. SharePoint 2013 supports user authentication based on the following methods:

  • Windows claims
  • Security Assertion Markup Language (SAML)-based claims
  • Forms-based authentication claims .

These claims-based authentication methods are now the recommended authentication methods for SharePoint 2013.

Yes

Yes

Yes

Mobile Device Connectivity

SharePoint Server 2013 offers new, optimized viewing experiences across different mobile platforms. Additionally, several new features available include optimized mobile browser experience for Smartphone mobile devices, rendering of a single published SharePoint site in multiple designs to accommodate different device targets, push notifications, support for a new geolocation field type that can be used for mobile application development, view business intelligence content such as PerformancePoint Web Parts, Excel Services reports, and SQL Reporting Services reports, and view Office Web Apps.

Yes

Yes

Yes

Health Analyzer Yes Yes Yes

Windows PowerShell for SharePoint 2013

Windows PowerShell cmdlets that you use in SharePoint 2013 help you complete simple and complex administrative tasks. Command-line Help is available in the SharePoint 2013 Management Shell. For information about Windows PowerShell in general, visit the Windows PowerShell Technology Center.

Yes

Yes

Yes

Business Connectivity Services

With Business Connectivity Services (BCS), you can use SharePoint 2013 and Office 2013 clients as an interface into data that doesn’t live in SharePoint 2013 itself. BCS can access external data sources through Open Data (OData), Windows Communication Foundation (WCF) endpoints, web services, cloud-based services, and .NET assemblies, or through custom connectors.

Yes

Yes

Yes

eDiscovery

The eDiscovery functionality in SharePoint Server 2013 provides improved ways to help you protect your business.

No

Yes

Yes

Records Management and Compliance

The records management and compliance features in SharePoint Server 2013 provide improved ways to help you protect your business. The records archive and in-place record retention from earlier versions of SharePoint Server are still supported. SharePoint Server 2013 adds retention policies that are applied at the level of a site.

No

Yes

Yes

Business Intelligence

Business intelligence (BI) in SharePoint 2013 provides comprehensive BI tools that integrate across Microsoft Office applications and other Microsoft technologies. These BI tools are: Excel 2013, Excel Services in SharePoint 2013, PerformancePoint Services in SharePoint Server 2013, Visio Services in SharePoint, SharePoint 2013, and Microsoft SQL Server.

No

No

Yes

Social Computing

The social computing features in SharePoint Server 2013 offer an improved administration and user experience, in addition to new functionality for enterprise users to share and collaborate with others in their organization. The introduction of Community Sites offers a forum experience to categorize discussions around subject areas, and connect users who have knowledge or seek knowledge about subject areas. Improvements to My Sites offer a more intuitive workflow for users to develop their personal profiles, store content, and keep up-to-date with activities of interest.

No

Yes

Yes

Web Content Management

SharePoint Server 2013 includes new and improved features for web content management that simplify how you design publishing sites and enhance the authoring and publishing processes of your organization. SharePoint Server 2013 also has new features that use the power of search to surface dynamic web content on publishing sites.

No

Yes

Yes

Workflow

SharePoint Server 2013 brings a major advancement to workflow: enterprise features such as fully declarative authoring, REST and Service Bus messaging, elastic scalability, and managed service reliability. SharePoint Server 2013 can use a new workflow service built on the Windows Workflow Foundation components of the .NET Framework 4.5. This new service is called Workflow Manager and it is designed to play a central role in the enterprise. Processes are central to any organization and workflow is the orchestrator of processes.

No

Yes

Yes

Search

Search helps users quickly return to important sites and documents by remembering what they have previously searched and clicked. The results of previously searched and clicked items are displayed as query suggestions at the top of the results page.

No

Yes

Yes

Access Services

It allows creation of new Access service applications using the Access 2013 Preview client. You can view, edit, and interact with Access Services database in a browser.

No

No

Yes

Access Services 2010

Access Services 2010 allows continued maintenance of SharePoint 2010 Access Service applications by using Access 2010 clients and Access 2013 Preview clients. It doesn’t allow user to create new applications.

No

No

Yes

App Management Service

This feature allows you to install apps from the Internal Catalog or the Public SharePoint Store.

Yes

Yes

Yes

Excel Services

Excel Services allows you to view and interact with Excel files in a browser.

No

No

Yes

Machine Translation Service

This feature performs automated machine translation

No Yes Yes

Managed Metadata Service

Access managed taxonomy hierarchies, keywords, and social tagging infrastructure as well as Content Type publishing across site collections.

No

Yes

Yes

PerformancePoint

Access the information you need when you need it with interactive dashboards and scorecards. Easily analyze root causes and make effective decisions by using new features like the Decomposition Tree, visualizations, and improved filtering.

No

No

Yes

PowerPoint Conversion

Allows you to convert PowerPoint presentations into various formats.

No

Yes

Yes

Secure Store Service

Provides single sign-on authentication to access multiple applications or services

No

Yes

Yes

State Service

Provides temporary storage of user session data for SharePoint Server components.

No

Yes

Yes

Usage and Health Data Collection

Collects farm wide usage and health data and provides the ability to view various usage and health reports

Yes

Yes

Yes

User Profile

Adds support for My Sites, Profiles pages, Social Tagging, and other social computing features.

No

Yes

Yes

Visio Graphics Service

Allows you to view and publish Microsoft Visio diagrams in a Web browser.

No

No

Yes

Word Automation Services

Performs automated bulk document conversions

No Yes Yes

Work Management

Provides task aggregation across work management systems, including Microsoft SharePoint products, Microsoft Exchange Server, and Microsoft Project Server.

No

Yes

Yes

Microsoft SharePoint Foundation Subscription Settings Service

Tracks subscription IDs and settings for services that are deployed in partitioned mode. Windows Powershell only.

Yes

Yes

Yes

Error When Creating new Database on Clustered SQL Environment

Recently I got an Clustered SQL 2012 environment created with two nodes as I needed to deploy SharePoint 2013 on it. SharePoint Installation gone well but I got below error when I’m tying to create a new web application.

“Cannot use file ‘D:\MSSQL11.MSSQLSERVER\MSSQL\DATA\WSS_Content_7777.mdf’ for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the SQL Server does not have a dependency on it. CREATE DATABASE failed. Some file names listed could not be created. Check related errors.”

tried though SQL Management Studio to create a new DB in order to verify and it gives the same error. so it should be from SQL cluster side for sure.

image

 

 

 

 

anyway, we love these kind of little damns because always we learns something though them. let’s find out what it is.

when I look at the error it was clearly mentioning something about Dependency. so yes obviously my cluster is brand new. didn’t fine tune well because was bit hurry on deployment of SharePoint.

So it’s all about Configuring Dependency from Windows cluster.

  1. SQL Server depends on the Network Name and a Disk Resource.
  2. SQL Network Name depends on the IP Address.
  3. SQL Agent depends on SQL Server.
  4. The IP Address and the Disk Resource do not depend on anything.

generally SQL prevents the creation of Databases on volumes which are not Dependency of SQL Server resources. So The point of having dependencies is to prevent situations where SQL Server comes online before the disk containing the data goes on line. Therefore the term “DEPENDANCY.”

Let’s see how we can add the dependencies to get this fixed. by the way you don’t have to do this once you got a new clustered environment created as The dependencies are automatically established when you create the SQL cluster. but if you substitute any disk resources don’t wait till the error remind you for it, you have to add the dependencies.here in my case it was the point, I added some disk resources and I forgot to re-add the dependencies Winking smile.

Open Failover Cluster Manager –> Select your clustered application (SQL) –> Right-click on your SQL Server resource then click Properties –> Click on the Dependencies tab –> Click the Insert button to add an additional row, then select the shared disk that contains your SQL databases –> Ensure that all resources are required (there is an AND next to subsequent resources) then click OK.

The Following Illustrate the Resource Settings of SPLAB which is my testing environment.

clip_image001

  • The Name Depends on the IP Address

clip_image002

  • IP Address does not depends on anything

clip_image003

  • If Analyses services are Installed, it depends on the Network Name

clip_image004

  • Cluster Disks has no Dependencies

clip_image005

  • SQL Server has Dependencies of Disks and Network Name

clip_image006

  • And Finally Agent depends on SQL Server

clip_image007

once all these added. you done !

Setup could not find any available products to install SharePoint 2013

just started of my very first Production SharePoint 2013 Deployment and suddenly got an Error saying that “Setup could not find any available products to install SharePoint 2013” when I ran the setup. All Prerequisites are perfectly gone and tried again to run by logging as local admin but still issue persists.

can remember that I had an same kind of a issue on installing Office 2013 first time and it was because of corrupted installer.

so guessed it would be same here, got the whole setup copied newly and then ran again, yes it worked !!

HTTP : 500 Service Unavailable in a just installed Brand new SharePoint 2010 BOX

Installed an brand new SharePoint 2010 Application server (SPS-APP01.mydomain.int) with Service pack 1 and August 2012 cumulative update. All prerequisites and installation went perfectly but once the product wizard completed I’m getting “HTTP : 500 Service Unavailable” error while loading Central administration also the Central administration app pool get stopped.

Wasted probably two hours by looking all around to find out the point of this occurrence.

  1. Installed SharePoint and ran product config wizard through Farm account and Farm account also has full control to Database server so no point of checking more on database level permissions.
  2. Checked the IIS app pool account of Central Admin and all required IIS security groups and all are there as needed.
  3. Farm account also a member of local admin group.
  4. Demoted whole farm and again provisioned but the result was same.

So what else I have to huh ? None isn’t it ? But actually yes one more thing.

Suddenly popped out that one key permission which was missing while I’m checking – "Log on locally as batch job" on local security policy of SP Server.

Administrative tools –> local security policy –> User rights assignment –> right click and edit "Log on as a batch job"

clip_image001

clip_image002

My farm account (Central Admin App pool account) should be here but it wasn’t. tried to add but couldn’t can you see the add users button has been grayed out so realized that Infra admin has defined this particular group policy through AD.

Asked Admin to Edit the default domain policy –> User rights assignment –> right click ad edit "Log on as a batch job"

clip_image003

Added Farm (Central admin App pool account) account in to the group since this policy has been defined (enabled).

clip_image004

After applying just ran a GP Update/force from SP Server and checked whether this user has been added,

clip_image005

yes it was as above and then tried to open up the central admin.

Capture

Bingo !!! It opens now.

Sign in as Different User is gone in SP 2013

 

An another significant feature dropped in SharePoint 2013. Sign in as different user no more available by default. this is one of the most frequently used feature in early SharePoint versions for Demonstration and testing purposes. as per Experts around “It has been removed from OOTB feature based on security considerations, specially on production environments“

clip_image001

however still it’s as simple as editing and adding few lines on Welcome page. here I’m stepping you to get it back but I would say it shouldn’t be done in PROD environments as Microsoft has dropped it reasonably.

1. Direct to – C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\CONTROLTEMPLATES\

2. Keep Welcome.ascx file originally copied somewhere and edit the original one through notepad and save it.

3. Add the following element before the existing element with the id of “ID_RequestAccess”:

<SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser"

Text="<%$Resources:wss,personalactions_loginasdifferentuser%>"

Description="<%$Resources:wss,personalactions_loginasdifferentuserdescription%>"

MenuGroupId="100" Sequence="100"

UseShortId="true"

/>

so it’ll look like this once you edited

clip_image002

go open up your sites and see. yeah it’s back in there.. Enjoy !

clip_image003

Configuring a Virtual SAN Using ISNS in Windows Server 2012

    Yet Another very useful and free tool from Microsoft. If you remember the earlier version of this feature, it was an downloadable application where you can install separately but now with latest version of windows server 2012 it has been bundled in as a feature under roles and features.

    I was heavily using iSCSI software target for my testing purposes where I needed an Virtual SAN such as on SQL/Windows Clustering etc.. I loved this because I got the real SAN Experience without any hardware or software cost. You can read my previous article if you are a pre windows 2012 user.

    Note: This Tool only for Testing purpose and not recommended to propose for production environments.

    Windows 8 Doesn’t Support this Feature anymore, you cannot install iSCSI software target 3.0 nor the ISNS server. This has been detached from client Operating systems.

    Alright, Here is the scenario, I have two servers where I need this to be configured with.

    Server 01 (Host) – ISNS Target Server which is the Central place where holding all the Disks

    Server 02 (Initiator-Client) – Initiator servers where my SQL Instance about to host

    Setup steps falls in to two levels as

  • Server Configuration (Host Server/Target)
  • Client Configuration (Initiators)

So Let’s get configured this server.

  • Run this power shell command on Target Server – Add-WindowsFeature FS-iSCSITarget-Server (This will install the feature for you so nothing to be done through roles and features)
  • clip_image001[5]

  • Just hold on few seconds
  • clip_image002[4]

  • Now direct to Server manager of Target Server and in to iSCSI tab like shown below. Basically this is the interface you manage your SAN here after. Looks pretty nice huh ? !!
  • clip_image003[5]

  • So the next thing is to get our virtual disks created which should include in to our Target. Two methods to get it done, Either From the above tab simply click on Tasks and say New virtual Disk and completing that steps will create your disk/s else as usual go to disk management and right click on Disks and say Create VHD as shown below so it does the same.
  • clip_image004[4]

  • Then to attach the disk we got created. Server manager again and under iSCSI click on Import Virtual disk
  • clip_image005[4]

  • Browse and locate your disk here and click next.
  • clip_image006[4]

  • Now to assign Target. This simply means the configuring of our Target Server. Choose New Target and hit next.
  • clip_image007[4]

  • Specify the Name as you desire, make it a tricky one
  • clip_image008[4]

  • Yes the important part now, specifying server which are will be accessing this target server. In my case it’s my SQL Servers that I’m about to cluster. Click Add.
  • clip_image009[4]

  • Select the method to identify the initiators here.
  • clip_image010[4]

  • Specify the Initiators here. Either you can easily provide the IP address/s or else the IQN (which is an unique identifier of particular node that you can get from the initiator servers by just launching iSCSI initiator and then through configuration tab [Eg- iqn.1991-05.com.microsoft:db01.testlab.int] )
  • clip_image011[4]

  • Authentication is optional so can be ignored.
  • clip_image012[4]

  • Have a look at the summary and hit Import to proceed.
  • clip_image013[5]

  • Just few seconds to import
  • clip_image014[5]

  • Everything gone perfectly. Cool result UI huh !
  • clip_image015[4]

  • Direct again in to Server Manager and check the result. of course you can expand your SAN by adding more disks in to pool.
  • clip_image016[4]

  • Let’s configure the Initiator Servers now. Just type iSCSI on search and launch it (iSCSI initiator – readily available on windows servers). Say yes to the massage to start the service.
  • clip_image017[4]

    clip_image018[4]

  • Provide the target address here and hit Connect (your Host Server where we configured SAN before)
  • clip_image019[4]

  • So we are success here. Say done to close this.
  • clip_image020[4]

  • Direct to Volumes and devices and click auto configure so whatever the available disks of SAN storage pool will be mapped in. say ok for this window.
  • clip_image021[5]

  • Let’s see the real thing through disk management. Wow !! So my disks are attached automatically
  • clip_image022[4]

       So it’s ready to play with and up to you. will be back in Clustering part with another post Smile