2019 is here but there are a lot of companies still running on SharePoint 2010 which is going to be out of extended support in October 2020 and that should be enough to make a decision and then a migration either to SharePoint 2019 or Office 365.
Recently, one of my clients reported an issue where they were not able to access their SharePoint 2010 on Windows Server 2008 R2. It was really interesting that only some users were affected and it’s turned out that it wasn’t working just for local members of local “Administrators” group.
In short, there was an issue with a Microsoft update KB4480970 released on January 8, 2019 and then 3 days later Microsoft release a fix for it KB4487345.
Microsoft just launched a solution to launch and scale a freelance workforce in an Org. Basically, the idea is really nice and simple and includes these areas
Of course, all of these are covered by Office 365, i.e. SharePoint, Teams, Power BI and Flow.
For me, it’s interesting to see that Microsoft is trying to show the value for clients and to show how different products could work like a single solution. And it’s worth to mention that it’s available for free for existing subscribers.
The SharePointDsc PowerShell module (formerly known as xSharePoint) provides DSC resources that can be used to deploy and manage a SharePoint farm.
This new major release contains many improvements/fixes, including several breaking changes! So, if you are upgrading from an earlier version of SharePointDsc, please make sure you update your existing configurations
I was writing about this tool before here and just experience the issue where I’ve realized it doesn’t work under Admin account and looks like there is no way to fix that. So, in my case, the tool wasn’t able to create logs folders because of this issue and I was able to do that using a separate box where another user account wasn’t limited by UAC.
Note: this issue was verified for version 220.127.116.11 and could be fixed later but there is no any guarantee on that.