Visual Studio 2010 SharePoint Power Tools

Microsoft has released Visual Studio 2010 SharePoint Power tools today on the Visual Studio Gallery. These tools will extend the Visual Studio 2010 with sandboxed-compatible visual web parts and compile time errors for the disallowed code in the sandboxed solution.

 http://visualstudiogallery.msdn.microsoft.com/en-us/8e602a8c-6714-4549-9e95-f3700344b0d9

This is must for any SharePoint developers and make sure your development machine has these tools installed.

Hide “Add New Item” Link on the SharePoint 2010 List View Web Part

When you add SharePoint 2010 Lists in the web part pages or wiki pages, it shows the “Add New Item” at the bottom of the list by default. In most cases, wiki pages are considered as a mashup views along with other contents and you don’t want “Add New Item” as one of the options.

The reason for this link is web part toolbar type property sets to the “Summary Toolbar” by default. Change this setting to the “Full Toolbar” or “No Toolbar” and you will be able to hide the “Add New Item” link.

Hope this helps

Enable the SharePoint 2010 Workflow Visualizations

Workflows represents business process and visualizing business process using flow charts are one of the first things everyone does when explaining the business processes to others. SharePoint workflows represents the business process and Workflow Visualizations are one of the most welcome features added in the SharePoint 2010 Workflows.

It is important to remember that workflow visualizations are powered by the SharePoint 2010 Visio Services available as an Enterprise CAL license. Contrary to many sources (including Sahil Malik’s SharePoint 2010 Book, Page 294), workflow visualizations don’t require Office Web Apps installed on the SharePoint farm.

To enable the workflow visualizations (or to troubleshoot why workflow visualizations doesn’t work), make sure following steps are already configured.

• On the Manage Services on Server page in the Central Admin Site, verify that “Visio Graphics Services” is started.
• On the Manage Web Applications in the Central Admin Site, verify that Visio Graphics Service is available as the Service Connections for the given web application hosting the site where workflow visualizations needs to be enabled.
• On the Manage Farms feature page in the Central Admin Site, “Visio Web Access” feature is activated
• On the Manage Site Collections Feature page hosting the site for the workflow visualizations “SharePoint Server Enterprise Site Collection features” feature is activated.
• On the Manage Site Features page hosting the workflow visualizations, verify that “SharePoint Server Enterprise Site features” feature is activated.
• Verify that Silverlight 3 or later is installed on the client browser.
• From the workflow settings page in the SharePoint Designer, verify that “Show Workflow visualizations on Status Page” checkbox is selected.
• Republish the SharePoint Designer workflow from the SPD

Once each of the above steps is properly configured, workflow visualizations should be visible on the workflow status page.

Step by Step: Consuming SharePoint 2010 Lists Data in the SSRS 2008 R2 Reports

In the SSRS 2005 and SSRS 2008, one of the biggest limitations of the SSRS integration with the SharePoint technologies in the native mode or integrated mode was that there were are no intuitive ways to report against the SharePoint lists into the Reporting Services reports. Only way you can access the  SharePoint Lists from the SSRS reports is using the XML as a data source to consume the SharePoint lists. Please review my previous blog for more details: http://nikspatel.wordpress.com/2010/04/30/step-by-step-consuming-sharepoint-lists-data-in-the-ssrs-reports/

Like SSRS 2005 and SSRS 2008, although query designer has improved the overall experience of consuming SharePoint 2010 lists in the SSRS 2008 R2, SSRS can still accesses only one list at a time using the SharePoint Lists as a data source. For many real-world scenarios, this could be show stopper where reports need to access the data from the multiple lists and join them together for final presentation. Fortunately, since SSRS supports XML as a data source, SSRS reports can consume data from any custom web service which could be wrapper of multiple SharePoint list web service calls by joining multiple lists into single list required by the SSRS. Alternatively, you can use the SharePoint 2010 list enhancements and list relationships to define the joined list schema in the SharePoint.

In this article, I am going to demonstrate the step by step process to access the Single SharePoint list from the SSRS Reports using SharePoint Lists as a data source. This data source supports inbuilt query designer which would allow end users or developers to select the list, define the parameters and filters on the report without understanding detailed SOAP or CAML as a Query language.

Let’s assume that we have a requirement that we need to create the reports against the SharePoint lists and we need to host the SSRS reports on the SharePoint dashboards. To accomplish this, we need to have SharePoint List, SSRS reports consuming the SharePoint list, and SharePoint document libraries or web part pages to host the SSRS reports. In nutshell, we have a SharePoint as data provider and data presenter and SSRS as Reporting mechanism.

Step 1: Ensure that you have a SharePoint List.

In this demo, we will report against SharePoint Products List.

Step 2: Understand the SharePoint List Web Service Interface.

SharePoint has a lists.asmx web service which provides interface to download the SharePoint lists data in the non-SharePoint systems. You can access the SharePoint list web service using the http://siteurl/_vti_bin/lists.asmx. You can use the GetListItems method which returns dataset to download all the list items for the specific list.

Step 3: Create new Shared Data Source and Report Server Project

Create a new Report Server Project in the Business Intelligence Development Studio (BIDS). First step of configuring the SSRS report is creating the new shared data source. Select the SharePoint List as a data source type and specify the SharePoint Site URL hosting the lists for the connection string.

On the credentials tab, specify either windows authentication or no authentication if anonymous authentication is enabled on the SharePoint Site. Please do no select any other options. None of the other options would work for the SharePoint List Web Service.

Step 4: Create a new Report.

Next steps would be creating the report specific data source and data set to configure the data for the report. Make sure Report Data pane is available in the designer.

Step 5: Create a new Report Data Source.

Using the Report Data pane, create the new report data source. Specify the Shared Data Source as a report data source.

Step 6: Create a new Report Data Set.

Using the Report Data pane, create the new data set. Specify the Report Data Source as a data source. New Query designer support for the SharePoint Lists as a data source, allows the developers (from the BIDS tool) or end users (from the Report Builder tool), browse through the SharePoint lists, select the specific list, and define the filters and parameters without knowing detailed SOAP or CAML query language. As stated earlier, one of biggest limitations of this approach is SharePoint Lists as a data source doesn’t support selecting data from the multiple lists. One way you can avoid joining multiple lists is define the list relationships and bring the additional fields along with lookup column. For more complex joins, you can create the custom web service. Custom web service requires XML as a data source and specify the SOAP command to retrieve the data from the SharePoint Web Service in the query designer.

Here is the sample Query to access the web service through the SharePoint SSRS data interface

<RSSharePointList xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema“>
  <ListName>Product</ListName>
  <ViewFields>
    <FieldRef Name=”Title” />
    <FieldRef Name=”Product_x0020_Line” />
    <FieldRef Name=”Product_x0020_Description” />
  </ViewFields>
  <Query>
    <Where>
      <Contains>
        <FieldRef Name=”Title” />
        <Value Type=”Text”>
          <Parameter Name=”Title” />
        </Value>
      </Contains>
    </Where>
  </Query>
</RSSharePointList>

Step 7: Validate the fields returned by the Data Set

In the Query designer, you can verify if query is valid and returns the fields.
 

Optionally, you can click on the fields tab on the data set to see if query returns the data fields contained by the data set.

Step 8: Design the Report and Preview the Report in BIDS

Once you have properly configured the data source, data set, and fields, you can design the report by dragging and dropping the fields on the report designer. In this scenario, we will create a simple tabular report and preview the report to make sure reports renders fine in the BIDS before publishing to the SharePoint.

Step 9: Deploy the Report to the SharePoint

You can use the BIDS or upload the RDL files to the SharePoint Document Libraries directly.

Step 10: Verify the SSRS Report in the SharePoint
You can use Report Viewer or Report Explorer web parts if SSRS is installed in the native mode to consume the SSRS reports in the SharePoint. Alternatively, you can use the SharePoint SSRS integrated mode to create and consume SSRS reports more collaboratively by enabling the SSRS report content types in the document libraries. In this scenario, we have SharePoint Integrated environment and SharePoint document library is enabled to host the SSRS reports.

Differences between SSRS 2008 and SSRS 2008 R2 Report Data Sources

If you are running SSRS 2008 SP1 for your reporting needs, here is the quick comparison of SSRS 2008 SP1 and SSRS 2008 R2 report data sources. If you need to access SharePoint Lists and Azure databases from the SSRS reports, SSRS 2008 R2 would give you one more reason to upgrade.

SSRS 2008 SP1 Data Sources	SSRS 2008 R2 Data Sources
Microsoft SQL Server	Microsoft SQL Server
OLE DB	Microsoft SQL Azure
Microsoft SQL Server Analysis Services	Microsoft SQL Server Parallel Data Warehouse
Oracle	OLE DB
ODBC	Microsoft SQL Server Analysis Services
XML	Oracle
Report Server Model	ODBC
SAP NetWeaver BI	XML
Hyperion Essbase	Report Server Model
TERADATA	Microsoft SharePoint List
	SAP NetWeaver BI
	Hyperion Essbase
	TERADATA

Figure A: SSRS 2008 SP1 Data Sources (Above)

Figure B: SSRS 2008 R2 Report Data Sources (Above)

Creating the SharePoint 2010 RTM Virtual Machine – Step by Step Installation Guide

This article provides detailed steps to create the SharePoint 2010 RTM VM on the Windows 7 x64 Ultimate Edition as host OS and Windows Server 2008 R2 x64 Edition as Guest OS using VMware Workstation 7 and later version.

 ○   Verify that Software and Hardware Requirements of Your Computer

• Your computer is running the 64-bit installation of Windows 7.
• Your computer is running the VMware Workstation 7 or later version
• Your computer has minimum 4 GB RAM (8 GB recommended), minimum 80 GB Hard Disk Space (Optionally you can use the external hard drive for storage) 
• Your computer supports Virtualization (Enable Virtualization in the BIOS configuration)
• Your computer is connected to the Internet

 ○   Create new VMware Workstation Virtual Machine with following settings

• Guest OS – Windows Server 2008 x64 Edition
• Allocate minimum 50GB Disk Capacity
• Allocate minimum  2GB RAM (4 GB recommended)

 ○   Install and Configure the Operating System

• Install Windows 2008 Server R2 x64 Enterprise Edition as Guest OS
• Configure the Internet Connectivity on the VM.
• Install VMware Tools for better VM experience. It will install Mouse, Audio, and Video (SVGA) Drivers.
• Activate the Windows from the Initial Configuration Page
• Perform the Windows Update – Turn on and Install the Windows Update from the Initial Configuration Page. Once Windows Update is completed, turn off the Windows Update to avoid any accidental updates.
• Set the Administrator Password to Never Expires. Open the Server Manager -> Configurations -> Local Users and Groups -> Users. Change the Administrator user properties and verify that “User cannot change password” and “Password never expires” are checked.
• Change the Computer Name to user defined name. Open the server manager and click on the “Change System Properties” link from the “Server Summary” page. Change the computer name (e.g. “SP2010VM”) and verify that computer is the member of the workgroup.
• Disable the Windows Firewall. In the Server Manager, on the Server Summary page, Use the “Go to Windows Firewall” link in the Security Information to turn off the firewall for three windows profiles – domain profile, public profile, and private profile.
• Disable the Enhanced Security Configuration to avoid the Trusted Site warnings. In the Server Manager, on the Server Summary page, Use the “Configure IE ESC” link in the Security Information to turn off the settings for both Administrators and Users.

 ○   Setup the DNS and Install the Active Directory as Domain Controller

• Add Active Directory Domain Services through Add Roles wizard from the Initial configuration screen. This will also add Microsoft.NET Framework 3.5.1 windows feature.
• Launch the Active Directory Domain Service Installation Wizard at the end of the Active Directory Domain Services installation process or Run the “dcpromo” command with following settings – create a new domain in a new forest, specify the domain name (e.g. niks.local), and Forest level – Windows Server 2008 R2.
• You will be warned for the dynamically assigned IPAddress. Select Yes to use an automatically assigned IP address by DHCP Server.
• Reboot the VM and verify that login prompts the domain.
• Verify that DNS Server and Active Directory Domain Services roles are added on the Initial Configuration or Server Manager screen.
• Verify the Domain Name (e.g. niks.local) and full computer name (e.g. SP2010VM.niks.local) on the Initial Configuration screen.
• Verify that Administrative Password is set to never expire using Administrative Tools -> Active Directory Users and Computers. Verify that “Password never expires” and “User cannot change password” is checked.
• Verify the TCP/IPv4 settings for the Local Area Connection in the Network Settings. It should use the self DNS address – 127.0.0.1

 ○   Option1:  Install the SQL Server 2008 x64 Edition and SP1 and CU2 Bits

• Install the SQL Server 2008 x64 Edition – Full installation including reporting, integration, and analysis services. Specify the Administrator account (e.g. Niks\Administrator) and Mixed mode Authentication for Database Engine, Analysis Services, Integration Services, and Reporting Services.  Enable the FILESTREAM for the Transact-SQL and File I/O Streaming access.
• Install the Reporting Services but DO NOT configure the report server.
• Download and Install the Microsoft SQL Server 2008 SP1 (http://go.microsoft.com/fwlink/?LinkId=166490)
• Download and Install the Cumulative Update Package 2 for SQL Server 2008 Service Pack 1 (http://support.microsoft.com/default.aspx/kb/970315)

 ○   Option2:  Install the SQL Server 2008 R2 Edition

• Install the SQL Server 2008 R2 Edition – Full installation including reporting, integration, and analysis services. Specify the Administrator account (e.g. Niks\Administrator) and Mixed mode Authentication for Database Engine, Analysis Services, Integration Services, and Reporting Services.  Enable the FILESTREAM for the Transact-SQL and File I/O Streaming access.
• Install the Reporting Services but DO NOT configure the report server.

 ○   Install the SharePoint 2010 RTM Pre-requisites

• Review the Pre-requisites required for the SharePoint 2010 RTM (http://technet.microsoft.com/en-us/library/cc262485.aspx)
• Activate the PowerShell V2 RTM on the Windows Server 2008 R2. Please remember that Microsoft .NET Framework 3.5 Service Pack 1 and PowerShell V2 RTM are shipped with the Windows Server 2008 R2 as windows features. Open the Administrative Tools -> Server Manager. Select Features node and click on the “Add Features” link to activate the “Windows PowerShell Integrated Scripting Environment” feature. Reboot the VM. After the reboot, Initial Configuration Screen should show PowerShell in the installed features section.
• Download and Install ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2 (this will be added in the SharePoint 2010 SP1) –http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=3e102d74-37bf-4c1e-9da6-5175644fe22d
• Run the SharePoint 2010 RTM Bits to run the Pre-requisite Installer. Please note that pre-requisite installer requires internet connectivity because it will download most of these pre-requisites during the installation process. Alternatively, you can download all the pre-requisites, install them manually or  create the pre-requisite installer package as shown in Jai Li’s FAQ page – (http://blogs.msdn.com/opal/archive/2010/04/25/faq-sharepoint-2010-rtm-installation.aspx), and later run the pre-requisite installer to validate all the pre-requisites are installed properly. We will install all the pre-requisites manually for full control and to understand the process.
  • Download and Install the Windows Server 2008 R2 FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkID=166231). Run the Windows6.1-KB976462-v2-x64.msu.
  • Download and Install the Windows Identity Framework (WIF) for Windows Server 2008 R2. (http://go.microsoft.com/fwlink/?LinkID=166363) Please remember that if you have Microsoft “Geneva” Framework installed, you must uninstall it before you install the Windows Identity Foundation (WIF). Run the Windows6.1-KB974405-x64.msu.
  • Download and Install the Microsoft Sync Framework v1.0 (http://go.microsoft.com/fwlink/?LinkID=141237&clcid=0×409). Run the Synchronization.msi and it may confirm that it’s been already installed if you have installed SQL Server 2008 R2.
  • Download and Install the Microsoft Filter Pack 2.0. (http://go.microsoft.com/fwlink/?LinkId=191851). Run the FilterPack64bit.exe.
  • Download and Install the Microsoft Chart Controls for Microsoft .NET Framework 3.5. (http://go.microsoft.com/fwlink/?LinkID=141512). Run the MsChart.exe.
  • Install the Microsoft SQL Server 2008 Analysis Services ADOMD.NET. (http://go.microsoft.com/fwlink/?LinkId=130651). Run the SQLSERVER2008_ASADOMD10.msi
  • This is optional component – Install the Microsoft Server Speech Platform. (http://go.microsoft.com/fwlink/?LinkID=179612). It makes phonetic name matching work correctly for SharePoint Search 2010. Run the SpeechPlatformRuntime.msi. Please remember that installation process doesn’t inform the users that installation is completed.
  • This is optional component – Install the Speech Recognition Language for English. (http://go.microsoft.com/fwlink/?LinkID=179613). Run the MSSpeech_SR_en-US_TELE.msi. Please remember that installation process doesn’t inform the users that installation is completed.
  • This is optional component – Install the Microsoft SQL Server 2008 R2 Reporting Services Add-in for Microsoft SharePoint Technologies 2010. This is required to run the Access Services and List Reports. (http://go.microsoft.com/fwlink/?LinkID=164654&clcid=0×409). Run the rsSharePoint.msi.
  • Please reboot the machine to make sure all the pre-requisites are installed correctly before moving on the next step.
  • Run the SharePoint 2010 Product Preparation Tool (Pre-requisites Installer) to activate the Web Server and Application Server Role and verify all the pre-requisites installed.
• After the installation, restart the VM, Verify that all the pre-requisites are installed or activated as features or server roles.

○   Install and Configure the SharePoint 2010 RTM

• Run the SharePoint 2010 RTM Bits to install the SharePoint 2010 RTM. When you install SharePoint on a domain controller(DC), Setup doesn’t give you any option to choose installation type (standalone or server farm) or server type (complete or stand-alone) installation. This is a designed behavior. By default, installation will have following settings – Installation Option – Server Farm , Server Type – Complete
• Run the SharePoint Products and Technologies Configuration to configure the SharePoint 2010 environment with following settings – Connect to a Server Farm – Create a new Server Farm, Database Server Name and Account – Use the Administrator account (e.g. Niks\Administrator), Farm Security Settings – Passphrase, Central Administration Web Site Settings (e.g. port -5000), Authentication Provider – NTLM etc.

○   Configure the SharePoint Services and Basic team site

• Visit the Central Admin Web Site (e.g. http://sp2010vm:5000/default.aspx) and Click on the Configuration Wizards link to configure the service applications on the farm. This is not recommended option in real world scenarios with medium or large farm configurations but great for quick demo boxes where you can configure all the services by walking through steps of the wizard.
• Launch Farm Configuration Wizard. Specify the service account (e.g. niks\administrator). Accept the default selection and click Next to provision the services on the server. It may take a while to configure the services on the server.
• Last step is to configure the default site collection with the default web application using the URL of the machine name. (e.g. http://sp2010vm). You may skip this step if you want to configure the web application name with proper host header URL to host the root site collection. In this scenario, Select Team Site and Click OK to create the default site. It may take a while to provision the web application and root site collection. At the end of the process, wizard will show the summary of service applications provisioned and root site URL provisioned through the process.
• Activate the services that are not automatically activated during the services configuration wizard – Claims to Windows Token Service and Microsoft SharePoint Foundation Sandboxed Code Service.
• On the Central Administration Site, verify that Manage Servers in the farm and Manage Services on the Server displays all the services are running properly.
• Visit the default site collection, team site to verify that installation and configuration is completed (e.g. http://sp2010vm/)
• Configure the IE for automatic windows authentication to automatically login to the SharePoint Sites using logged in user using IE Browser -> Tools -> Internet Options ->  Security tab -> Local Intranet Zone, Sites -> Advanced

 ○   Install the Microsoft Office Professional Plus 2010 (32-bit)

• After the installation, activate the office 2010  and open the Microsoft Word to verify it works properly. Please note that Office 2010 contains SharePoint Workspace 2010 along with standard Microsoft office applications like Access, Excel, InfoPath, OneNote, Outlook, PowerPoint, Publisher, and Word.
• When installing Office 2010 on the same machine as SharePoint Server 2010, you must disable the protected view to save files to the SharePoint Server and view the Office 2010 documents from the SharePoint 2010. To turn off protected view, open the word, PowerPoint, and excel, Office Backspace -> Options -> Trust Center Tab -> Trust Center Settings -> Protected View Tab -> Uncheck any of all of the protected view options.
• If you are planning to use the Office OneNote 2010, Activate the Desktop Experience feature on the Windows Server 2008 R2.
• Upload the documents to the SharePoint Team Site and Verify that documents are accessible in the Office Clients.

 ○   Install Microsoft Office Web Applications 2010 (64-bit)

• After the Installation, Run the SharePoint Products and Technologies Configuration. Visit the Central Admin site and configure the word viewer and PowerPoint service through farm configuration wizard.
• Activate the OfficeWebApps feature on the Root Site Collection
• Run the additional PowerShell commands and verify that Word and PowerPoint files are accessible through the Office Web Viewers. Excel documents should be opened by the Excel Services. See the Jai Li’s FAQ page – (http://blogs.msdn.com/opal/archive/2010/04/25/faq-sharepoint-2010-rtm-installation.aspx).

 ○   Download and Install Microsoft SharePoint Designer 2010 (32bit).

• Please remember that you cannot install 64bit of SharePoint 2010 Designer with the 32-bit of the Office 2010 Professional plus Edition.
• Download the free 32-bit version of the SharePoint Designer 2010. (http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=d88a1505-849b-4587-b854-a7054ee28d66) and run the SharePoint Designer 2010 x86.exe to install the 32-bit version of the SPD 2010.
• Open the SharePoint Designer 2010 and click on the Open the Site to open the SharePoint Team Site (e.g. http://sp2010vm). SharePoint designer will communicate with SharePoint 2010 Server through web services interface and should open the site contents.

 ○   Install Microsoft Visio Premium 2010 (32-bit). Open the Visio Premium, activate the product, and verify that it installed correctly.

 ○   Install the Microsoft Visual Studio 2010 (32-bit). Open the Visual Studio 2010 and access the Server Explorer from the View menu. Expand the SharePoint Connections and verify that SharePoint team site contents are accessible from the explorer.

 ○   Next Steps

• Upload content the team site for better Content Search experience
• Configure the Enterprise Search
• Configure the Basic Search Center for Content Search
• Configure the Enterprise Search Center for both Content and People Search
• Configure the User Profile Synchronization (http://blogs.msdn.com/sharepoint/archive/2009/11/18/path-to-user-profile-synchronization-success-in-sharepoint-2010-beta.aspx)
• Configure the My Sites and Perform the People Search (Please note that default My Site Host is already created part of the Profile Service configured through Farm Configuration Wizard)
• Configure the SharePoint and SSRS Integrated Mode Configuration
• Configure the SharePoint and SSRS Native Mode Configuration
• And, many many more…..

Comparison of SharePoint 2010 Farm Level Solutions/Features Actions supported in Browser, PowerShell, and STSADM

I was recently looking at the deploying SharePoint WSPs from the Central Admin and was surprised to see that deploying farm level WSPs wasn’t supported through browser interface. Quick research confirmed that it was supported only using either PowerShell or STSADM commands. Here is the high level table which layouts all the available options for solution deployment/retraction and feature activation/deactivation. Hopefully it will be useful. 

Solutions Actions	Browser – Central Admin(System Settings -> Farm Management -> Manage Farm Solutions)	PowerShell	STSADM
View Solutions	Yes	Get-SPSolution	-o enumsolutions
Add Solution - Add Solutions to Farm Solutions Gallery	Not Supported	Add-SPSolution	-o addsolution
Deploy Solution - Deploys Solutions to the web applications	Yes	Install-SPSolution	-o deploysolution
Update Solution - Update the deployed solution	Not Supported	Update-SPSolution	-o upgradesolution
Retract Solution - retract solutions from the web applications	Yes	Uninstall-SPSolution	-o retractsolution
Remove Solution - Remove the solution from the farm solutions gallery	Yes	Remove-SPSolution	-o deletesolution

 

Feature Actions	Browser – Farm, Application, Site, and Web Level Features Page	PowerShell	STSADM
View Features - View features at the farm, web application, site collection, or site scope	Yes	Get-SPFeature	Not Supported
Install Feature - Install feature at the farm, web application, site collection, or site scope	No	Install-SPFeature	-o installfeature
Activate Feature  - Activate feature at the farm, web application, site collection, or site scope	Yes	Enable-SPFeature	-o activatefeature
Deactivate Feature - Deactivate feature at the farm, web application, site collection, or site scope	Yes	Disable-SPFeature	-o deactivatefeature
Uninstall Feature - Uninstall feature at the farm, web application, site collection, or site scope	No	Uninstall-SPFeature	-o uninstallfeature