A certification from a different era
My first technical certification was not Microsoft, Azure, security, compliance, or AI. It was the Novell NetWare 4.0 Certified NetWare Administrator credential.
That was nearly 30 years ago, and it represents a very different chapter in enterprise technology. Before Microsoft 365, Entra ID, Intune, Defender, Copilot, Azure, or modern cloud identity, many organizations ran their daily business on local area networks built around file servers, print queues, login scripts, mapped drives, and shared applications.
For people who entered IT later, NetWare may sound like a museum piece. For those of us who worked through that era, it was foundational. It was the network. If the server was unavailable, users felt it immediately. Files were unreachable. Printers stopped working. Line-of-business applications could not be launched. The network administrator was not just managing technology; they were protecting daily business operations.
Why NetWare mattered
Novell NetWare was a network operating system developed by Novell, Inc. It began in the early 1980s and became one of the dominant platforms for PC-based networking. It was especially known for file and print services, centralized access control, and strong performance in local area network environments.
In the early and mid-1990s, NetWare was everywhere in business computing. Organizations needed reliable ways to connect desktop PCs to shared resources. NetWare provided that platform. Users authenticated to the network, accessed shared volumes, printed to network printers, and worked from centralized resources long before cloud services became the default conversation.
The release of NetWare 4.0 was especially important because it introduced NetWare Directory Services, commonly known as NDS. NDS replaced the older bindery model with a global, distributed directory that could represent users, groups, servers, volumes, printers, and other network resources in a more centralized and scalable structure.
Looking back now, it is hard not to see the connection between those early directory concepts and the identity platforms that followed. NDS exposed administrators to ideas that are still relevant today: centralized identity, directory objects, delegated administration, replication, resource rights, authentication, and user context.
Learning without the modern safety net
The certification journey itself was very different from certification preparation today.
There was no Microsoft Learn. There were no cloud-hosted labs available on demand. There were no YouTube walkthroughs for every topic. There were no AI assistants to explain an error message, summarize a configuration path, or help generate a troubleshooting checklist.
Learning was often built around printed manuals, classroom training, instructor-led labs, practice exams, and hands-on work with actual equipment. You learned by installing, configuring, breaking, repairing, and repeating.
That kind of learning created a strong respect for fundamentals. You could not simply click through a portal and hope a policy worked. You had to understand what the server was doing, how authentication worked, where rights were assigned, how print queues were configured, how users were organized, and why a login script behaved differently for one person than another.
What the NetWare chapter taught me
The products have changed dramatically, but many of the lessons from that first certification still apply.
Identity comes first
The longer I work in IT, the more convinced I am that identity is the control plane for almost everything else.
In the NetWare world, that meant understanding users, groups, rights, containers, objects, and directory context. Today, it means understanding Microsoft Entra ID, Conditional Access, MFA, Privileged Identity Management, device compliance, app access, and identity governance.
The names have changed. The cloud has changed the architecture. The principle remains the same: know who the user is, understand what they should access, and apply controls consistently.
Infrastructure exists to serve users
NetWare environments made this very clear. If users could not access files, print documents, or launch applications, the technology had failed from their perspective.
That lesson still matters. Whether I am working through a Microsoft 365 migration, an Intune deployment, a Defender rollout, a SharePoint permission design, or a compliance configuration, the goal is not simply to make the platform technically correct. The goal is to make it reliable, secure, supportable, and usable.
Documentation is not optional
Directory structures, server names, volumes, printer mappings, login scripts, administrative rights, and backup routines all needed documentation. When something failed, documentation helped separate guessing from troubleshooting.
That has not changed. In modern Microsoft 365 environments, the same principle applies to Conditional Access policies, Intune profiles, Defender settings, Purview configurations, SharePoint permission models, tenant migration plans, and licensing decisions.
A well-documented environment is easier to support, easier to secure, easier to audit, and easier to hand off.
Fundamentals outlast products
NetWare is no longer the platform sitting at the center of most organizations. The industry moved on. Microsoft Active Directory became dominant, cloud identity changed the management model again, and today many conversations are centered around Microsoft Entra ID, Zero Trust, SaaS governance, endpoint management, and AI-assisted administration.
But the fundamentals did not disappear.
- Authentication still matters.
- Authorization still matters.
- Change control still matters.
- Backup and recovery still matter.
- User experience still matters.
- Documentation still matters.
- Operational discipline still matters.
That is one of the most important lessons from a long career in technology. Products will come and go. Interfaces will change. Licensing models will change. Acronyms will change. But the people who remain effective are usually the ones who understand the underlying principles.
From NetWare to Microsoft 365
It is interesting to look at the arc from that first certification to the work I do today.
Back then, the focus was on network operating systems, local servers, directory trees, mapped drives, print queues, and LAN administration. Today, my work is centered on Microsoft 365 security, compliance, identity, endpoint management, tenant migrations, Power Platform solutions, and cloud governance.
At first glance, those worlds look completely different. In many ways, they are. But when you step back, the core questions are familiar:
- Who should have access?
- How is that access granted?
- How is it monitored?
- How do we protect sensitive data?
- How do we recover when something breaks?
- How do we make the user experience workable?
- How do we keep the environment supportable over time?
Those questions were relevant in a NetWare 4.0 environment, and they are still relevant in a Microsoft 365 tenant today.
Why first certifications matter
Your first certification may not end up being the most advanced credential you ever earn. It may not be the one that stays on your resume forever. It may not map cleanly to the technology you use 10, 20, or 30 years later.
But it can still be one of the most important.
That first certification validates more than a product skill. It proves that you can study technical material, build hands-on understanding, sit for an exam, and commit yourself to professional growth. It creates momentum. It builds confidence. It opens the door to the next learning path.
For me, Novell NetWare 4.0 was that starting point. It was the first formal checkpoint in what became a long career of learning, adapting, troubleshooting, building, securing, migrating, and helping organizations make technology work better.
Thirty years later
Thirty years later, I am still studying. I am still earning certifications. I am still learning new platforms. I am still watching the industry reinvent old ideas in new ways.
That is one of the things I enjoy most about IT. The work changes constantly, but the learning never stops.
My first certification was Novell NetWare 4.0 Certified NetWare Administrator. It came from a very different era of enterprise computing, but the lessons from that chapter still influence how I think about modern identity, security, documentation, and operational readiness.
Everyone starts somewhere.
For me, it started with NetWare.
Historical references
For readers interested in the historical background, NetWare is covered in the public NetWare historical overview, and Novell's original 1993 AppNote on NetWare 4.0 highlights the introduction of NetWare Directory Services and other major platform features.