Once in a while you can bump into a warning from K2 Setup Manager which says: “The selected user needs to have Domain Users privileges to proceed” on K2 Site Application Pool Configuration which looks as shown below:
I was not able to confirm what exactly triggers this, but I do know that it happens while specified user in fact has Domain User group membership and I saw it with both K2 4.6.x and K2 Five installers. Good news that bypass this blocking warning is easy – you just need to edit Product.config file in your installation directory and set domainusercheck value to false as shown below:
You will need to restart K2 Setup Manager after saving this change and you should be able to proceed without receiving any any warnings.
So with new wave of releases from Microsoft we now have Visual Studio 2015 and Windows 10 amongst other things, and depending on what you do you may be more excited about one or another of these two. But what is common between VS 2015 and Windows 10 they all come with .NET 4.6. There is much more in these new versions, but for example for Windows 10 two salient features you will notice are built in .NET 4.6 and Edge browser.
Now to K2. Upcoming 4.6.11 release promises us full support of Windows 10 (excluding Edge browser), but there is an interesting thing with old versions of K2 and .NET 4.6. In case you are doing development for older versions of K2 platform you may want to use Windows 10 and/or Visual Studio 2015 on your development workstation and this may pose a small issue.
Here is screenshot from clean Windows 8.1 Enterprise machine on which Visual Studio 2015 installed. This is what we have in terms of .NET on this machine:
As you can see we have .NET 4.5 as well as .NET 4.6 installed. But here is what K2 Setup Manager 4.6.8 thinks about this:
So you don’t have .NET Framework 4.5 🙂 Some other applications may have issues with detecting your .NET version with advent of 4.6, but as Microsoft says in such cases “if app was written accordingly to our recommendations you won’t have any issues.” You may read up a bit about this in the related blog post at Aaron Stebner’s WebLog.
No worries – you will see this only with 4.6.8 and earlier versions, starting from 4.6.9 and onwards .NET detection works OK whether you have .NET 4.6 or not. You may also contact K2 support to obtain a coldfix for K2 setup manager 4.6.8 which will will solve this issue.