From 30f3314a0f70bff6c447164a60463f10731c4805 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Thu, 17 Apr 2003 16:08:22 +0000 Subject: Edits in progress. (This used to be commit c1dea19852d8eedf590323ac464f863eb3b92c83) --- docs/docbook/projdoc/NT4Migration.sgml | 64 ++++++++++++++++++++++++++++++++-- 1 file changed, 62 insertions(+), 2 deletions(-) (limited to 'docs/docbook/projdoc/NT4Migration.sgml') diff --git a/docs/docbook/projdoc/NT4Migration.sgml b/docs/docbook/projdoc/NT4Migration.sgml index 1f7371de36..3640c78942 100644 --- a/docs/docbook/projdoc/NT4Migration.sgml +++ b/docs/docbook/projdoc/NT4Migration.sgml @@ -15,16 +15,76 @@ Samba-3 based domain control. Planning and Getting Started -You must use at least the following ... +In the IT world there is often a saying that all problems are encountered because of +poor planning. The corrollary to this saying is that not all problems can be anticpated +and planned for. Then again, good planning will anticpate most show stopper type situations. + + + +Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control +environment would do well to develop a detailed migration plan. So here are a few pointers to +help migration get under way. Objectives -Blah blah objectives here. +The key objective for most organisations will be to make the migration from MS Windows NT4 +to Samba-3 domain control as painless as possible. One of the challenges you may experience +in your migration process may well be one of convincing management that the new environment +should remain in place. Many who have introduced open source technologies have experienced +pressure to return to a Microsoft based platform solution at the first sign of trouble. + + + +It is strongly advised that before attempting a migration to a Samba-3 controlled network +that every possible effort be made to gain all-round commitment to the change. Firstly, you +should know precisely why the change is important for the organisation. +Possible motivations to make a change include: + + + + + Improve network manageability + + + Obtain better user level functionality + + + Reduce network operating costs + + + Reduce exposure caused by Microsoft withdrawal of NT4 support + + + Avoid MS License 6 implications + + + Reduce organisation's dependency on Microsoft + + + + +It is vital that oit be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers +an alternative solution that is both different from MS Windows NT4 and that offers some +advantages compared with it. It should also be recognised that Samba-3 lacks many of the +features that Microsoft has promoted as core values in migration from MS Windows NT4 to +MS Windows 2000 and beyond (with or without Active Directory services). + +What are the features the Samba-3 can NOT provide? + + + + Active Directory Server + Group Policy Objects (in Active Direcrtory) + Machine Policy objects + Logon Scripts in Active Directorty + Software Application and Access Controls in Active Directory + + Steps In Migration Process -- cgit