On Fri, 2006-06-16 at 19:20 -0400, ross brunson wrote: > Right on, I see the Samba exam as being something that tests your > ability to properly bridge or integrate the two environments, 'cause > let's face it, Samba exists so that it can help other systems > interface or replace or emulate etc. as or to a Windows system.
But there are many facilities _outside_ of Samba that _also_ bridge the two environments. Network authentication, directory and naming services that are _not_ provided by the Samba project do such for UNIX/Linux and Windows integration. They are just as key, and not just Samba provided ones. > Yeah, nothing is worse than a bigoted Microsoft technician who hates > Linux and Unix and yet has to work around and with it for his job, > unless it's an equally bigoted OSS person who can't be bothered to > learn Windows technologies because they are "dirty" and > "proprietary". Actually, it goes worse than that. _Nothing_ is worse than someone who puts in a Linux solution but doesn't know the first thing about UNIX/Linux services alongside Windows. That's why the Linux server merely remains as a Windows server and _nothing_ else. > Solid point, I would recommend it be a Migration/Integration focus, > and that would be one way only. I feel no responsibility > *whatsoever* to teach/certify someone about how to migrate from Samba > to AD. And if "Migration/Integration" is the key, at what point are we saying, "oh, Linux makes a great Windows server ... oh, but, we don't care about other client support." > The Microsoft desktop certification has little to do with network > configuration. Windows networking is covered over a range of > training courses and certification programs - each of which has its > own examination. The MCDST _does_ address some of the _client_ support. In fact, the MCDST and MCSA address _all_ of the Windows client support. The MCSE addresses *0* beyond what the MCSA does. > It's even worse now, it's no longer one MS course per exam, they are > mixed up some now so that you can't just take a single course and get > a single exam out of the way. Because technologies are inter-related. That's the problem. That's always the problem. The only way is to try to break it up into exams, but much courseware is still inter-related, because of how the services inter-operate. You don't take just an exam on ADS that addresses everything. > Again, my hope is that we all remember that this is a Level 3 cert, > and by this time people should have a good working set of networking > skills and not be a Window Virgin, very damn few positions I have > seen could be so isolated in todays networking environment, perhaps > at an ISP or some large corporation's Server group, but surely not in > the SMB or middle tier market. And I think it's to be said that you should _not_ be a UNIX/Linux client virgin either. And you have to go _beyond_ just basic broadcast and legacy resource list services -- and into _modern_, _enterprise_ network authentication, directory and naming services for _any_ platform. You don't have to do a full exam on OpenLDAP or FDS. But you had better understand some basic authentication protocols, their services setup, common compatibility as well as how different resource services are listed and available across an enterprise for different clients -- all in addition to basic DNS, DDNS updates and key objects, such as SysV records for Kerberos, etc... This is level 3. -- Bryan J. Smith Professional, technical annoyance mailto:[EMAIL PROTECTED] http://thebs413.blogspot.com ---------------------------------------------------------- The existence of Linux has far more to do with the breakup of AT&T's monopoly than anything Microsoft has ever done. _______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/mailman/listinfo/lpi-examdev
