SMS 1.2 Exam
Chapter 2: Prepare a site for SMS installation
Configure NT to replicate Logon scripts
Create Service Accounts
Service account must have Administrative rights in all environments (dealt with). In a trust relationship environment, create the account in the master or trusted domain. For LAN Manager, create the account in the ADMINs group. All accounts across all environments must have the same user name and password
Note: Remember: needs Logon as a Service right, Replication and Backup Operator privileges
Configuring Netware Support
For Netware, must have full access to all volumes. Netware also requires; IPX/SPX and correct frame type, GSNW and the correct SMS Service account n the Netware Server.
Configure SQL Server for use with SMS
Hardware Requirements: NT 3.51 or later, RAM: 16 or 32 with Replication, 60mb (+15 for SQL online reference). Note: realistic estimate is 128 meg of RAM
Security- Three Types: Standard (SQL server specific), Integrated (uses Windows NT security and the SQL Server Security Manager) and mixed
SQL Executive Service Account: manages replication task, event and alert managers
SQL Server installation: nine stages selecting character set, sort order and network support
Installation Defaults:
Master Database 25 meg
Character Set: ISO 8859-1
Sort Order: dictionary, case-insensitive
Note: changing the character set or sort order will require that the DB be rebuilt and the data reloaded
SQL Server Services
MSSQLServer has three states; started (accepts new logons and responds to requests, paused (responds to requests, does not accept new logons) and stopped (no requests and no new logons)
SQL Executive allows for event scheduling, alert notification and other management functions
Configure SQL Server for use with SMS
Memory: assign most of the available RAM to SQL server but leave 16meg for NT
Connections: each session of SMS administrator takes five connections (37 Kb of RAM for each connection)
Open Objects: 500 is default, 5000 is recommended
Procedure Cache: default is 30 (percent). For servers with more that 128 meg or RAM, bump this number down to 15 or 10 (percent)
Size of TempDB: default is 2meg, recommended is 20% of SMS database
Monitoring SQL Server
SQL Server Cache hit ratio: should be high
Windows NT paging: should be low
Locks: ??
CPU: consistent use of over 80% is a bad thing
Chapter 3: Installing an SMS site
Identify changes made to site server and logon servers
Install a secondary site
Add domains to an SMS site
Installing SMS site Servers
Requirements:
SMS 1.2 requires 500meg NTFS HDD.
SQL Server logon
If installed on a different machine than SQL server, must manually create two devices and databases (SMS database and one for the transaction log)
SMS requires 20 user connections to the SQL server
SMS database device default: 45 Meg
SMS log database device: 10 Meg
Installation Failure? Check SMSSetup.log
SMS Services
SMS_CLIENT_CONFIG Manager: carries out configuration of the site
SMS_Executuve: provides the parent service used by SMS
Alerter: processes alerts
Applications Manager: creates and copies information about packages to components between sites
Despooler: decompresses and distributes packages to distribution servers
Inventory Data Loader: loads MIF files to the database
Inventory Processor: checks RAW files for consistency, compiles RAW files into MIF files, maintains history for each machine.
Maintenance Manager: maintains consistency between sites, takes inventory of Netware servers
Scheduler: Compresses software for distribution chooses appropriate sender
Sender: Manages communication between sites.
Site reporter: reports inventory to parent site
SNMP Trap Receiver: monitors SNMP traps
SMS_Hierarchy_MANAGER: monitors database for changes, creates a site control file, passes it to
SMS_CLIENT_CONFIG_MANAGER
SMS_INVENTORY AGENT: gathers inventory information for NT machines
SMS_PACKAGE_COMMAND_MANAGER_NT: executes run jobs on NT machines
SMS Remote Control agent: enables remote control
SMS_SITE_CONFIG_MANAGER: configures a site based on information received from
SMS_Hierarchy_MANAGER
Viewing Directory Changes
Upon install, three new shares are created, upon creation of the first package one more is created.
SMS_SHR as SMS\Logon.SRV: exists on SMS logon servers. Where client gathers files relating to inventory, software distribution and logon validation
SMS_SHRX as X:\SMS: SMS services use this directory to share info.
SMS_SITE as \SMS\Site.SRV\Despooler.box\Receive: remote sites use this share to send data to the local site
SMS_PKGx is created on the hard drive with the most space. Implies that the local server is a distribution server.
Setting up Secondary Sites
A secondary site reports to a parent site and does not have its own SMS database. To attach to another parent site, you must de-install from the first site and the re-install to the new parent site. Note: SMS tools are not installed on a secondary site
Requirements:
50 Meg NTFS HDD
Secondary site must an SMS account (Administrative privileges)
If second site is connected by SNA, need to manually install and start the bootstrap services
Secondary Site Setup (4 Phases)
During install three system jobs are created: site pre-install, site install and site control.
Removing a Secondary Site
Use SMS administrator and just delete the fucker!
Adding Netware Logon Servers
Use IPX/SPX (SMS does not support Netware IP)
Install and enable GSNW (allows for the use of NCP)
Create SMS Admin account on Netware server (needs all rights to all volumes)
Note: SMSLS.SCR is used by Netware to install SMS on clients
Chapter 4: Understanding the Site Configuration Process
Site Configuration Process
Two SMS services are involved: Hierarchy Manager and the Site Configuration Manager (see description in chapter 3)
Process Flow:
The process begins with a *.CT0 (located under Sitecfg.box) file representing the current config.
Hierarchy Manager checks database. If there are proposed changes, creates a *.CT1 file (change request file)
The CT1 file is passed from the Hierarchy Manager to the Site Configuration Manager and a CT2 file is created to indicate that the changes have been committed. (A confirmation file)
The CT2 file is then passed back to the Hierarchy Manager who then updates the database and creates the SITECTL.CT0 file (current status file)
Configuring Client Options
Note: Under the Client configuration form, choose the Options button to set which groups can remotely control Windows NT computers and which video accelerators to use.
Configuring Inventory
Hardware and software scans occur once every seven days (can change the interval from every logon to once every 365 days)
Inventory Slow Link Options: always take inventory, prompt the user, and dont take inventory. A slow link is 1024 bytes transferred in more than 850 ms. (14000 BPS modem)
Inventory and RAS: use the CHECKRAS and SKIPINV utilities
Note: Global inventory settings are stored in the DOMAIN.INI (located on the logon servers) and local settings are stored in the SMS.INI file.
Configuring Distribution Servers (Package Server)
A machine chosen as a distribution point for SMS packages
Note: With Netware clients, ensure that at least one Netware package server (or else your clients will not get their packages)
Helper Servers
Four SMS services that can offloaded onto a helper server;
To add a helper server, use SMS administrator, choose the Services button, and enter the name of the helper server
Service Polling Intervals
Very fast (test mode): one-minute intervals
Fast: five-minute intervals
Medium: fifteen-minute intervals
Slow: thirty-minute intervals
Configuring SNMP Traps
Note: May require latest SMS service pack
Configuring Logon Scripts
Three major steps in configuring logon scripts
Note: NT replication must be working correctly for the script replication to work.
Note: Users will have their logon script set to SMSLS.BAT (SMS Logon Script) unless they already have a logon script. Netware users will have a SMSLS.SCR file
Manually Configuring Logon Scripts
Use the RUNSMS.BAT file to manually specify to specify your SMS logon server. If replication is not used (or not working) copy all of the files found in the SMS\Site.SRV\Maincfg.box\client.src folder to the desired NETLOGON share
SMS Trace (SMSTRACE.EXE)
Loads log files for SMS services. Log files "wrap" after 128 K (1000 lines) so reload the file if you think the file has "wrapped". Duh!
Chapter 5: Installing the SMS Client
Inventory Agent
MSDOS. Windows 3.x,95,98: INVDOS.EXE (invoked by SMSLS or RUNSMS)
Windows NT/SMS Logon Servers: INVWIN32.EXE (polls every 24 hours and runs under the security context of the SMS administrator account
Windows NT workstations: INVCLI32.EXE (under local system account and polls every 24 hours). CLIMONNT.EXE checks determines if a user is logged on.
OS/2: INVOS2.EXE (just like the DOS client)
Macintosh: InvMAC (run from the Startup Items folder, not at logon)
Methods for client installation
SMSLS.BAT or RUNSMS.BAT: Windows NT, Windows 3.x, and 945 clients
SMSLS.CMD or RUNSMS.CMD: OS/2, LAN Manager, and IBM LAN Server
SMSLS.SCR: Netware clients
Apple Installer Utility: Macintosh clients
Note: Apple clients will require some manual intervention
Client Software
Package Command Manager: Installs software or runs commands
Program Group Control: runs shared applications
Remote troubleshooting: allows remote control
MIF Entry: allows clients to fill out custom forms
Client Installation Process
SMS.INI file
A hidden file, unique to each computer, should never be copied to another workstation
Sections
[Package Command Manager] : determines PCM location files, results directory and local status files
[Servers] : a list of logon servers for the client domain
[Share] a list of the shares used by the client components
[Program Group Control] location of network application database that stores configuration information for shared applications
[MSTEST16.20] Location of the default script processor
[WorkstationStatus] client status, includes inventory and failed hardware checks
[SMS] SMS configuration settings. Duh!
[Local] local configuration settings (also used by PCM)
[Sight] help desk settings
[AppleServers] list of Apple servers
Installing SMS Client on Windows 95 Machines
The following files are modified;
Autoexec.bat: \MS\SMS\DATA\CLIENT.BAT is run before starting Windows
WIN.INI: SMSRUN16 is added to the LOAD= line
SYSTEM.INI: NetHeapSize is changed and the line DEVICE=%WINDIR%\VUSER.386 is added to support remote troubleshooting.
Installing SMS Client on Windows NT Machines
The Package Command Manager (PCM) is installed as a service. Program Control Group is not a service, even under NT. The SMS installation requires administrator rights and the "Logon as a Service" right.
Troubleshooting Client Installs
For Windows NT clients;
Files Stored on the Logon Server
DeInstall.BAT: uninstall the SMS client
RUNSMS.BAT: installs and runs the SMS client
DOMAIN.INI: master template for the SMS.INI file
\Appctl.box: instructions for shared applications
\Inventory.box: inventory files until they are moved to the site server
\MSTest: support files for MSTEST
PCMins.box: instructions for Package Command Manager
\SMSID: contains the next available SMS ID number
\X86.bin: EXE and DLLs for the SMS client installation
Interacting with the Client
Each client receives the following from the logon server:
Each client places the following on the logon server
Configure Client Options
Chapter 6: Managing Hardware and Software Inventory
The Inventory Process
Managing Inventory
Three ways for the inventory process to happen;
Configure logon scripts to include the inventory process
Configure a manual inventory collection
Install the Inventory agent as a service (Windows NT)
Hardware Inventory
Cant change the defaults; CPU, memory, HDD. For anything else, you need custom MIFs
Software Inventory
Create an Inventory package: Quick and easy. Can collect files if found but not for more than 2-3 files.
Note: PKG_16.CFG is the config file for Inventory packages, located under LOGON.SRV and applies to all clients
Perform software Audit: scan workstation for files (100s or 1000s)
AUDIT.RUL contains 5000 files to audit (located under SMS\PrimeSite.srv\Audit) which is converted to AUDIT.CFG by the RUL2CFG batch file.
Loading Files into the SMS Database
Process as follows;
The Maintenance Manager service moves the files from the Logon server to the Site Server
The Inventory Processor takes the RAW or MIF files, determines if there is a change from the history file (\SMS\Site.SRV\Inventory\History) and then creates a Delta-MIF file which contains the differences. Delta-MIFS are created in the \SMS\Site.srv\Dataload.box\deltamif.col folder
The DataLoader Service takes the Delta-MIF file and uploads it to the SQL database. Record matches are determined by; SMS ID, computer name and MAC address.
To minimize re-syncs;
Running the Inventory Agent Early
Three ways;
Set the SMS site to take inventory at each logon (bad as this a global settings for the whole SMS domain)
Edit the SMS.INI file and manually change the date of the last scan
Use the /F switch to force an inventory
Note: /v is for verbose, /e is for Windows NT services to run as EXEs
Customize Inventory Data
Creating Alerts
Alert: a query run at regular intervals which then can perform an action (raise and NT event, execute a command line or send a popup message)
Must do Chapter 6 again!!!!
Chapter 7: Managing the SMS Database
Adding Custom MIFS
Use the SMS MIF form generator to create a MIF
Distribute your MIF by a Run Command (workstation job)
Note: MIFSs are stored on the client under \MS\SMS\BIN
Database Security
Access to SMS depends on three types of SQL controls:
Backing Up Databases
Backup the SMS database involves three set of items;
Two ways to run a backup; use a SQL specific agent to backup the database or perform a database backup (dump)
Restoring an SMS Site
If the SMS database becomes corrupted; Delete the database and the devices the databases reside on, then make a new database at least as large as the previously corrupted one.
If the SMS site server becomes corrupted; restore the files, folders and registry from backup. Logon servers should use the normal system backup. SMS clients can have a re-install (then use the SMS Database Manager to merge the new records.
Chapter 8: Help Desk and Diagnostics
Note: No helpdesk or diagnostic support for Macs or OS/2 or NT 3.5
Diagnostic Utilities
Provides list of; CMOS info, Device Drivers, ROM, Interrupt Vectors, DOS memory and the Ping test (not the TCP/IP ping)
For Windows machines, the following additional services are available; Windows memory, modules, classes and tasks, Global and GDI heap
For Windows NT machines; OS Version, Services, DMA, hardware, devices, network and drivers.
Remote Help Desk Utilities
The following remote control utilities are available; remote control, remote reboot, remote chat, file transfer, remote execute.
Help Desk Utility and Diagnostic Requirements
The client must have been inventoried
Remote control agent must be enabled on the client computer
The user must allow remote access to the computer
Both computers must share a common protocol.
Remote Control Software
Windows computers: WUSER.EXE
Windows NT computers: WUSER32.EXE (as a service)
DOS computers: USERTSR.EXE or USERIPX.EXE for Netware servers (also for Windows machines connecting to Netware servers.
Required INI Files (SMS.INI [SIGHT])
The following values are required in the hidden SMS.INI file under the [SIGHT] section;
Allow Takeover, Allow Reboot, Allow File Transfer,
Allow Chat, Allow Remote Execute, Visible Signal, Audible Signal
Allow ping test, Allow DOS diagnostics, |Allow Windows diagnostics, permission required.
NetBIOS and LANA Numbers
With machines with multiple protocols loaded, the viewer computer will search through all of its available protocols (IPX, IP, and NetBIOS) while the end machine will only use the first loaded protocol. So, use the CLIOPTS utility to set the remote machines SMS.INI (the OPTIONS and LOCAL sections) to support a specified LANA number (most likely 1 or 2)
Remote Control can not be used over the SNA protocol, third party stacks or Netware IP.
Windows NT Computers and Remote Control
WUSER32 is already started as a service (if the installation was successful)
Note: Uncheck the Permission Required and Visible Signal boxes, as they are a real pain. Also, select all of the Remote Viewer option checkboxes.
On a Windows NT box, the port address you are listening to is listed
Windows 95 Computers and Remote Control
Ensure that the WUSER.EXE file is loaded either by adding it to the LOAD= line in the WIN.INI or in the RUN=
Note: LOAD starts the remote control program in minimized mode, while starts it in maximized.
Remote Control and DOS Machines
Need a USERTSR or USERIPX command line added to the AUTOEXEC.BAT file. Starting USERTSR or USERIPX with the v switch enables the SMS.INI sight section for one time only.
Notes on Remote Control
RAS Issues:
DOS Client Issues
The MS Network Client (3.0) that ships with NT will not work when NWLink is the primary protocol.
A DOS client will not work with TCP/IP and WINS. The viewing computer will need a LMHost file with the target computers address.
Novell Netware Issues
The following files are required when Netware clients only logon to a Netware server; NWNETAPI.DLL, NWCALLS.DLL and NWIPXSPX.DLL. If the client does logon to a NT server then most likely only NWNETAPI.DLL will be missing
Chapter 9: Managing Software Distribution
Three Types of Packages;
Distribution Jobs
There are four types of jobs;
Note: Software rollback procedures impact all designated servers and workstations try a limited roll-out of one or two users before the big push. Microsoft recommends that you wait 48 hours after canceling a job before you delete it.
Creating Software Distribution Packages
Basic steps;
Distribution Job Phases
Job Phases:
Send phase sends the package to target sites
Distribute phase sends the package to distribution servers
Run phase send the package to client computers
SMS Service Operations
Important: Remember the order of these events
Note: the SMS share SMS_PKGx is off the root of the drive, not under the SMS directory
Note: Wxx workstation packages, Sxx server jobs and Pxx represent Removal jobs
Running Distribution jobs using PCM
The clients that support PCM; MS DOS, Windows 3.x, 95 and NT, and Macs
Monitoring the Distribution Process
Things to check when things go wrong with a job
Job Progress by Directory
Removing Packages from Servers
File locations to check when Removing Run Commands on Workstation packages
To remove a package, simply create a job with a job type "Remove package from Server" (listed in the job type drop-down box)
Chapter 10: Managing Shared Applications
Benefits of using Shared Applications
Shared Application Setups
Two methods: software is installed on the client computer from a shared source, or all the software resides on the server and users run the application across the network.
Shared Applications on Users Computers: Uses PCM and "Share application on Server" Job. This method uses a server as a source repository with a specific install command offered to the client via the PCM.
Share Applications on a Server: The Program Group Control application acts as the connecting point to the source software on the server.
Requirements for Shared Applications
Changing the User group interval
Two ways of changing the user group reporting interval (the period of time between user group enumeration events the default is once every 24 hours)
Using the registry, change the User Group Reporting Interval setting:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\SMS\COMPONENTTS\SMS_SITE_CONFIG_MANAGER
Or, use the SETGUG.EXE utility (SETGUG /E ON|OFF /I DAYS)
To manually force user group enumeration;
UGMIF.EXE (also requires SMSAPI.DLL and OBJECTTY.DLL)
SENDCODE.EXE SMS_SITE_CONFIG_MANAGER 195
Configuring the Client
The SMSRUNxx.INI (located under \MS\SMS\Data) file tells the client which programs to load and where to the find the programs. The SMSRUNxx.EXE file reads the INI file, loads the correct programs. The APPCTLxx.EXE program reads the NAD (Network Application database located under \SMS\LOGON.SRV\APPCTL.BOX\DATABASE and build the program groups.
APPSTART.EXE locates and runs SMS shared applications (located under the WINDOWS directory). It is also responsible for randomly selecting a distribution server. Windows 95 machines have a file called SMSROUTER.VXD that handles the random distribution of servers
APPSTART.EXE does the following;
Note: the SMSROUTER.VXD requires UNC names.
Removing Shared Applications
Creating a Remove Share Application package deletes the following files;
\SMS\SITE.SRV\DESPOOLER.BOX\STORE\SMSID.SRV
The package share name
The following files stay;
\SMS\SITE.SRV\SENDER.BOX\TOSEND\SMSID.Sxx
\SMS\LOGON.SRV\APPCTL.BOX\DATABASE\xxx.HAF and xxx.HGF
Note: To delete the xxx.HGF and xxx.HAF files delete the program group from the Program Groups window in SMS Administrator
Monitoring Shared Application Processes
Shared application groups have the extension HAF and HGF
Instead of Wxx files, Sxx files are found in \SMS\SITE.SRV\SENDER.BOX\TOSEND folder
Instead of a final directory called SMS_SHRx, you will have directory called by the name you gave the initial package
SMSTRACE will show the replicate of the HGF and HAF files.
Chapter 11: Planning your SMS Hierarchy
Some requirements when planning a multi-site hierarchy
The following network infrastructure concerns should also be reviewed;
In multiple SMS Site installations the following rules apply;
Note: The network limit for deciding whether a site should be a child site is 64 Kb.
Parent-Child Relationships
The top site in the hierarchy is the central site. A secondary site is always a child to a parent site. Secondary sites do not have their own SQL database or the Data Loader Service
Configuring Site to Site Configurations
Configuring communications between sites is done with Site Addressing. You cant configure both addresses at the same site.
Manual Site Addresses configuration is not required for secondary sites as when the secondary site was created, the parent child addresses were automatically created.
Three pieces of information that are required when setting up site to site communication;
Note: the account on the destination server only really requires Change rights to copy files over.
Attaching a Primary Site to another Primary Site
Removing a Primary site
Sender and Address Configuration Notes
Total Concurrent Sessions: 5, with 3 per site (default)
Retry at 5 times every 1-minute
Note: SMS assumes you have 4 gig of available bandwidth
Adjusting the estimated bandwidth for your network change the following registry key;
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Sites\site_code\Addresses\site_code\sender_number
Configuring Senders
Three type of RAS senders; X.25, ISDN and Asynchronous
Two types of SNA senders, batch and interactive
Chapter 12: Monitoring and Trouble Shooting SMS
Each process has its own logs (stored under \SMS\LOGS). The SETUP LOG is stored under the root directory and the Site Configuration Manager is in the root of the SMS directory
SMS Logs warp at 128 KB (1000 lines). Use the SMS Service Manager to increase the size of the log (under the Tracing Button). Use SMSTRACE to view the log files.
Trouble Shooting SMS Services
Heres a review of the SMS services
Trouble Shooting Primary Sites:
Installation Requirements:
Note: check the SCMAN.LOG file located at the root of the drive where SMS was installed
Trouble Shooting Secondary Site Server Installations
You can look for software problems as follows;
Three system jobs are created; Site pre-install, Site Install and Site Configuration
Note: most common failure is lack of disk space
Site Pre-install Failures:
Site Install Failures
Site Configuration Failures
Most likely a problem with a sender (meaning RAS or SNA) or the SMS account does not have the correct rights (check the SCMAN.LOG)
Trouble Shooting Inventory Collection
Three major places where the inventory process can go wrong
Trouble Shooting the Client Side
Trouble Shooting the Server Side
Two general methods for trouble shooting the inventory process on the server side:
Watch files as they are processed and moved through the system
Watch log files from services
The process is as follows;
Note: if a client is creating bad inventory files use RAWCHECK.EXE
Trouble Shooting Software Distribution
Note: DUMPSEND.EXE can be used examine the contents of an SRQ or SRS file.
Trouble Shooting Shared Applications
Trouble Shooting Site to Site Communications
Interesting References
TechNet Articles:
Q168724
Q173120
Q123317
Q171342
Search the Microsoft Web Site for:
Tracing a stuck job
Installing the PCM Service on SMS 1.2 Clients
How to report Package Installation Status
Interesting EXEs and Tools
ISMIF32.EXE will report the success/failure state of an application installation routine