Which URLs must be configured on a firewall/ proxy in order to run a diagnostic package?
30/06/2015 Leave a comment
https://support.microsoft.com/en-us/kb/2598970
The following URLs are accessed when you run a diagnostic package:
All my posts are provided "AS IS" with no warranties, and confer no rights.
30/06/2015 Leave a comment
https://support.microsoft.com/en-us/kb/2598970
The following URLs are accessed when you run a diagnostic package:
27/06/2015 Leave a comment
The new APIs that are available to help with migrations moving forward
We have great documentation that talks through what it means to be blocked, how to look for it (HTTP 429s), and how to avoid it at https://msdn.microsoft.com/en-us/library/office/dn889829.aspx.
SPO Migration PowerShell cmdlets are designed to move on-premises content from file shares and SharePoint Server libraries and One Drive to SharePoint Online and OneDrive for Business. Requiring minimal CSOM calls, it leverages Azure temporary BLOB storage to scale to the demand of large migration of data content.
SPO Migration User Guide: https://technet.microsoft.com/en-us/library/mt203923.aspx
Video of the new API : https://channel9.msdn.com/Events/Ignite/2015/BRK3153
CreateMigrationJob: https://msdn.microsoft.com/en-us/library/office/microsoft.sharepoint.client.site.createmigrationjob.aspx
DeleteMigrationJob: https://msdn.microsoft.com/EN-US/library/office/microsoft.sharepoint.client.site.deletemigrationjob.aspx
GetMigrationJobStatus: https://msdn.microsoft.com/EN-US/library/office/microsoft.sharepoint.client.site.getmigrationjobstatus.aspx
Doc for the PowerShell Commands : https://technet.microsoft.com/en-us/library/mt143608.aspx
(Special thanks for my colleague Dustin)
12/06/2015 Leave a comment
Heads up , Technet Distributed Cache Articles are updated !
Plan for feeds and the Distributed Cache service in SharePoint Server 2013
https://technet.microsoft.com/en-us/library/jj219572.aspx
Microsoft has updated the following sections:
• Capacity planning for the Distributed Cache service
• Memory allocation
The memory issues have been noted here. Now we are requiring at least 34GB of memory for 16Gb Cache Servers. If more than 16GB’s are required, we now require at least 2 cache servers
Manage the Distributed Cache service in SharePoint Server 2013
https://technet.microsoft.com/en-us/library/jj219613.aspx
Microsoft has updated the following section:
*Fine-tune the Distributed Cache service by using a Windows PowerShell script
*Changed the Graceful Shutdown procedure
In the “Fine-tune the Distributed Cache” section we called out the MaxConnectionsToServer issue and have a script to tune these settings. We are also tuning the “DistributedLogonTokenCache” and “DistributedViewStateCache” as the defaults are too small.
This should eventually eliminate many support cases that occur after customers follow bad advice from random Blogs and utilize default settings.
15/05/2015 Leave a comment
Well , It depends .
If you have a Workflow Manager farm (more than one server) and one of the WFM EndPoints recieve a request without any load balancer ,it balances the load across the WFM servers .Yes thats correct . WFM farm have an internal load balancing mechanizm to do that.
But if you don’t use a load balancer ,WFM only balance the load , not switch between endpoints if active endpoint dies . There is only one endpoint be active at a time . And if something happens on that EndPoint or its host machine then you may face an outage even your other servers are alive. Because SharePoint knows only one endpoint url and it is not reachable.

So it depends that how much you want a high availability . Actually in real , load balancer is resposible not to share load , just keeps high availability if an endpoint dies between your SharePoint farm and WFM farm .