Since that time this customer has gone on to do some amazing things with their SharePoint 2010 farm, including rolling out several more public facing web sites and an extranet.

So I titled this post “Tips for SharePoint Beginners” and I am sure by  now you are asking, where are the tips?  I wanted to first establish a bit of background so you can see where my opinions on SharePoint 2010 came from.  These tips are really aimed at the person or persons who are planning a SharePoint deployment.  Hopefully a few of these tips will provide you with a bit of wisdom and guidance to help you be successful.

• Know why you are deploying SharePoint.  This may seem obvious, but I have seen many organizations decide that they need to deploy SharePoint just because they hear everyone else is doing it.  Before you even begin to think about deploying SharePoint, make sure you fully understand the products capabilities and licensing models.  Ensure that you have a good business reason for deploying SharePoint.  Don’t start out with SharePoint as your solution and then go looking for a problem that it can fill.  I believe that every organization can benefit greatly from SharePoint, however, you need to identify why YOUR organization is going to use SharePoint.
• Don’t be an army of one.  A single person or department (…I’m looking at you in IT) should not take on a SharePoint deployment alone.  If you want a successful, well adopted implementation, you need to include representation across the user base during planning and governance.  Implementing a SharePoint steering committee is a very good practice. For the best outcome, have representation from different departments within the organization invited to be on the steering committee.  I also recommend rotating people in and out of the steering committee to keep fresh ideas and perspectives.
• Choose the right tool.  SharePoint is like a hammer. It is a great tool that helps you accomplish specific tasks.  The key is to know when you really need a screwdriver.  By reviewing the SharePoint documentation and overviews you will have a better understanding of when SharePoint should be used and when it shouldn’t.
• A single conversation with a wise man is better than ten years of study.  If you or your co-workers are not experienced with SharePoint deployments, ask for help!  There are many great Microsoft partners that have deep SharePoint expertise.  SharePoint is not just about technology but it is also about business processes.  Working with an experienced SharePoint team will give your organization a much better chance of fully utilizing your SharePoint environment and seeing higher user adoption.
• Have a plan beyond deployment. Having a healthy SharePoint environment requires more than just a good deployment.  Installing the software in a properly architected server farm is just the beginning.  A healthy SharePoint environment can only stay that way if there is a good governance plan in place.  This plan outlines the who, what and why of your SharePoint Farm.   Who is the project sponsor?  Who has final authority over policies?  Who is the SharePoint administrators?  Who has access to SharePoint?  What is the usage policy for SharePoint?  What features will be enabled in the environment?  Why is SharePoint being used in the organization?   I could keep going on and on.  A solid governance plan will help end user adoption and will ensure that the SharePoint farm is being managed and used as intended.
• The tortoise wins the race. Quickly pushing out a SharePoint environment to an organization will almost certainly fail.  Users do not like change and they are even less likely to use SharePoint if they feel forced.  Start with a small SharePoint project and get buy in from those who will be impacted.  Over time you can slowly bring on new features or users to the environment, building on the success of the previous project.
• Empower the user.  SharePoint enables a distributed management system for sites and content.  By empowering the user to create their own sites, libraries, lists and workflows you will see an increase in productivity and employee satisfaction.  Users who constantly have to wait for a SharePoint administrator to build everything will be frustrated an unhappy.  Empowering users doesn’t mean that you let them run wild and do anything they want.  A well defined governance plan working in concert with SharePoint security and quota controls can make a user feel empowered to build solutions to their own issues. 
• KISS principle.  The biggest obstacle when deploying and managing SharePoint is controlling complexity.  Focus on the out of the box capabilities and resist the urge to install a bunch of 3rd party solutions (or develop your own).  Don’t run past your current knowledge or skill set.  Take your time and learn about all of the features of SharePoint.  You might be surprised at what you can do with lists, libraries, web parts and SharePoint Designer.   Of course there are always exceptions and in some cases the whole reason for deploying SharePoint is to support a 3rd party solution or another product (such as Team Foundation server or Project Server).
• Don’t reinvent the wheel.  You may run across a situation where you need to extend SharePoint for a specific task or requirement.  Before you jump into Visual Studio I recommend that you do a bit of research to see if the solution you require has already been built.  Purchasing a pre-built solution can be less costly than trying to build your own.  A pre-built solution you purchase will also most likely have some sort of support option in case you run into an issue.
• Play in the sandbox. Developing custom solutions in SharePoint 2007 was a dangerous affair. The first issue is that every custom solution had to be deployed at the farm level.  This means that if a single custom solution starts to misbehave it has the capability to impact performance and stability of the entire SharePoint farm.  The second issue is that Visual Studio didn’t provide an easy way to build solution packages (.wsp) so many people resorted to manually copying and deploying files to a SharePoint server.  Both of these situations can really cause a mess in a production SharePoint environment.  With SharePoint 2010 there is a new feature called sandbox solutions.  A sandbox solution is built with Visual Studio 2010 and deployed as a SharePoint solution package (.wsp).  The difference is that the sandbox solution runs within a separate controlled process space on the SharePoint servers.  If the solution misbehaves then it only affects itself and not the whole farm.  A good rule of thumb is that if you are going to build customizations, build sandboxed solutions.  In some cases a solution can only be built as a farm solution.  In those circumstances make sure you carefully test the solution before deploying.  One last note, only sandbox solutions are allowed to be deployed in SharePoint Online. 
• If it is not a solution, it is a problem.  In the previous bullet point I mentioned SharePoint solution packages.  Any custom developed solution should only be deployed to SharePoint if it is in a solution package.  A solution package contains all of the solution’s files along with a manifest that directs SharePoint on how to install the files.  This allows for easy deployment  and retraction of your solution across one or more SharePoint farms.  If you don’t use a SharePoint solution package for your customizations then you will quickly find that supporting your environment becomes a nightmarish task.  Don’t be that guy (or girl) that just copies custom solution files directly to the SharePoint servers and NEVER manually modify the web.config file.
• Prevent frustration with education. People, in general, resist change.  People despise change if they feel that they cannot understand the new “thing”.  In this case the thing is SharePoint.  A solid training plan when well executed will drive adoption to the new SharePoint environment you are deploying.  Training doesn’t have to be an expensive proposition. There are many free online resources such as webcasts, videos and hands on labs that your team can utilize.  Some of my previous customers have taken on a train the trainer style of education.  They select a few people who are excited about SharePoint and send them to formal training.  When those people return they host classroom style training for the other employees.  This helps control costs while building up a key set of employees who are experts in the usage and management of SharePoint.
• You can lead a horse to water.  You will never be able to force people to use SharePoint.  The more you insist, the more they will resist.  The key is to have an active marketing effort internal to your organization about SharePoint.  Demo the features and capabilities.  Show people how they can accomplish tasks more quickly and become more productive.  When people get excited and are not forced into a solution they seem to adopt it with less resistance.

Do you have tips for those starting out with SharePoint?  Let’s hear them in the comments section!

SharePoint Resources

I have compiled a selection of documentation, case studies, how-to articles and training on my SharePoint resources page. 

SQL Server 2012 removed the system stored procedure sp_dboptions.   This is a required stored procedure for installing SharePoint 2010 RTM.  Service pack 1 for SharePoint 2010 does eliminate the dependency for the sp_dboptions stored procedure.

To install SharePoint 2010 on SQL 2012 you will need to ensure that you have the SharePoint 2010 with Service Pack 1 installer or you will need to slipstream the service pack so that it is included in the RTM build of SharePoint.

Check out the following blog post if you need instructions on how to slipstream a service pack into the SharePoint 2010 RTM.

http://blogs.msdn.com/b/ronalg/archive/2011/07/11/slipstream-sharepoint-2010-sp1-and-language-packs-w-sp1-into-rtm.aspx

Note:  Official support of SharePoint 2010 on SQL 2012 has not been announced by Microsoft.

The conference will include Keynote presentations along with 3 different session tracks; developer, infrastructure and business user.

Sponsor’s this year include Microsoft, ICC, Quest Software, KnowledgeLake, Nintex and CriticalPath Training.

Make sure you register soon to secure your spot!  This event will fill to capacity quick!

For more information visit: http://iccsharepoint.com/

The very first and most important concept that I didn’t mention in the previous post is that all custom development for SharePoint should be packaged as a SharePoint solution.  You should never deploy customizations to SharePoint by copying source files to locations on the SharePoint server’s file system.  This includes image files, custom web services, and web.config modifications. You must learn what a solution file is and how to create one before you can be successful in building customizations or branding for SharePoint.

There are two different types of SharePoint solutions that can be built; farm solutions and sandboxed solutions. My recommendation is to always build sandboxed solutions if possible. Sandboxed solutions provide protection against misbehaving code and also allows Site Collection owners to deploy the solutions.  Sandboxed solutions are also  the only type of solution allowed to be deployed in SharePoint Online.

In some cases the type of customization you wish to make to an on-premises SharePoint deployment can only be accomplished with a farm solution. In those situations you will want to test, test and re-test all of your code in the solution prior to deployment.  A simple mistake in a farm solution has the potential to impact the stability of the full SharePoint farm.

In the original article I made some recommendations for a developer environment and they still are valid today. The developers should all have a 64 bit Windows 7 computer with at least 4GB of RAM (8GB recommended).  On that computer you will install SharePoint Foundation 2010, Visual Studio 2010 and SharePoint Designer 2010.   Each developer, including graphic designers, should have this exact same build.   Now, in some cases you may need to install the Standard or Enterprise version of SharePoint if your solution requires APIs that are not available in Foundation.

I also recommended the use of Team Foundation server for managing source code and for tracking work items, bugs and issues.  If you choose not to use Team Foundation server you will need at least some sort of shared source control system that integrates well with Visual Studio.  If it doesn’t integrate with Visual Studio then you are just greatly reducing the productivity of your developers. 

A good shared source control system is key for any successful team development project!

The lead developer should be responsible for setting up the project structure and ensuring that every person on the development team, including graphic designers, are all working out of the same shared source control system.  The team development process should occur just like any other .NET development effort.

One big hang-up I think happens when people start building up SharePoint development skills is figuring out how to do the Dev to Test to Production move when working with SharePoint in a team environment. The first thing is to ensure that every developer is working in their own completely isolated development environment (hence the reason for separate Windows 7 development systems).  This is important so that developers are not stepping on each other while trying to debug their code. Having developers share a single SharePoint environment will lead to frustration and potential mistakes.

When it comes time to test the full solution, the lead developer (or test lead) will get the latest source code for the project from Team Foundation Server (or whatever source control system you are using) and do a build.  That build will generate a SharePoint solution package that will then be copied to the SharePoint test farm and deployed.  The testers can then proceed to take the necessary actions to verify that the custom solution is working as intended.  Any bugs or issues can be logged and sent back to the developers.

Developers may wish to do basic integration testing from time to time.  At any time the developers are able to retrieve the latest code from source control so they can do a quick integration test on their local dev machines prior to the real test process on the SharePoint test farm.

Another key concept that must be understood is that there is a big difference between content and customizations (or code).  Customizations, or better known as SharePoint solutions, should go through a dev, test and then production process just like any other development project. Content should not. Content should be built in the production environment and possibly follow an approval workflow process in that environment.  Think of content as any list, library, images, text, documents or other data that is not directly used by your custom solution.

Everything isn’t just black and white.  There are times when content should be deployed as part of a solution.  Usually this content will be Office document templates, images, or other files that are in direct support of the solution itself.  A good example of a solution with built in content is the Productivity Hub.  A good rule is that if the content will be created, edited or maintained by a SharePoint content editor then you should probably not include the content as part of a SharePoint solution.  You should also not include that content as part of a dev, test, production deployment cycle.

Document libraries and lists may not be considered just content if your solution directly relies on those items. For example, your solution may use a custom SharePoint list for storing information.  In this case, the list is not just content but a required part of your solution. You will need to ensure that your custom solution has a way to automatically provision that list when the solution package is installed and activated.  Never rely on a person to manually create supporting content as part of your solution install process.

SharePoint Designer is a great tool to assist in the development process. Keep in mind that when you use SharePoint Designer you are just creating content. Using SharePoint Designer to modify a master page or to create a workflow process is just creating content within a SharePoint site collection.  You should always copy or export the work you do in SharePoint Designer and place it into your Visual Studio project so that it is packaged as part of your SharePoint solution.  Remember that by having the customizations in a SharePoint solution package you can easily deploy it to other SharePoint farms.  Solution packages are reusable, content generally is not.

You might be wondering, if I build all of my content in my production site, how will I ever use that in my test or dev environments?  You will do site collection backups of the portion of your production site you need to work with in the test and dev environment and then restore it into the appropriate environment.   I usually look at it like this:  solutions move from dev to test to production.  Content moves from production to test and dev.

To wrap up, below are a few tips that I feel make SharePoint Development a bit easier:

• Always use Visual Studio 2010 to build custom SharePoint solutions.
• Always use a shared source control system.  I recommend Team Foundation Server.
• Never share a development environment with multiple developers. Shared development environments can cause issues which will greatly reduce the productivity of the developers.
• Never manually deploy files to SharePoint servers; always deploy your customizations using a solution package.
• SharePoint Designer just creates content. If you use SharePoint Designer, think about how it will impact your ability to deploy your solution.
• Don’t break your development efforts up into a bunch of little Visual Studio projects unless it makes good sense.  One solution package is easier to manage and deploy than several.
• Content should always be created where it will live. Don’t try to run content through the dev, test, and production deployment cycle.
• Use the shared test environment to ensure that all of the solutions you build work properly and integrate well with each other.
• Copy site collections from the production to the test server if you need that content to test your custom solutions.
• Limit the number of people who have the ability to deploy a custom solution build to the test farm. 
• Content is not code, don’t try to manage it the same way.
• Branding should always be placed in a SharePoint solution package so it can be reused.

Do you have your own tips for SharePoint team development?  Let us know in the comments section below!

Post updated 1/22/2012 to include the office365.com email address as mentioned by Loryan Strant in the comments.

With an iPad device running an operating system prior to 5.0.1 the user will experience issues when trying to utilize some of the features included in Office 365. These issues occurred because the Safari browser did not fully support HTML standards, including the contenteditable property. The lack of full HTML standards caused issues with many web applications including SharePoint Online, and in particular the ability to use the Office Web Apps feature to view and edit Office documents in the browser.

With iOS 5.0.1 we have some good news, Apple updated the Safari browser to support the contenteditable property! This means that you can now more fully take advantage of the features included in Office 365 with your iPad device. To ensure you have the best experience, first check to see if you are running version 5.0.1 or higher on your iPad device.

Checking the iOS version on the iPad

· Click on the iPad’s “Settings” icon

· Select “General” and then then “About”

· Look at the Version number.

If you see that you are not running version 5.0.1 or higher, you will want to update the operating system on your iPad.

Updating to a newer version of iOS

Over the air or wifi update

· Under “Settings” and “General,” check to see if you have the “Software Update” option. If not, go to the next section to find out how to use iTunes to update your iOS.

Using iTunes

· Install iTunes on your computer if you have not already done so.

· Connect the iPad to the computer via USB.

· iTunes should detect the iPad so that you can select the device in the iTunes menu. Select the iPad under “Devices” and then “Check for Updates.”

After you have verified that you have at least iOS 5.0.1 installed on your device, you can begin configuring the iPad to work with Office 365. This next section will describe how to configure your iPad to use Exchange Online.

Exchange Online with the iPad

There are basically two ways to access your mail, calendar, and contact information on your iPad. Using Outlook Web App (OWA) HTTPS method, and/or ActiveSync.

Using Outlook Web App (OWA) – HTTPS method

· To use Outlook Web App (OWA) on the iPad, simply open the safari browser and connect to OWA via the URL http://mail.office365.com.

· Note that when you use OWA on the iPad’s Safari browser, you are using OWA Light. So features such as “drag-and-drop” do not work. For a richer client experience, you can choose to use the iPad’s iMessage and iCalendar applications (see next section). For a detailed discussion on the differences between Exchange 2010 OWA versus OWA light, please see Ilse Van Criekinge’s blog on Technet: http://blogs.technet.com/b/ilvancri/archive/2010/04/07/exchange-2010-owa-versus-owa-light.aspx

Using iMessage and iCalendar – ActiveSync method

· Go to “Settings” and then select “Mail, Contacts, Calendars” and choose to “Add Account…”

· Select “Microsoft Exchange” when prompted for the type of email service to add.

· Enter your Office 365 login credentials and then click on the “Next” button (top right).

· Select what items you would like to synchronize with your iPad by sliding the On/Off switch. We will see how we can further customize this later. Click on the “Save” button (top right) when you are done selecting your synchronization options.

· Note that you can add multiple accounts from difference service providers. All the accounts that you add appear in the list under “Settings,” “Mail, Contacts, Calendars…”

· By selecting one of the accounts that you have configured, you can further refine your synchronization options. In the screenshot below, you can see that I can choose the number of days of mail I would like to synchronize, as well as the folders to synchronize. This is also the location where you can choose to delete the account.

· You are now ready to use the iPad’s iMessage and iCalendar applications to access Exchange Online. The “Mail” application icon will have a red bubble floating on top of it to indicate the number of total unread items from all your mail service providers.

· When you select the “iMail” application, you will be presented with the following screen. All the Inboxes from all your service providers are organized at the top. If you want to drill down by the other folders within each specific account, these are organized at the bottom.

· For Calendaring, the iCalendar application, like the iMessage application, shows the number of items in your calendar.

· When you open iCalendar, you will be able to browse your calendar items and the details in a day-planner type User Interface.

· When creating calendar items, hold down on the time slot and when the item details appear, enter all the information. Then select the “Calendar” option in the same dialog box to select the calendar service to synchronize the new item back to. In this case, you see that Exchange Online is one of the options.

· Click on “Done” (top right) when you are ready to save the new calendar item.

· Calendar reminders pops-up and you can then choose to “Close” the reminder or “View” to view the details, where you can then choose to select “Maybe” (tentative), “Decline,” or “Accept” the meeting.

· One last note about iCalendar. It seems like even though the iPad uses location services to update the device’s time zone, this does not seem to be reflected within the iCalendar application itself.

· Contacts – The Contacts application allows you to access all the contacts that have been synchronized via ActiveSync. You can view “All Contacts,” Search for contacts, or select the “Groups” (top left) tab that would allow you to view contacts based on which service account synchronized that information.

· Here are screenshots of the “Groups” view in Contacts.

Managing the iPad – Details, Status, Remote Wipe

A synched iPad appears in the “Options” settings in your Outlook Web App (OWA).

· Log in to https://portal.microsoftonline.com and go to Outlook. Alternatively, you can go directly to the Outlook Web App (OWA) URL http://mail.office365.com.

· Side note – for a full list of URLs used by Office 365, please refer to this TechNet article: http://technet.microsoft.com/en-us/library/cc745934.aspx

· Once you are in OWA, click on the “Options” menu item at the top right, and then select “See All Options.”

· The iPad will be under the “Phone” section (as seen below).

· Some of the management capabilities for the iPad include the ability to see the status and Last Sync Time,

· More details

Optional – Determine Exchange Online Settings if you need to configure mail via the POP/SMTP/IMAP protocols (not specific to iPad, applicable to any device supporting these protocols)

· If for whatever reason you need to configure your device to retrieve mail through POP/SMTP/IMAP instead of using ActiveSync, you can do so.

· Log in to https://portal.microsoftonline.com and go to Outlook. Alternatively, you can go directly to the Outlook Web App (OWA) URL http://mail.office365.com.  

· Side note – for a full list of URLs used by Office 365, please refer to this TechNet article: http://technet.microsoft.com/en-us/library/cc745934.aspx

· Once you are in OWA, click on the “Options” menu item at the top right, and then select “See All Options.”

· Under the “Account” category, click on the “Settings for POP, IMAP, and SMTP access…” link.

· Take note of all the settings information. Your device will prompt you for these settings when you set up POP/SMTP/IMAP.

SharePoint Online

Accessing SharePoint collections from the iPad is like accessing any website. However, unlike just any website, the most important things we need to ensure for SharePoint Online are:

· The CSS Ribbon in SharePoint is rendered correctly, and

· Does Office Web Apps work

SharePoint Ribbon

When browsing SharePoint site collections, the Ribbon, such as the one that provides “Document” and “Library” functions, work as expected.

Office Web Apps

· Excel – Excel “View in the browser” and “Edit in the browser” functions work, including the co-authoring capabilities

· Word – Word “View in the browser” and “Edit in the browser” functions work as well. When you open the document, you may be prompted to “download and install Silverlight.” Ignore this request as you would not be able to install Silverlight on the iPad. There is no consequence to not installing Silverlight. As the message indicates, Silverlight would improve the speed in which documents open. Prior to iOS 5.0.1, one of the symptoms you will encounter is that the keypad would not come up, thereby making it impossible for you to edit the Word document in the browser. This now works correctly with iOS 5.0.1. Co-authoring in Word requires the Word client and cannot be done in the browser.

· PowerPoint – You can view PowerPoint slides, but editing the slides in Safari is extremely limited at this time. You can duplicate and delete slides as well as add notes. However, you are not able to insert pictures and graphics.

Lync

The Lync client for iPad and iPhone has been released to the Apple App Store. To use Lync on the iPad, you would need to:

1. Go to the Apple App Store to download and install the Lync Client for iPad (note that there is a different one for the iPhone)

2. Have an account on a Lync Server

Once connected to your Lync server, you can configure simultaneous ring, your status (synchronized with your Exchange Online calendar if so desired), as well as logging.

The phone number you configure in Lync will be used for voice calls. For example, if you choose to “Return a Call” from within Lync, the Lync Server will bridge your number with the number you wish to call. At that point, your phone will ring as it gets connected to the number you wish to contact. If you have caller id, you will see that the incoming call is coming from your Lync server as it bridges the call for you.

The core capability of the Lync iPad Client is to provide you with Instant Messaging (IM) and Presence capabilities

You can view your Exchange Online calendar events from within the Lync iPad client.

Tips and Tricks for using Apple iPad with Office 365

· Clear out the Safari browser’s data cache and cookies if you receive any errors when you try to access Office Web Apps in SharePoint Online. Go to “Settings” and then select “Safari.”

· The Safari browser does not display scroll bars in certain circumstances. This can cause some confusion to end users since there are no visual cues to indicate that they can scroll a section of a page.

· The Safari browser does not support single finger scrolling in certain circumstances. If you are unable to scroll a section of a page, try using 2 fingers to scroll.

Summary

· iOS 5.0.1 updated the HTML standards in Safari that allows it to properly work with Office 365.

· You can use your iPad with Exchange Online to have access to your email, calendar, contacts and tasks.

· You can use your iPad with SharePoint Online to access and view content. You can also view and make light editing to Word, Excel and PowerPoint documents using Office Web Apps.

· You can keep in touch with your colleagues by using the Lync client for the iPad and Lync Online.

· Office 365 was not designed for a touch first experience, however, with a combination of built in iOS applications and new Office productivity apps such as One Note and Lync you will have access to all of your content stored in Office 365.

This event begins at 8:30am and concludes at 3:10pm.

Topics include:

• Six Pillars of SharePoint 2010
• Governance
• BI with Performance Point Services
• Tools to assist with migration
• Document and Image capture for SharePoint
• Visio Services and InfoPath
• Enhancing SharePoint Workflow

Keynotes and presentations will be delivered by:

• Microsoft
• Nintex
• AvePoint
• KnowledgeLake
• Tandem Solution
• SIS

Lunch will be provided and parking is free.

Download the flyer for more details and then make sure you register ASAP.

• as an extranet for collaboration with vendors, partners and customers.
• as a public facing web site.
• as an enterprise search platform for your intranet, extranet and public facing sites.

Guarantee you spot by registering today!

Session 1: SharePoint Extranets

Date: Tuesday, January 24, 2012 | 11:00 AM – 12:00PM PT

Extranets connect organizations to employees, partners, vendors and customers and provide a secure, engaging and personalized interaction with people, information, applications and business processes. With the proper strategy in place, extranets can provide a strong competitive advantage, reduce costs and ultimately foster business growth.

Perficient”s SharePoint Extranets Webinar is a must attend event for organizations looking to:

• Reduce supply chain inefficiencies
• Interact with your loyal customer base
• Extend customer self service strategies
• Share business resources with partners
• Enable mobile capabilities
• Extend remote employee access

Join Perficient”s SharePoint experts for this informative webinar to discuss extranet capabilities, best practices, and use cases. Register today!

These courses are delivered live and are approximately 90 minutes long. Make sure you register soon and mark your calendars for these great training sessions!

End User Tips n” Tricks on Office 365

This session gives users an overview of Office 365 while highlighting its most exciting features. Users can watch a live instructor showcase a tip or feature every couple of minutes, providing a broad and real-world understanding of what the platform can do. Topics include:

- Email Tips with Exchange online
- Collaborate with SharePoint Online
- Getting the most out of Lync Online

Training Date:
Thursday, February 16, 2012, 11:00 A.M. 12:30 P.M. Pacific Time
Register for this session

End User Tips n” Tricks on Office 365: Focus on SharePoint Online

If you”ve been wondering what SharePoint Online is and how it can impact your organization and the role it can play in your employees” productivity experience, this is a great training session to attend. Topics include:

- Collaborating with team sites
- Simplifying document access through Office Web Apps
- Coauthoring content using Microsoft Office and SharePoint Online
- Automating business processes
- Improving communication with Lync Online integration

Training Date:
Friday, March 16, 2012, 11:00 A.M. 12:30 P.M. Pacific Time 
Register for this session

End User Tips n” Tricks on Office 365: Getting the most out of Exchange Online with Email

Exchange Online can be a great tool for business and your organization. This session provides insight into the role it can play in your productivity and the impact it can have on your organization. Topics include:

- Organizing your Inbox in Outlook 2010
- Connecting with your contacts
- Accessing your mail anywhere on virtually any device
- Keeping track of your day in Outlook 2010

Training Dates:

Friday, January 13, 2012, 10:00 A.M. 11:30 A.M. Pacific Time
Register for this session

Wednesday, April 18, 2012, 10:00 A.M. 11:30 A.M. Pacific Time
Register for this session