Conference koolit::vms_curriculum

Here's how the proposed outlines for the three courses were created:

Following the IPF, Wendy, Phil, Val, and I got together, compared
our notes with Sheery's, and came up with a list of all of the topics
that had been suggested at the IPF.

Wendy then categorized each topic under its appropriate task and assigned
it a learning objective.

Using the categorized topics as a first draft, Wendy and I rearranged
things, came up with alternate objectives, and fitted the instructor
that had come in on the first draft into a working outline.

With a few minor changes, that's the outline that is posted for your
review.

One important point I want to make: If you look at the outlines and 
compare them to the topic list, you won't find a 100% match. The reason is
that the outlines are based on *tasks*, not *topics*. For example,
the IPF topics list included:

	-Authorize

		Add
		Delete
		Modify
		Show
		List

These are topics. The *tasks* that you will see in the outline are:

	- List the user accounts on the system

	- Add a user account to the system

	- Modify a user account

	- Delete a user account from the system


These tasks incorporate the topics from the IPF list.

All of the outlines are like this. If you think a topic is missing, ask
yourself what task that topic might fall under, and look for the task.

Sometimes you'll find a 'topic in the raw', especially in the first chapter
of each course and in the intro to each chapter. These are 'knowledge nuggets'
that are required to understand the following tasks.

I believe that the outlines reflect the intent of the folks attending the
IPF. Please take a few minutes to look them over and comment on them.

Comments can be posted here or sent to SUPER::DONHAM. I'd prefer to 
see them here.

Regards,

Perry

We need to make sure that the people reviewing these items are aware that it
is the intent of the new curriculum to REMOVE a majority of the USER training
for the SYSNET courses.  The plan is to have the VMS for Users and VMS for
Managers a 'merged' course.  95%+ of the material in the User course is fine
for a system manager.  The more advanced topics would still be in SNI, but as
a follow-on to the 3-day user course.

$

One other point, in case I haven't said it often enough... :^)

When reviewing the outlines, if you find something is missing, we need to
know what the *task* that's missing is.

In other words, "Hey, you forgot BACKUP/NORESTORE!" is not useful information,
but "Hey, you missed 'Backing up vaporware'" is.

You'll get a chance to comment on individual topics under the tasks when 
chapters go out for review.

One other thing...at this point all of this revampment is *just a proposal*.
We haven't received the green flag yet.

Perry

So, I assume that the outlines are perfect and that silence = consensus?

<NOT!>

Seriously, has anyone actually *read* the outlines? We're starting work
on these things this week...

Perry

Hi,

        I would like to make the following general remarks
  about the new proposal:

* Has the naming of the new string left unchanged ? This was requested by
  a lot of replies to note 49...  We had a lot of trouble
  with customers expecting "network management".  Altough less obvious, even
  a students enrolled for Sysnet III, believing it was a follow-on to the
  old Sysman II...  Also alot of students don't believe Sysnet I is a basic
  course with some system management stuff in it, but believe it's all about
  system management.  Seems to me that they don't read course descriptions,
  don't look to the course flows; just the title...
  We decided to change the course titles into:
        - VMS Skills for System Managers * (= VMS skills for users + SNI)
        - VMS System management * ( SNII)
        - Advanced VMS System Management * (SNIII)
                * in a networked and clustered environment

* I agree that a lot of systems run in a network or in a cluster. We found out
  that most of our students have a "PC environment". I have not seen much focus
  on this configuration nor its products... Do we deal here essentially with a
  character-cell terminal environment (probably at the time of the survey...) ?

* As far as I can see, the following "topics" are nowhere included:
        - SUBMIT command, and more advanced batch-job management
        - install utility
        - accounting utility

* networking == phase IV  ?!?

* AS many replies to the famous note 49 indicated, we also experieced the
  following facts:
        - topics are cutted into pieces, and spread over the sysnet stream;
          this generates lots of questions (they want to know more) and lots
          of trouble for the instructor (will be treated later = unsatisfied
          customer)

        - difficult to relate all the various topics and build a consistent
          course. In the end they know a little bit about everything; when
          going to the next course they seem to have forgotten that little bit..

  This is really contradictory:  they prefer a much more in-depth explanation
  and  don't even seem capable to remember the material when they go to the next
  course.

  To what extent is (or can) this phenonena addressed in the proposal ?

* A weak point in the Sysnet stream were the "superficial exercises"; are they
  being reworked too ?


	Christian Meersman,
	Learning Services Belgium
                                                                                

    
    
    I have a real feeling of deja vu, here, and it's NOT a good feeling. 
    In many ways, we are back to where we were 2 years ago!!!
    
    Though I prefer the layout of the new Sysnet I, II, and III as compared
    to the "old", all that has really been accomplished, in my opinion, is
    to take the topics of system management, network management, and
    cluster management (which used to be 3 one week courses) and shuffle
    them into the three week string.  (Of course, the assumption is they
    have the "user" course as pre-requisite, as was also the case before.)
    
    We have not taken a step forward in this new curriculum.  We have, in
    my opinion taken several steps backward.  I don't care about the "task"
    concept.  It's just a word that, in my opnion, no-one in the course
    development group has EVER really clearly defined.  All "you" have
    given us is courses that I think, don't work.  They are NOT
    pedagogically sound.  There is no clear flow of topics.  And, the
    topics themselves often aren't even related to each other.  
    
    I long for the days when we had ONLY U&C, SMI, Network, VAXCluster, and
    SPM.  
    
        GJD

The tasks *are* related to each other, in this way:

They answer the question, "What are the tasks that a system manager at 
one of the three levels will be doing 80-90% of the time?"

Perry

I don't agree with this task- oriented stuff. I tried to find a customer who
had three levels of System Managers but I couldn't find any. In practice we
have real (three levels in one) system managers, sometimes network managers and
if needed operators to assist the system managers.

There was not one customer who told me after a SYSNETI course "this is what I
needed, now I can go back and start doing my job", but they all told me "we
desperately need to come back for the SYSNETII course to be able to do our job,
this is NO system Management .... and when are we going to learn something
about networking....and what about the PC integration????....".
(Remark: In the old curriculum people had also to come back for a second course,
but they didn't expect to become a system manager when they started the U&C
course. The point I want to make here is that it has no sense to give them this
little system management.)

The only thing I like about this new curriculum is that system management is
treated as being more than standalone VMS system management.

I completely agree with the comments in reply 6 and I, together with my
colleague instructors, also long for the days we had the U&C, SMI.... 

Mia

>There was not one customer who told me after a SYSNETI course "this is what I
>needed, now I can go back and start doing my job", but they all told me "we
>desperately need to come back for the SYSNETII course to be able to do our job,
>this is NO system Management .... and when are we going to learn something
>about networking....and what about the PC integration????....".

Mia, this is the entire reason we're revising the curriculum, to put the
system management material back into SysNet 1.

PC integration into a network is most certainly not in SysNet's scope.

Regards,

Perry

    
    
    Related, maybe (IF I use my imagination!!!!).  I stand by my previous
    statements:  This curriculum is flawed in its very design, and no
    amount of fixing/patching/repairing is going to make any siginficant
    difference.  My opinion only, of course.
    
        

An update on what we're doing:

The team spent Thursday comparing the task outlines to the TBIs...the goal
was to identify which material in the TBI could be used in the new LL, and
which tasks would need new material.

We're using the TBIs as a starting point because the feeling is that they are
in better shape than the LLs.

We finished identifying material in SN1 and about half of SN2, which we'll 
work on early next week.

Since the TBIs are 'modularized', we can easily pick out the 'chunks' needed
for the topics under each task...Mel will be using this information to 
pull together a first-pass copy of each course. While she's doing that, the
developers will be busy writing the new material identified earlier.

I'll post more detailed outlines next week; these will contain the 
topics under each task. Please continue to suggest changes to the task
outlines that were posted earlier.

Regards,

Perry

    
    I know this probably isn't the appropriate place, but wanted to take
    this time to let you know that I have been TFSO'd and my last day will
    be Friday.
    
    After nine years with Digital, I am gone.  I enjoyed working with all
    of you and am sorry I will not be here to see the finished products. 
    (Who knows, maybe they will hire me back as a consultant!!!! -- ok, so
    I won't hold my breath.)
    
    Keep up the good work everyone.  Hopefully no one else on the IPF team
    will be hit and you can all still make it to Australia for the next
    one (isn't that where we were going to meet????).
    
    Guess this is goodbye,
    
    Dee

    


                  I N T E R O F F I C E   M E M O R A N D U M

                                        Date:     23-Sep-1992 02:13pm EDT
                                        From:     Frank Bruno
                                                  BRUNO.FRANK
                                        Dept:     
                                        Tel No:   276-8745

TO: See Below

Subject: A/I:Request for Comments:Network Management Customer Training          

    Based on the rollout of the restructured VMS System Management and 
    DECnet-VAX Network Management curricula for customers, a number of 
    opportunities have emerged that must be addressed to improve the 
    OpenVMS System and Network Management curriculum (refer to Bill 
    Simcox's memo dated 16-Sept-1992.
    
    Through this memo, we hope to address the issue of a specific network 
    management course that becomes a necessary prerequisite prior to 
    students attending the remaining network specialty courses.
    
    Your comments, input, and feedback are essential in our attempts to 
    qualify the need and content for this course. The information we have 
    collected thus far is based on a session conducted by Arthur Lessard 
    with the U.S. Instructors Product Forum. The topics listed below are 
    those topics that this group felt should be included in the "Managing 
    the DECnet Environment" course.
    
    It is assumed that the basic installation and node configuration 
    information will have been covered in the newly revised SYSNET string. 
    It is also assumed that this course will address only DECnet Phase IV.
    
    The proposed topics include:
    
    o	Technology Overview: an overview of networking concepts, OSI-7, 
        DECnet, and DECnet's place in the network environment.
    o	Advanced DECnet Network Control Program (NCP) topics, for example:
        - creating and defining network objects
    	- using the task object
    	- objects that are installed with new products
    o	Network Security (additional). Note: a word of caution on this 
        topic, we must understand the ramifications of including this here 
        as opposed to including it in the System and Network Management 
        Security course.
    o	Network Administration topics, including
    	- node topology planning
    	- network maps
    	- network help desk
    o	Network Monitoring Tools, including the use of Event Logger, NCP 
        Counters.
    o	Discussion of Network Management Tools
    	- Digital Management Control Center (DECmcc)
    	- POLYCENTER SNMP (formerly Management Station for ULTRIX)
    	- DECelms
    	- Remote System Manager
    o	A Troubleshooting section that provides examples of the most common 
        errors faced in the DECnet environment.
    o	Installation, configuration, and management of new terminal servers 
        (to cover the gap of what is not discussed in the SYSNET string).
    
    To facilitate timely completion of the requirements process, please 
    provide your comments to me (Frank Bruno @OGO) no later than 
    07-OCT-1992.
    
    In advance, we appreciate your time and input in shaping the content 
    for this essential customer training course.
    
    This message has also been posted in the following NOTES conferences:
    
    SUPER::VMS_CURRICULUM
    NETCUR::ESCM_DEVELOPMENT
    
    Regards,
    
    Frank Bruno
    

Distribution:
 
TO:  Remote Addressee                     ( bob smith @fac )
TO:  Remote Addressee                     ( barbara burns @pko )
TO:  Remote Addressee                     ( sherry groover @alf )
TO:  Remote Addressee                     ( sylvia hankins-allen @aci )
TO:  Remote Addressee                     ( bob bianchi @wro )
TO:  Remote Addressee                     ( david rogers @pko )
TO:  Remote Addressee                     ( mal poulin @dco )
TO:  Remote Addressee                     ( snowdale@esmail@vmsmail )
TO:  Remote Addressee                     ( dellarocco @esmail@vmsmail )
TO:  Remote Addressee                     ( pont@esmail@vmsmail )
TO:  Remote Addressee                     ( trayser@soaeds@vmsmail )
TO:  Remote Addressee                     ( rine @teach@vmsmail )
TO:  Remote Addressee                     ( john cole @dvo )
TO:  Remote Addressee                     ( doug myers @aci )
TO:  Remote Addressee                     ( arthur lessard @lao )
TO:  Remote Addressee                     ( bob romano @pko )
TO:  Remote Addressee                     ( giancarlo duella @geo )
TO:  Remote Addressee                     ( jack moore @pko )
TO:  Remote Addressee                     ( rick wardrop @wao )
TO:  Remote Addressee                     ( bill gaudette @wao )
TO:  Remote Addressee                     ( ken mouser @ako )
TO:  Remote Addressee                     ( marc latouche @vbo )
TO:  Remote Addressee                     ( omalley @mcis2@vmsmail )
 
CC:  Remote Addressee                     ( pete buswell @ako )
CC:  Remote Addressee                     ( john coffey @rka )
CC:  Remote Addressee                     ( dick mccarthy @wao )
CC:  JIM MALANSON                         ( MALANSON.JIM )
CC:  Remote Addressee                     ( simcox@sonata@vmsmail )
CC:  Remote Addressee                     ( trant @sonata@vmsmail )
CC:  Remote Addressee                     ( mcinnes @took@vmsmail )
CC:  Remote Addressee                     ( caprio @sonata@vmsmail )
CC:  Remote Addressee                     ( joss @tang@vmsmail )
CC:  Remote Addressee                     ( trant @sonata@vmsmail )
CC:  Remote Addressee                     ( costigan @netcur@vmsmail )

The sub-titles of the three SysNet courses will be removed for this rev.

In other words, no more 'Survival Skills' or 'Managing Change and Complexity'.

(I kinda liked 'Managing Established Systems', but it's outa there, too.)

Perry

Subject: A/I:Request for Comments:Network Management Customer Training          
...
    The proposed topics include:
...    
|    o	Advanced DECnet Network Control Program (NCP) topics, for example:
|       - creating and defining network objects
|    	- using the task object
|    	- objects that are installed with new products
  
  At the Instructor Product Forum this pas summer the Sys Net 2 and 3
  outlines we wrote on the board included introductory info on Network
  objects, their use, how to define/redefine them.  The context was in
  'fixing' an entry that had been deleted or damaged.  I.e. MAIL$SERVER
  vs the DEFAULT account, how to add it in, etc.
  
|    o	A Troubleshooting section that provides examples of the most common 
|        errors faced in the DECnet environment.
  
  Check with Emmalee Tarry, some or all of this might be in the new System
  Trouble Shooting course, which is supposed to include VMS, DECnet and
  Cluster troubleshooting.
  
  $

    There is a good manual that should help you with OpenVMS Alpha
    system management questions. 
    
    A Comparison of System Management on OpenVMS Alpha and OpenVMS VAX
    AA-PQYQA-TE
    
    You can get it over the network at:
    BULOVA::DOCD$:[ALPHA_VMS_REVIEW.POST]ALPHA_SYSMGT_COMP.PS

    Happy reading!
    

I'm trying to get this manual included in the instructor packages for 
SN2 and SN3.

This manual is *very* important as we move into the gray area between 
AlphaVMS and OpenVMS...they really are quite different at this point. The 
book exaplains what the differences are very clearly.

If anyone needs a hardcopy, please send mail to me at SUPER::DONHAM and
I'll get one to you.

Regards,

Perry

For those of you have taught the 'revised' SysNets:

Regarding the chapter terms that appear in the Instructor Guide, but 
not in the Student Guide, would you prefer to have them

	o Not change

	o Appear in both student and instructor guides

		- In the front of each chapter

		- In the back of each chapter (near the summary)

We'll be doing V6 updates soon, so now is the time to change things.

Regards,

Perry

What about the start of each section? In other words, define the new
terms for that section.

P

    I could go with Buck or Perry, as long as they are included! 
    
    

    
    	The chapter terms in the instructors guide are fine with me.  It
    gives the instructor flexibility on when to talk about them since 
    they are not in the student guide.
    
    Jeanine

  Defining terms is a 'self-paced' concept.  I've never attended a lecture
  where they told me all the terms upfront and gave me definitions except
  in cases of abbreviations.  A list of terms at the beginning of the
  chapter wouldn't be so bad, but not the definitions -- give me an
  opportunity to present the material.  If you want the definitions in the
  beginning of the Instructor's manual and in the the back of the Student's
  guide, that's OK too.  But give me a chance to teach the material, in
  a method and fashion that works without making me skip excessive numbers
  of pages to get the the 'meat' of a chapter!
  
  Just for your information, except in chapter one where I cover all the
  pages, I usually skip the objectives, the resources, the introduction and
  start with the first page of lecture.  That's "fluff" that might be
  useful for some, but I'd prefer the RESOURCES also go in the back (much
  like a bibliography) because I have little to say on that topic either.
  There will be more than enough covered during lecture, and I'd like to
  end the discussion with a short summary, a review of the important terms,
  and mention places they can get more information on the topic.  Digital's 
  training material is one of very few references/lecture materials that
  have this stuff up front, most other coures I've taken (Microsoft,
  college, A.M.A., Learning Tree, etc.) have these near the back.
  
  $

    The summary of topics and commands at the end of each chapter is 
    excellent (in Sysnet2, anyway!) and this seems the obvious place 
    (to me) to put the summary of terms met in that chapter!

    Putting them there still allows the instructor to introduce them
    earlier if s/he wishes.  
    
    Re .23
    
    The list of resources could also go at the end of each chapter as far
    as I'm concerned, but I *always* run through the intro and objectives
    at the beginning of each chapter.
    
    Geoff

    I strongly suggest that the "Chapter Terms" pages be incorporated in
    the Student Guide.  I have been making copies of these pages for my
    students and they seem to be very much appreciated.  As far as where
    the pages should be placed, I would prefer that they be placed at the
    beginning of the chapter.  I don't think that the instructor needs to
    cover the pages, but I do feel that they help set the tone for the
    chapter.
    
    sj

                  I N T E R O F F I C E   M E M O R A N D U M

                                        Date:     26-Feb-1993 04:01pm EST
                                        From:     CHUCK HEISEL
                                                  HEISEL.CHUCK AT A1 at DV780 at DVO
                                        Dept:     Educational Services
                                        Tel No:   (505) 857-7033

TO: See Below

Subject: RE: Sysnet Chapter Terms                                    

         Hi folks,
         
         I think that there is enough material to cover.
         
         If the terms are in the summary (behind it) then the students 
         can read them at their leasure.
         
         Yours,
         
         Chuck
         

I'm leaning toward putting the chapter terms in alphabetical order in the
Summary section of the Student guide, and perhaps up front in the Instructor
guide.

Which book are you folks teaching from, the student or instructor guide?

Perry

If any of you have additional material that you think should be in one of
the Sysnets, please post it in the appropriate note here, or send me mail.

I'm especially looking for Instructor Notes, but if there's a task you think
is missing, we can talk about that, too.

Oh, labs, too...the labs need some help. Let me know if you have any thoughts
about new or modified labs.

Perry

    Perry;
     
    As I begin each chapter with a definition of each of the important
    terms that will be used in that chapter I would prefer that the terms
    be positioned at the begining of each chapter.  I very much want these 
    terms included in the :Student Guide".
     
    The new format for the "Instructor Guide" is not nearly so useful as
    the opposing instructor pages.  The very best IG that I have
    encountered in my seven years with Ed Serv. is the Rdb 4.1 IG. It uses
    the facing page format and "the instructor pages are full of USEFUL
    information".  The new format, with page numbers that do not always
    match the student guide, is - in my opinion - a step backward.
     
    Arnold Tarling, DLO10::TARLING
      
    

    I want to second (or third or...) Buck's reply (.23) about moving the
    reference biblio list to the back - he has made a good case!  I stumble
    over why I am skipping these pages and seem to be half way into the
    module before I use the material when there are longs "lists" of
    reading suggestions.  
    
    ih 

I'll talk to the design team here about why the resources are in the front. I
personally don't care where they go, as long as they are usable. 

Seems to me that the giant list of resources isn't always accurate, either...
probably they haven't been checked for several versions.

Perry

    I'll add my voice to those asking for the definitions in the summary. 
    It really is better if the instructor doesn't have to make excuses for
    skipping pages.  There are always those students who have to scrutinize
    everything on every page.  If there are definitions that require an
    understanding of most of the module before they're meaningful, there
    can be a real conflict.  If an instructor really likes covering the 
    definitions first they always have the option to zip back to the definition 
    page before starting the module.  
    
    Mark Thorne

    
    Sounds like we have a plan...if there are no major objections
    from my instructional designer, we'll put the chapter terms thus:
    
    	o IG - in front of each chapter
    	o SG - in Summary section
    
    Perry

    THIS RESPONSE IS A CONSENSUS FROM ALL INSTRUCTORS AT THE LQO TRAINING
    FACILITY.
    
    Regarding the chapter terms that appear in the Instructor Guide, but  
    not in the Student Guide, we would prefer to have them

	o Appear in both student and instructor guides

		- In the back of each chapter (AFTER the summary)
    
    
    Regards,
    
    
    Jason Fish
    

    I agree with Tarling.  If you are looking for a format to follow
    the RDB material has it all over the SYSNET stuff.  The new instructor
    guide is awful to work from andf yes I do need help in teaching this
    material, but putting the instructor notes within the material only
    makes it more difficult to use.

    
    Given that the two-book approach isn't likely to change in the near
    future (it seems to be a corporate mandate), is there a way to 
    make the instructor guide more useful?
    
    Perry

    Re .36
    
    What about keeping the facing page format, but only produce a facing
    page if there is something to put on it?  Some Instructor Guides have a
    lot of empty Instructor pages (wasn't this a comment from way back
    when which led to reviewing the IG format ?) 
    
    I don't know about the ease of production of such a book, but it seems 
    to me that it would keep everyone happy?  I've just thought of a problem
    as I'm writing!  It would require the student pages to be printed
    single-sided to maintain the spacing.  No, it wouldn't!  Most (all?)
    sites would have access to a PS printer that prints double sided?
    (Current cost-cutting directives mean that all our documents are printed
    double-sided by default. We can overide that if necessary.)
    
    In that case, does it matter that Instructor Pages sometimes *don't*
    physically face the Student Guide page they refer to but are printed on
    the back of the same sheet?  It wouldn't upset me, but I tend to teach
    from an anotated copy of a student guide and just use the IG for prep.
    
    This would keep all the page numbers the same in both the IG and SG
    (removing a big problem with the "embedded note" approach) and keep the
    overall size of the document down to a minimum, both on disk and on
    paper.
    
    The IGs with Instructor Notes embedded amongst the student guide text 
    really are not very helpful!
    
    
    Any comments?

There won't be any more facing-page IGs. There are significant costs involved
in maintaining the software that enabled the format; that's the biggest
reason for their demise.

Of course, two years from now we'll have a huge meeting and decide that what
we really need are facing-page IGs.

Given that, how can we improve the current IG?

Right now the IG contains everything from the SG. Would you rather *not* have
the repeated material, and just have the IG be full of instructor notes?

Or how about an IG that talked about teaching the course in general, then about
each chapter in general? (Right, developers writing about how to teach...NOT!)

Any more ideas?

Perry

With regard to the format of instructor guides, has anybody taken a look at the
Building Dependable Systems format.  It has the following features.

	A student guide  which is double sided.  Paging will be improved by the
	editor.

	The instructor guide contains all the map heading of the student guide
	and each map starts on a new page.  There is a block header for every
	student guide block header.  NO STUDENT MATERIAL OTHER THAN THE HEADERS
	(and the solutions to exercises) IS REPEATED IN THE INSTRUCTOR GUIDE.
	Each block of the instructor  guide is clearly marked with "Instructor 
	Notes".  If there is no instructor material for a block a space is 
	left where the instructor can place their own notes.  The page numbers 
	do not match, but maps always start on a new page.  


To familiarize yourself with this format, you could review some BDS chapters.
Suggestions should be made by April 8.

    I am organizing what material from the TTT (v6, BLADE, DELTA, CORAL & 
    EPSILON) to distribute and how to ensure a "readiness" plan is in place
    for the rollout of v6, updated courses and other concerns.  I have a
    vague target date of Q1, July.  Can someone closer to the updates of
    the Sysnet string give more specific dates?  
    
    My management and fellow instructors have limited time and limited
    flexibility in scheduling what time remains in Q4 to be "in place,
    ready and on-time".  We appreciate any target date info that can be
    incorporated into the "dots" and instructor/resource scheduling. 
    
    Jack, Bill or Perry???
    
    Thanks in advance, 
    Irene

    Irene,
    
    I'm the person you want to talk to about that (re -.1).  However,
    we haven't set a date for the rollout of the updated SYSNET courses
    yet.  I do have the dates for the V6 Update Seminars for customers
    and am in the process of contacting the unit managers to give them
    the information.
    
    -Sherry

    Sherry, 
    
    Thanks bunches -- we are looking at several things converging on the
    same timeframe, and hoping to make sane decisions (!).  Will look
    forward to seeing the update dates.   I realize there are several
    interdependencies that can affect the timelines. 
    
    Regards, 
    ih

I am preparing to teach OpenVMS System and Network Mgmt. I after teaching
several times the "old style" VMS courses.

I noticed that in the courseware there is no reference to terminal servers.
In what course can the students find a detailed list of things to be done
in order to add a printer to the system via terminal server?

Regards
						Mario

    Chapter 3 of SYSNET II.