Thursday, February 26, 2015
Tuesday, February 24, 2015
- USE [master]
- ALTER DATABASE[SharePoint_Config] SET RECOVERY SIMPLE WITH NO_WAIT
- USE [SharePoint_Config]
- DBCC SHRINKFILE ('SharePoint_Config_Log')
- ALTER DATABASE[SharePoint_Config] SET RECOVERY FULL WITH NO_WAIT
- USE [SharePoint_Config]
Friday, February 20, 2015
SharePoint 2013 as a Knowledge Management Application for your Organization
This whitepaper prepared by iGrid Consulting gives you insights into how SharePoint's features along with iGrid's customization / additional add-ons & products can provide an organization with a comprehensive Knowledge Management Solution
Why Knowledge Management?:
For any organization, attrition and turnover are huge risks. In addition to the costs of hiring and training new employees, there's also the cost of losing the institutional and functional knowledge that walks out the door when an employee leaves. Capturing, managing and retaining that kind of knowledge is a challenge that knowledge management solutions aim to overcome. Think of knowledge management as a way to retain the knowledge that your employees are creating as well as the tacit, institutional knowledge that employees gain over time.
Why SharePoint for Knowledge Management?
For the last 12 years or so, SharePoint has served as a great tool for content management. Since it serves as a collaboration platform and document repository, it provides a central location for the work products your employees are creating. Over time, SharePoint has added features that take it far beyond a file share's knowledge management capabilities.
SharePoint makes it easy to manage versions, allowing users to check in and check out of files and projects. More recently, SharePoint has enabled co-authoring, with the technology reconciling changes made by two individuals who are collaborating on a single work product at the same time.
SharePoint's Native Capabilities:
With SharePoint Foundation, Standard or Enterprise, you get the below capabilities out of the box:
- Setting up Sites for your different Departments, Divisions, Units
- Setting up Document Libraries, Lists as organized stores for your Documents and Records
- Versioning, Check-In, Check-Out, Co-Authoring
- Creating Folders, Views, Alerts
- Configuring different Document Templates through Content Types
- Setting up Metadata columns for your Documents
- Search (even inside your documents)
- Configurable Permissions
- With Office Web Apps, viewing capabilities as well, within your browser itself for MS Office documents
- Blogs, Wikis, Discussion Forums, Surveys
With SharePoint Standard or Enterprise, you get the below capabilities out of the box:
- Document Sets with its own metadata and workflow
- Out of the Box Workflow Templates
- Enterprise Metadata / Taxonomy using Groups, Term Sets & Terms
- Tags & Notes
- Information Management Policies
- My Sites Integration
- Community Portals
With iGrid's Customization / Add-Ons, you get the below capabilities:
- Integrated Scanning & OCRing
- Date Field Based Reminders
- Choice Field Based Alerts
- Custom Metadata Forms
- Copy Folder Structure
- Custom Search
- eForms & Custom Workflows
- Configuration & Customization to achieve
Our KM SharePoint 2013 Foundation, Standard, Enterprise or SharePoint Online (Part of Office 365)
Thursday, February 19, 2015
Step 1: Install SQL server 2012 with SP1 or 2014. And remove 'Reporting Services – Native' from the feature selection.
Setp 2: Install SharePoint Prerequisites
Step 3: Install SharePoint with Farm Installation using domain account.
Step 4: Run below commands in SharePoint 2013 Management shell prompt (run as administrator)
Step 5: Install SSDT (SQL Server Data Tools) (Business Intelligence for VS 2013). Download it from http://www.microsoft.com/en-us/download/confirmation.aspx?id=42313
Note : This is 32 bit exe.
Step 6: In the above installation – new instance has to be selected.
Step 7: Check the SQL SERVER Reporting Services in SharePoint 2013. Go to Central Admin -> General Application Settings. We can see the SQL Server Reporting Services.
Step 8: Install Visual Studio 2013.
Step 8: Create a New web Application, Site Collection. And Enable Reporting Server Integration Feature and Reporting feature.
Step 9: Configure Target Report Folder in SharePoint
- Create a new document library named "Reports" in SharePoint Site
- Enable content type in "Advanced settings"
- Open "Report" document library, library setting "Add content type from existing" and add below content types (Report Builder Model, Report Builder Report, Report Data Source).
- Create a folder in the document library
Step 10: Create a SQL server reporting services in SharePoint service application and select the previous selected web application.
Step 11: Start the "SQL server reporting service" from Services on Server
Step 12: Open VS 2013 and select new reporting server project as below (after successful installation of SSDTBI setup installation we can see the business intelligence types in VS2013)
Note : In Connection specify the User Id and Password also.
See output in preview
Check the project properties before deploy.
Deploy the report and refresh the document library. We can see the updated data source and report.
Click the report.
Monday, February 16, 2015
Wednesday, February 4, 2015
This link is to split and run across 4 servers
This link is to run same 6 components in 2 servers
$hostA = Get-SPEnterpriseSearchServiceInstance -Identity "SGTCX-SP2APP01"
$hostB = Get-SPEnterpriseSearchServiceInstance -Identity "SGTCX-SP2APP02"
Start-SPEnterpriseSearchServiceInstance -Identity $hostA
Start-SPEnterpriseSearchServiceInstance -Identity $hostB
Get-SPEnterpriseSearchServiceInstance -Identity $hostA
Get-SPEnterpriseSearchServiceInstance -Identity $hostB
$ssa = Get-SPEnterpriseSearchServiceApplication
$newTopology = New-SPEnterpriseSearchTopology -SearchApplication $ssa
New-SPEnterpriseSearchAdminComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
New-SPEnterpriseSearchCrawlComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
New-SPEnterpriseSearchIndexComponent -SearchTopology $newTopology -SearchServiceInstance $hostA -IndexPartition 0
New-SPEnterpriseSearchAdminComponent -SearchTopology $newTopology -SearchServiceInstance $hostB
New-SPEnterpriseSearchCrawlComponent -SearchTopology $newTopology -SearchServiceInstance $hostB
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostB
New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostB
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostB
New-SPEnterpriseSearchIndexComponent -SearchTopology $newTopology -SearchServiceInstance $hostB -IndexPartition 0
Set-SPEnterpriseSearchTopology -Identity $newTopology
Get-SPEnterpriseSearchTopology -SearchApplication $ssa
Get-SPEnterpriseSearchStatus -SearchApplication $ssa -Text
Now stop in the other app servers
Stop-SPEnterpriseSearchServiceInstance -Identity "SGTCX-SP1APP01" (Where central admin is present)
Stop-SPEnterpriseSearchServiceInstance -Identity "SGTCX-SP1APP02" (Where central admin and other services are running)
$ssa = Get-SPServiceApplication –Name “Search Service Application”
$active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active
Get-SPEnterpriseSearchComponent -SearchTopology $active
The above 3 cmdlets are for finding index location, if the RootDirectory is not returning any results, then run the below 2 cmdlets
$ssa = Get-SPEnterpriseSearchServiceApplication
This should show the correct Path. If you are not happy with this path, then run the below command to set the Index location to a drive which has more space.
Set-SPEnterpriseSearchServiceInstance -DefaultIndexLocation "D:\SP Search Index"
Friday, January 30, 2015
|Using Asset Picker in our code|
|Using SharePoint Image Picker|
|Using SharePoint People Picker in Custom Webpart|
|Custom Asset Picker with Enhanced URL Field|