<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rss/1.0/modules/syndication/" xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:wfw="https://wellformedweb.org/CommentAPI/" xmlns:slash="https://purl.org/rss/1.0/modules/slash/"
  version="2.0">
  <channel>
    <title>I Have a Cunning Plan...</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/antgut/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/antgut/feed.xml</link>
    <description>The Inane Ramblings Of A Dysfunctional IT Geek</description>
    <lastBuildDate>Wed, 17 Apr 2019 03:44:27 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>Where Did AntGut Go?</title>
      <link>https://docs.microsoft.com/archive/blogs/antgut/where-did-antgut-go</link>
      <pubDate>Mon, 17 Sep 2018 09:24:10 GMT</pubDate>
      <dc:creator><![CDATA[AntGut]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/antgut/?p=425</guid>
      <description><![CDATA[With the passing of time, things change. It's inevitable. In IT, this seems to be even more...]]></description>
      <content:encoded><![CDATA[With the passing of time, things change. It's inevitable. In IT, this seems to be even more accelerated than the "real world" and very little if anything can remain static and relevant at the same time. Some historians believe that purging these "dead" artefacts from the digital world may be detrimental to our future generations. Unlike stone tablets, papyrus and books that provide contextual reference and cross-correlation, this won't be the case for the untold amounts of digital information that are deleted. Those helpful hints, snippets of conversation, banter, etc. are just gone, leaving holes in the connectivity of our cumulative history.

Wait... This is supposed to be a technical blog with the occasional personal spin. Where is my brain?!?!

After that weird little tangent I have to refocus on the issue at hand and it basically comes down to this...

For a number of reasons (that will eventually come to light), I'm moving my stuff to my personal WordPress site, <a href="https://antgut.wordpress.com/">AntGut.WordPress.com</a>. See ya there!!!]]></content:encoded>
    </item>
    <item>
      <title>SPS 2013, Host Name Site Collection Caching Fix in KB 3114945</title>
      <link>https://docs.microsoft.com/archive/blogs/antgut/sps-2013-host-name-site-collection-caching-fix-in-kb-3114945</link>
      <pubDate>Fri, 16 Feb 2018 15:04:32 GMT</pubDate>
      <dc:creator><![CDATA[AntGut]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/antgut/?p=65</guid>
      <description><![CDATA[Short and to the point...

KB 3114945 (April 12, 2016, update for SharePoint Foundation 2013)...]]></description>
      <content:encoded><![CDATA[Short and to the point...

<a href="https://support.microsoft.com/en-us/help/3114945">KB 3114945</a> (April 12, 2016, update for SharePoint Foundation 2013) lists the following issue as being fixed:

<em>Assume that you sign in a host name site collection and then other site collections in the same web application. If the host name site collection is deleted and the cached user token is still valid, you receive an error message on later attempts to access remaining site collections.</em>

What the article does <span style="text-decoration: underline">not</span> include is the method for enabling this fix!!!

To do so, execute the following:

<p style="padding-left: 30px"><pre><span style="color: #339966"># This setting affects the whole farm.</span>
<span style="color: #ff0000">$sts</span> <span style="color: #808080">=</span> <span style="color: #0000ff">Get-SPSecurityTokenServiceConfig</span>
<span style="color: #ff0000">$sts<span style="color: #808080">.</span></span><span style="color: #000000">WindowsModeIgnoreCache</span> <span style="color: #808080">=</span> <span style="color: #ff0000">$true</span>
<span style="color: #ff0000">$sts<span style="color: #808080">.</span></span><span style="color: #000000">Update()</span></pre>

Thanks to <a href="https://blogs.msdn.microsoft.com/josrod">Joe Rogers</a> for the info.]]></content:encoded>
    </item>
    <item>
      <title>Announcement: Upcoming Release - Daughter 2017</title>
      <link>https://docs.microsoft.com/archive/blogs/antgut/announcement-upcoming-release-daughter-2017</link>
      <pubDate>Mon, 30 Oct 2017 10:40:08 GMT</pubDate>
      <dc:creator><![CDATA[AntGut]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/antgut/?p=55</guid>
      <description><![CDATA[Not necessarily "tech", but figure this would be a good "first post."

So, about 4 months ago...]]></description>
      <content:encoded><![CDATA[Not necessarily "tech", but figure this would be a good "first post."

So, about 4 months ago (late June), I sent the following email out (MS-internal)...
<blockquote><span style="color: #000000;font-family: Calibri">Proud to announce that Casa de Gutierrez is well over a third of the way through developing Daughter 2017. Official RTW (release to world) is Dec 5, but as with previous products (Daughter 2008 and Daughter 2009), delivery will be scheduled 1-2 weeks earlier (sometime between Nov 20 &amp; Nov 30). Final date to be determined by delivery management team with consideration of product maturity, holidays and other contributing factors.</span>

<span style="color: #000000;font-family: Calibri">At that time, potentially a few days prior, I will commence work-stoppage and assume responsibility for all CDG operations; to ensure developer has no distractions, existing products are taken care of and CDG facilities are in proper order. This period of non-work will be approximately 6 weeks; resumption of "work" is tentatively scheduled on or about Jan 8, 2018. As it is still early in to the dev cycle, post-release product support requirements are unknown and limited staff on hand (no parent companies to rely on), this time-frame may change. Further details will be provided as new information is gathered.</span>

<span style="color: #000000;font-family: Calibri">All concerned parties are very happy. D08 &amp; D09 are very excited about D17. They did not want a dissimilar product type; this would have apparently caused major incompatibilities.</span>

<span style="color: #000000;font-family: Calibri">Note that the developer is doing well (no ill effects thus far) and product has met all milestones. Expectation is that this will continue to be the trend for the remainder of the dev cycle.</span></blockquote>
A bit scary, but we are now 31 days out from RTW (Nov 30)! Work-stoppage officially starts Nov 17, so we will hopefully be prepared. Otherwise, everything appears to be on track and good to go. Exciting times!!!

More to follow...]]></content:encoded>
    </item>
  </channel>
</rss>