Search

1 to 10 of 33
Sort by

Blog Entry
High Level Best Practices: SharePoint Source Code Management and the Related Deployment Process

Deployment configuration Visual Studio 2010 provides deployment configurations for use in SharePoint deployment. A deployment configuration is a set of deployment steps with each step associated with a deployment action

Errin O'Connor's profile image

Blog Entry
Hybrid Office 365 Search Deep-dive: SharePoint Server 2013 & Office 365 Integration

Hybrid Search Deep-dive: SharePoint Server 2013 & Office 365 Integration One of the most common configurations that is starting to emerge into today’s IT landscape is that of a hybrid cloud architecture and is something you must plan for in your organization's long-term SharePoint and/or Office 365 roadmap

Errin O'Connor's profile image

Blog Entry
Deep-Dive of Search in SharePoint 2013, Office 365 and SharePoint Online "From the Trenches"

Configurations stored in Admin database ■ The Admin database contains information regarding the crawl servers via their synchronized registry and corresponding information regarding content sources and schedules ■ Crawl modes ■ Full Crawl ■ Incremental Crawl ■ Continuous Crawl These crawls crawl the various content sources and provide back both the crawled items in terms of their actual content as well as their associated metadata which is then routed to the content processing component

Errin O'Connor's profile image

Blog Entry
SharePoint 2010 Upgrade Options, Considerations & Best Practices

There are four upgrade options as follows, each with pros and cons depending on your specific SharePoint implementation and environment: In-Place Upgrade - recommended for small or non-production environments Database Attach - recommended if farm level configurations are minimal Hybrid Approach 1: Read-Only Database Upgrade - recommended over Database Attach as downtime is mitigated Hybrid Approach 2: Detach Database Upgrade - recommended if farm level configurations are significant Detailed information about these options can be found on the Microsoft TechNet site

David Kruglov's profile image

Blog Entry
DIY SharePoint

In order to do these things correctly, and to ensure adoption, an organization has to possess a broad array of skills that fall into the following categories: IT Pro Information Architecture Software Development Evangelist & Trainer The IT Pro’s job is to set up and configure the platform which requires, at a minimum, a firm understanding of hardware, virtualization, Windows Server, IIS, Active Directory, SQL Server and SharePoint (configuration and administration)

David Kruglov's profile image

Blog Entry
Wanted: Information Management Policies

Leon, Tynes and Cathey’s “Microsoft SharePoint Server 2007” devotes a few pages to records management specifically and I find it the most helpful—primarily because the planning steps are simplified and based on configuration, not customization (since it’s 2010 and you’re just implementing MOSS 2007, this will be a BIG win with your IT department)

Mimi Dionne's profile image

Blog Entry
Building a Best Practices Information Architecture for SharePoint 2013 and\or Office 365

Detailed overview showing SharePoint 2013’s information architecture flow and structure SharePoint 2013’s Application Pool and Web Application capabilities, as shown in the image below, have a different configuration model than those in previous versions of SharePoint

Errin O'Connor's profile image


Blog Entry
Security & Identity Management Considerations for Application Development in SharePoint 2013 & Office 365

There are nine overall key steps you must take in the configuration of an S2S trust which are as follows: Create a x509 certificate Make the certificates public key accessible to SharePoint Utilize Windows PowerShell to create a trusted security token issuer based on public key Develop a provider-hosted app which has access to the private key file Create S2S access tokens with the help of TokenHelper class Pass access token by calling into SharePoint using the CSOM or REST API Select one of the two available methods to make a certificate available Pass the file path of certificate to SharePoint Expose the certificate from app as metadata endpoint The underlying architecture of an S2S trust contains the following elements and configurations: ■ App that has x.509 certificate with public/private key pair ■ Private key used to sign certain aspects in access token ■ Public key registered with SharePoint farm ■ The public key creates a trusted security token issuer ■ App creates access token to call into SharePoint, as shown in figure below ■ App creates access token with a specific client ID and signs it with private key ■ Trusted security token issuer validates signature ■ SharePoint establishes app identity ■ App identity maps to a specific client ID ■ Availability to have multiple client IDs associated with a single x.509 certificate #SecurityArchitectureBestPractices #SecurityandIdentityManagement #SharePoint #SharePoint2013andOffice365IdentityManagement

Errin O'Connor's profile image

Blog Entry
Issues with using SharePoint 2010 for Records Management

Link : DocAve Backup and Restore Moving records must maintain metadata, history and library configuration ISSUE If a document is moved to another library, or site (records center), it is imperative that all its associated metadata, history and necessary library configuration also moves with that document

Mark Jones's profile image