MS TCPIP on NT 3 by kpg20724

VIEWS: 7 PAGES: 14

									                                  SMS 1.2 Study Guide
                                              Darwin Sanoy


Concepts and Planning Manual (Ch 3: Understanding Sites)
   Terms: “SMS Logon Servers” - servers that support the configuration and maintenance of SMS clients.
    Some or all of the Network Logon Servers can be SMS Logon Servers, “Network Logon Servers” -
    Netware, Windows NT and LAN Manager Servers that perform logon validation.
   Domain Types: “Site Server Domain” - the domain of the domain controller on which an SMS Site
    server has been installed, “SMS Domain” - group of servers and clients that have been included in an
    SMS site - an NT or LAN Manager Domain that has been added to a SMS Site becomes an SMS
    Domain, a group of Netware servers added manually make up a “logical” SMS Domain.
   Site Types: “Central” - the primary site at the top of the hierarchy, “Primary” - has an SQL Database to
    store data for itself and all subsites, “Secondary” - does not have an SQL database, reports all data to
    it’s parent (primary) site, “Parent” - has sub-sites reporting to it, “Child” - reports to a another site,
    “subsite” - a site at any level beneath the current site
   Site Details: *) Cannot attach a site beneath a secondary site, *) Cannot move a secondary site - must
    de-install / re-install, *) cannot change site code after installation, *) Primary site can have one or more
    secondary site children and/or one or more primary site children *) if site server fails - cannot process
    inventory or jobs or generate events or alerts. *) if SQL server fails - cannot run SMS Admin, cannot
    add/delete data, *) if either fails - clients can still: be configured for SMS, report inventory, run
    package command manager, use program group control and complete MIF forms.
   Benefits of Hierarchical Model: *) simplifies viewing and managing a large number of clients, *) can
    setup sites according to administrative needs: such as central or distributed management, grouping of
    computers, etc., *) it scales to sites of all sizes, *) SMS structure can map directly to physical network,
    *) allows phased deployment of SMS
   Senders: *) can have multiple senders of different types on a computer, *) multiple senders of same
    type at one site if they are on different computers (sender selection based on throughput history), *)
    LAN sender can consume almost all bandwidth on a slow link, *) senders of a specific type (big 3
    types) use a common outbox, *) Senders must have a least one address for their intended destinations,
    *) SNA senders require that SNA server be installed on the sender machine, *) since job data is not
    passed through the hierarchy, addresses are needed for every site that a site needs to send to, for
    example the central site must have an address for every subsite that it needs to send job data to, *) when
    adding a new primary child site you must add an address to the parent site as well as an address from
    the parent to the new primary, you may also need to add an address to the central site to the new
    primary
   Site server requirements: *) NT 3.51 or NT 4.0, *) Running as a domain controller (PDC or BDC),
    one NTFS partition with enough space to install SMS Server. Additional Requirements for Primary
    Server: *) access to SQL server on the same LAN (or same computer)
   Logon modes of SQL server: *) Standard - use SQL server logon ID and password, *) Integrated - use
    NT account, *) Mixed mode - both types of security.
   Domains and Logon Servers: *) once an NT domain has been added to an SMS site, it becomes an
    “SMS Domain” *) “Package Servers” - two types “Source Servers” - where a package originates and
    “Distribution Servers” that distribute the packages, *) “Helper Servers” - must run NT, can be used for
    Scheduler, Despooler, Inventory Processor, Inventory Data Loader and Senders.
   Domain Configuration: Automatic - continues to auto-detect and configure new logon servers - only
    way to automatically configure all clients - always targets “SYS” volume on netware servers for SMS
    Logon Server software installation, NT software installation always targets largest NTFS volume with
    largest FAT volume as a secondary option if no NTFS volumes exist, Auto works best for small sites
    and simple domain models, automatic can actually cause problems at sites that use one domain across
    multiple sites or use a master-resource domain model.
SMS Concepts and Planning Manual (Ch 10 - Designing Your System)
   Four Phases of Design: *) Defining site boundaries, *) Defining site hierarchy, *) Defining site types,
    *) Defining how to build and maintain sites as your network grows
   Careful Planning For: *) Many physical locations (especially if each has few users), *) Many
    domains (especially domains used in more than one place, or master account domain / resource domain
    models, *) Many computers, *) Many types of network connectivity, *) Many hardware platforms
    (especially if some are not supported by SMS), *) current servers or clients heavily loaded, *) clients
    with slow or no access to servers in their domain, *) widely differing administrative needs at different
    locations, *) widely differing client or user needs within a site.
   Considerations for boundary Planning: *) Physical location, *) network connectivity, *) domain
    structure, *) logical considerations, *) servers, *) capacity guidelines, *) platforms, *) site size, *)
    number of sites, *) user needs, *) SMS network applications, *) multiple languages within a site.
   Reasons to Split an NT domain into multiple SMS Sites: *) Primary reason: improve performance
    on networks geographical divided by slow links, *) allow SMS administrative access to sub-sets
    computers in the same NT domain.
   When splitting an NT Domain into multiple SMS Sites, follow these steps: *) Modify SMSLS.INI
    to specify which SMS site each client will be added to, *) modify client logon script to connect to a
    specific logon server and run the SMSLS.BAT file from there.




MCSE Study Guide

SMS Setup
   Distribution Servers: *) For Macintosh clients - must be running “Services for MacIntosh”, *) For
    Netware Clients - must be a Netware server (not running MS Client) and must be a server they are
    logged on to (make only logon servers distribution servers) *) If site contains multiple domains there
    must be at least one distribution server per domain since clients will be using the security access of
    their logon domain to get to the distribution files.
   Helper Servers: *) NT Server 3.5, *) NTFS Partition, *) Can offload: “Scheduler”, “Despooler”,
    “Inventory Processor”, “Inventory Data Loader”, “Senders”
   Logon Servers: *) Can only specify “Automatically Configure Workstation Logon Scripts” if you
    specify “Automatically Detect Logon Servers” (except for Novell), *) SMS (Site Configuration
    Manager) automatically enumerates all Netware, LAN Manager and trusted global NT groups and
    stores them in the database, *) SMS does not track where the group came from - duplicate groups
    across domains or logon servers are treated as the same group if the duplicate groups report to the same
    site server OR on any parent servers have information rolled up from subsites that includes duplicate
    group names.
   SMS Service Account:
         General:
          Consider changing the SMS administrator username when you change the password. If SMS
              goes down during the change, it may not be able to restart properly to finish making this
              change. If both are changed, then the new and old will work when restarting after a crash that
              occurs during this process.
          Configure SMS service account with following attributes (all NOSes): *) Do not force the user
              to change their password at the next logon, *) Do not configure the password to expire, *)
              Make sure the account can logon at all hours.
          Make sure that your user account name and password choices conform to all NOS limitations,
              all NOS security policies, all NOS security auditing programs and company policies for all
              company subsidiaries, divisions, departments, geographies and operating systems that SMS
               will operate on. It is a very big headache to have to change these half way through
               implementation.
         Windows NT:
         Administration per server: Local Account - *) create same username account and password on all
         necessary servers, *) grant “log on as a service” right on all servers.
         Administration per Domain (with trusts): Global Account - *) create account in the NT domain
         where the SMS service account should reside (does not have to be the site server domain), *) add
         the SMS service account to “Domain Administrators” group, *) grant “Log On As A Service” right
         in SMS Service Account Domain, *) ensure that all SMS domains that SMS will operate in trust
         the domain where the account is created, *) add the SMS service account to the local
         “Administrators” group in all trusting domains, *) grant “Log On As A Service” right in all trusting
         domains.
         Administration per Domain (without trusts): Global Account - *) create account in the NT domain
         where the SMS service account should reside (does not have to be the site server domain), *) add
         the SMS service account to “Domain Administrators” group, *) grant “Log On As A Service” right
         in SMS Service Account Domain, *) create an SMS service account in each domain where SMS
         will operate, *) add this service account to the local “Administrators” group in all domains, *)
         grant “Log On As A Service” right in all domains, *) when configuring sender addresses and
         attaching sites, ensure that the appropriate SMS service account name and password is entered for
         each non-trusted domain. This must be the SMS Service Account defined in the non-trusted
         domain.
         Administration per Network: Global Account/Global Group - *) create SMS service account in the
         NT domain where the SMS service account should reside (does not have to be the site server
         domain), *) create global SMS service group in domain where SMS service account resides, *)
         Add the SMS service account to the SMS service group, *) add the SMS service account to
         “Domain Administrators” group, *) grant “Log On As A Service” right in SMS Service Account
         Domain, *) ensure that all SMS domains that SMS will operate in trust the domain where the SMS
         service group and account are created, *) add the SMS service group to the local “Administrators”
         group in all trusting domains, *) grant “Log On As A Service” right to the SMS service group in
         all trusting domains.
         Netware:
         *) Create SMS service account with same name and password on all servers where SMS will need
         to run, *) Grant “SUPERVISOR” equivalence to SMS service account, *) On Netware 4.x only,
         create the group “EVERYONE” and include all Netware users in the group
         IBM LAN Server Domains (OS/2):
         *) create SMS service account with the same name and password as the Windows NT sms service
         account, *) add the LAN Service SMS service account to the “Administrators” group on the LAN
         Server domain.
         LAN Manager 2.x Domains:
         *) create SMS service account with the same name and password as the Windows NT sms service
         account, *) add the LAN Manager SMS service account to the “Admins” group on the LAN
         Manager domain.



SQL Server
The installation process will create the SQL database devices only if the SQL server is running on the same
server as the site server - otherwise they must be manually created ahead of time. Devices can only be
created using the “sa” account. Server must be configured with a minimum of 20 connections for
installation of SMS. Synchronize time of all computers that will be touched by SMS with the SQL server.

SMS Setup (Primary Site)
Switches: *) /noacctcheck - used when setting up SMS in a resource domain that has a one-way trust
relationship to the account domain where the SMS service account exists. Account cannot be verified
during installation, because there is no trust relationship setup.
SMS Setup (Secondary Site):
Using RAS Sender: test phone book entries and access permissions before starting the install to ensure that
the installation will go smoothly.
Using SNA Sender: must install the SNA receiver and bootstrap on the secondary site using the
SNASETUP.EXE program from the processor specific directory on the CD.
Two Different Items on Installation Screen: “Installation Sender Type” and “Site Server Platform” (Intel,
MIPS, Alpha).

“Automatically Detect Logon Servers” (during setup) “Use All Detected Logon Servers” (after setup)
setting:
NT/LAN Manager 2.2 Domains: *) enumerates all PDCs and BDCs, *) if turned off, NT and LAN
Manager logon scripts will not be automatically configured, even if “Automatically Configure Workstation
Logon Scripts” is turned on when configuring client properties. *) Is the only way to force which NT drive
letter is used to install SMS logon server support - otherwise “most free space wins” method is used.
Netware Servers: *) Detects ALL Netware servers within 16 router hops, *) If turned off, logon script
configuration still happens with Netware as long as “Automatically Configure Workstation Logon Scripts”
is turned on when configuring client properties. *) Is the only way to force which Netware volume is used to
install SMS logon server support - otherwise SYS volume is used.

Setting Up NT Directory Replication:
1. Create user account with no password expiry, no “change password at next logon” and ensure that it
    can has no time restrictions.
2. Add to “Backup Operators” and “Replicator” local groups on domain.
3. Grant “Logon as a service” right on domain.
4. Use Server Manager / Services to configure Replication Service as “Autostart”
5. Use Server Manager / Services to configure Replication Service as “logon as user” and specify user
    account specified in the first step.
6. Use Server Manager / Replication to configure PDC as Export
7. Use Server Manager / Replication to configure PDC as Import from itself
8. Use Server Manager / Replication to configure each BDC as Import from PDC

SMS Files:
\SMS\LOGON.SRV\*.UID - file name is next available client id.

SMS Shares:
      SMS_SHRx - SMS install directory. If SMS is installed on the C: drive, the share is named
      “SMS_SHRC” SMS root directory found on all site, logon and helper servers. Used by SMS
      Services to communicate with each other.
      SMS_SHR - mapps to “SMS\LOGON.SRV” - main interface between clients and SMS: found on
      all logon servers, used by clients during setup, inventory and distribution. Used by Inventory
      Agent, Program Group Control, PCM and MIF Data Entry. Group “EVERYONE” is assigned full
      control,
      SMS_SITE - maps to “\DESPOOLR.BOX\RECEIVE” subdirectory under “SMS\SITE.SRV” -
      exists on site servers for by remote sites when communicating with local site.
      REPL$ - used by directory replication,
      NETLOGON - map to “\<winnt_dir>\system32\Repl\Import\Scripts” - used by SMS for logon
      support files (ONLY 1.1 ?????)

SMS Directories:
Directory                   Servers    Description
C:\SMS\SITE.SRV             Site       Components
C:\SMS\PRIMSITE.SRV         Primary    Samples scripts, secondary site configuration information
                            Site
C:\SMS\HELPER.SRV           Site,      Contains support for PCM, Inventory Agent for NT, and Helper
                         Logon   Server
C:\SMS\LOGON.SRV         Logon   Client installation, logon and inventory support.
C:\SMS\NETMON            Site    Support files for Network monitor
C:\SMS\LOGS              Site    Service log files

SMS Services:
Service Name (NT in all caps,      Service Description
“SMS only” in proper case)
SMS_HIERARCHY_MANAGER              (Autostart) Monitors the SMS database for configuration changes
                                   and updates database with completed changes.
SMS_SITE_CONFIG_MANAGER            (Autostart) Implements configuration changes, installs secondary
                                   sites, starts all other NT services.
SMS_INVENTORY_AGENT_NT             Collects inventory at the site server
SMS_PACKAGE_COMMAND_MA             Provides unattended package installation at NT servers
NAGER
SMS_CLIENT_CONFIG_MANAGE           Installs SMS Service-based components on Windows NT clients.
R
SMS Remote Control Agent           (Autostart) NT remote control agent.
SMS_EXECUTIVE                      NT service that performs the following SMS services.
                                   (can run on helper servers for indicated SMS services)
       Scheduler                   Schedules jobs and compresses job-related files.
                                   (can run on helper servers)
       Despooler                   Decompresses packages.
                                   (can run on helper servers)
       Senders                     Supports communication between sites
                                   (can run on helper servers)
       Maintenance Manager         Maintains SMS client components at logon servers. Collects client
                                   inventory and status files from logon servers and forwards
                                   information to site servers.
       Inventory Data Loader       Loads and maintains inventory events, job status and user group
                                   data into the SMS database.
                                   (can run on helper servers)
       Inventory Processor         Maintains inventory history by reading RAW files and creates
                                   Delta-MIF files that are processed by the Inventory data loader to
                                   update the SMS database. Maintains history records for each
                                   client. Converts mifs in ISVMIF directory into delta-MIFs.
                                   (can run on helper servers)
       Alerter                     Processes alerts by creating an event log item in SMS, Windows
                                   NT Event Log, executing a command or sending messages.
       Applications Manager        Monitors for Shared Applications package activity. If a shared
                                   package is added, updated or deleted this service updates the
                                   Program Group Control Database and creates system jobs to
                                   replicate the package to all subsites.
       Site Reporter               Creates system jobs to pass inventory, event or jobs status
                                   information to the parent site.
        Trap Filter                Filters SNMP traps.
OS/2 Services
SMS_INV_OS2LM                      Inventory collection for OS/2 clients and servers
SMS_NET_MAPPER                     Helps OS/2 find logon and distribution servers

Installed Icons and Functions:
SMS Administrator (SMS.EXE) - configure and view SMS database.
SMS Network Monitor (NETMON.EXE) - network tracing features.
SMS Security Manager (SECURE.EXE) - manage SMS database security.
SMS Service Manager (SMSVCMGR.EXE) - start, stop, trace SMS services.
SMS MIF Form Generator (MIFGEN.EXE) - create custom data forms.
SMS Setup (SETUP.EXE) - modification of SMS setup.
SMS Books Online (SMS.HLP) - SMS books online.
SMS Database Manager (DBCLEAN.EXE) - used to delete SMS database items such as old records.
SMS Sender Manager (SNDRMGR.EXE) - configure bandwidth limits on senders.
SMS SQL View Generator (SMSVIEW.EXE) - create views to use with ODBC reporting tools.

SQL Security
Two Security Modes: “standard” - separate SMS logon, “integrated” - NT logons are passed straight
through to SQL.
SQL Security: Within SQL the SQL logon id is different from the “database user” In addition, SQL alias
can be setup to alias multiple SQL logon ids to a single database user. All of this can bet setup in SQL
Administrator, SQL Enterprise Manager or with SQL commands. Database permissions are assigned to the
database user, not the SQL logon.

SMS Security Manager
Securities and objects:
         No Access - user cannot access object.
         View - user can view, but not change.
         Full - user can view and change.
 Security Object                                               Access
Alerts                 Alerts window and properties
Architectures          Inventory
Diagnostics            Diagnostic utilities and access to Diagnostics group under the personal computer
                       properties
Events                 Events windows and properties
Helpdesk               help desk utilities and access to Help Desk group under personal computer properties
Jobs                   Job windows and properties
Machine Groups         Machines Groups window and properties
Network Monitor        Network Monitor and access to Network Monitor group under the personal computer
                       properties
Packages               Packages windows and properties
Program Groups         Program Groups window and properties
Queries                Queries window and properties
Site Groups            Site Groups window and properties
Sites                  Sites window and properties

Provided SMS Security Templates: “Asset Manager”, “Job Manager”, “Network Monitor”, “Software
Manager”, “Tech Support”
User names in SMS Security Manager: come from the “sysusers” database user table in the site database.

Site Properties
Inventory - frequency of inventory collection, dial-up action
Clients - configure logon scripts, shared apps, remote support
Services - service response time and setup helper servers
Account - Modify SMS Service account
Parent Site - view/set the parent site
Domains - view/add domains and logon servers
Servers - Add/Remove servers from Default Package Servers list
Addresses - View/set site addressses
Outboxes - View/set outbox properties
Senders - View/Manage senders
SNMP Traps - configure SNMP traps to be written to SMS database.
Response Modes (Server Response Time)
Very Fast - every 1 minutes - Test Mode
Fast - every 5 minutes - Heavy Load on SMS
Medium - every 15 minutes - Medium load on SMS
Slow - every 30 minutes - Light load on SMS

Items Installed and Changed on Clients
 Create SMS.INI
 Change autoexec.bat to client.bat (DOS/Win 3.1)
 Change win.ini to add “RUN=SMSRUN16.EXE” (NT has registry LOAD=SMSRUN32.EXE)
 Change system.ini to increase netheap size and add vuser.386 device driver (3.1 only)
 Create SMSRUN16.INI or SMSRUN32.INI
 Install files on \MS\SMS\BIN

Site Communications
Files:
        *.SRQ - Send Request File - instructions to sender, scheduler places in sender outbox
        *.I* - Instruction File for workstation
        PackageID.W* - Run Command on Workstation Job
        PackageID.S* - Share Package on Server Job
        *.P* - system job (e.g. install secondary site server)
        *.PKG - package update to child sites
        *.I* is renamed to *.INS and *.PKG is renamed to *.PCK and *.SRQ is renamed to *.SRS during
        transmission.
Sender Types:
 LAN
 SNA Batch
 SNA Interactive
 RAS Async
 RAS ISDN
 RAS X.25

TroubleShooting
Logs:
SQL Server Events - viewed through SQL Server Error Log window in SQL Enterprise Manager
SMS Events logged to NT Event Log - viewed through NT Event Log Viewer
SMS Events - (copied from NT Event log) viewed through “events” window in SMS Administrator
Service Tracing - configured through “SMS Service Manager”, viewed through “tracer.exe” or a text
editor. Located in \SMS\LOGS
Installation Log - root directory of C:
Sender Logs - One for each sender type. Located in \SMS\LOGS
Secondary Site Bootstrap Log - SMS root of secondary server - called BOOT.LOG
Site Configuration Manager Log - root of partition where SMS is installed. (SCMAN.LOG)

Client Inventory Processes

MIF KEY = SMS ID, Name, NetCardID
Logon Scripts: Windows (all), MS-DOS - run smsls.bat or runsms.bat, OS/2, LAN Manager, LAN Server
run smsls.cmd or runsms.cmd, Netware - run smsls.scr
Modifications:
          Create SMS.INI hidden on first local hard drive
          Modify “autoexec.bat” [MSDOS]
          WIN.INI modification to [3.1/95] to add SMSRUN16.EXE to LOAD= line
          Registry modification to [NT] to add SMSRUN32.EXE to Run key
            SYSTEM.INI modification to [MSDOS/Windows] to bump NetHeapSize and add
             Device=vuser.386
            SMSRUN16.INI created on [3.1/95] for reading by SMSRUN16.EXE
            SMSRUN32.INI created on [NT] for reading by SMSRUN32.EXE
            STARTUP.CMD modified on [OS/2 2.x and 3.x] to run SMSOS2AG.EXE
            LANMAN.INI modified on [OS/2 2.x and 3.x] to add SMSOS2AG.EXE to [Services] section
            IBMLAN.INI modified on [OS/2 2.x and 3.x] to add SMSOS2AG.EXE to [Services] section

Important Utilities
pcmdump.exe - dumps Package Command Manager instruction files (<smsid>.ins), found in
\support\debug\platform
viewnad.exe - displays contents of Network Application Database files (*.NAD), found in
\support\debug\platform


Help Desk
Protocols: Must use Netbios over the same transport (NetBEUI or TCP/IP) or use IPX. NT clients can use
sockets over TCP/IP. Remote sessions can be established over RAS. Remote sessions cannot be done over
SNA. SMS Administrator searches the first 8 loaded LANAs for a common protocol, the client uses the
first loaded protocol. Client protocol can be specified with cliopts.exe.
DOS/Win 3.1: autoexec.bat calls client.bat which loads useripx (IPX) or usertsr (Netbios).
Windows 95: does not require TSR, just wuser.exe (client.bat is still executed for smswork.exe functions)
SMS.INI, [SIGHT]: this ini file section configures Help Desk utilities on the client.

SNMP and SMS:

Two Main Facilitities:
 Conversion of Windows NT Events into SNMP traps
 Receive SNMP traps from SNMP manageable devices and write them to NT event log

Flow of events:
Conversion of Events to Traps
1. NT Client with SNMP and SMS Installed
2. converts NT System, Security and Applications logs into SNMP traps
3. and optionally logs them to the SMS database
4. as a result of the trap generation SNMP forwards them to any defined SNMP NMS

Conversion of Traps to NT Events
1. SNMP managed devices send traps to the SMS Traps receiver to be recorded in the SMS database.

Requirements for Event to Trap Translator:
NT 3.51 SP4, TCP/IP, SNMP

SMS Backup and Recover:
 Backup SMS SQL Database with a approved SQL Database backup tool
 Save registry key: HKLM\Software\SMS
 Backup master site control file at: \SMS\SITE.SRV\SITECFG.BOX\SITECTRL.CT0
Client and Server Requirements



                     Site Server        Primary Site       Central Site        Secondary Site      Logon Server       Software          Helper Server     SMS Administrator
                                        Server             Server              Server                                 Distribution      (additional to    Utilities
                                        (additional to     (additional to      (additional to                         Server            Logon Server
                                        Site Server        Primary Site        Site Server                            (additional to    Requirements)
                                        Requirements)      Server              Requirements)                          Logon Server
                                                           Requirements)                                              Requirements)
Hardware                                                                                                                                                  Intel Pentium,
Requirements                                                                                                                                              Alpha, MIPS

CPU                  Intel Pentium,                                                                Any supported
                     Alpha, MIPS                                                                   by NOS
RAM                  32MB               32MB (no SQL),     32MB (no SQL),      32MB
                                        48MB (w/ SQL)      48MB (w/ SQL)
Disk                 NTFS; 130 MB       NTFS; 130 MB       NTFS; 130 MB w/     NTFS; 26MB; 50-     50 MB; NTFS        NTFS                                50 MB
                     w/ Secondaries,    w/ Secondaries,    Secondaries,        100KB per client;   preferred, FAT     preferred, FAT
                     85MB without;      85MB without;      85MB without; 50-                       used if no         used if no
                     50-100KB per       50-100KB per       100KB per client;                       NTFS available     NTFS available
                     client; 500MB is   client; 500MB is   500MB is
                     recommended        recommended        recommended
OS & NT Service      NTS >= 3.51        NTS >= 3.51        NTS >= 3.51 SP3     NTS >= 3.51 SP3     NTS >= 3.5         NTWS >= 3.5       NTS >= 3.51 DC,   Any NT >= 3.5
Requirements (Also   SP3, DC            SP3 DC, SQL        DC, SQL Server      DC, NO SQL          SP2 DC;            SP2, NTS >=       NTFS Volume
see “Additional                         Server 6.x         6.x                 SERVER              Netware 3.x or     3.5 SP2
Requirements” for                                                                                  4.x, MS LAN        (including non-
non-NT NOS and                                                                                     Man >= 2.2c,       DC)
NON-MS Clients)                                                                                    OS/2 >= 1.3x;
                                                                                                   IBM LAN
DC= Domain                                                                                         Server 3.x, 4.0,
Controller                                                                                         (DC and non-
                                                                                                   DC) OS/2 >=
                                                                                                   2.11
OS & NT                                                    Separate Domain                                            Remove
Recommend                                                  - don’t validate                                           Central Site
                                                           production logons                                          Server from
                       Site Server   Primary Site     Central Site     Secondary Site    Logon Server   Software            Helper Server      SMS Administrator
                                     Server           Server           Server                           Distribution        (additional to     Utilities
                                     (additional to   (additional to   (additional to                   Server              Logon Server
                                     Site Server      Primary Site     Site Server                      (additional to      Requirements)
                                     Requirements)    Server           Requirements)                    Logon Server
                                                      Requirements)                                     Requirements)
                                                                                                        Distribution
                                                                                                        Servers Group;
                                                                                                        If site contains
                                                                                                        multiple NT
                                                                                                        domains
                                                                                                        without trusts
                                                                                                        make sure that
                                                                                                        there is a
                                                                                                        distribution
                                                                                                        server in each
                                                                                                        domain -
                                                                                                        otherwise make
                                                                                                        sure that trust
                                                                                                        relationships
                                                                                                        are setup
                                                                                                        appropriately to
                                                                                                        ensure the the
                                                                                                        clients will have
                                                                                                        NT security to
                                                                                                        distribution
                                                                                                        servers; For
                                                                                                        Netware, only
                                                                                                        allow logon
                                                                                                        servers to be
                                                                                                        distribution
                                                                                                        servers
                                                                                                        (attached /
                                                                                                        logged on
                                                                                                        requirement)
Special Installation   From CD or    From CD or       From CD or       From Primary      From Site      From Site           From Site Server   From CD or Network
Requirements           Network       Network          Network          Site, Using RAS   Server         Server
                                                                       sender - must
                                                                       configure RAS
                                                                       phone book
                      Site Server   Primary Site     Central Site     Secondary Site        Logon Server      Software          Helper Server    SMS Administrator
                                    Server           Server           Server                                  Distribution      (additional to   Utilities
                                    (additional to   (additional to   (additional to                          Server            Logon Server
                                    Site Server      Primary Site     Site Server                             (additional to    Requirements)
                                    Requirements)    Server           Requirements)                           Logon Server
                                                     Requirements)                                            Requirements)
                                                                      entries, Using
                                                                      SNA Sender -
                                                                      must run
                                                                      SNASETUP.EXE
                                                                      on receiving NT
                                                                      computer.
                                                                      MS White Paper
                                                                      and utility tells
                                                                      how to do this
                                                                      from CD - this
                                                                      procedure would
                                                                      not be on the test.


SMS Services:
Scheduler                                                                                                                       Optional
Despooler                                                                                                                       Optional
Inventory Processor                                                                                                             Optional
Inventory Data                                                                                                                  Optional
Loader
Senders                                                                                                                         Optional

Additions:
Mac Client Support                                                                          Site Server: 1)   Distribution
                                                                                            NTFS Volume,      Server: 1)
                                                                                            2) Services for   NTFS Volume,
                                                                                            Macintosh         2) Services for
                                                                                                              Macintosh
Netware Client                                                                                                Distribution
Support                                                                                                       Server: 1) Must
                                                                                                              be Netware
                                                                                                              NOS, 2) must
                                                                                                              be attached or
                                                                                                              logged onto
                       Site Server          Primary Site         Central Site         Secondary Site    Logon Server      Software         Helper Server    SMS Administrator
                                            Server               Server               Server                              Distribution     (additional to   Utilities
                                            (additional to       (additional to       (additional to                      Server           Logon Server
                                            Site Server          Primary Site         Site Server                         (additional to   Requirements)
                                            Requirements)        Server               Requirements)                       Logon Server
                                                                 Requirements)                                            Requirements)
                                                                                                                          distribution
                                                                                                                          server to run
                                                                                                                          packages
SNA Sender /           SNA Server on        SNA Server on        SNA Server on        SNA Server on
Receiver               Site Server or       Site Server or       Site Server or       Site Server or
                       Helper server        Helper server        Helper server        Helper server
                       running SNA          running SNA          running SNA          running SNA
                       Sender               Sender               Sender               Sender
Netware 3.x Server                                                                                      Site Server: 1)
Support                                                                                                 Gateway
                                                                                                        Services for
                                                                                                        Netware
                                                                                                        (GSNW)
Netware 4.x Server                                                                                      Site Server: 1)
Support                                                                                                 Gateway
                                                                                                        Service for
                                                                                                        Netware
                                                                                                        Netware: 1)
                                                                                                        Bindery
                                                                                                        Emulation
                                                                                                        Mode 2) Create
                                                                                                        “EVERYONE”
                                                                                                        group account.
Capabilities
Require SQL Server     Yes                  Yes                  Yes                  No                N/A               N/A              N/A              N/A
Site Management        Yes                  Yes                  Yes                  No                N/A               N/A              N/A              N/A
Child Sites            Yes                  Yes                  Yes                  No                N/A               N/A              N/A              N/A
Configuration Issues   Can be moved         Can be moved         Can be moved         CANNOT be         N/A               N/A              N/A              N/A
                       within Hierarchy     within Hierarchy     within Hierarchy     moved within
                                                                                      Hierarchy
Logon to and           Directly at server   Directly at server   Directly at server   Must administer   N/A               N/A              N/A              N/A
Administer Site                                                                       from a Primary
                                                                                      Site Server
                   Site Server        Primary Site     Central Site     Secondary Site   Logon Server     Software         Helper Server    SMS Administrator
                                      Server           Server           Server                            Distribution     (additional to   Utilities
                                      (additional to   (additional to   (additional to                    Server           Logon Server
                                      Site Server      Primary Site     Site Server                       (additional to   Requirements)
                                      Requirements)    Server           Requirements)                     Logon Server
                                                       Requirements)                                      Requirements)


Group Collection   1) All Global
                   Groups in all NT
                   domains
                   contained in the
                   site.
                   2) Global groups
                   in NT domains
                   trusted by the
                   domains
                   included in the
                   site.
                   3) All Netware
                   groups.
                   4) All LAN
                   Manager
                   Groups.


                                      Windows                            MacIntosh                            OS/2                               DOS
Event to Trap Translator              NT >= 3.5x SP4                     N/A                                  N/A
HW / SW Inventory                     NT >= 3.5x SP2, 95, WFW 3.11,      System 7                             1.3, 2.11,Warp                     >= 5.x
                                      3.1
Software Distribution                 NT >= 3.5x SP2, 95, WFW 3.11,      System 7; Apple Installer (not       >= 2.1                             >= 5.x
                                      3.1                                provided)
Shared Applications                   NT >= 3.5x, 95, WFW 3.11, 3.1      N/A                                  N/A                                N/A
Remote Support                        NT >= 3.51, 95, WFW 3.11, 3.1      N/A                                  N/A                                >= 5.x
 DOS Diagnostics (Interrupts,         NT >= 3.51, 95, WFW 3.11, 3.1      N/A                                  N/A                                >= 5.x
 CMOS, device drivers, ROM
 info, DOS memory, “ping” test)
 Windows Diagnostics                  NT >= 3.51, 95, WFW 3.11, 3.1      N/A                                  N/A                                N/A
 (Memory, Modules, Tasks,
Classes, Heaps)
Help Desk (Remote Control,     NT >= 3.51, 95, WFW 3.11, 3.1   N/A   N/A   >= 5.x
Remote Reboot)
Help Desk (Remote Chat, File   NT >= 3.51, 95, WFW 3.11, 3.1   N/A   N/A   N/A
Transfer, Remote Execute)

								
To top