<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Saul Rodgers</title><link>https://saulrodgers.net/</link><description>Recent content on Saul Rodgers</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 29 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://saulrodgers.net/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Entra ID Connect Sync - Connected data source error code 5</title><link>https://saulrodgers.net/posts/entraconnectsync-permissionissue-connecteddatasource-5/</link><pubDate>Thu, 29 Jan 2026 00:00:00 +0000</pubDate><guid>https://saulrodgers.net/posts/entraconnectsync-permissionissue-connecteddatasource-5/</guid><description>&lt;p>Today I had come across a new error I had not previously experienced where only some of the Microsoft 365 Groups were not writting back to our on-premises Active Directory anymore. This issue was the loverly &amp;ldquo;permission-issue&amp;rdquo; but with the Connected data source error code: &amp;ldquo;5&amp;rdquo;.&lt;/p>
&lt;p>While I have not been able to pinpoint the root cause of this error starting (will update if I find out), I was able to work out the solution.&lt;/p></description></item><item><title>Fixing Repeater IDing on AllStarLink 3 (the Right Way?)</title><link>https://saulrodgers.net/posts/allstarlinkv3-identing/</link><pubDate>Sat, 26 Apr 2025 00:00:00 +0000</pubDate><guid>https://saulrodgers.net/posts/allstarlinkv3-identing/</guid><description>&lt;p>A couple of months back, I switched from &lt;a href="https://www.hamvoip.org/" class="external-link" target="_blank" rel="noopener">HamVoIP&lt;/a> over to &lt;a href="https://www.allstarlink.org/" class="external-link" target="_blank" rel="noopener">AllStarLink v3&lt;/a>. Main reason? I wanted updated software to reduce the risk of compromise—especially since I&amp;rsquo;m port forwarding IAX from the open internet. Makes sense, right?&lt;/p>
&lt;p>Now, this post isn’t about installing AllStarLink 3 from scratch (that’s already covered &lt;a href="https://allstarlink.github.io/user-guide/pi-detailed/" class="external-link" target="_blank" rel="noopener">here&lt;/a>. Instead, I want to talk about getting identing working properly. Why? Because here in VK (Australia, for those outside the ham world), we’re required to ID every 10 minutes when transmitting, or when running a repeater or simplex &amp;ldquo;hotspot.&amp;rdquo;&lt;/p></description></item><item><title>Projects</title><link>https://saulrodgers.net/projects/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://saulrodgers.net/projects/</guid><description>&lt;p>Nothing to see here&amp;hellip; Yet 😉&lt;/p></description></item></channel></rss>