Proper approach for a SharePoint deployment

Wednesday, January 30, 2013 by Paul Haynes

Given my role as an account executive at IncWorx, I interface with many customers that are looking at deploying a new SharePoint farm or migrating to a newer version.  One of the big things that sets IncWorx apart is our approach when it comes to these types of engagements.  It's important to properly plan in the beginning to ensure that your business realizes the full benefits of SharePoint and it doesn't become an unused platform that your IT staff is burdoned with supporting.  The approach below outlines the steps we generally follow in one of these engagements. Please note, installing and configuring SharePoint is the easy part....having experts that can understand your business and align their needs with SharePoint is the hard part...It's also our forte!  You can also learn a bit more here!

 

Phase 1: Discovery

During the Discovery phase IncWorx generally performs a complete audit of the current systems in use that will be phased out and also conducts “Pain Points” meetings with business users to understand how they could utilize the features of SharePoint 2010/2013.  This phase generally includes the following:

  • Analysis of current technology infrastructure
    • Current means of document storage
    • Current intranet (if any)
    • Home grown internal systems that act as a hub for the company
  • Review of high level Client requirements for intranet
  • Pain Points meetings with key departments to determine fits for new/enhanced functionality in SharePoint 2010, and understanding Client’s near term and short term goals with the SharePoint platform

 

Phase 2: Information Architecture (Governance and Taxonomy Planning)

During the information architecture phase, IncWorx will work with Client to understand current governance and taxonomy strategies with the goal of understanding the current pain points or gaps.  We will then develop new models based on our extensive experience that will align with Client goals and will ensure optimal usability for end users.  This phase will include a review of any available documentation of the current taxonomy as well as current Governance documentation.

 

Phase 3: Documentation and Migration Plan

During this phase, IncWorx will create documentation that outlines our findings and recommendations from phases 1 and 2.  The documentation will include, as appropriate, the following:

  • Findings from the Discovery phase
  • Recommended  taxonomy model(s) from Phase 2
  • Governance overview and/or outline
  • Recommended features/functionality  found in SharePoint 2010 based on Pain Points meetings
  • Determination of the appropriate migration path for existing data that will be housed in SharePoint
  • Recommendations for 3rd party tools based off of our findings in Phases 1 and 2 (if applicable)
  • Hardware/software shopping list (if applicable)
  • Roadmap and deployment plan that provides approach and strategy short and long term platform growth

 

Phase 4: Hardware/Software Procurement(if applicable)

During this phase Client will procure the hardware and software based on IncWorx recommendations.  IncWorx will lend guidance for properly configuring and installing components if necessary.

 

Phase 5: Proof of Concept

During Phase 5, IncWorx will create a SharePoint 2010/13 POC environment based on the roadmap and deployment plan from Phase 3 and will perform one or more data migration tests to validate the approach prior to the Production deployment.  This phase will include:

  • Creation of Service Accounts
  • Installation of SharePoint 2010/13 (if applicable)
  • Test migration(s) of data
  • One department/test group built out with data and desired functionality for validation of the approach
  • Documentation of all issues encountered as well as their resolutions

 

Phase 6: Deployment

Once the POC and migration tests are complete, IncWorx will perform the production deployment. 

 

Phase 7: Testing, Tuning, Tweaking

During this phase, IncWorx will review the production SharePoint 2010/13 environment with Client to ensure that the criteria from the roadmap and deployment plan have been met and that all desired functionality within the scope is present.   IncWorx will also perform a post deployment analysis and ensure that all features and functionality are working properly, that all migrated data is intact, and to finally ensure that client has a solid foundation from which they can continue to build and expand upon for future phases.

 

Deliverables from all phases:

  • Comprehensive roadmap and deployment documentation
  • A fully functional SharePoint 2010 POC
  • A fully functional SharePoint 2010 production implementation that meets the criteria outlined in the Roadmap and Deployment Plan

 

Please contact me if you need help or would like to discuss further.  Paul dot Haynes at IncWorx dot com or 847-839-9679.

Recently Viewed Documents in SharePoint 2010

Wednesday, May 2, 2012 by Paul Haynes

If you have been following our blog or have seen any other posts, you're probably very familiar with our new UI/UX package called BrandIt.  If you haven't been, BrandIt is an easy-to-deploy UI/UX package that includes a custom master page as well as Web Parts that were designed to help improve the user experience and bolster user adoption. 

With BrandIt having been in production state since the end of March, our next phase is to roll out new web parts to continue to increase the usability of SharePoint.  Our most recent web part/functionality roll out is the "Recently viewed documents" view.  This is a feature that many users of the various office tools enjoy using that is not available in SharePoint out-of-the-box.  Having provided this functionality within the BrandIt package, we have equipped users with yet another added benefit that will make them LOVE using SharePoint 2010! 

If you have any questions or would like to see a demo, contact Paul.Haynes (at) IncWorx.com

SharePoint Document Routing

Thursday, April 19, 2012 by Patrick Kelleher

IncWorx Consulting is thrilled to announce that they have recently added another remarkable product to their arsenal. This one is a rules-based document routing tool for SharePoint 2010, and is appropriately called RouteIt. This helpful package actually trumps the very basic Content Organizer feature within the SharePoint design for a variety of reasons. This blog will help you understand the differences between the two so you can see how RouteIt will dramatically increase user acceptance within your organization.

RouteIt is similar to Content Organizer in many ways, but there are numerous benefits that RouteIt provides where Content Organizer falls short.

  • To start, RouteIt is compatible with SharePoint Foundation, Standard, and Enterprise versions, whereas Content Organizer is not available on Foundation.
  • With RouteIt, any number of lists or document libraries is allowed per site, but Content Organizer only supports one.
  • The user may find it annoying when a new document library called “drop off library” is created when trying to enable routing on an existing document library, but RouteIt eliminates this frustration.
  • RouteIt also works with lists as well as document libraries, but Content Organizer only supports the latter.
  • Content types are not required with RouteIt, since rules are based on columns of metadata, but the opposite is true for Content Organizer because rules are based on properties of a specific content type.
  • The final thing I’d like to point out is the fact that RouteIt supports metadata-based destination URLs, whereas Content Organizer is a little trickier. It allows folders to be specified using metadata, but the destination site, list, library, and folder hierarchy remain static.

As you can see, RouteIt for SharePoint 2010 benefits your organization in a multitude of ways. The convenient improvements RouteIt brings to the table greatly outweigh the Content Organizer feature. RouteIt will help you customize SharePoint to make it even easier to use and you will be wondering how you ever lived without it! Contact us today and RouteIt!

New Branding Package Web Part: Interactive Tabbed Banner

Wednesday, March 21, 2012 by Patrick Kelleher

IncWorx Consulting is very excited about a brand new product they just rolled out called BrandIt. This is a comprehensive branding package for SharePoint 2010 and a great way to customize SharePoint to give your organization's intranet a better look and feel.

One of three web parts contained in this package is an interactive tabbed banner. This is advantageous because it is list-driven and supports full HTML. This was also built using jQuery, which allows content to be automatically populated from multiple lists and list views if the user simply hovers their mouse over a tab.

If you’ve ever had the problem of being lost or not knowing the happenings within the company, this collaborative tool will help you because it was built to keep everyone on the same page.

The other benefit to the interactive tabbed banner is the convenience factor. Instead of sending an email organization-wide and having some people miss it (it’s hard to keep track of all those email we get per day!), this web part allows companies to deliver consistent messages organization-wide. In this way, it acts as the Yahoo! or MSN homepage, updating you on current events or announcements within the organization.

As you can see, the interactive tabbed banner is a very useful web part within our new comprehensive branding package, BrandIt.

If you would like to learn more about the announcement banner or if you would like to see a demo of BrandIt in its entirety, please contact Patrick Kelleher at 847-839-9679 or email me at patrick.kelleher (at) incworx.com

Could not establish trust relationship for the SSL/TLS secure channel with authority - Troubleshooting SharePoint

Thursday, February 16, 2012 by Mario McGuire

Calendar overlays are one of the great SharePoint 2010 benefits, but if not setup correctly during the SharePoint implementation it can be a nuisance. I want to share with everyone this fix to the error "Could not establish trust relationship for the SSL/TLS secure channel with authority" when adding an Exchange overlay.

 

Problem -

Error message: Could not establish trust relationship for the SSL/TLS secure channel with authority

After adding an Exchange overlay SharePoint 2010 displays this error.

 

Cause -

 This error is caused by a trust relationship issue when using 3rd party certificates between your SharePoint server and Exchange Server.

Or

The trust relationship between the SharePoint Farm and the Exchange server doesn't exist or hasn't been configured correctly.

 

Solution -

1) Go to "Central Administration" and click on "Security"

2) Under "General Security" click on "Manage trust"

3) Create a name (e.g. Name: Webmail) 

4) Root certificate for the trust relationship:  <enter cert provided downloaded from third-party CA> (You may have to locate the root cert from your third-party vendors site)

5) Click OK

 

After completing the resolution steps you should be able to reload your page and see your calendar overlay.

 

Contact IncWorx Consulting at help@incworx.com with your next SharePoint support question!

 

Integrating Mobile with SharePoint 2010

Friday, January 13, 2012 by Michael Mayes
IncWorx Consulting has taken leaps and bounds in the mobile arena to integrate mobile devices to SharePoint Server 2010.

Recently mobile devices have become more powerful and easy to use. Laptops, netbooks, tablet PCs, and mobile phones are relied upon to provide workers access to the information and applications that they must have to do their jobs. Additionally, developing applications for mobile devices is now easier than ever. As a result, more and more often business scenarios demand integrating client applications together with business processes and workflows.

Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010 to provide workflow capabilities that enable you to model business processes and integrate them with multiple applications and systems. You can create client applications to extend reach of the workflow and make it available outside the context of SharePoint sites. Creating client applications to access workflows in SharePoint sites requires a client application, networking (services), and integration with SharePoint lists and workflows.

Scenarios

The following scenarios are examples of using mobile devices with SharePoint workflows:

  • An insurance company that uses mobile applications to locate insured assets and file claim reports for customers
  • A company with underground infrastructure, such as a telephone, electric, or cable company, that uses mobile applications to locate underground infrastructure and mark it to ensure it is not damaged during digging
  • A water company that uses mobile applications to record how much water each customer uses
  • A retail company which uses mobile applications as a point of sale application at outdoor events (concerts, sporting events, carnivals, etc)

As the previous scenarios show, the need for rich functionality, data access, and process integration in mobile applications is common. Creating mobile applications that integrate with SharePoint 2010 saves time developing mobile applications that meet these requirements.

This article focuses on integrating client applications together with the SharePoint framework, particularly showing how to read and write data from SharePoint lists to integrate with workflow processes.

Benefits

Extending SharePoint workflows beyond SharePoint sites in a web browser provides several benefits to workflow participants. The benefits include, but are not limited to the following items.

  • Interacting with workflows from a mobile client application (mobile access)
  • Reducing the steps to interact with a workflow
  • Enhancing the workflow process with rich data and functionality
  • Automating parts of the workflow process.

Components

You must create several components to integrate mobile client applications together with SharePoint workflows. These components include the computer that is running SharePoint Server, sites, lists and workflows to store data, define business processes, and define security permissions, the mobile client applications that access the data in the SharePoint lists and workflows, and the services which support communication between the mobile client application and the computer that is running SharePoint Server. The following figure shows these components and how they are related. Rely on our SharePoint Experts to configure these types of scenarios.

Don Funk

(Provided by MSDN)

If you are looking for a Microsoft Gold Partner to help with your SharePoint Deployment to integrate mobile technology than call the experts at IncWorx at 847-839-9679. 

Web Application Zones in SharePoint

Friday, December 23, 2011 by Nikolai Brendler
In talking with several clients, I've found that one of the more confusing aspects of SharePoint (both 2007 and 2010) is web application zones. There are a few reasons for this confusion, but I think one of the biggest is that the SharePoint Administrative UI usually only tells half of the story. To get the whole picture, you also need to look at how IIS, DNS and sometimes your firewall are configured.

In simplest terms, a web application in SharePoint is an associate of one or more content databases to one or more IIS web sites. Each IIS web site corresponds to a zone, and each web application can use up to 5 zones -- Default, Intranet, Extranet, Internet and Custom.

Source of confusion #1: The zone names are just labels. With the exception of "Default", they don't have any implication on the behavior of that zone. If you wanted to, you could set up all traffic from the Internet to use the "Intranet" zone. Provided everything else is configured correctly, it would work fine.

The Default zone is an exception only because certain administrative functions in SharePoint will use the Default zone and no other, so it's important to make sure that all of your SharePoint servers can resolve this name in DNS.

When a web application is first created, only the Default zone is defined. If you want to use other zones, you need to "Extend" the web application. This will create a new IIS web site for that zone.

Source of confusion #2: When you extend the web application, you're not done. You still may need to configure the bindings and possibly host headers on that IIS web site in order for it to work correctly. Depending on the values entered when extended the web application, you might also need to make modifications to Alternate Access Mappings.

What are the benefits of using separate zones? Having separate zones allows you to specify different URLs and authentication providers for the same content. This allows you to set up situations where external users log in using forms-based authentication while internal users can continue to use NTLM, and both can view and collaborate with the same content.

You can also employ user policies to great effect using separate zones. For example, if you set up a separate zone for VPN traffic, you can prevent users from editing or viewing content on the VPN, even if their account normally has access to the site when viewed internally.

Hopefully this sets you on the right path when planning how many web applications you need, and how they should be accessed.

Need a SharePoint developer or SharePoint consultant? Or just some SharePoint support? Give IncWorx Consulting (a SharePoint-focused Microsoft Gold Partner) a call today!

SharePoint 2010's Web Content Management Sweet Spot

Thursday, December 8, 2011 by Mat Agrest
SharePoint 2010 as a web delivery platform
I happened to find this article on cmswire.com that was talking about where SharePoint 2010 is at its best as a web delivery platform.  I think the author, William Saville makes some good points in the article, and I would like to breifly touch on some of these points.

SharePoint 2010 as a facing application deliery platform
Site visitors want a website that is interactive and provides some service that will deepen the users experience.  SharePoint has many features that prove to do just this.  It has the ability to let organizations built their own online community through blogs, wikis, discussion boards, and user profiles.  All of these features help provide end users with a vast array of informatino that strengthens customer relations and brand.

Search-Driven web experience
SharePoint 2010 is all about search, whether it be out of the box or having FAST search implemented.  Most users these days want to be able to have a way to find information pertinent to them.  Any form of SharePoint's search options can and will provide this functionality to your users.  "The quicker people can find what they are looking for on a website, the more likely they are to engage and take an interest one step further" (Saville).  

Microsoft Centric Organizations
Most organizations these days use some type of Microsoft product, for example Microsoft Office 2010.  SharePoint 2010 integrates with the entire Office suite beautifully and flawlessly.  This also helps your IT department since any support they may have to do, will all be based around a single platform.  End users also benefit as they only have to learn one set of authoring tools.  All of this can greatly impact an organization's digital progress.

Feel free to check out the rest of the article here:
http://www.cmswire.com/cms/customer-experience/sharepoint-2010-as-a-web-delivery-platform-013675.php
 

IncWorx Consulting is a leading Microsoft Gold Partner focusing on SharePoint Consulting, SharePoint Support, and SharePoint Application Development.

SharePoint 2010 Tip Of The Week - How To Optimize Your SharePoint 2010 Farm For Enterprise Search

Friday, November 11, 2011 by Mario McGuire

Many SharePoint admins know that Search is the 800 pound gorilla in your SharePoint farm. There are several schools of thinking when it comes to making your farm run better when using enterprise search. At SharePoint Conference 2011 there was a nice lecture done on the subject of performance tuning in SharePoint 2010. 

The lecture was done by presenter Eric Shupps a SharePoint Server MVP. Eric strongly suggested that you setup your search databases the SQL server's fastest disk. Another important tip is to isolate the crawl and temp databases. The reason that disk placement and database isolation are important is due to these facts -

  • Crawl databases can be very large.
  • High index sensitivity.
  • Heavy transaction volume.
Hopefully these tips will help you in your quest for a finely tuned SharePoint environment or helping with implementing of SharePoint 2010. It is also important that you take time in your SharePoint planning to make sure you put your best foot forward toward a well designed and very functional environment. There are many SharePoint 2010 benefits that you can take advantage of. IncWorx Consulting is a Microsoft Gold Partner that specializes in SharePoint from Implementation to troubleshooting.

AvePoint Released DocAve 6 Public Beta

Saturday, October 22, 2011 by Ameil Abdallah

AvePoint released the DocAve 6 public beta that simplifies deployment, monitoring, and enforcement of Microsoft SharePoint 2010 governance policies.  It manages development and lets you test production farms with ease.  It also features a redesigned, ribbon based interface to simplify and automate SharePoint governance and management. 

Key benefits of DocAve 6 include Increase Business Productivity, Reduce Total Cost of Ownership, Provides IT Assurance and Enable Security & Compliance for Business Content.  These benefits help deliver high-performance, global collaboration, increase operational efficiency and improve quality of service & minimize business disruption. 
DocAve 6 is built upon Microsoft technologies including .NET, WCF(Windows Communication Foundation), and Silverlight which works well with SharePoint Design.

IncWorx Consulting is a Microsoft Gold Certified Partner and recipient of the Microsoft Partner of the Year award! Need SharePoint help?  Let IncWorx Consulting come along side of your organization and be your SharePoint Partner. Give us a call today!

SharePoint 2010 Access error on Android's default browser - SharePoint Mobile

Friday, August 26, 2011 by Mario McGuire

With more and more people using Android Phones and Tablets, it has come to my attention that the Android Phone’s and Tablets default browsers block the SharePoint 2010 credentials popup window. This makes it difficult to login and edit your site on the go. If you have a SharePoint site, and plugin your URL into the Android browser you might get a 401 Unauthorized error. Unfortunately, the default browser blocks the login prompt popup which could prevent anyone on one of these devices from logging into their SharePoint site. I recently spent a few minutes testing my own HTC EVO 4G to access our SharePoint 2010 team site.

To fix this issue, just goto the Application Market and download Firefox or Opera browsers. Opera and Firefox are both officially supported by Microsoft for SharePoint 2010 and will allow you to login to your SharePoint site and login. Both browsers will provide SharePoint’s login popup which allows you to login to your site! By using the Firefox or Opera for your browsers, you can properly login and view your site. I also tested a few other browsers like Miren and Dolphin browser that do login but don't view the SharePoint site correctly.

If you have an Android OS phone or tablet and want to use SharePoint Mobile. Give this a try! It is very possible that this could affect SharePoint iPhone user access.

Using mobile phones to access your data really shows off some of the SharePoint 2010 Benefits for end users.

Release Earnings Faster on Wall Street Using SharePoint Server 2010.

Wednesday, August 24, 2011 by Jeffrey Scalet

IncWorx Consulting, a Managed Gold Partner

Problem:

For decades, financial reports and data gathering were very time-consuming practices, especially when earnings were expected to be delivered to the SEC in such short time frames. Even more pressure was added considering what happened in 2008. Analysts would spend an exorbitant amount of time gathering quantitative data, checking and rechecking numbers, tracking down support documentation and getting sign-offs from Executive Management. This in turn, added costly mistakes when an analyst reported inaccurate numbers and the company’s stock prices were affected due to high percentage of user entry error. 

A team of analysts needed to spread the work out to various sectors in the organization so that it would not bottleneck. Analysts would need a better way to collaborate and required better collaboration tools. Organizations want to release earnings as quickly as possible to Wall Street, but they also strive for an error-free and an efficient process. 

Solution:

By using SharePoint Server 2010 and having the top consulting firm, IncWorx, help you organization architect a solution; your financial analysts no longer have to submit Excel spreadsheets through e-mail messages that could get caught by spam filters. They can now post them into SharePoint along with all other supporting documentation. The final versions of the financial statements are stored in SharePoint so that anyone questioning a figure need only view the document in the SharePoint portal where one “true” copy of the document lives. Financial staffers can create task lists for individual stakeholders that require additional information. Also, the online tasks and calendars make it easier for analysts to manage their piece of their workflow in SharePoint. Every team member will be fully aware of where they are in the process and can pull any document they need to review and approve.

 

SharePoint 2010 Benefits:
By using SharePoint 2010, analysts have been able to streamline its complex, time-pressured financial closing and reporting activity; achieve significant time savings; and better focus its financial professionals on moving the business forward. Being able to release earnings faster and file financial statements quicker is a huge benefit to the financial community. An organization would experience reduced e-mail volumes and can quickly and efficiently locate and collaborate on documents in compressed timeframes. Instead of spending three to four weeks in a quarter on closing data, a team can cut this time in half and release earnings faster to Wall Street. Now analyst can concentrate on their core expertise and work more efficiently.

I have numerous financial experiences prior to joining IncWorx. We won the SharePoint Partner of the Year Award from Microsoft and we have worked with many notable clients in the financial sector including Citadel, Duff and Phelps and Next Financial. If you find this information beneficial and want to learn more about how we can help your organization, please feel free to contact Jeffrey Scalet at 847.839.9679 Ex 211.

What's New in SharePoint 2010 Service Pack 1?

Tuesday, July 19, 2011 by Patrick Kelleher
What are the new features offered by Service Pack 1 for SharePoint 2010?

Support for SQL Server 2011
SharePoint's ability to integrate with SQL Server has greatly enhanced the product. With new features emerging in the "Denali" version of SQL Server, implementing SharePoint 2010 will become even more powerful.

Shallow Copy
With this new feature, you are now able to move site collections to new content databases without moving Remote Blob storage content. This way, you don't have to copy the unstructured data in the file store because only the ownership information is moved.

Site Recycle Bin
Have you ever accidentally deleted a site/site collection before? Now, administrators can restore these sites and site collections with the Site Recycle Bin. This is definitely a good tool to have available in case anything devastating happens. SharePoint has had a Recycle Bin feature for lists, libraries, and documents, but this is a nice addition to the SharePoint design.

Storage Space Allocation Page
StorMan.aspx was originally removed from SharePoint 2010. However, it is reintroduced in Service Pack 1 as one of the many SharePoint 2010 benefits. This new functionality displays better quota information to users as well as deletes content that users do not need, making it easier for users to clean up their sites.

Cascading Filters in PerformancePoint Services
You can pass filter values from one filter to the next with Service Pack 1.

Broader Browser Support
Internet Explorer 9 and Google Chrome are now supported in SharePoint 2010 SP1.

The new functionalities that Microsoft offers with Service Pack 1 are reasonable upgrades and prove to be very helpful in tackling your SharePoint 2010 initiative.

If you are looking for SharePoint Consulting, please reach out to IncWorx at (847) 839-9679. Trust a Microsoft Gold Partner and count on us for any SharePoint help you may need.

Ruven Gotz: SharePoint Saturday Chicago: Suburbs Edition

Monday, June 13, 2011 by Michael Mayes
SharePoint Saturday Standout: Ruven Gotz

I attended SharePoint Saturday this weekend 6.11.11 and was blown away by Ruven Gotz's presentation on Effective Requirements Gathering Workshop - How to organize and Run Them. He highlighted ways to help organizations have a successful SharePoint implementation by gathering the right information from the start. 

Ruven suggested to have a group from three to eight people to gather information about documents, meta data, site structure, wire-framing & business process workflows. He introduced tools like MindJet MindManager for site structure and taxonomy, Balsamiq for wireframing, and Visio for business process workflows.

"Never demo SharePoint until after the pain points meetings" Ruven Gotz

For a successful SharePoint deployment the "envisioning, discovery, requirements gathering, or pain points meetings" are vital. Once this information has been gathered you can have a demo to show the SharePoint 2010 benefits. This was the suggested agenda from Ruven:

Agenda of Pain Points Meetings
  • About the Project , Our Team & Goals
  • SharePoint Overview
  • Department and Role
  • Document Collaboration
  • Document Storage and Search Compliance, Records Management & Off-line
  • Questions
  • Meta Data Overview
  • Homework: Complete Meta Data Documentation
Road-mapping
  • Summarize workshop results
  • Build Gap Analysis
  • Identify dependencies
  • Lay out a time-line (not a project plan at this point)
Navigation
  • Site Structure build with MindMapping
Document Inventory/Taxonomy
  • Use Meta Data homework (document inventory) and MindMapping to interactively build out the taxonomy with the stakeholders
Business Process
  • Mapped with Visio

For the full slide deck Ruven was nice enough to send me a hyperlink with all of his material from the presentation.

Ruven Gotz: Effective Requirements Gathering Workshop

About Ruven Gotz
Ruven Gotz is a Senior Consultant & SharePoint MVP. With over 20 years of IT industry experience, Ruven has spent the past seven years delivering award-winning SharePoint solutions for a wide range of clients.

About IncWorx

IncWorx Consulting has been working with SharePoint since 1998 when the platform was named Site Server. IncWorx specializes in SharePoint architecture, deployment, SharePoint development, and SharePoint support.

SharePoint Branding: Mobile Solutions

Friday, May 13, 2011 by Brian Prigge
In a world that is increasingly mobile, there is an increased need for enterprise systems that easily translate to a mobile platform.  One of the major SharePoint 2010 benefits is the out of the box functionality that allows users to view a condensed version of SharePoint. 

SharePoint 2010 will automatically determine if a user is using a mobile browser and, if so, redirect accordingly.  This featuer is customizable using the "compat.browser" file within your virtual directories.  It is customizable at the site collection level.

The default mobile view is an exteremly condensed version of SharePoint that affords you little more than access to the lists and libraries.  That being said, the mobile pages are customizable and it is possible to allow your corporate branding to come through on the mobile pages.  Any changes made to the mobile pages are at the server level not the site collection level.  A SharePoint Developer can access these files and help you change them. 

Prior to beginning any development to change the branding of the mobile pages, make sure you have a SharePoint design that meets the needs of all of your mobile users. 

IncWorx Consulting is a Microsoft Gold Certified Partner serving clients across the united states.

How to redeem your SDPS vouchers

Wednesday, May 11, 2011 by Paul Haynes
Most people who have Microsoft enterprise agreements have software assurance benefits, and with these benefits are SDPS Vouchers.  SharePoint Deployment and Planning Services is what the acronym stands for.  The program was designed (by IncWorx and Microsoft) to help customers not only take advantage of their Enterprise Agreements, but also to point them into the direction of SharePoint firms who have a proven track record with the platform.  In order for a SharePoint firm to become a SDPS certified partner, they must pass a number of tests, have a number of credientials and have positive client references for SharePoint work done. 

The services come in 1,3,5,10, and 15 day packages, meaning that you get X amount of days of free SharePoint consulting.  These services are traditionally used for deployment and planning, but can also be used for other consulting needs if you already have SharePoint deployed. 

In order to redeem these benefits, have the person who handles your company's Microsoft licensing agreement check how many days you have available, and then have them create the vouchers and then assign them to us.  We handle the rest from there. 

Most of the people that I work with know that they have these vouchers available to them, but they do not know how to redeem them.  Because of this, a number of folks will just let the vouchers expire rather than redeeming them for free SharePoint consulting! 
Please reach out to us over here at IncWorx if you need any help or have any questions. 

P.S. We won Microsoft's 2010 award for SDPS - we are just the partner to help you out! 

Scanning, Indexing and Regulatory for Financial Services: Implementing SharePoint 2010

Friday, March 25, 2011 by Jeffrey Scalet

In the financial service industry numerous papers and important information are processed hourly. From prospectuses to important client information, organizations are striving to find a platform to store emails, faxes and compliance documents that are vital to day to day operations. Unexpected overhead is incurred when this process is manual, this in turn adds to the spike in operational costs including employee time to manage paper documents and opportunity cost lost in preforming these tasks opposed to other more meaningful tasks. Financial institutions need effective ways to securely, capture, exchange, and manage this information appropriately in a cost-effective way.

SharePoint 2010 takes the hassle out of managing important paperwork and can provide higher return of investment compared to other document management systems. The SharePoint 2010 benefits are vast and can lower cost of document management. With IncWorx Consulting's help, we can automate the time spent managing the paper trail and allow more time in delivering the core competencies of your organization. SharePoint 2010 helps maximize collaboration features for document repository needs. A huge advantage of using the platform is the ability to configure and restrict user access to documents based on individual user roles. The roles are predefined by system administrators and can provide a framework that allows account managers segregation from account executives. In these scenarios managers looking at client histories will never overlap executives accessing corporate strategy documents.

Having a firm like IncWorx Consulting to manage SharePoint can optimize operation efficiencies, boost customer service, create and clear audit trails, and help ensure regulatory compliance through secure access to content on SharePoint-based systems.

Team Foundation Server Integration With SharePoint

Tuesday, March 15, 2011 by Patrick Kelleher

Team Foundation Server (TFS) is the first full feature software development life cycle product that Microsoft introduced. It offers source control, data collection, reporting, and project tracking and is mostly utilized for software development projects where collaboration is key to the completion of the project. TFS can be used by itself or in collaboration with Visual Studio Team System, serving as the back end platform. If you use it while implementing SharePoint 2010 as well, TFS can be a life saver.

Think of TFS as a wheel. Source control is in the middle, acting as the main cog in the wheel. From there, four spokes emerge that are named requirements management, defect management, task/project management, and release management. This diagram will help you understand how TFS works and the functionalities it provides.

One notable feature of TFS is its very tight coupling with the SharePoint design. Due to this great benefit, TFS can provide a ton of SharePoint help by exposing out pieces of information about a project into SharePoint. For example, say that you are a manager that is managing Project X, and want to have a really quick way to see how many open defects at a high priority level still exist in Project X. You don’t have to go to TFS or get a developer involved. By exposing that project out through SharePoint (which is a relatively straightforward process), any manager could look at that project site in their SharePoint farm or site collection. There are a whole slew of web parts that ship with TFS that can be added to your standard SharePoint environment. You can get a list of tasks, open items, release management, and more.

From a SharePoint developer perspective, there are custom web parts in the project web site that, based on your user ID, will tell you what tasks you have left. All of this is integrated into the development tools that you would be using to develop anyway, such as Visual Studio. There’s also a free product called Team Explorer for TFS. This is the way business analysts and project managers can get insight into projects and information. For the developer, it’s integrated directly into their development environment. It is a single toolset, so you never have to leave your development environment to see existing tasks, bugs that have been allocated against the work you’ve done, etc.

But what if I don't want to use TFS with SharePoint?

There is no limitation to the functionality of TFS if it isn’t integrated into a SharePoint environment. The SharePoint integration is simply there to allow non-developers easy access to information that is housed inside of TFS. For instance, a developer can go in real quick and run a report inside their development environment, finding out how many outstanding bugs they have for a project. A business manager might not know what TFS is, but still wants to know how many open issues there are in Project X. The ability to expose out those pieces of information into SharePoint is how Microsoft solved that problem.

SharePoint just gives non-technical users access to information that is business critical, but housed in TFS. There is nothing that will not happen if you don’t have a TFS public interface, everything works just the same. All the functionality that TFS can provide is exposed through its integration with Visual Studio.

There are a myriad of other functionalities TFS can provide, including the use of build agents, test-driven development, branching and labeling, and its IDE agnostic capabilities. Also, TFS with SharePoint implementation will increase the quality of your software and save you money from what you would have spent on tools that were needed in the past. Call IncWorx and talk to a SharePoint consultant about how to optimize your business processes with TFS today!
 


SharePoint 2010 My Site Capabilities

Friday, March 11, 2011 by Patrick Kelleher
A very interesting  and relatively new feature of SharePoint implementation is the My Site functionality. My Site is very similar to Facebook regarding the personalized look and feel of your profile. My Site provides a way to save and share your work, find and connect to other employees in order for them to view your work, and even customize who views it or how they view it. SharePoint 2010 Mysite

In the private view, you will see information of interest to you based on your membership in a particular audience. For example, a new employee might see links to training resources. From this single place, you can manage documents, view and set up alerts, connect with other people and information, check your email, and maintain a calendar. The private view includes information pertinent to you as an individual and is your own personal space that allows you to customize SharePoint.

On the other hand, My Site also has a public view that links you to information that you share with other employees. Your most recent documents and any other links or sites that you may want other people to see will appear on this page. To do this, you can easily update your profile, provide appropriate links, and send a link to other people in your organization easily and conveniently. In addition to this, all the functionalities of SharePoint 2010 are available on your public profile page, such as document libraries, surveys, tasks, lists, etc. Links and documents you create in your personal site can be shared with other users in your public site by simply adding them to public document libraries.

Just as you can share information with others in the public view of your personal site, you can also find and connect with people through their public views of their sites. When you connect to an employee, you will also see the links to sites, people, and documents that person has chosen to share. Furthermore, you can see what interests and hobbies you have in common.

The site administrators can grant permissions in terms of the level of personalization that users are allowed to have on their site. They can also modify web parts, the shared view of My Site, and target audiences for content such as links and documents.

As you can see, My Site is just another one of the SharePoint 2010 benefits and parallels Facebook in a lot of different aspects. The customization of your profile, privacy settings, the ability to post links, and the search option to help maintain employee relationships makes it easier for end users to familiarize themselves with SharePoint and help them get acquainted with the SharePoint design.

SharePoint mobile device compatibilities in the Higher Education vertical

Monday, March 7, 2011 by Patrick Kelleher

Since most college students today are constantly attached to their cell phones, it was only logical to assume that SharePoint developers would eventually create mobile device compatibilities. These functionalities include most features of SharePoint and allow the user to access them on-the-go.

Implementing SharePoint 2010 Workspace Mobile allows the user to browse document libraries and lists right from your phone! You can also open, edit, and sync documents directly for viewing or editing in the various mobile office apps like Word 2010, Excel 2010, and PowerPoint 2010, and sync to SharePoint 2010. In addition to this, you can also perform a multitude of tasks such as people and document searches or receiving SMS alerts on SharePoint content. Since SharePoint 2010 supports accessing information from a web browser enabled mobile phone, it offers:

•Lightweight interface and navigation for accessing document libraries, lists, wikis, blogs, web part pages and LOB data
•Web companions for viewing Word, Excel and PowerPoint documents
•Mobile MySite for staying in touch with colleagues
•Mobile search experience for finding people, contact information, SharePoint content and finding data in custom databases
•SMS Alerts for changes to SharePoint content
•Features are customizable and, all the information is in SDK.

SharePoint also supports a wide variety of mobile browsers, which includes:

•IE Mobile on Windows Mobile 5/6/6.1/6.5
•Safari4 on iPhone 3G/S
•BlackBerry 4.x and newer versions
•Nokia S60
•NetFront 3.4, 3.5 and newer versions
•Opera Mobile 8.65 and newer versions
•Openwave 6.2, 7.0 and newer versions
 
SharePoint mobile device compatibilities out-of-the-box include web part pages, document and picture libraries, lists, blogs, wikis, office documents, search, and MySite. In order for SharePoint to be accessible  outside the corporate firewall, however, IT administrators must publish SharePoint via an SSL VPN gateway, use a mobile proxy, or expose SharePoint server to internet directly.

SharePoint's ability to be mobile within a cell phone could drastically increase the importance of using SharePoint in the collegiate environment. It is projected that SharePoint mobile capabilities will cause an increase in frequency of utilization in the classroom setting as well as relevancy in real world applications. Accessing SharePoint has never been so easy and versatile, and this is just one of the many SharePoint 2010 benefits. College students already carry their cell phones with them wherever they go, and now SharePoint can be with you on-the-go as well.

Source: http://blogs.technet.com/b/office2010/archive/2010/03/09/configure-sharepoint-server-2010-for-mobile-device-access.aspx