||boek: MCSE Study Guide Windows NT Server & Workstation 4|Joe Cassad|Wayne Dalton|Steven Tate|Keith Bruno|New Riders Publishing

||door: Joe Casad, MS Certified Systems Engineer MCSE

||taal: en
||jaar: 1996
||druk: ?
||pag.: 1240p
||opm.: paperback|like new|possibly with CD

||isbn: 1-56205-549-6
||code: 1:002285

--- Over het boek (foto 1): MCSE Study Guide Windows NT Server & Workstation 4 ---

Readers will get expert tips and tricks from an MCSE and certified trainer on how to pass the Windows NT and Workstation 3.5X exams. Organized in a concise, easy-to-read manner that dispenses the most valuable information efficiently, this comprehensive study guide contains hundreds of tips, test questions, lists, tables, notes, and tricks to completely prepare the reader for the exams.

• Helps users build a solid understanding of the MCSE program, and ways to master Windows NT Server 3.5X and Windows Workstation 3.5X
• CD-ROM contains NT Server and Workstation test engines, plus hundreds of sample questions

[source: https--www.amazon.com]

Save your money - get a different book [1998-10-15]

On the road to becoming an MCSE this was the most expensive book I purchased - and the least useful. When I bought it, the MCSE training materials section of my local book store was pretty bare and this looked like the most comprehensive book. Luckily, there is now a much bigger selection now, so all you budding MCSE's can pick better books. So, why don't I like this book? Complaint #1) This book could be one third of the size (and price) and contain the same information. The first third of the book covers NT Workstation in detail, from the beginning of the installation to configuring everything. My complaint here is that it seems to be written for someone who has never even installed NT before. Well, if you haven't at least installed NT before, this book is not the ticket to passing the test - you WILL need some hands-on experience. Weeding out the non-MCSE level info would make this section half as long. Then the second third of the book is about NT Server, BUT - get this - everything covered in the NT Workstation section is repeated. There is only 30 pages of new information specifically about NT Server. Big waste! Finally, the last section (a little less than a third) has NT Server in the Enterprise info. Frankly, by the time I got to the NT Server in the Enterprise test, I had given up on this book. I did not use it as my study material. The parts that I have read had some good info along with some glaring factual errors. It looks like it covers about half of what you need to know for the Enterprise test. Here are my two other complaints (a little more briefly): Complaint #2) As mentioned above, there are factual errors throughout the book. I didn't highlight them in my book, so I can't give examples, but they are in there. Worst of all is the CD-ROM sample test - LOTS of the "correct" answers were wrong, and the ambiguousness of many of the questions made this sample test useless. Complaint #3) I have read lots of technical books, and no matter what the subject is, some are enjoyable to read and some put me to sleep. It is hard to quantify except that the sleep-inducing books tend to be more detailed, covering every option on every dialog box and lengthy, often unnecessary explanations of everything. This book is a definite sleeper! Enough said... My guess is that this book was just an attempt by NRP to get out the first, most comprehensive SEEMING, all-in-one MCSE study guide. Now there are several others, and one of the other ones MUST be better. But to make this criticism constructive, here is my suggestion to NRP - hack the first section down to half its size, keep only the 30 pages of new info in the second section and beef up the Enterprise part. Remove the long boring explanations, run it through a spell checker, have a couple of MCSEs read it and check out the facts, dump the useless CD and drop the price to $24.99. Jeremy

Jeremy A. Ellis [source: https--www.amazon.com]

Core topics to average depth, needs better sample questions [1997-08-19]

The book covers NT Server, Workstation, and Enterprise concepts. The included CD had Networking Essentials in PDF-format as an added bonus.

The Workstation and Server sections contained much repeated material--even the same typos, in some cases.

Sometimes the book dwelled on the details of particular actions: Selecting button x brings up window 1, which has y choices. Choice A does...

I'd rather have a book present something on a more conceptual level.

Sample test questions were marginal. The first few chapters included rationale with the correct answers--a big plus, but later chapters just had answers. Some appeared to come from Microsoft's certification roadmap, others were too easy to be from Microsoft. In some cases, two out of four answers could be ruled out immediately. I hope nobody testing for MCSE picks answers like:
"Give the user the Administrator password and..."

After reading the book, I don't feel comfortable taking the exams, so I'm looking for another book.

berringer@mail.utexas.edu [source: https--www.amazon.com]

An OK place to start [1997-12-31]

I have recently finished reading the WS and Server potions of this work. I have also briefly glanced at the Enterprise portions as well. While I agree with the other reviewers of this work that the content and edit quality of this book leave much to be desired, I can not totally trash this work. If you are a beginner to the NT arena you might consider purchasing this book. It is not that expensive considering what you get: a basic explanation of WS and Server with some Enterprise thrown in. In essence this work provides nothing more than a cursory introduction to the NT environment. To really understand this material you should purchase the specific Microsoft authorized work for whatever exam you plan to take.

By NO means should you use this book as your sole resource for passing the exams. (I have the pitiful scores and a $100 hole in my wallet to prove it).

THE SAMPLE QUESTIONS ARE ABSURDLY EASY. Beg, borrow, or steal a copy of the Transcender exams at all costs. They are the ONLY thing that will tell you if you are ready for the exams or not. Good Luck!

mattdegurse@hotmail.com [source: https--www.amazon.com]

Suitable as a door-stop [1998-07-30]

This book rambled and contained many factual errors. I would recommend this book to no one who was attempting to study for a Microsoft exam. Total waste of time and money. Buy the Sybex books instead.

Clark Alexander, MCSE, MCT clark@jftr.com [source: https--www.amazon.com]

Buy an approved guide and SKIP THIS BOOK! [1997-10-27]

The content of this book is TERRIBLE. Though intended for professionals seeking certification, the information, sketchy and shallow, is seemingly steered toward persons totally unfamiliar with Windows NT. Though I passed the certification exams, this book was little more than a guide that allowed me to reference other materials for in-depth information.

There are few things more irritating than a typo in a published book, and this book is FULL of them! I even found a pre-press typesetting heading in one of the section titles. A note to the publishers: Hire some editors!

Bottom line? Spend your money on something else!

Michael F. Maddox [source: https--www.amazon.com]

Does the Job [1998-03-07]

Basically, the value of any MCSE study guide is seen AFTER you take the test. This book got me through the core exams (an excellent value when you think of it). Although the Enterprise section could have been more extensive, I certainly recommend this book to anyone who wants to get certified... S.Hamel, C.L.S., M.C.S.E., Master C.N.E.

S. Hamel [source: https--www.amazon.com]

"Get it done well and get it done fast" are twin, apparently opposing, demands. Data architects are increasingly expected to deliver quality data models in challenging timeframes, and agile developers are increasingly expected to ensure that their solutions can be easily integrated with the data assets of the overall organization. If you need to deliver quality solutions despite exacting schedules, "The Nimble Elephant" will help by describing proven techniques that leverage the libraries of published data model patterns to rapidly assemble extensible and robust designs. The three sections in the book provide guidelines for applying the lessons to your own situation, so that you can apply the techniques and patterns immediately to your current assignments. The first section, Foundations for Data Agility, addresses some perceived aspects of friction between "data" and "agile" practitioners. As a starting point for resolving the differences, pattern levels of granularity are classified, and their interdependencies exposed. A context of various types of models is established (e.g. conceptual / logical / physical, and industry / enterprise / project), and you will learn how to customize patterns within specific model types. The second section, Steps Towards Data Agility, shares guidelines on generalizing and specializing, with cautions on the dangers of going too far. Creativity in using patterns beyond their intended purpose is encouraged. The short-term "You Ain't Gonna Need It" (YAGNI) philosophy of agile practitioners, and the longer-term strategic perspectives of architects, are compared and evaluated. Consideration is given to the potential of enterprise views contributing to project-specific models. Other topics include industry models, iterative modeling, creation of patterns when none exist, and patterns for rules-in-data. The section ends with a perspective on the modeler's possible role in agile projects, followed by a case study. The final section, A Bridge to the Land of Object Orientation, provides a pathway for re-skilling traditional data modelers who want to expand their options by actively engaging with the ranks of object-oriented developers.

[source: https--books.google.be]

Helps users build a solid understanding of the MCSE program, and ways to master Windows NT Server 3.5X and Windows Workstation 3.5X. CD-ROM contains NT Server and Workstation test engines, plus hundreds of sample questions. Covers Latest Version.

[source: https--www.bol.com]

--- Over (foto 2): Joe Casad ---

Joe Casad is an engineer, author, and editor who has written widely on computer networking and system administration. He has written or cowritten 12 books on computers and networking. He currently serves as editor-in-chief of Linux Pro Magazine and ADMIN Magazine. In a past life, he was the editor-in-chief of C/C++ Users Journal and the technical editor of Sysadmin Magazine.

[source: https--www.informit.com/authors/bio/BDA0923C-3585-4307-8A7B-629D5A1581A4]

Joe Casad is a writer, editor, engineer, and occasional gardener in Lawrence, KS. He is the Editor in Chief of Linux Pro Magazine and the author of SAMS Teach Yourself TCP/IP in 24 Hours.

[source: https--www.fosslife.org/user/19]

Joe Casad
As seen in: Linux Magazine, Admin Magazine

[source: https--muckrack.com/joe-casad/articles]

Cheers! Celebrating 20 years of Linux Magazine
Article from Issue 240/2020

Editor-in-chief Joe Casad reflects on the enchanting 20-year story of Linux Magazine.

I roll out of bed and start the coffee. The dog follows me around, expecting breakfast. I feed him; take a shower. It is still early and the first rays of sunlight are tangled in the trees over my neighbor's house. I pour a cup of coffee and sit at the desk in the small bedroom I use as my office ...start my Linux system, call up Slack, check my notes: 9 o'clock Zoom call?

Like many companies around the world, our office has gone all-virtual due to the COVID-19 pandemic. We meet together online once per week for a roundup of company news, but information passes between us all the time, all day, in email, texts, Zoom calls, and posts to workgroups. A publishing office is a frenetic place even on the slow days, and when it gets busy, it is impossible to imagine how it all can stay floating - text files, layout files, emails, author queries, and social media posts fly in every direction, and all the threads converge magically at a sacred moment when we upload the issue to the printer. I'm always amazed when nothing breaks, and the fact that we have smoothly navigated to a remote workday is a testament to our experience, versatility, and espirit de corps. But you see, it hasn't always been so virtual. Most of our years we have worked together face-to-face, and our vibrant office culture has always been a source of pride.

Linux Magazine launched way back in 2000. Our parent company at the time, Linux New Media AG, had been publishing a high-quality Linux magazine in Germany since the very early days of Linux. The founders had a vision for a network of magazines in different languages around the world - an international community like Linux itself - sharing information, expertise, and resources. At one point we had Linux Magazines in German, Polish, Romanian, Spanish, Brazilian Portuguese, and English - all published in tiny offices like ours with small budgets, but all cooperating and making the most of shared resources.

The original English edition was a joint venture with a company in the UK, and the founding editor was Julian Moss. At around the sixth issue, the torch passed to John Southern, who served as editor until I started with Issue 48. Somewhere around Issue 26, the publishing and layout gravitated back to the continent. The English team shared production and marketing resources with the parent company in Munich for a few years, but everyone knew that, when the time was right, they would look for a home in the English-speaking world.

When I first started, I was the only US employee and worked out of my basement in Lawrence, Kansas, editing and coordinating the production with the team back in Munich. The founders had originally wanted to put the U.S. headquarters on one of the coasts - wondering, as do many, what was in between - but the CEO visited Lawrence and quite liked it, conceding that the beer at our local brew pub was more than acceptable to the German palate. (That's a good sign, when people from Munich like your beer.)

Dirty Baby

Our official mascot is a baby doll we found in the fork of a tree one day outside of our office. Dirty baby shows up for all our parties and rarely behaves well. Visit Dirty Baby on Facebook at @itsdirtybaby.

After a couple years of toil, with circulation and ad sales trending up, we had gained enough momentum to open our first office in the US. At first it was just me and distinguished alumna Rikki Endsley, who started as managing editor and then became associate publisher when our publisher, Brian Osborn, a young American ex-pat with an infectious poker face and a rare knowledge of publishing on two continents, took on additional responsibilities at the corporate level. Our office was a one-room space above Buffalo Bob's Smokehouse. We had a big bank of windows that looked out on Massachusetts Street. (The main downtown street in Lawrence is called Massachusetts Street because the town was settled by radical abolitionists from Massachusetts in the 1850s.)

We worked hard, talked about life, and watched a lot of time go by, not just in our lives, but in the evolution of Linux. Our friends in the local publishing community would stop by to see our hip office space. I think they were all a little jealous about our cool gig putting out our own Linux magazine in our funky downtown office. One of the reasons for starting the company in Lawrence was the indigenous reserve of IT-publishing veterans who got their start at local companies like R&D Publications and CMP. Over the years, we've enticed several former co-workers to come and join us.

A couple times a year, Brian would come to town, often on his way to a tech conference or other event, and we would spend a week planning (more like scheming) about where we were going and what dragons we would be hunting next. With each issue, the whole thing felt more like a real company and less like an experiment. Gradually we brought in new services and capabilities, scaling up our operation. We launched our special edition series, added an off-site ad sales team, and increased our involvement with conferences and the open source community. At one particularly surreal moment, we had to occupy a temporary location at the back of the building so they could install a balcony on our office (how often does that happen?). We put out the first edition of The Shell Handbook crammed into a tiny windowless cubicle previously used by a psychotherapist while they crashed down the facade and installed the balcony. The balcony was super cool and made our friends even more jealous, but when our population rose to four in our little one-room space, we knew it was time to find another home.

Our next office was a house converted into an office building that was on a street a couple blocks off the downtown. The building had a big front porch and looked out on a park. The park had a large decommissioned steam locomotive that I could see from my desk at a second-story window. When I was a kid, they let you climb all over that train, poking around and exploring the mechanical crannies. Now there was a big fence around the train, so you couldn't just go poking around on it, but that was OK with me, I often thought, because now I get to poke around on Linux.

We expanded our scope considerably during the train park years, with newsletters, websites, custom content, and lots more stories to tell. Like the time a distributor went bankrupt and left three months of magazines stranded in a warehouse, or the time we were threatened by a patent troll who claimed he had a patent on attaching a DVD to a magazine. And then there was the episode when the DVD company accidentally put a porno film on some of the UK copies of the DVD. We have weathered every crisis together with a rare combination of aptitude and attitude that would be the envy of any small company.
Amy and Megan are our stalwart final defense against the solecistic and labyrinthine.

Eventually, the global organization split up, and the English-language operation spun off to become a separate company. It's just us now, although we still collaborate with some of our former international counterparts. We've moved from the train park office to another location in a fancier part of town that isn't quite as bohemian, but it sure is easier to find a parking place.

I'm struck by how much Linux has changed since I started this job - and how the publishing industry has itself remained in a perpetual state of reinvention. It is one thing when the subject of the magazine is continually transforming - and quite another when the very context in which you operate is a moving target. There's no doubt in my mind that the secret to our success is our hard-working team of professionals, who stay calm under pressure and show up every day with ideas and good energy: They never say "no"; they just start thinking about how.

When I look back over my years at Linux New Media, I remember lots of great magazines and lots of grace under fire. I remember fabulous Christmas parties and afternoon escapes to Dempsey's tavern. I recall the kids who have been around the office through the years and adorned our walls with their art - including my own kids, who are now well into their 20s, as well as our pets, and even our parents. Birthday snacks, Valentine cards, meeting-day pizzas, and warm nights watching the 4th of July fireworks from the alley ...

Through the years, I've had the privilege of watching the rise of the Linux community with a special little community of battle-worn pirates at Linux New Media. Happy 20 years everybody. Here's to 20 more.

Joe Casad [source: https--www.linux-magazine.com/Issues/2020/240/20-Years-of-Linux-Magazine]

--- Over (foto 3): MS Certified Systems Engineer MCSE ---

An MCSE (Microsoft Certified Systems Engineer) is someone who has passed exams about the Microsoft Windows NT operating system, related desktop systems, networking, and Microsoft's BackOffice server products. To prepare for the exams, you can take courses at a certified training company location, in certified courses in a high school or college, or through self-study at Microsoft's self-study Web site or through certified training materials.

The MCSE program is the most popular of a set of training programs that Microsoft calls the Microsoft Certified Professional (MCP). In other MCP programs, you can gain certification as a Microsoft Certified Solution Developer (MCSD), a Microsoft Certified Product Specialist (MCPS), or a Microsoft Certified Trainer (MCT).

[source: https--www.techtarget.com/searchwindowsserver/definition/Microsoft-Certified-Systems-Engineer-MCSE]