[EN] How To Do It? Enable Versioning on Site Collections

In this series I occasionally (yes, too occasionally) writing about small useful advices, which are answers for my colleagues, students and sometimes customers. I know that many of this kind advices are well known for many of technical blog readers, but from my perspective it’s very helpful for me. Why? Sometimes I need solution on demand and sometimes I don’t remember how something simple do. But I remember: “Wait, bastard! You wrote about it on blog!” Now I’m writing about Site Collection Versioning in SharePoint 2013.

One of my client asked me about enabling versioning for brand new SharePoint 2013 farm with few separate site collections, and sites, lists, libraries inside. First point for solve this request is going to Central Administration… where I spend half an hour to find simple answer: how to enable versioning on ALL site collections. And the answer is simple – this feature is not working on Farm Level, just on Site Collection level. That means: If I have four, five, ten Site Collections – I need to enable versioning on all site collection manually separately. Does not make sense and it’s really boring.

But… I have Power! I can use PowerShell with one simple script for enabling versioning on all my site collections and libraries and list if I need. The original post has been written by Keith Tuomi (Canadian SharePoint MVP) here, but is worth to be partially quoted and re-discover.

image

Pict.1 Whole script for enabling versioning on all site collections.

If I need I can enabling versioning with Major and Minor levels fon all Document Libraries on my SharePoint Farm (in this example 5 major and 10 Minor versions). Script have two parameters:
1. Required: Site collection URL e.g. http://intranet.company.com (specifies the site collection to operate on)
Example 1 – run the script in report mode only (no changes effected):
   c:sharepointadminaccount.Enable-Versioning.ps1 http://intranet.company.com

2. Optional: execute Script runs in report mode only unless you add the word execute
Example 2 – run the script in execute mode:
    c:sharepointadminaccount.Enable-Versioning.ps1 http://intranet.company.com execute

Easy? Yes! And it works. As additional advice – it’s possible to add this script for Windows Task manager for run on regular basis to be shure that all new site collection, site, library, list are versioning. Script you can downolad from resources page.

[EN] SharePoint 2013 December 2014 CU is available

LOGO__SharePoint2013_bigintoMicrosoft SharePoint Product Group released two important updates packs in December: one for the SharePoint 2010 and one for the SharePoint 2013. In this post I writing about newest SharePoint product. Before you will go to download and install you should remember that this December 2014 Cumulative Update for the SharePoint 2013 (buld no 15.0.4675.1000) require SharePoint Server 2013 Service Pack 1 or March 2013 Product Update (PU) for SharePoint 2013, adnd this cumulative update does not include Service Pack 1, and the SharePoint Server 2013 CU contains the SharePoint Foundation CU, and the SharePoint Server 2013 with Project Server CU contains Project Server CU, SharePoint Server CU and SharePoint Foundation CU. Just be aware.

This time we get four goups of files and four knowledge base articles for all updates:

  • KB 2910945 – about SharePoint Foundation 2013 and few fixed problems
  • Assume that you configure a Security Assertion Markup Language (SAML) token provider for a SharePoint 2013 site. Then, you add the CookieHandler.Domain property to the web.config file of the site. When your session to the site is expired, you may be unable to log on to the site again.
  • When you browse to a SharePoint 2013 page that contains an UpdatePanel control, the page may be refreshed randomly. Therefore, if you type something in a text field on the page, the text field may become empty.
  • This hotfix improves managerial effectiveness in SharePoint 2013 by letting the administrators manage the language settings by using the Client Object Model.
  • Assume that you add an XsltListView Web Part to a SharePoint 2013 page, and the Web Part contains a link to another SharePoint 2013 site. When you click the link, you are redirected to an error page.
  • Assume that you create a subsite in a SharePoint 2013 site collection, then you open the Site Settings page of this subsite. When you try to open the Site columns page, it may take long time than expected.
  • Assume that you add an item that contains a choice field to a SharePoint library or list, and the field contains an ampersand (&) character, and then you save it. When you select the item and then click the View Item button or theView Properties button, the ampersand (&) character in the choice field does not appear correctly.
  • Assume that you send an email message that contains many attachments from an iPhone to a SharePoint 2013 document library. In this situation, the email message that is sent to the document library may contain an empty attachment that has no file name. Additionally, the other attachments may be missing.
  • Assume that you create a Lookup column in a custom list, and the lookup column gets information from a Date and Time type column. Then you create a standard view and set the lookup column in the Group By section. When you display the view in the custom list, the date is displayed in an incorrect format (MM/DD/YY instead of DD/MM/YY).
  • Assume that you open the Schedule page of a project in Project Web App (PWA). When you click the Print button on the Options tab to view the print preview information, the task bar is missing from the Gantt chart in the print preview window.
  • This hotfix improves managerial effectiveness in SharePoint 2013 by letting the administrators configure the SPSite.SecondaryContact property by using CSOM APIs.
  • You may be unable to create sub-folders while you are creating many sub-folders inside a folder in parallel.
  • After you run a content deployment job on a SharePoint 2010 Server, additional thumbnails of the original thumbnails are generated.
  • KB 2910938 – about SharePoint Server 2013 and few fixed problems
  • This hotfix improves crawl performance for SharePoint 2013 when deadlocks occur in the link databases.
  • This hotfix improves the accuracy of the Most Popular Items report by counting the usage event statistics for all documents in a SharePoint 2013 library.
  • This hotfix improves the @Mention feature on My Site pages by displaying the login when you move the pointer over a display name. This improvement helps you distinguish different users who share the same display name.
  • Assume that you configure a SharePoint 2010 farm to consume a Search service application of a SharePoint 2013 farm. Then you configure alternate access mappings for the SharePoint 2010 farm. In this situation, when you search for content in the SharePoint 2010 search center, the URLs that appear in the search result are incorrect.
  • In some cases the "Did you mean" spelling correction feature does not work on a multi-node SharePoint 2013 search farm.
  • In multi-node SharePoint 2013 search farm setup, the restart of the primary indexer node (for example for maintenance or applying updates) may cause a restart of the secondary node which results in a query outage during the restart of the primary node. This fix makes sure that the restart of the primary node does not lead to a restart of the secondary node. Therefore, the search service will still be available.
  • Assume that you sign in a SharePoint 2013 site by using Security Assertion Markup Language (SAML)-based claims authentication. When you search for content in the site, no result is returned.
  • When you use enterprise search in a SharePoint 2013-based server, the Best Bets feature may not work.
  • KB 2910911 – about SharePoint Server 2013 with Project Server and six important problems has been fixed
  • Assume that you add actual work to a task in a timesheet and then save it. Later, the project manager publishes another task, and the new task appears on the same timesheet. You add actual work to the new task and you submit the timesheet for approval. In this situation, the timesheet line for approval of the new task is not displayed in the Approval center.
  • Assume that you change the working time of the enterprise calendar associated with your project to a nondefault working timesuch as 9:00-17:00. Then you publish a task. You go to the Tasks page in Project Web App (PWA), then you change the finish date and the duration of the task and save the change. In this situation, both the finish hour and the task duration are incorrect.
  • Assume that you create a risk or an issue for a project in PWA, then you save it. When you visit a Project Centerview that includes Active Risks and Active Issues fields, the values are always zero.
  • Assume that you have a custom field that is defined to include a lookup table and the table contains many values. In this situation, you may be unable to select lookup table values from the custom field on a Project Detail Pages page that shows this field.
  • Assume that you apply a filter in the Approval Center in PWA. When you refresh the page, or when you go back to the Approval Center after you visit other pages, the filter is not applied though it is already set in the ribbon.
  • Assume that you set a baseline for a project, and then you publish and check in the project in PWA. When you open theSchedule project details page, the baseline value is incorrect. For example, the baseline value should be $1.00. However, it is displayed as $100.00
  • KB 2899574 – about Office Web Apps Server 2013 and just one small problem
  • You may be unable to create sub-folders while you are creating many sub-folders inside a folder in parallel.

You can downolad all necessary files (in total ca 10 GB size) directly from download center (almost directly – ‘cos you have to fill mail address twice uthorization code and next you will get download link on email message). Be aware tahta based on size of updates (eg. for SharePoint Server 2013 size is close to 3.5 GB) Microsoft splitted files for one .EXE file anf two .CAB files which are downloaded separately, but all are necessary for installation process:

After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.

More related important links (from SharePoint Release Team) are below:

[EN] SharePoint Solution Deployer 5 is available

Matthias Einig MVP {BLOG|TWITTER|FACEBOOK|LINKEDIN} LOGO__BannerGross_SPSDwho works with FANTASTIC TEAM at Tretton 37 and is owner Rencore AB company gave me, and other SharePoint enthusiast new version of his fantastic tool exactly for New Year. SPSD > SharePoint Solution Deployer is highly configurable special PowerShell tool for deploying wsp packages into Microsoft SharePoint 2010 and 2013. Based on information from his blog (LINK) we can find new features:

  • New: SPSD now has an extension system which allow you to create your custom PowerShell extensions and integrate them in the deployment process!
  • New: Added and example extension
  • New: Environment file can now be passed as parameter to the batch files
  • New: Added timestamps to better measure execution time
  • New: Added new deployment command “Ask” which asks the user for the deployment command.
  • New CP16167: SPSD now works also when run though an application (e.g. console app), output will be just logged into the log file
  • New: Countdown after deployment until windows closes

And of course we are very happy, that Matthias had enough time for fixing some bugs:

  • Updated: SharePointVersions.xml to include new SharePoint versions for SP2010/SP2013
  • Changed: Renamed CustomTarget SkipSolution to ProcessSolution
  • Changed: Stability improvements
  • Changed: Memory disposal improvements
  • Fixed CP16490: Incompatible with PowerShell 4.0 due to switch statements
  • Fixed CP16441: Compatibility Level ignored for global deploys
  • Fixed: CloseAllPSSessions had unused parameter in signature
  • Fixed: Startup in batch with relative path when not running from cmdline was failing when user UAC was enabled

This software working on Windows Server 2008/2008R2/2012 and Windows 7 (that’s official).

Great and big article with screenshots and introduction slidedeck You can find in the TechNet Gallery. More informations, build releases history You can find at CodePlex.

IMPORTANT (based on slideshare slide 9): Before unpacking the ZIP field, open the file properties and unblock the file!

Download, Deploy, Enjoy!