July 2014 Cumulative Update for SharePoint 2013 has been released. SharePoint Foundation: KB882999 http://support.microsoft.com/kb/2882999 SharePoint Server 2013: KB2882989 http://support.microsoft.com/kb/2882989 Project Server 2013: KB2882990 http://support.microsoft.com/kb/2882990 Office 2013 April 2014 Cumulative Updates: KB2978164 http://support.microsoft.com/kb/2978164
April
2014 Cumulative Update Packages for SharePoint Foundation 2013 and SharePoint
Server 2013 have been released April 2014 CU for SharePoint Foundation 2013 - KB 2863892
·Owner: Owner has a complete control over site, list, library and
other content placed on site.
·Designer: Users having designer role limited to certain activities. User
can view, add, update, delete and approve content. Users can even customize the
things, they have access to.
·Editor: Editor role users are not allowed to customize site design or
content. Users can add, edit, update and delete content from the site.
·Contributor: Very limited role. They can delete content items which they
have created but not by other.
·Reader: Users are only allowed to view the content of site. Users are
assigned to Reader roles can download and edit the content but cannot save it
back on SharePoint site.
Roles can be established at different level in SharePoint
2013. Role could be created from highest level that is Site Collection or at
Individual site level or based on specific apps within site, library or list.
Roles provide a way of managing permission at broadest level from site to site
or within site and at apps level.
If you are looking forward to clear 70-332 paper and looking for practice questions answers like me, here i have combined a set of links which can be useful. The best place where i could see the questions and answers is mcseananswers.com I am listing down the links to go step by step these are 12 part series which contains 70 questions and answers which might give you an idea of stuff you can expect in 70-332 paper -----------------------------------------------------------------------
The product group makes every effort to validate that
SharePoint functionality works correctly with released versions of
Internet Explorer. Customers who want a more deeply validated browser
interaction experience should strongly consider Internet Explorer.
Internet Explorer 10, Internet Explorer 9, Internet Explorer 8
Other supported browsers
Google Chrome (latest released version)
Mozilla Firefox (latest released version plus immediate previous version) For example, if the latest released version is 10, then version 9 would be supported.
If you've not had time yet to work with SharePoint 2013 Preview, here's a look at
what's new so far. Your assessment of the value of said new
features will vary, depending on your mileage and usage.
Authentication
Microsoft says that SharePoint 2013 Preview has
been improved to make claims-based authenticationeasier to use.
It extends support for application authentication via Open Authorization 2.0 (Auth)
as well as for server-to-server authentication.
Users can grant apps in the SharePoint store and
catalog access to certain resources and data. Server-to-server security tokens
that contain user identity claims enable cross-server authenticated access
between, say, SharePoint 2013 Preview and Exchange
2013 Preview. (See also Microsoft's architecture posters websitefor the one
labeled "Extranet with Dedicated Zones for Authentication" and
to see full views of the image excerpts below.)
Business Connectivity
Services
Microsoft added a bunch of new features to BCS in
SharePoint.
You might like these: Support for OData Business
Data Connectivity (BDC) connections, in addition to connections for WCF, SQL
Server, and .NET assemblies. Automatic generation via Visual Studio 2010 of BDC
models for OData data sources. An event listener with an event subscriber on
the SharePoint 2013 Preview side, to enable SharePoint users to receive notifications
of changes to the external system. Self-contained apps for SharePoint.
But wait--there's more: Enhancements to external
lists that bring them to functional parity with other SharePoint lists. The
exposure of the REST APIs for web and mobile app developers to use. Six new
Windows PowerShell cmdlets specifically for OData. And the ability, via
Business Connectivity Services Client Runtime, to have side-by-side
installations of Office 2010 and Office 2013 Preview on the same client
computer.
eDiscovery
Showing SharePoint's increasing presence in the
world of litigation, eDiscovery improvements have been added that,
unfortunately, are probably sorely needed. They include a new site template,
the eDiscovery Center, which creates a portal for managing cases—you can access
cases to search, hold content, and export content.
Microsoft has added improvements to in-place
holds, including site-level preservation; the ability for users to work with
content that's preserved; and the ability to define the scope of preservation
via a query filter.
You can also now take the results of your
eDiscovery search—including documents, wiki pages, Exchange email messages and
tasks-- and export them into a review tool.
Mobile devices
Optimized viewing for mobile device users was a
no-brainer addition to SharePoint Server 2013 Preview—it had to be done.
Other new features include the following: The
ability to render a single SharePoint published site in multiple formats for
different devices. The ability to enable a push notification service on a
SharePoint site to send device updates to a Windows Phone device.
We're not done yet: A new geolocation field type
for use in mobile app development. The ability for
some devices to display PerformancePoint Web Parts, Excel Services reports, and
SQL Server Reporting Services reports. And finally, enhanced viewing of Office
Web apps (Word, Excel, and PowerPoint) via mobile browsers.
Records management
and compliance
Reflecting perhaps not a dearth of added
features, but the distance SharePoint 2010's records management features had
improved from SharePoint 2007's, you'll find that SharePoint 2013 Preview has
enhanced compliance simply by extending retention policies to SharePoint sites.
This also applies to any Exchange Server 2013
Preview team mailboxes associated with those sites.
Business intelligence
SharePoint 2013 Preview adds tons of new
features, including the following: New features in Excel for business
intelligence (BI): In-Memory BI Engine (IMBI) for near-instant analysis of
millions of rows of data; Power View Add-in for Excel, which offers
visualizations, animations, and smart querying to enable users to visualize
modeled data; decoupled PivotChart and PivotTable reports allowing for the
creation of PivotChart reports without having to add a PivotTable report on the
same page; and the ability to do trend analysis from cells in PivotTable
reports that use OLAP data.
It also adds Excel service enhancements such as
an updated Business Intelligence Center site template, and improved timeline
controls.
Visio Services improvements include the ability
for users to add comments to a Visio drawing on the web via Visio Services.
And PerformancePoint improvements include the
ability for users to copy dashboards and dependencies to other users or site
collections; an enhanced UI; support for Analysis Services Effective User
feature, which eliminates the need for Kerberos delegation for per-user
authentication; and support for PerformancePoint on the Apple iPad.
Social computing
It's no surprise that Microsoft wanted to beef up
the social computing features in SharePoint, and with SharePoint 2013 Preview,
it's on track for doing so. Basically, it's enhanced the administration and
user experience, and added ways for enterprise users to collaborate more fully
and naturally using social media features.
One way is by enhancing the ability create
discussions—via two new templates called Community Site and Community Portal.
Microsoft also redesigned the UI for MySites, and added Microblog and Newsfeeds
features, and improved features users need around saving, synchronization,
sharing, and moving content.
Because of the new MySites features, you'll also
find Microsoft made several changes to the User Profile service application
settings in Central Administration around configuring permissions, privacy,
micro-blogging and newsfeeds, and more.
Web content
management
Microsoft improved the video upload process for
content authors, and improved image display and performance of a site with its
image renditions feature, which reduces the size of an image file that is
downloaded to the client.
It added an integrated translation service that
gives content authors or managers the ability to choose which content will be
exported for human translation and which for translation by machine.
And cross-site publishing does just as it says,
giving you the ability to display content in one or more publishing site
collections. You can also designate any library or list as a catalog, enabling
content to be reused on publishing site collections.
It added managed navigation, which lets you use
term sets to define and maintain navigation on a site. And it added the ability
to create more user-friendly URLs.
In the area of branding, Microsoft made it less
mysterious, and now designers use such tools as Adobe Dreamweaver, Microsoft
Expression Web, or another HTML editor, rather than having to use SharePoint
Designer or Visual Studio 2013 to brand a SharePoint site.
And it added the ability for designers to design
sites for display on different devices, such as tablets, smartphones, and
desktops. Additional features enhance search, authoring, and publishing.
Workflow
Microsoft made architectural changes in
SharePoint Workflow. If you want to have the nearly identical experience of
building workflows in SharePoint 2013 Preview as you do in SharePoint 2010, you
simply install SharePoint Server 2013 Preview.
But if you want the SharePoint 2013 workflow
platform, you need to install and configure Windows Azure Workflow to
communicate with your Preview farm. SharePoint Designer 2013 Preview includes
new functionality designed specifically for Windows Azure Workflow, and called
the SharePoint 2013 Workflow platform.
These new features include a visual workflow that
uses a Visio 2013 Preview add-in, the ability to enable no-code web service
calls from inside a workflow, new actions for the task process, the ability to
start a workflow built on SharePoint 2010 from a workflow built on SharePoint
2013, and new workflow building blocks called Stage, Loop, and App Step.
Note that to manage and monitor the Windows Azure
Workflow in SharePoint 2013, you must use Windows PowerShell. (To get a head
start on working with PowerShell, consult our latest SharePoint and PowerShell
article "Exploring and Inventorying SharePoint Using Windows PowerShell.
In
SharePoint 2013 Dev dash has helped the admins to help troubleshoot a lot of
performance issues .The Developer Dashboard can now be extended by injecting custom
JavaScript code into the developer dashboard window.
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.
Problem:You could see in SharePoint Health Analyzer rule "Business Data Connectivity connectors are currently enabled in a partitioned environment."
Background:Business Data Connectivity (BDC) Models containing External Content Types with database, WCF, Web service or custom connectors can be used by tenants to elevate their user permissions. In a partitioned environment, we recommend you disable the Business Data Connectivity connectors.
Reason for error: Business Data Connectivity connectors are currently enabled in a partitioned environment.
Resolution: Disable unwanted connectors by using Windows PowerShell.
To disable unwanted connectors, follow these steps:
1.Click Start, click All Programs.
2.Click Microsoft SharePoint 2010 Products.
3.Click SharePoint 2010 Management Shell.
4.At the Windows PowerShell command prompt, type the following command, and then press ENTER:
Get-SPServiceApplicationProxy
5.Note the Business Data Connectivity proxy instance.
6.You must set the EnableSystemType property to false for each unwanted connector. To do this, at the Windows PowerShell prompt, type the following command, and then press ENTER:
Visual upgrade: The visual upgrade feature in SharePoint Server 2010 is not available in SharePoint 2013 Document Workspace site template: The Document Workspace site template was removed from SharePoint 2013 to simplify the list of templates that are available when a user creates a new site collection. The Document Workspace site template will continue to operate in SharePoint 2013. The Document Workspace site template will be removed completely from the next major release of SharePoint and sites that were created by using the Document Workspace site template will not be supported. Personalization Site site template: The Personalization Site site template was not a widely used site template. The Personalization Site site template was removed from SharePoint 2013 to simplify the list of templates that are available when a user creates a new site collection. Meeting Workspace site templates: When you create a site in SharePoint 2013, all five of the Meeting Workspace site templates are not available. This includes the Basic Meeting Workspace, Blank Meeting Workspace, Decision Meeting Workspace, Social Meeting Workspace, and Multipage Meeting Workspace. Group Work site template and Group Work solution: When you create a site in SharePoint 2013, the Group Work site template is not available. This Group Work site template provides a groupware solution that teams can use to create, organize, and share information. The Group Work site template includes the Group Calendar, Circulation, Phone-Call Memo, document library, and other basic lists. The Group Work site template and the Group Work solution are discontinued and not available in SharePoint 2013. Unghosting and customizing CSS files: The following methods are included in SharePoint 2013, but will be removed from the next major release of SharePoint: • Microsoft.SharePoint.SoapServer.Webs.CustomizeCss • Microsoft.SharePoint.SoapServer.Webs.RevertCss The methods are outdated and are no longer needed. Excel Services — Can't edit workbooks in the browser that have external data connections: This is a design limitation in SharePoint 2013. Web Analytics in SharePoint Server 2010 Web Analytics in SharePoint Server 2010 has been discontinued and is not available in SharePoint 2013. Analytics processing for SharePoint 2013 is now a component of the Search service. Search capabilities: The search capabilities of SharePoint Foundation 2013 have changed, and are now based on the same search implementation as SharePoint Server. This provides many improvements, but also means that the search configuration is very different. Supported document formats: SharePoint 2013 no longer supports rarely used and older document formats that are supported in FAST Search Server 2010 for SharePoint by enabling the Advanced Filter Pack. Both the ULS logs and the crawl log indicate the items that were not crawled Source : http://technet.microsoft.com
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)
I read a very good article onDan Holme's Viewpoint on SharePoint Blogon 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.