The SharePoint 2010 February 2015 Public Updates have been released: SharePoint Foundation: http://support2.microsoft.com/kb/2910904 SharePoint Server 2010: http://support2.microsoft.com/kb/2899558 Project Server 2010: http://support2.microsoft.com/kb/2899557 Office 2010 February 2015 Cumulative Updates: http://support2.microsoft.com/kb/3032763
The February 2015 Public Update introduced a change to quickly allow you to migrate a Path-based Site Collection to a Host-named Site Collection. Here is how you would use this feature. [crayon-54e0a49172dbb290774229/] And that’s it! You’ve migrated http://siteUrl to http://host.example.com.
The post Quickly Migrate SharePoint Path-based to Host-named Site Collections appeared first on Nauplius.
The SharePoint 2013 March 2015 Cumulative Updates have been released: SharePoint Foundation: http://support.microsoft.com/KB/2956159 SharePoint Server 2013: http://support.microsoft.com/KB/2956166 Project Server 2013: http://support.microsoft.com/KB/2956162 Office Web Apps Server 2013: http://support.microsoft.com/KB/2956158
The SharePoint 2010 March 2015 Cumulative Updates have been released: SharePoint Foundation: http://support.microsoft.com/KB/2956183 SharePoint Server 2010: http://support.microsoft.com/KB/2956201 Project Server 2010: http://support.microsoft.com/KB/2956198
SharePoint has a mode known as multi-tenancy. This allows you to have multiple ‘tenants’, or isolated data sets for multiple customers. This mode is similar to how SharePoint Online operates. SQL Server Reporting Services does work in multi-tenant mode, until you install SSRS 2012 Sp2. While there is an explicit “no support” statement for SSRS 2014, this note does not (yet) exist for SSRS 2012 (or for the installing SSRS on SharePoint 2010 SSRS 2012 and SSRS 2014 articles). With SSRS 2012 pre-SP2, multi-tenancy functions as expected. After applying SP2 (tested up to CU6), the value of Globals.SPSiteSubscriptionId is a null value. This value must be equal to the SPSite.SiteSubscription value in order to function properly. After opening a case on this, this appears to be a non-tested, unsupported usage scenario for SQL Reporting Services. A bug report has been filed, but my assumption is that the documentation will simply be updated across the board to indicate that there is no support for using SQL Server Reporting Services in SharePoint multi-tenancy.
The post SQL 2012 SP2, Reporting Services, and SharePoint Multi-Tenancy appeared first on Nauplius.
Today I’m announcing the SharePoint Patch Service. This service allows you to quickly look up SharePoint patch information based on a SharePoint farm build number or knowledge base article. Todd Klindt has been storing this information on his website for a long time now, and I wanted to get it into database form. So, I’ve developed the SharePoint Patch API service. SharePoint Patch Service As of today, this service supports the following products: SharePoint Foundation 2010 SharePoint Server 2010 Project Server 2010 Office Web Apps 2010 FAST Search Server 2010 SharePoint Foundation 2013 SharePoint Server 2013 Project Server 2013 Office Web Apps 2013 Prior to the next Patch Tuesday, the remaining patches from security updates will be added for all products. In addition to the service (which is Restful and emits JSON output), I’ve also developed a PowerShell cmdlet to access the service. The cmdlet is in it’s first version, and will be undergoing updates to improve on functionality. Any comments, questions, ideas , or if I’ve missed any patches or known community issues, please contact me via the blog or Twitter.
After applying the March 2015 CU (and possibly MS15-022), it is no longer possible to Filter a View based on criteria in the Task list (e.g. Task Status). This appears to only impact new Task Lists created post-patch. One workaround is to place the Task list on a Page. Edit the Web Part and check “Server Render” under Miscellaneous. This does not appear to be a Lists.asmx Web Service issue as the filtered view correctly filters in 3rd party tools, such as Stramit Caml Viewer.
The SharePoint 2010 October 2015 Cumulative Updates have been released: SharePoint Server 2010: https://support.microsoft.com/en-us/kb/3085603 Project Server 2010: https://support.microsoft.com/en-us/kb/3085598 Office Updates: https://support.microsoft.com/en-us/kb/3099951 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!
[This post is based on the SharePoint 2016 Preview — Functionality is not guaranteed to be supported, configured identically, or exist in RTM] SharePoint 2016 brings a SharePoint Online feature called the Compliance Center, or a subset of the features, specifically the Document Deletion Policies. This allows for a centralized location to set document deletion based on a few parameters, such as when the document was created or last modified, and what the target Site Template is (e.g. you can target sites created with the Team Site template). This post will cover the internals of the Compliance Policy feature, instead of the user-facing feature itself. A site created from the Compliance Policy Processing template (POLICYCTR#0) may only be created by a Farm Administrator. This Site Template is not available through Self-Service Site Creation. When a Compliance Policy Processing site is created, the Web Application has a property of “PolicyCenterUrl” set to the Site.Url value. SharePoint will not allow for a second Compliance Center site to be created. It is possible to create a second one if the PolicyCenterUrl property is deleted. At the heart of the Compliance Policy feature are five timer jobs: Compliance Dar Task House Keeping Compliance High Priority Policy Processing Compliance Dar Processing Compliance Policy Processing Unified Policy OnPrem Sync Job In the same order, here are the names and schedules of each job: Name Schedule DarTaskHouseKeeping daily between 02:00:00 and 02:30:00 HiPriPolicyProcessing every 15 minutes between 0 and 59 DarProcessing every 10 minutes between 0 and 59 PolicyProcessing daily between 03:30:00 and 04:30:00 UnifiedPolicyOnPremSyncTimerJob hourly between 0 and 59 For ULS logging, all of these log under the “Information Policy Management” category under the “Document Management Server” Product (or Set-SPLogLevel -TraceSeverity traceSevLevel -Identity “Information Management. The timer jobs processing sites will ignore sites with the following Site Templates: “POLICYCTR”, “EDISC”, “TBH”, “TENANTADMIN”, “OFFILE”, “OFFILE”, “CENTRALADMIN”, “MYSITE”, “SPSMSITEHOST” HiPriPolicyProcessing has a maximum run time of 15 minutes, and runs against each Content Database in a Web Application. It executes the stored procedure, proc_GetWorkItemCountForType with an input value of “29A8C505-1DAA-44E9-8974-B7BA3996794B”. This sproc looks for the GUID in dbo.ScheduledWorkItems.[Type] column. If no entries are found, the timer job exits. Otherwise, it executes the assigned policy when that policy is marked High, or a Category of 2. DarTaskHouseKeeping will cleanup completed or failed tasks based on the expiration date of the task * -1. It then moves onto setting tasks to have a reoccurrence of None, Recurrent, or enqueue the task for execution. DarProcessing has a maximum runtime of 10 minutes and runs against each Content Database in a Web Application. It enqueues and executes Dar tasks. Dar tasks are held within the List, Lists/DarTasks. It executes the assigned policy when that policy is marked Urgent, or a Category of 3. PolicyProcessing is very similar to HiPriPolicyProcessing, except it has a runtime of 1440 minutes (24 hours) and only runs Dar Tasks with a priority of Medium, or a Category of 1. UnifiedPolicyOnPremSyncTimerJob does not appear to do anything as during the initial execution, it validates if the SPWeb has a Property of “MsoTenantId”. If not, it returns. MsoTenantId appears to be for hybrid DLP scenarios (and possibly SPO only). Those are the basics! Hopefully the SharePoint PG will add additional DLP options in the future to cover other scenarios.
The SharePoint 2010 November 2015 Cumulative Updates have been released: SharePoint Server 2010: https://support.microsoft.com/en-us/kb/3101534 Project Server 2010: https://support.microsoft.com/en-us/kb/3101530 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!
The SharePoint 2013 November 2015 Cumulative Updates have been released: SharePoint Foundation: https://support.microsoft.com/en-us/kb/3101368 SharePoint Server 2013: https://support.microsoft.com/en-us/kb/3101373 Project Server 2013: https://support.microsoft.com/en-us/kb/3101369 Office Web Apps 2013: https://support.microsoft.com/en-us/kb/3101367 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!
SharePointUpdates.com provides you with information on SharePoint 2010, 2013, and next year, 2016 updates. Changes have been deployed today for the Patches and Issues pages. With the number of patches approaching 500, the list was becoming quite slow for IE 11 users. Due to this, the list is now paginated and should perform similarly across all browsers, including mobile devices. And speaking of mobile devices, the lists are now responsive! This should make it easy to review patch information from anywhere. Lastly, there are new export options — just in case you want the data offline. Let me know what you think!
The SharePoint 2010 December 2015 Cumulative Updates have been released: SharePoint Server 2010: https://support.microsoft.com/en-us/kb/3114408 Project Server 2010: https://support.microsoft.com/en-us/kb/3114405 Office Updates: https://support.microsoft.com/en-us/kb/3121650 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!
The SharePoint 2013 December 2015 Cumulative Updates have been released: SharePoint Foundation: https://support.microsoft.com/en-us/kb/3114339 SharePoint Server 2013: https://support.microsoft.com/en-us/kb/3114345 Project Server 2013: https://support.microsoft.com/en-us/kb/3114341 Office Updates: https://support.microsoft.com/en-us/kb/3121650 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!
SharePoint Libraries include a search box for that specific library, e.g.: Prior to the August 2015 Cumulative Update, it was possible to find an item within the specific folder of a library. In the above example, if you went into Subfolder and then searched for an item, the search would be limited to items within that subfolder. After the August 2015 CU has been applied, the search box is no longer context sensitive. All items will be returned from the library that match the specific search term. This is due to a change in the file INPLVIEW.js (and INPLVIEW.debug.js) where a function call was dropped which prevents the context sensitive search from working. As a temporary workaround, it is possible to modify these files to get this search functionality to it’s original state. The first thing that needs to be done is to make copies of INPLVIEW.js and INPLVIEW.debug.js, which are located in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\. These copies must be restored prior to installing a SharePoint patch, otherwise the files may not be updated by a patch. Next, in INPLVIEW.debug.js, open the file with a text editor and go to line 3058. This line will be within the function named “HandleRefreshViewInternal”. Line 3058 should not have any text. Add the text: For INPLVIEW.js, find the text . Immediately after that text, add: For INPLVIEW.debug.js, the entire function will look like: And for INPLVIEW.js: There is a PSS case open for this issue to revert the change back to pre-August 2015 CU behavior.
The post Context Sensitive List Search Broken by August 2015 CU appeared first on Nauplius.
Developers have reported that after applying the October 2015 CU, they are unable to follow content programmatically using SPSocialFollowingManager.Follow method. While reported for the October CU, the change appears to be from the September 2015 CU, thanks to an improved hybrid User Profile experience. The September 2015 CU added the option to follow on-premises Sites and have the followed Sites appear in the user’s SharePoint Online user profile. This is a great feature, but unfortunately broke the functionality. What has broken this functionality is . This method now contains the line . The method is calling , however is null. Because the service context is null, adding the followed item fails with the error: That said, there’s a workaround! What needs to be done is to properly set . If, within the scope of your custom code, is set (even through a console application), will not be null and an item can be followed.
Another year of SharePoint! This year we have the big release of SharePoint 2016 Beta, which is a very large step forward for SharePoint on-premises. Check out the Top Posts of 2015! On a personal level, I’ve jumped a few jobs this year, including working at Microsoft IT to manage their SharePoint on-premises environments, which involved upgrading multiple farms from SharePoint 2010 to 2013. From there, I moved onto the SharePoint Product Group, supporting SharePoint Online Dedicated, Microsoft’s internal SharePoint Online ring, and other internal SharePoint 2016 farms. And now I’ve moved to a Senior Consultant role at another company! Lots of moving around, but always working on something exciting! Here are the top posts by views for 2015: August 2015 CU Error – “File names can’t contain the following characters” A big impact to the community, one of the issues that was fixed relatively quickly in terms of CU breaking issues. SharePoint and the Web Application Proxy Role The Web Application Proxy role for ADFS is becoming more and more popular. This is a basic configuration guide on how to implement WAP specifically for SharePoint using constrained delegation and without converting SharePoint to SAML! March 2015 CU/MS15-022 Task List Filter Issue There has to be more than one major community-impacting bug per year, and it is always unfortunate to see it in SharePoint security patches. Again, another manual workaround provided, but at least it was fixed within 2 months! PowerPivot Mid-Tier Process Account Does Not have Full Read PowerPivot is another one of my hobbies, and what would PowerPivot be without it’s fair share of cryptic and incorrect Health Analyzer Rules? April Updates Unable to Install on Service Pack 1 Another patch-related issue, this time with Service Pack 1 detection. Fortunately an easy, but annoying workaround was available, and then subsequently ‘fixed’ in future CUs. Quickly Migrate SharePoint Path-based to Host-named Site Collections A short one, but none the less it is always great when Microsoft provides us with new functionality. This one is extremely useful when you decide it is time to move to HNSC from Path-based Site Collections. No more backup/restores! SharePoint 2016 Durable Links One of the new features of SharePoint 2016, this post goes into Durable Links, how to enable them, and how they work. Chrome Support of the SharePoint 2013 Media Webpart Google made a great decision to drop NSAPI support this year in Chrome, forcing developers to move to HTML5 for video functionality SharePoint Support for Disabling SSL 3.0 and TLS 1.0 One for the security folks, this article goes into the supportability of disabling deprecated security transport protocols, and what SharePoint requires. We’ll see how this plays out in PCI DDS environments! Creating Search Alerts in SharePoint 2013 Last, but not least, the FAST team at Microsoft wanted to do away with Search Alerts, and certain APIs available with SharePoint 2010 were no longer supported in SharePoint 2013. With no further documentation out there, here’s the workaround! On to my favorite articles of the year. This will clearly be centered around SharePoint 2016, as I’ve been immersed into it for the past 6+ months. While a few of these features won’t get SharePoint 2016 RTM support, there is always hope that in the future the Product Group brings these features to SharePoint on-premesis. Azure Blob Storage for SharePoint Documents One of the big selling points for SharePoint Online is Fort Knox. With the Preview version of SharePoint 2016, it was possible to enable Fort Knox! This feature will not be available in SharePoint 2016 RTM, but it is always worth requesting from the Product Group on SharePoint UserVoice. SharePoint 2016 Site Masters Site Masters is a new feature in SharePoint 2016, and one I’m personally excited about. There are a significant number of SQL queries required in order to create a Site Collection. Site Masters bypasses many of them and speeds the process up. Announcing the SharePoint Patch Service This is something I’ve wanted to do for awhile, and one of my first non-SharePoint development projects in some time (MVC, Razor, Entity Framework, hosted on Azure SQL PaaS and Web Sites). This site keeps you up to date with all of the available SharePoint 2010, 2013, and in the future, 2016 patches. Not only that, but it also comes with a set of cmdlets to help you manage patches for your on-premises environment, including downloading and installing! If you haven’t tried it out already, give it a shot and let me know what you think! SharePoint 2016 Compliance Policy Internals It’s always good to know how things work, especially when they break. Understanding a critical feature like Compliance Policies is important for a SharePoint administrator, especially given the scenarios this feature is used for. Azure SQL PaaS for SharePoint Content Databases Another great, but ultimately unsupported feature for SharePoint. Storing your Content Databases in Azure PaaS sounds like a nice cost-savings feature, but due to latency, it simply isn’t possible. As always, if the feature interests you, use UserVoice! Using a CDN for Static Resources on SharePoint 2016 Many corporations use SharePoint with users spanning across the globe. SharePoint has many system files, which are static and never change. Well, why not use a global CDN to serve those files? SharePoint 2016 Large List Auto Indexing A very common scenario that frustrates end users of SharePoint is dealing with large SharePoint Lists and how to cope with the List View Threshold. SharePoint 2016 adds a new feature to automatically create List Indexes to help end users better support themselves when dealing with these large Lists. Unable to Follow Content Programmatically Thanks to the newest Hybrid functionality in SharePoint 2013 CUs, following content programmatically became slightly more complicated. This post details what the issue is, and how to work around it. SharePoint EventCache Cmdlet Have you ever used the EventCache? Or even knew it existed? It’s a store of valuable information, including CYA when that user tells you something deleted their document. Well, now you can prove they […]
The SharePoint 2013 January 2015 Cumulative Updates have been released: SharePoint Foundation: https://support.microsoft.com/en-us/kb/3114492 SharePoint Server 2013: https://support.microsoft.com/en-us/kb/3114497 Project Server 2013: https://support.microsoft.com/en-us/kb/3114493 Office Updates: https://support.microsoft.com/en-us/kb/3131245 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!
The SharePoint 2010 January 2016 Cumulative Updates have been released: Project Server 2010: https://support.microsoft.com/en-us/kb/3114556 Office Updates: https://support.microsoft.com/en-us/kb/3131245 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!
If MS16-004 is applied to a farm, users will see a TypeError when viewing SharePoint lists: This was noted on SharePoint StackExchange and the TechNet forums. The resolution is to apply the January 2016 Cumulative Update for SharePoint.