Saturday, October 13, 2012

Friday, October 5, 2012

Discontinued features in SharePoint 2013


Recently the MSDN article is published on discontinued and modified features in SharePoint 2013. This is very important to know as what all are discontinued compared to the previous version for future planning on upgrades or migrations. Below are the main features (according to me) among all the list Microsoft published.
Enterprise Content Management (ECM):
  • Barcode: Inserting barcode command is no more available in ribbon. Which means you cannot add the SharePoint generated barcode to Word documents.
  • Print labels: Ability to generate, embed a label containing the metadata about office files is no more supported.
I believe the above two features are not so popular and the demand to use these features are less. So, I believe we don’t bother much.
Site Templates:
Document Workspace Template: While you are trying to create a site in SharePoint you are no more see the Document Workspace template. In my view this its not big effect to us.
Meeting Workspace Template: This template also removed from the list of site templates available in SharePoint 2013. I believe this is a bad decision as I am much integrating the meeting workspace with my Outlook client to fix appointments, saving meeting minutes documents and saving the details about the conference codes details etc. in our organization. Not a good idea from Microsoft.
Personalization site template: This is also got removed from list of site templates. I believe no one mind about it.. as no one uses it.
Group work site template: Removed in new version.
Search:
RSS Feed for Search results is no more available. Hurray! I was using this search results data via RSS in some scenarios…
UI:
The Visual Upgrade option is no more available.
BI Related:
  • We cannot generate the Visio pivot diagram from SharePoint task list any more.
  • Chart web part is no more available. Still you can use the excel services to render charts etc..
  • SharePoint KPI and status list are also discontinued..
As we already know most of the discontinued features are less used by any organization. The main reason why they discontinued due to performance related. You can read more details about this topic in office document.

Memory leaks in SharePoint 2013?

I believe yes, there are. As this is the preview version there are possibilities for the memory leaks and other development issues. In the SharePoint 2013 server go to task manager and see what is taking more memory. You should see something like below.

Memory_Leaks_In_SharePoint_2013_Preview

We see the Name of the component which is taking huge memory is "Microsoft Office 2013 component". Yes, this is the reason for memory leaks. When you switched to process view you will find out what is that process. It is noderunner.exe. 

image
As far as I know this is related to the search service process with new name. Even though our farm is new with very less data the noderunner processes are running and taking huge amount of memory. After good amount of research and read I have found the fix in the technet article here.

Solution:
  • We can reduce the performance level of the search service by using the below powershell command.
    1. Set-SPEnterpriseSearchService -PerformanceLevel Reduced  
  • Open the file from the location C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config and find the line <noderunnersettings tag. We must set the attribute memoryLimitMegabytes value from 0 to some value which you should like to give. I have given 256, so that it will not grow too much that it should. The tag should look like below.
    <nodeRunnerSettings memoryLimitMegabytes="256" />
Note: This fix is needed only for SharePoint 2013 preview edition as the actual version should fix this issue.

SharePoint Server 2013 capabilities


Microsoft SharePoint Server 2013 Preview makes it easy for people to work together. SharePoint Server 2013 Preview enables us to set up web sites to share information with others, manage documents from start to finish, and publish reports to help everyone make better decisions.

SharePoint Server 2013  has the following capabilities:
Sites - Provides a single infrastructure for all your business web sites. Share documents with colleagues, manage projects with partners, and publish information to customers.

Communities - Delivers great collaboration tools—and a single platform to manage them. Make it easy for people to share ideas and work together the way they want.

Composites - Offers tools and components for creating do-it-yourself business solutions. Build no-code solutions to rapidly respond to business needs.

Content - Makes content management easy. Set up compliance measures ”behind the scenes”—with features like document types, retention polices, and automatic content sorting—and then let people work naturally in Microsoft Office.

Insights - Gives everyone access to the information in databases, reports, and business applications. Help people locate the information to make good decisions.

Search - Cuts through the clutter. A unique combination of relevance, refinement, and social cues helps people find the information and contacts they need to get their jobs done.

Monday, September 3, 2012

Installing SSRS 2012 without upgrading your database server


SQL 2012 RTMed last month (March 2012) with much fanfare. For us SharePoint types, SQL is a big deal, as SQL is the backbone of SharePoint. SQL 2012 has a few new or updated features that are of interest to SharePoint aficionados, but this blog post is specifically about SQL Server Reporting Services (SSRS). SSRS got a major overhaul in SQL 2012. It is finally a SharePoint service application. Anyone that has installed SSRS previous to SQL 2012 can appreciate how big of a deal that is. SSRS 2012 is better than SSRS 2008 R2 in a whole lot more ways, but as an IT Pro, the installation and management improvements take the cake.
But what if you already have SharePoint 2010 in place, and it’s running on a SQL 2008 R2 database backend? Do you get to enjoy all the gloriousness that is SSRS 2012 without upgrading your entire SQL instance to 2012? Of course you can, or else this would be a very, very short blog post. This blog post will walk you through installing the SQL 2012 version of SSRS even though all your databases are a SQL instance that is not 2012.
First, I must take a minute to thank Steve Caravajal. This blog post is all his idea. I overheard him telling someone else about this and I stole his idea. Shhhhh! Don’t tell him. He’s difficult enough to get along with without him getting a big head. Enough about Steve, let’s get back to SSRS.
The TLDR version is this; run the SQL 2012 installer on one of your SharePoint boxes. Only install the SSRS components. Then create an SSRS service app.
Here’s the longwinded version. First you need to acquire the SQL 2012 installation. You need the BI or Enterprise editions of SQL 2012 to use SSRS. Be careful with the Developer Edition, or evaluation edition. I had some issues with “Edition Mismatch” errors when I used them. It also wouldn’t hurt if you had a SharePoint 2010 farm handy, too. On your SharePoint server run the SQL 2012 installation. Instead of installing the database engine and all the other fun stuff, just install the Reporting Services bits and the SQL Server Management Studio, like this:
image_thumb3
That’ll install all the fresh and funky new SSRS bits you want. After the installation is complete start up Central Admin and browse to the Manage Service Applications page. Click New and see what we’ve got there:
image_thumb8
Go ahead, click it. It won’t bite. It will walk you through creating a shiny new SSRS service application. Whoopee! Let’s look at the screens:
image_thumb13
Give the service app an appropriate name. Put your database server’s name in the server database blocks. This is the important part. That database server does NOT need to be SQL 2012. This TechNet article explains the database backed for SSRS 2012 can be any version of SQL from 2005 to 2012. You’ll also want to remove the evil GUID off of the default Database name.
image_thumb15
Then choose the web apps you’ll be using SSRS with. You’ll see this screen:
image_thumb17
And then this one:
image_thumb19
Hurray! At this point you have SSRS installed, but you still need to configure it. I haven’t done much of that yet, so I’m not going to cover it in this blog post.
I do want to mention that not only do you get a UI for creating and configuring SSRS, you also get a batch of PowerShell cmdlets as well:
image_thumb21
Here you can see running Get-SPRSServiceApplication returns back the service application I just created. You can configure SSRS with Central Admin, or if you want to show off, you could finish it up in PowerShell. Go ahead. I dare you.
Here’s another good link to help you get SSRS 2012 running.

Sunday, September 2, 2012

How to find Non-active laptop or computer records in effective directory?


Do you know how can we do this? Either we question the AD to get the details by composing value in C# or personally examine the AD for the non-active records. But, there is another easy way which will get this details without any big initiatives. Yes, using Powershell program
  1. $COMPAREDATE=GET-DATE  
  2. $NumberDays=90   
  3. $CSVFileLocation='C:\TEMP\OldComps.CSV'   
  4. GET-QADCOMPUTER -SizeLimit 0 -IncludedProperties LastLogonTimeStamp | where { ($CompareDate-$_.LastLogonTimeStamp).Days -gt $NumberDays } | Select-Object Name, LastLogonTimeStamp, OSName, ParentContainerDN | Sort-Object ModificationDate, Name | Export-CSV $CSVFileLocation   


You have to provide the days - the timeline of inactive accounts and where to save the output of inactive accounts list.


Program to set up SharePoint 2010 in Microsoft windows 7


You are prepared to set up SharePoint 2010 in Windows 7? Then you are at the right position. For the set up you have to obtain all needed and adhere to the finish MSDN content and then perform comprehensive. If there is something which do all the actions for you then how it is? Excellent right?