Friday, November 30, 2012

Sharepoint 2013 videos


Watch or download the following content for information about how to plan for, install, or manage SharePoint 2013.

Content Description

Video (play button) icon
Video: Social computing overview in SharePoint Server 2013 View a video of enterprise social computing and collaboration in SharePoint 2013, featuring Bill Baer, SharePoint Senior Product Marketing Manager.

Video (play button) icon
SharePoint 2013 training for IT pros Find IT pro-focused how-to training and walkthrough videos with this interactive course about SharePoint 2013 including changes and new features for search, social, plus deployment and performance/scalability.

How to enable the audit log in SharePoint 2013

To enable the audit log by using Central Administration

·         On the Central Administration home page,
·         In the Application Management section,
·         Click Manage service applications.
·         Select the Secure Store service application.
·         On the ribbon, click Properties.
·         From the Enable Audit section,
·         Click to select the Audit log enabled box.
·         To change the number of days that entries will be purged from the audit log file, specify a number in days in the Days until Purge field.
·         The default value is 30 days.
·         Click OK.

Configure audit settings for a site collection

Please use the following link in which Microsoft has given a very detailed description that references each and every minor point regarding audit settings:

It consists of:
·         Auditing event information
·         Trimming the audit logs (new enhancements in SP2010 and SP2013 as compare to earlier versions)
·         Configure audit log trimming
·         Configure events to audit


View audit log reports
Following link will help you to understand the following points:
·         Events available for audit log reports
·         Available audit log reports
·         View audit log reports

Migrating From SharePoint 2007 to SharePoint 2013




I read a very good article on Dan Holme's Viewpoint on SharePoint Blog on SharePoint 2007 to SharePoint 2013 migration, the most important thing I loved is we can SKIP SharePoint 2010 migration from this process


If you are currently running Microsoft Office SharePoint Server 2007 (MOSS 2007) or Windows SharePoint Services v3 (WSSv3), you might be struggling to identify your roadmap to newer versions of SharePoint. In this first of a two-part article, I will share with you the business and technical reasons why my roadmap to SharePoint 2013 does not stop at SharePoint 2010.

This migration is a “skip it” migration. Just say “no” to SharePoint 2010.
But first, let me send you greetings from beautiful Melbourne, Australia! I’ve just finished participating in the SHARE event, which focuses on the business-side of SharePoint. This is the last stop in a round-the-world epic journey, which started at home in Maui three weeks ago, went to the SharePoint Conference in Vegas, then on to SharePoint Connections in Amsterdam, SharePoint Evolves in London, and then after a super-long flight from London via Sydney, to Melbourne. Next, I head home for a whole week before SharePoint Saturday Honolulu (which is actually on a Friday, Pearl Harbor Day in fact) and SharePoint 360 Live! in Orlando. Whew! I won’t see home again until 2013.
Now, back to migration… specifically from 2007 to 2010.

Do Not Stop at SharePoint 2010
One of the questions I get regularly at events these days comes from customers who have MOSS 2007 or WSSv3 and are developing their roadmaps forward. Many (or most) of my customers in this situation are giving serious thought to skipping SharePoint 2010 altogether, and that is certainly my guidance to you: Move straight to SharePoint 2013.
Do not stop at SharePoint 2010. Do not waste your time or money.
The current needs—the current workloads, teams, and projects—that you are supporting on MOSS 2007 will migrate to SharePoint 2013 just the same as they would to SharePoint 2010. There’s really nothing that you can do on SharePoint 2010 that you can’t do—a little or a lot better—on SharePoint 2013.
But by moving to SharePoint 2013, you’re going to be much better equipped to support your future needs—and by “future” I mean the needs your business already has “queued up” today. Because the odds are that your business is going to require functionality that can only be supported by SharePoint 2013. This includes business workloads that fall into the “big bet” categories of SharePoint 2013—the features that Microsoft invested heavily in, including social, search, business intelligence, and web content management for public-facing websites, intranets, and extranets. And, it’s likely your business currently needs—or will soon need—the ability to support workloads on mobile devices, on non-Windows devices, or on browsers other than Internet Explorer.

Consider SharePoint Training and End-User Adoption
You also must consider training and user adoption. If you move users from 2007 to 2010, that’s going to require training—a significant amount of training, in fact. SharePoint 2010 has rough edges in discoverability, and gaps in usability, that were solved in SharePoint 2013. That means that your users will require more training going from 2007 to 2010, than from 2007 to 2013. You’re also going to have to train users twice. You’ll have to train them to use 2010, and then when you do finally move to SharePoint 2013, you will have to train them again because the user interface and user experience is quite different in each version of SharePoint.

Consider Your SharePoint Customizations
From a purely technical perspective, the hard part of your migration from 2007 to 2010 or 2013 is the evaluation of your 2007 customizations. You must look at code-based customizations, whether custom-built, in-house code, or third party tools, add-ins, or web parts, and determine what will and won’t work in the target version of SharePoint.

The odds are pretty good that some of your customizations won’t work, and you will have to decide whether the functionality those customizations provide is still necessary, or whether the customization can be left behind. If the customization is necessary, but incompatible, you will have to determine the cost and effort required to remediate the customization so that it works with your target version.
The effort I’ve just described is the same whether you are going to 2010 or 2013. And, in fact, it’s extremely likely that the remediation you undertake will result in the customization being ready for either version.
It’s not the target version of SharePoint that is the issue. It is the mess you have in your 2007 environment that is the real problem. Once you solve that, you are ready to migrate to either 2010 or 2013.


Exam 70-665

PRO: Microsoft Lync Server 2010, Administrator

Published:March 29, 2011
Language(s):English, French, German, Japanese, Spanish, Portuguese (Brazil)
Audience(s):IT Professionals
Technology:Microsoft Lync Server 2010
Type:Non-Proctored Exam
Preparing for an Exam
The Microsoft Certification website and this preparation guide contain a variety of resources to help you prepare for an exam.Preparing for and Taking an Exam — FAQ provides answers to frequently asked questions about exam registration ,preparation,scoring ,and policies , including:
  • The most effective way to prepare to take an exam.
  • The relationship between Microsoft training materials and exam content.
  • Microsoft policy concerning the incorporation of service pack and revision updates into exam content.
  • Exam question types and formats.
  • Exam time limits and number of questions asked.
We recommend that you review this preparation guide in its entirety and familiarize yourself with the FAQs and resources on the Microsoft Certification website before you schedule your exam.
Audience Profile
Candidates for this exam are IT and telecommunications professionals who design and plan solutions for unified communications. Candidates should have a minimum of two years of experience with Microsoft Lync Server 2010, Office Communications Server 2007, or Office Communications Server 2007 R2 and related technologies. In addition, candidates should be proficient with Windows Server Active Directory 2008, data networks, and telecommunications components that support the configuration of Communications Server 2010.

Candidates should know how to design and plan solutions for Lync Server 2010 for end users, endpoint devices, telephony, audio/video and web conferences, security, and high availability. Candidates should be familiar with the requirements for integrating Lync Server 2010 with Microsoft Exchange Unified Messaging.
Credit Toward CertificationExam 70-665: PRO: Microsoft Lync Server 2010, Administrator: counts as credit toward the following certification(s):
Microsoft Certified IT Professional (MCITP): Microsoft Lync Server 2010 Administrator
Note This preparation guide is subject to change at any time without prior notice and at the sole discretion of Microsoft. Microsoft exams might include adaptive testing technology and simulation items. Microsoft does not identify the format in which exams are presented. Please use this preparation guide to prepare for the exam, regardless of its format.

Exam 70-664

TS: Microsoft Lync Server 2010, Configuring

Published:March 15, 2011
Language(s):English, French, German, Japanese, Portuguese (Brazil), Chinese (Simplified)
Audience(s):IT Professionals
Technology:Microsoft Lync Server 2010
Type:Proctored Exam
Preparing for an Exam
The Microsoft Certification website and this preparation guide contain a variety of resources to help you prepare for an exam.Preparing for and Taking an Exam — FAQ provides answers to frequently asked questions about exam registration,preparationscoring, and policies, including:
  • The most effective way to prepare to take an exam.
  • The relationship between Microsoft training materials and exam content.
  • Microsoft policy concerning the incorporation of service pack and revision updates into exam content.
  • Exam question types and formats.
  • Exam time limits and number of questions asked.
We recommend that you review this preparation guide in its entirety and familiarize yourself with the FAQs and resources on the Microsoft Certification website before you schedule your exam.
Audience Profile
Candidates are IT or telecommunications professionals who have experience with complex deployments. They should know how to deploy and configure Lync Server 2010 for end users, endpoint devices, telephony, audio/video and web conferences, security, and high availability. The candidate should also know how to monitor and troubleshoot Lync Server 2010 using Microsoft tools. In addition, candidates should have experience with Windows Server Active Directory 2010 and network and telecommunication components that support the configuration of Lync Server 2010.
Credit Toward CertificationWhen you pass Exam 70-664: TS: Microsoft Lync Server 2010, Configuring, you complete the requirements for the following certification(s):
Microsoft Certified Technology Specialist (MCTS): Microsoft Lync Server 2010, Configuration
Exam 70-664: TS: Microsoft Lync Server 2010, Configuring: counts as credit toward the following certification(s):
Microsoft Certified IT Professional (MCITP): Microsoft Lync Server 2010 Administrator
Note This preparation guide is subject to change at any time without prior notice and at the sole discretion of Microsoft. Microsoft exams might include adaptive testing technology and simulation items. Microsoft does not identify the format in which exams are presented. Please use this preparation guide to prepare for the exam, regardless of its format.

Tuesday, November 6, 2012

Use managed paths with host-named site collections

SharePoint Server 2010 adds support for managed paths with host-named site collections. Hosters can provide multiple site collections to the same customer with each site collection sharing the customer’s unique host name but differentiated by the URL path after the host name.


Managed paths for host-named site collections are different from managed paths for path-based site collections. Managed paths for host-named site collections do not apply to path-based site collections; nor do managed paths for path-based site collections apply to host-named site collections. Managed paths created for host-named site collections are available to all host-named site collections within the farm regardless of which Web application the host-named site collection is in. You must create a root host-named site collection for a host name before you can create a managed path host-named site collection for that host name.

You can create a managed path for use with host-named site collections by using the Windows PowerShell New-SPManagedPath cmdlet with the -HostHeader parameter, as shown in the following example:

New-SPManagedPath pathname -HostHeader

A host-named site collection created at a managed path is shown in the following example:
 
New-SPSite http://host.header.site.url/pathname/sitename -OwnerAlias DOMAIN\username -HostHeaderWebApplication http://servername

Remove an existing managed path use by using the Windows PowerShellRemove-SPManagedPath cmdlet, as shown in the following example:
 
Remove-SPManagedPath pathname -HostHeader

Programmatically create a host-named site collection

In addition to using the Windows PowerShell to create host-named sites, you can use the SharePoint Server 2010 object model. The following code sample creates the host-named site collection with the URL http://host.header.site.url in the SharePoint Server 2010 Web application with the URL http://servername:


SPWebApplication webApp = SPWebApplication.Lookup(new
Uri("http://servername"));
SPSiteCollection sites = webApp.Sites;
SPSite Site = null;
Site = sites.Add("http://hoster.contoso.com", "Site_Title",
"Site_Description", 1033, "STS#0", "contoso\owner",
"Owner_Display_Name", "Owner_Email", "contoso\secondaryowner,
"Secondary_Owner_Display_Name", "Secondary_Owner_Email", true);

SharePoint Server 2010 ships with a set of Web services for various user and administrative tasks. One of these administrative tasks is creating a new site collection. The CreateSite Web service method does not support the creation of host-named site collections. A workaround for this issue is to write a Web service that wraps the API sample code.

Configure SSL for host-named site collections

In hosting scenarios, hosters can configure a single Web application with SSL and then create multiple host-named site collections within that Web application. To browse to a site over SSL, a server certificate has to be installed and assigned to the IIS Web site. Each host-named site collection in a Web application will share the single server certificate assigned to the IIS Web site.


Hosters need to acquire a wildcard certificate or subject alternate name certificate and then use a host-named site collection URL policy that matches that certificate. For example, if a hoster acquires a *.contoso.com wildcard certificate, the hoster has to generate host-named site collection URLs such as https://site1.contoso.com, https://site2.contoso.com, and so on, to enable these sites to pass browser SSL validation. However, if customers require unique second-level domain names for their sites, the hoster has to create multiple Web applications rather than multiple host-named site collections.

To configure SSL for host-named site collections, enable SSL when creating the Web application. This will create an IIS Web site with an SSL binding instead of an HTTP binding. After the Web application is created, open IIS Manager and assign a certificate to that SSL binding. You can then create site collections in that Web application.

Ref: http://technet.microsoft.com/en-us/library/cc424952.aspx#section7

Create a host-named site collection

You must use Windows PowerShell to create a host-named site collection. You cannot use the SharePoint Server 2010 Central Administration Web application to create a host-named site collection, but you can use Central Administration to manage the site collection after you have created it.
You can create a host-named site collection by using the Windows PowerShell New-SPSite cmdlet with the -HostHeaderWebApplication parameter, as shown in the following example:


1.      To create a host-named site collection using Windows PowerShell, verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2.      On the Start menu, click All Programs.
3.      Click Microsoft SharePoint 2010 Products.
4.      Click SharePoint 2010 Management Shell.
5.      From the Windows PowerShell command prompt (that is, PS C:\>), type the following:

New-SPSite “http://portal.contoso.com” -HostHeaderWebApplication “http://HNSC01.contoso.com” -Name “Portal” -Description “Customer portal” -OwnerAlias “contoso\administrator” -language 1033 -Template “STS#0”

This creates a host-named site collection with the URL http://host.header.site.url in the SharePoint Server 2010 Web application with the URL http://servername.

Ref: http://technet.microsoft.com/en-us/library/cc424952.aspx#section3

Monday, November 5, 2012

Office 2013, SharePoint 2013 and Exchange 2013 RTM; Office 365 Update Due Nov.

Microsoft's next-generation Office solutions and other "2013"-branded products have reached the release-to-manufacturing (RTM) stage, the company announced on Thursday.
The RTM milestone indicates that the products are complete and close to being available on the market for purchase. However, it's not just Office 2013 that is emerging fully baked; also at the RTM stage are Exchange 2013, Lync 2013, SharePoint 2013, Project 2013 and Visio 2013.
Kirk Koenigsbauer, corporate vice president of the Microsoft Office Division, announced the RTM milestone in a blog post. He claimed that the 2013-branded Office represents "the most ambitious release of Office we've ever done."
In July, Koenigsbauer and Microsoft CEO Steve Ballmer showed off touch-friendly Office 2013 apps. These apps will run on the "Desktop" side of the Windows 8 user interface. Microsoft is also building "Metro-style" Office apps, but so far only the OneNote Metro-style app is available for testing. Gartner analyst Steve Kleynhans has described the new Office 2013 apps as very similar to those in Office 2010, but with screen layouts optimized for touch. Kleynhans added that he didn't consider Office 2013 to represent a major user interface change, but those familiar with Office 2007 and Office 2010 will notice some differences.
Office 2013 Availability
Those wanting to get their hands on the new 2013 products can expect them to be available in the "first quarter of 2013," according to Koenigsbauer. In the meantime, Microsoft will be running a promotional deal for new Office 2010 buyers, offering a free upgrade to Office 2013 when it's released. This promo will start on Oct. 19 for those buying Office 2010 from retailers or resellers.
Microsoft's volume licensing customers will have the ability to download the 2013 products before general availability. Those products will be available through Microsoft's Volume Licensing Service Center by "mid-November," with pricing available on Dec. 1.
Microsoft's TechNet and MSDN subscribers also will have access to the 2013 product bits by mid-November.
When Windows RT devices hit the market starting on October 26, they will contain a preloaded "preview" version of Office Home and Student 2013. This preview can be upgraded for free to the Office and Home Student 2013 product after a few months, according to an earlier Microsoft announcement. The Windows RT version of Office won't be available as a boxed retail edition.
Office 365 Service Update
Office 365, Microsoft's service that delivers hosted versions of Exchange, SharePoint and Lync, along with a premises-installed Office Professional Plus, is also getting new capabilities. The Office 365 improvements happen a bit differently from the RTM releases because Microsoft continually updates its Office 365 services through various "service update" releases. The next service update with the new 2013-branded capabilities will start becoming available to Office subscribers in November.
Developers building on Office 365 could see a bit of downtime during the service update transition period, according to a Microsoft blog post. Developer tools, including Napa, will get an upgrade too at the time of the service update.

Office 2013, SharePoint 2013, Exchange 2013 Released to Volume Licensees

Volume licensing customers can now access Microsoft Office 2013, plus various application servers with the "2013" branding, according to a report by ZDNet's Mary Jo Foley.

Microsoft confirmed Foley's account, indicating that volume licensees with Software Assurance can now download release-to-manufacturing (RTM) versions of Office 2013, SharePoint 2013, Exchange 2013 and Lync 2013 from the Microsoft's Volume Licensing Service Center. Pricing for the products will be disclosed on Dec. 1.
 
Volume licensing availability arrives a little early. Microsoft indicated earlier this month with the RTM release that volume licensees would get the bits "by mid-November." Microsoft's TechNet and MSDN received access to RTM versions of 2013 products a week ago.
Those Office 365 subscribers getting hosted versions of Lync and SharePoint are just beginning to get the latest service updates from Microsoft, according to Foley's account. Microsoft had previously said that Office 365 subscribers would start to get the next service update in November. The service updates get delivered to customers extending into early 2013.
The 2013-branded products are expected to hit "general availability" in the first quarter of 2013, according to Microsoft. That's Microsoft terminology for when boxed copies of Office 2013 will be available, although Foley's sources are suggesting that it will happen early in that quarter -- namely, in January.
Microsoft currently has a promotional offer for those buying retail copies of Office 2010 that allows them to upgrade to Office 2013 at no extra charge. The offer is limited to 25 "redemptions per person or organization" and Microsoft sends an e-mail to those signing up indicating when the Office 2013 upgrade will be available. There's one catch in that the "offer cannot be redeemed after the redemption end date has passed," according to the offer's terms. That end date isn't yet been specified by Microsoft, as of this writing.
The version of Office that comes with the new Microsoft Surface RT machines, Office Home and Student RT, initially was shipped on machines as a preview version. However, but the free upgrade to the full Office Home and Student RT was already available on Oct. 26 when the Surface RT machines appeared in Microsoft Stores.
Microsoft is also going to deliver the new Office version for Windows Phone 8 devices, including HTC, Nokia and Samsung models, when those devices become available. The new Windows Phone 8 devices are expected to be available starting in late November, near the Thanksgiving holiday. The phones will have an Office Mobile version that doesn't have all of the capabilities of Microsoft's Office 2013 flagship product.

User Profile Synchronization Service failed to start..can be fixed


if you want to do a User profile import in SharePoint 2010.. you should have the
'User Profile Synchronization Service' started. But there are many reason why this
service wont start. Following are some points to check before doing something crazy
like re-install the farm.

Pre-requisites

If you have all of the above set right.. Check the following..
1.    Determine which service account will be used to User Profile Syncronization (UPS) ..Goto CA > Application Management > Manage Services on Server > User Profile Synchronization Service > Click on Start. you will see a default account name already filled in. Make a not of this account. Wait, don't be in a hurry..just check the account used. When you are finished with all the steps below..come back to this step and enter the credentials to start the service.

2.    Make sure this service account is a domain account with local administrator permissions
on WFE servers.. if not add the user account to the administrators group and Re-boot
system ( resetting IIS and Timer service may also work.. if not you have to re-boot)
3.    DirSync permissions set for the service account. To be sure give permission for
both "Replicating Directory Changes" and "Replication synchronization"

4.    Service account has full control permissions on User Profile Service application. for this goto Central Admin >Application Management >Manage Service Applications >Click on the bar of "User Profile Service Application " (.. dont click on the link). In the ribbon, make sure that under Administrators and Permissions Menu, the service account has full control.
5.    Make sure both Forefront Identity Manager services are configured to run with the
service account identified. you can configure logon account by rightclick on service
> properties > log on .
Note: that the services may not be running. it will automatically
start when the User Profile Sync starts.

6.    Go back to step 1 and fill in the credentials and start service