Discussion Locked

Novell Guy Learning Windows

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm a Novell/Linux guy. Inside my house there is a little alter. A red "N" sits amid burning candles. On the wall behind the "N", is a velvet Elvis poster. This is not your standard poster. Photoshop has been used. Elvis is wearing a t-shirt that says "Provo Rocks on the front." On the back it says, "I will never lose my mind, it's stored in eDirectory." On his guitar there must be fifty little penguin stickers...and one little sticker that says "Novell YES CERTIFIED".
You get the picture, my blood runs Novell Red. Now I'm learning Windows server 2003. I'm starting with the 70-294 Active directory. Every page I turn, I bob my head like Wanda Sykes and say "Oh No You D-int." Active directory is a truncated, scaled down, limited, version of eDirectory. The nomenclature itself serves to obscure the real processes. For example, lets look at "Trust Relationships." Hmmm... OK they got stuck with this nomenclature back in the NT days and can't bring themselves to change it. What a "Domain" is today is an OU. A trust relationship is putting another object on the ACL of the "Domain" OU. Period. Why have to identical objects with two different names (OU & Domain)? Because they must feel the Microsoft Administrators wouldn't be smart enough to go straight to using OU's. I imagine that when we are forced to upgrade to Windows Server 2011 Extreme Professional Datacenter version, they might drop the "Domain" Nomenclature. I'm MCSE NT, CNA, CNE, CNI certified.

1 reply

by robo_dev

I look back wistfully at the hours spent running compsurf, compiling the ARCNET drivers for the Netware 2.11 servers, making Token-Ring work with IBM PS/2 hardware. Ahh, those were the days....NLMs, NLMs. Ahhh the boxes and boxes of those orange and tan diskettes....

In so many ways, you wish that Windows had written their server products such that you could run the whole thing from the CLI. The Bindery and NDS is sooo much more advanced than the use of the Windows registry on any day, and a server bootup error would fail gracefully with a usable error message....not the horrible BSOD.

If only Novell had been quicker to adopt TCP/IP.

A game of Snipes, anyone?

This discussion is closed to new replies.