# Active Directory Active Directory is Microsoft's directory service for identities, computers, groups, and policy; it matters here as an institutional naming and authentication layer. ## Historical and Technical Context The page fuses three administrative strata: directory/network naming, Apple database internals, and blockchain node processes. In Algorand’s node architecture, `algod` is the node daemon, while `kmd` is the key-management daemon responsible for generating/importing spending keys, signing transactions, and mediating key storage; it can run separately from the network-facing node to isolate keys. [S08] The handwritten distinction between “algod” and a “special wallet” shows the author approaching a crucial systems principle: **separate consensus/network participation from custody of signing authority**. The Core Data fields above it suggest the same epistemic technique as page 4—discovering system boundaries through internal names. ## Role in Scanned_20260730-1802 The primary identifying evidence appears on PDF page 6. A lined page of acronyms and field names. The top begins with plain-language expansions, the middle returns to `Z`-prefixed database notation, and the lower boxed cluster introduces Algorand components. Arrows connect “algod” to wallet-related text. Within that page, Active Directory helps the notebook move from a visible name or artifact toward the underlying identity, protocol, ownership, or control structure. ## Notebook Evidence - `Scanned_20260730-1802.pdf`, PDF page 6: "AD active directory" **Evidentiary status:** Visible evidence: correct expansion of KMD and explicit Algorand developer-portal note. Verified fact: KMD handles keys and signing. Strong inference: the author was studying configuration files and daemon separation, not trading or price speculation. The canonical name **Active Directory** is normalized outside the quotations. The quoted lines preserve the completed reconstruction's spelling, capitalization, and uncertainty markers. ## Relationships On PDF page 6, Active Directory appears in the same evidentiary cluster as [[Over-the-Air Update|Over-the-Air Update]], [[Fully Qualified Domain Name|Fully Qualified Domain Name]], [[Core Data|Core Data]], [[Algorand|Algorand]], [[Key Management Daemon|Key Management Daemon]]. These links record page-level proximity and the reconstruction's systems map; they do not by themselves prove corporate ownership or a direct technical dependency. ## Cross-Notebook Significance This page is an early bridge between device administration and cryptographic custody. It anticipates later collection-wide interest in identity, continuity accounting, blockchain, and distributed trust. ## Scanned_20260730-1706 Overlay **Source overlay:** [[Scanned_20260730-1706|Scanned_20260730-1706]] (specific PDF page references follow). `Scanned_20260730-1706.pdf`, PDF page 39 moves from the abbreviated directory reference on `Scanned_20260730-1802.pdf`, page 6 into a concrete privilege question: “allow administration by groups: enterprise admins.” The newer source therefore clarifies the earlier note’s directory layer as Windows forest-level administration rather than only a naming acronym. [[Enterprise Admins|Enterprise Admins]] is highly privileged; proximity does not prove that any account held that role. ## Missed Signals and Open Leads Resolve whether “Kmd Config” is Algorand’s KMD configuration or an unrelated kernel-mode driver abbreviation. Verify the `Z...` fields against the database on pages 4-6. Determine what “Volume Configmanager” referred to. ## Sources - [[Scanned_20260730-1802|Scanned_20260730-1802]], especially PDF page 6. - `Scanned_20260730-1802.pdf`, cited as a plain archival filename; the PDF is not stored in `wiki-notes`. - **[S08]** Algorand Developer Portal, “Node Artifacts”. https://dev.algorand.co/nodes/reference/artifacts/ ## Scanned_20260730-1659 overlay **Source evidence:** [[Scanned_20260730-1659#PDF page 11 — TPM 2.0 and cloud identity directories|page 11]], [[Scanned_20260730-1659#PDF page 62 — Microsoft Exchange, Workspace, Azure, and domain renewals|page 62]]. [[Trusted Platform Module|TPM 2.0]] supplies protected cryptographic operations and measured-boot state; `tpm.msc` is a Windows management console. [[Active Directory|Active Directory]] is Microsoft's on-premises directory; `Azure AD` is normalized to [[Microsoft Entra ID|Microsoft Entra ID]]. [[Okta|Okta]], [[OneLogin|OneLogin]], and Google directory tooling are cloud/federated identity alternatives. **Relationship overlay:** [[Access Token|Access Token]] · [[Domain Renewal|Domain Renewal]] · [[Google Cloud Directory Sync|Google Cloud Directory Sync]] · [[Google Workspace|Google Workspace]] · [[Microsoft Azure|Microsoft Azure]] · [[Microsoft Entra ID|Microsoft Entra ID]] · [[Microsoft Exchange|Microsoft Exchange]] · [[Okta|Okta]] · [[OneLogin|OneLogin]] · [PERSON REDACTED] · [[Trusted Platform Module|Trusted Platform Module]]. This evidence supplements rather than replaces earlier notebook interpretations. It connects the existing note to [[Identity Continuity|identity continuity]], [[Device Sovereignty|device sovereignty]], and [[Scanned_20260730-1659|Scanned_20260730-1659]].