<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Enterprise on Le Site de François</title><link>https://lesitedefrancois.be/en/tags/enterprise/</link><description>Recent content in Enterprise on Le Site de François</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 François</copyright><atom:link href="https://lesitedefrancois.be/en/tags/enterprise/index.xml" rel="self" type="application/rss+xml"/><item><title>AD (Active Directory)</title><link>https://lesitedefrancois.be/en/security/ad/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/security/ad/</guid><description>&lt;p&gt;&lt;strong&gt;Active Directory (AD)&lt;/strong&gt; is Microsoft&amp;rsquo;s enterprise directory and identity platform, first released with Windows 2000 and now the dominant identity provider in enterprise environments worldwide. It combines four technologies into a single integrated system: &lt;strong&gt;LDAP&lt;/strong&gt; as the directory access protocol for querying and modifying identity data; &lt;strong&gt;Kerberos 5&lt;/strong&gt; as the authentication protocol for issuing tickets that prove identity without transmitting passwords; &lt;strong&gt;DNS&lt;/strong&gt; as the service location mechanism that clients use to discover domain controllers, Kerberos KDCs, and LDAP servers; and &lt;strong&gt;Group Policy&lt;/strong&gt; as the configuration management system that pushes security settings, software installation, and policy enforcement to every joined machine. These four components are inseparable in practice: a Linux host joining an AD domain receives a Kerberos principal in AD&amp;rsquo;s KDC, a machine account object in the AD LDAP directory, a DNS record for its hostname, and (optionally) Group Policy Objects applied to it. The AD forest is the trust boundary: multiple domains can exist within a forest and all share a common schema, configuration, and Global Catalog, with transitive Kerberos trust between them.&lt;/p&gt;</description></item><item><title>Private 5G</title><link>https://lesitedefrancois.be/en/telco/private-5g/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/telco/private-5g/</guid><description>&lt;p&gt;&lt;strong&gt;Private 5G&lt;/strong&gt; (also &lt;strong&gt;non-public 5G&lt;/strong&gt;, &lt;strong&gt;dedicated 5G&lt;/strong&gt;, or &lt;strong&gt;campus/industrial 5G&lt;/strong&gt;) denotes &lt;strong&gt;3GPP-conformant 5G systems&lt;/strong&gt; operated for a &lt;strong&gt;defined organisation or site&lt;/strong&gt; — factory, port, mine, hospital, stadium, or utility — rather than as a nationwide public mobile service. &lt;strong&gt;3GPP Release 16+&lt;/strong&gt; formalised &lt;strong&gt;Non-Public Networks (NPN)&lt;/strong&gt; with two principal models: &lt;strong&gt;Standalone NPN (SNPN)&lt;/strong&gt; — an isolated PLMN (dedicated &lt;strong&gt;MCC/MNC&lt;/strong&gt; or &lt;strong&gt;PLMN ID&lt;/strong&gt;) with its own &lt;strong&gt;5GC and NG-RAN&lt;/strong&gt;; and &lt;strong&gt;Public Network Integrated NPN (PNI-NPN)&lt;/strong&gt; — a &lt;strong&gt;slice&lt;/strong&gt; or dedicated &lt;strong&gt;DNN&lt;/strong&gt; on a &lt;strong&gt;public operator’s 5G&lt;/strong&gt; with contractual isolation. Private 5G delivers &lt;strong&gt;URLLC-capable&lt;/strong&gt; connectivity, &lt;strong&gt;local breakout&lt;/strong&gt; (traffic stays on-site via &lt;strong&gt;local UPF&lt;/strong&gt;), &lt;strong&gt;deterministic QoS&lt;/strong&gt;, and &lt;strong&gt;control&lt;/strong&gt; over upgrades and security policies — advantages over &lt;strong&gt;Wi-Fi 6/7&lt;/strong&gt; in mobility, scheduling, and industrial &lt;strong&gt;TSN&lt;/strong&gt; integration scenarios, at higher cost and regulatory complexity.&lt;/p&gt;</description></item></channel></rss>