I decided to move myself off Wordpress to something simpler since this blog has been laying inactive for a long while.
New blog is running on Writefreely. Which is a nice project for simple blogging.
All previous content has been copied over with a quick conversion to fit the new format.
No content has been edited beyond that.
There are many guides out there on how to implement Kerberos for application x-y-x.
But there are surprisingly few going into some of details that are important for the understanding what you are doing exactly.
So with this article I am going to hopefully help you understand how Kerberos works in a general sense, and that is not as difficult to implement as you might think (as long as you have the all the pieces of the puzzle).
Occasionally there are times when the solution seems correct since it fixes the issue there and then. But then it turns out you where looking in the entirely wrong place.....
So here is a quick one; ever had issues with DFS (Distributed File System) share being unable to resolve their name properly at seemingly random times?
If the answer is yes, here is a quick solution to test: Try appending a “.” (dot) at the end of the fully qualified domain. So \\anitblog.no\DFSRoot would become \\anitblog.no.\DFSRoot.
The reason for this is that appending the dot to a FQDN makes it an absolute query instead of an relative one.
I stumbled into an issue recently with Thunderbolt enabled computers.
By default the Thunderbolt Software that is used to approve Thunderbolt devices requires local administrator to work, this is not really practical in enterprise environments where most users are not local administrators.
So i dug into it and found some solutions to this issue.
The data you get from using Get-CIMInstance is rarely directly modifiable as the data returned is usually a snapshot of deeper system settings. To change this you will need to use the methods provided by the Class you are looking at.
So for my fist post on this blog i'll write some musings about PowerShell and using the WMI and CIM cmdlets.
WMI is the backbone of most PowerShell cmdlets that interact with system settings (and C# as well). And they are a powerful tool for collecting data and making system changes.