Nauplius.SharePoint.BlobCache is a SharePoint 2010 and 2013 solution that helps you manage the BLOB cache and all available settings, both documented and undocumented. New with this release is a bug fix for SharePoint 2010 and SharePoint 2013 to resolve an issue where the solution would not function if the Foundation Web Service was not running on the server with Central Administration (thanks, @brianlala!). This release also resolves an issue where previous settings were not removed with each use of the solution. You can download the solution and find the documentation at the project site.
The post Announcing the Release of Nauplius.SharePoint.BlobCache 1.6 appeared first on Nauplius.
SharePoint 2013 Service Pack 1 has been released. Note that while Service Pack 1 does support Windows Server 2012 R2, Windows Server 2012 R2 support requires a new SharePoint 2013 with Service Pack 1 ISO to be released. Slipstreaming or installing RTM and then SP1 on Server 2012 R2 is not supported. Foundation: http://support.microsoft.com/kb/2817439 Server: http://support.microsoft.com/kb/2817429 Project Server: http://support.microsoft.com/kb/2817434 Foundation Language Pack: http://support.microsoft.com/kb/2817442 Server Language Pack: http://support.microsoft.com/kb/2817438 Office Web Apps: http://support.microsoft.com/kb/2817431 Office 2013 Client: http://support.microsoft.com/kb/2817430 List of Server Updates: http://support.microsoft.com/kb/2850035 List of Client Updates: http://support.microsoft.com/kb/2850036
Service Packs typically contain little-to-no features. SharePoint 2013 SP1 is no different, however there are a couple of things I wanted to point out. First, both Yammer and OneDrive are apparently a critical SharePoint Central Administrator error: You can now configure Yammer and OneDrive for Business on Office 365 with SharePoint On-Premises integration. This can be done via Central Administration: OneDrive now replaces SkyDrive in the top link bar. Included with this is Yammer, if you activate the Yammer feature on-premesis via Central Administration. When you click on the Yammer link, you’ll be directed to /_layouts/15/Yammer.aspx and be asked to log in. That’s about it… Once Yammer is activated, the SharePoint “newsfeed” will now display this message when you visit your MySite. For OneDrive for Business on Office 365 integration, again in Central Administration -> Office 365 -> Configure OneDrive and Sites Link, you’ll simply input your OneDrive host in Office 365 (https://<tenant>-my.sharepoint.com) and the top link bar will redirect you there when you click on OneDrive. That is it for ‘on the surface’ new features! Another note I wanted to point out is use Russ Max’s installation script. It will save you hours of deployment on Service Pack 1. In addition, a reboot will not necessarily be required.
The post SharePoint 2013 and Office 365 with Yammer Integration appeared first on Nauplius.
With the release of SharePoint 2013 Service Pack 1, you can now re-calculate site storage metrics on demand. This is done via PowerShell. [crayon-530eaf7c1e907097838089/] This method executes proc_RecalculateStorageMetricsForSite, which can be found in each Content Database. The Content Database must be at the SP1 schema level. Storage metrics can be found on each site by visiting http://siteUrl/_layouts/15/storman.aspx.
If the SharePoint Configuration Cache folder, along with the cache.ini file go missing, you’ll likely notice the SharePoint Timer Service failing and restarting over and over again, along with a lack of scheduled timer jobs. The Timer Service failures will look like this in the System Event Log. [crayon-530eaf7c1bc02292821154/] Given this is the case, how do you restore the folder and cache.ini? The folder is a GUID, and unique to the farm, so creating just any folder isn’t going to work. The best method to recover the folder and file when no backups are available (and why would you backup a folder filled with transient files?) is to take a backup of your Configuration database and restore it under a new name (this is done for supportability reasons, SharePoint databases should be treated like black boxes). Then, query the Configuration database using the following command: [crayon-530eaf7c1bc1a030451474/] The returned value is the name of the folder that should reside in C:\ProgramData\Microsoft\SharePoint\Config\. Create this folder and create a new cache.ini. Within cache.ini, add “1″ (without quotes) and save the file. Start the timer service (or as it is probably continuously crashing, it will start itself), and that should resolve the timer service crashes. Note that if the farm has multiple SharePoint Servers, follow the standard advice on other SharePoint servers that are working — stop the SharePoint Timer service, and flush the cache, then after resolving the issue with the problematic SharePoint server, start the Timer service on all SharePoint servers. Once the folder and cache.ini are recreated, and the Timer Service back up and running, the folder will be populated with XML files, the timer service will stop crashing, and finally timer jobs will start showing up as scheduled and running.
Microsoft has released the SharePoint 2013 with Service Pack 1 ISOs (including Project Server and Office Web Apps). These ISOs are required for Windows Server 2012 R2 support as it includes an updated prerequisite installer, which does not ship with the normal Service Pack binary. The new ISOs are available via MSDN Subscriptions and while I do not have access, likely the Volume License center as well.
You may have a SharePoint installation where the servers have no Internet access. In this case, it is typically required that you run the prereqinstaller.exe with switches pointing to the binaries. But what if you didn’t know where to get the binaries, such as WCF Data Services 5.6 now required by the SharePoint 2013 with Service Pack 1 installer? Simple! Use one of two programs: Strings or Process Explorer. Both of these processes can be done on any 64bit Windows computer. With Strings, simply mount the ISO or extract the contents to disk and run strings using the -u switch (Unicode) against the executable: [crayon-533baf2b7fd8a086626701/] The result is: Alternatively, execute the prerequisiteinstaller.exe. On an unsupported Operating System (e.g., Windows 8) it will report that the tool does not support the current operating system. That’s OK, just leave it running. Next, run Process Explorer “As Administrator” and find prerequisiteinstaller.exe in the Process list. Right click and go to Properties (or double-click), then select the Strings tab. Make sure the Image button is selected, and search for “http://go”. All of the download links are grouped into this single section of the image. Alternatively, you can save the strings to text and search the text file. Now you now how to find all of the pre-requisite download URLs!
The Name property in the User Profile Service Application (also known as PreferredName) controls how a user’s friendly name will appear within the UPA (and by extension, SharePoint). By default, this property is mapped to a Synchronization Connection’s displayName attribute. Changing the Name property from the displayName attribute to another attribute will cause the Name property’s mapping to disappear on a restart of the User Profile Synchronization Service (for example, during reprovisioning after a full farm backup has taken place). If the SharePoint administrator then attempts to change the Name property mapping back to the displayName attribute, the mapping will also disappear during reprovisioning. The reasoning for this happening is that by default, SharePoint creates the Name property with the following flow using the displayName attribute: When changing the Name property to a new attribute, the flow is changed like so (in this particular case, the displayName attribute mapping was remove, and re-added, returning back to Manage User Properties in between each edit): Note the metaverse attribute is now PreferredName. Because this is a Direct mapping, it no longer correlates to the Name property in use by the UPA. Any changes to the Name property moving forward will change this new Direct mapping, rather than the proper Extension mapping. As a result, the Name property will appear to have no mapping: To resolve this issue, delete and recreate the Synchronization Connection. The default mapping will be restored and will not disappear on UPSS reprovisioning. As a result, I’d recommend not adjusting the mapping of this property. This issue was validated in SharePoint 2013 SP1.
The post Name User Profile Property Mapping Blank After Reprovisioning appeared first on Nauplius.
The April 2014 Cumulative Update for SharePoint 2010 has been released. SharePoint Foundation: http://support.microsoft.com/kb/2878270 SharePoint Server 2010: http://support.microsoft.com/kb/2878250 Project Server 2010: http://support.microsoft.com/kb/2878266, http://support.microsoft.com/kb/2878259 Office 2010 April 2014 Cumulative Updates: http://support.microsoft.com/kb/2953732
The April 2014 Cumulative Update for SharePoint 2013 has been released. SharePoint Foundation: Not released yet SharePoint Server 2013: Not released yet Project Server 2013: http://support.microsoft.com/kb/2863881 Office Web Apps Server 2013: http://support.microsoft.com/kb/2863899 Office 2013 April 2014 Cumulative Updates: http://support.microsoft.com/kb/2953733