Hardware and software inventory
Windows 16-bit and Windows 32-bit operating systems
Windows 16-bit and Windows 32-bit operating systems
Windows NT 3.51 _ 2000
Windows 32-bit operating systems
Windows 16-bit and Windows 32-bit operating systems
By configuring an SMS 1.2 site server to be a child site in an SMS 2.0 site hierarchy.
The SNMP Service
A primary site server, server A, can attach to another primary site server, server B. Server A is then a child to server B and server B is the parent to server A. A secondary site server can connect to a primary site server but a primary site server cannot connect to a secondary site server. This means that the secondary site server can be a child to a primary site server but it can never be a parent.
Only the site server is required to run SMS. The site server can run all services for a site, including the site database.
CIMOM is the proxy of most data and interfaces that comply with the WBEM initiative. For example, the SMS Administrator console uses the CIMOM API to communicate with the SMS provider and WBEM namespace.
SMS_S01 is the site database and SMS_S01_LICDB is the software metering database.
|Database||Primary data file
|Size: 20 MB||Size: 10 MB|
|SMS_S01_LICDB||Name: SMS_S01_LICDB_Data.MDF||Name: SMS_S01_LICDB_Log.LDF|
|Size: 10 MB||Size: 10 MB|
The SMS installation routine must access SQL Server to create the site database, and optionally, the license metering database. The account used to create the databases must have the following rights to the master database:
SQL Server version 7.0 is designed to self-configure parameters as needed. This database engine will start with allocating resources to accommodate minimum configuration settings and allocate more resources as needed, up to the maximum values of the configuration settings. If SQL Server resource requirements diminish, allocated system resources are returned to the pool of available system resources.
False. A Windows NT/2000 Server member server can be used as an SMS 2.0 site server and a Windows 2000 Server.
The SMS Administrator console is a WBEM-compliant application. WBEM uses a combination of the user's rights gained from logging on to the network (and thus the WBEM namespace) and rights configured for the user in the SMS Administrator console.
The primary SMS process is the SMS Executive. The SMS Executive uses thread components to complete a wide variety of SMS related tasks, such as configuration management performed using the Hierarchy Manager and the Site Control Manager thread components.
1) Assign a site boundary. 2) Enable a discovery method.
False. If a computer resource runs a client installation method, it will automatically be discovered regardless of discovery method settings.
The recommended procedure is to upgrade to SQL Server version 6.5 running SP4 and then upgrade to Windows NT Server version 4.0 running SP4a. SQL Server version 6.0 is not supported on Windows NT Server version 4.0
Hardware inventory and software inventory.
Scenario 1: You wish to collect hardware and software inventory once a week.
Use a simple schedule set for weekly collection. Set this for both the Hardware Inventory Client Agent and the Software Inventory Client Agent.
Scenario 2: You want to collect only hardware inventory and you need it to occur at 2 a.m. every third Monday of the month.
Use a full schedule from the properties of the Hardware Inventory Client Agent. Set the `Start' value to the third Monday of the current month. Set the `Recurrence Pattern' to Weekly, set the `Recur every' value to 3, and select the `Monday' radio button. Also, verify that the Software Inventory Client Agent is disabled.
Hardware inventory history is maintained on the Windows 32-bit client computer. The site server maintains hardware inventory history for a Windows 16-bit client computer.
The Inventory Processor processes all incoming NHM and RAW hardware inventory files and converts RAW files into binary MIF files. The NHM and RAW files are moved to the DATALDR.BOX directory by the Inventory Processor so that the Inventory Data Loader may move the data into the database.
It defines the classes and properties of hardware inventory that should be collected from client computers.
A package contains at least one program and may contain source files. Distribution points are specified as part of the package to begin the package distribution process.
Software distribution can accomplish scheduled maintenance tasks like virus detection and disk defragmentation; file updates such as a company phone lists distributed to all mobile computers; and application uninstall.
The reference computer is used to determine exactly what changes an installation routine makes to a computer. This information can be used to build an installation script. If the reference computer is significantly different in configuration from the client computers, the installation repackaging process may not build an installation script that will properly install the application.
The Repackage function monitors an application installation, recording all files copied and all files or registry settings modified. The Watch function monitors an application execution (not installation) to determine which compiler support files are necessary to successfully execute the application. It is normally used for custom-developed applications.
Uninstalling an application is simply a matter of selecting a single checkbox to enable it.
Rolling back an application is a matter enabling uninstall support, then either presenting a dialog box to the user to request the backup directory or defining a default backup location.
It uses data summarization schedules.
Exclude these programs from metering.
Configure SMS to use Original names instead of Standard names when identifying programs.
The administrator does not need to know. Automatic license configuring, called license balancing, is managed automatically by SMS.
REMCTRL under \windir\MS\SMS\CLICOMP
The Windows NT Diagnostics - \\COMPUTER2 window appears.
What version of Windows NT is running on Computer 2? Are any service packs applied?
Windows NT Workstation Version 4.0 with Service Pack 4a applied.
No, as determined by using the Services tab.
All Remote Tools utilities with the exception of the Windows NT Diagnostics require the Remote Tools Client Agent.
The computer resource must be an SMS client computer.
The client and the viewing computer must use a common protocol.
The client computer must have the Remote Tools Client Agent installed and started.
The client computer must have enabled permissions for the administrator if the administrator will not control these settings from a central location.
The client computer platform must be Windows 16-bit, Windows 95/98, or Windows NT 3.51 or greater.
Windows NT client computers use Windows NT Diagnostics, not the Remote Tools diagnostics.
Protocols are mismatched on the client computer and the viewing computer.
The Remote Tools Client Agent is not started or installed.
How large was the packet?
Answers vary depending on the number of shared resources in the list.
What is the source IP address?
What shares were listed for SERVER1?
Answers may vary, but should include: Netlogon, Admin$, IPC$, C$, D$, SMS, CAP_S01, SMS_SITE, and SMS_S01.
What was the elapsed time of the capture?
How many bytes were transmitted during the capture session?
Were there any broadcast frames in the capture?
Which protocol (other than FRAME or ETHERNET) generated the highest number of frames?
Answers may vary, but probably IP, TCP, and IP.
Which protocol generated the highest number of bytes claimed?
R_SRVSVC or SMB, depending upon the state of any connections.
Which address generated the highest number of frames?
Answers vary, but usually SERVER1.
Which address generated the highest number of bytes?
The Network Monitor Agent version 2 only runs on Windows NT/2000, and is only required if Network Monitor needs to monitor traffic on a remote segment. This agent is completely independent of SMS services and is not configured from the Client Agents node of the SMS Administrator console.
Filter for Address Pairs specifies the media access control address of each computer. Filter for Pattern Matches filters for specific patterns in Hex or ASCII contained in the packets.
1) Windows NT/2000 computers run the SNMP service to support the Event to Trap Translator Client Agent. 2) Windows NT/2000 computers log events using the Event Logging service, which writes to the event logs.
The Event to Trap Translator Client Agent and the Event to Trap Translator application.
Stop and start the SNMP service.
Info Agent, Info APS, and Info Sentinel.
You can only query using attributes within one object type at a time. For example, if you create a query using the Package object type, you cannot query using attributes contained in the System Resource object type. You can query using more than one attribute within multiple attribute classes as long as the attribute classes are contained in the same object type.
Queries use the WBEM Query Language (WQL) rather than the Structured Query Language (SQL) traditionally used to query SQL server databases. Query data is returned to the SMS Administrator console in the WBEM schema.
1) Define criterion or criteria. 2) Limit the query to a collection. 3) Use the Run Query Special feature to limit the number of records returned from the query.
You must select the Prompted Query criterion type. The answer to the second part of this question will vary. One possible answer is to create a prompted query using available disk space. When the query is run, a prompt will ask the user running the query to enter a percentage of available disk space to complete the query expression.
Info APS is responsible for this task. It is the core service of the reporting function in SMS 2.0.
1) A low performance network connection exists between the main headquarters and the branch office. 2) Local administrative staff are available to manage SMS locally. 3) There is political and organizational pressure to segregate the sites. 4) Software distribution will be used extensively between the main headquarters and the branch offices.
1) Fast and underutilized network connections exist between the main headquarters and branch offices. 2) There is a need to reduce administrative tasks by implementing sites only at the main headquarters. 3) Hardware inventory is the only SMS function that will be implemented between the main headquarters and the branch offices.
The central site should be located at the main headquarters where most employees are being supported. This will reduce the amount of network traffic generated from intersite communications.
Logon points are created in the SMS Administrator console from the Discovery Methods and Client Installation Methods node. Other site systems are created from the Site Systems node.
These files are involved in change management. The Hierarchy Manager creates a *.CT1 file to inform the SMS Site Control Manager of a proposed change. The Site Control Manager reads the *.CT1 proposed change, makes a copy of the master site control file (*.CT0) and initiates the change. A *.CT2 file is created and returned to the Hierarchy Manager to update the database with the changes made to the system.
All site systems are considered component servers. A common use of a component server is to provide a WAN Sender connection to other sites. This is often implemented using the RAS dial-out client software.
The site layout shows the entire network structure of the site. The trace layout only traces the path from the selected site system back to the site server.
View the site hierarchy from the parent site server (S01). The child site server name will be added to the hierarchy below the parent site.
SERVER1 and DOMAIN1\SMSSERVICE.
The `Type' value designates primary or secondary site status.
A parent site is a site with subsites below it. A child site is a site that has a parent site.
Only a primary site can be a parent site.
Each site can support one of each sender type. Therefore, a total of six sender types can be configured to communicate between sites: Standard Sender, SNA RAS Sender, Asynchronous RAS Sender, ISDN RAS Sender, X.25 RAS Sender, and the Courier Sender.
All senders except the Courier Sender fully support site-to-site communications. The Courier Sender supports only site-to-site package transfer using removable media.
The purpose of an address is to tell the sender how to reach the other site and how the network should be utilized when data is transmitted from one site to another. The purpose of a sender is to provide a mechanism for transporting data from one site to another.
Rate limits tell the sender how much and when the network connection should be utilized for transmitting data from one site to another. A schedule tells the sender when an address is available to receive data and what level of data priority is necessary to send data. Sender control settings control how many sender threads are created to send data from one site to another site or from one site to all sites. Retry settings control how many times and how often the sender attempts to transmit data between sites. In a multiple-sender configuration, sender priorities control the order of priority among all senders configured for a site. If a sender fails, the next highest priority sender transmits the data.
1) Provide redundancy in case of sender failure. 2) Provide more than one route for sending multiple jobs. 3) Provide the option of scheduling senders based on cost and time of transmission.
Discovery data is sent from the child to the parent site.
If a package and other data must be sent from a primary site to a site that is more than one-level deep in the hierarchy, the data can be sent via package routing.
NT Authority\System and Administrator.
Collections, packages, advertisements, status messages, sites, and queries.
All object instances of each object class.
A user should not be able to access any objects.
No. The shortcut to the SMS Administrator console could not be found.
No. NTFS permissions prevented access to the file.
The Administrators local group with Full Control permission and the SMS Site System Connection account with Read permission.
Yes. NTFS permissions allowed access to the required files.
No. The user does not have permissions to the SMS site database through the WBEM/SMS Provider interface.
Yes. NTFS permissions allowed access to the required files.
Yes. The user does have the required permissions to the SMS site database through the SMS Provider.
No. Only Read permissions were granted.
No. No permissions to queries were granted.
DOMAIN1\SMSService. This account was created during SMS setup.
Administrators, Domain Admins, and Domain Users.
Info Agent, Info APS, Info Sentinel, SMS_Executive, SMS_Site_Component_Manager, and SMS_SQL_Monitor.
It is used for remotely installing Windows NT client computers when the logged-on user does not have local administrator permissions.
The SMS Service account. For your configuration, it is DomaiN1\SMSService.
The SMS Service account must be added as a local administrator. This is accomplished by the automatic inclusion of the Domain Admins global group as a member of the client computer's Administrators local group.
No account is listed if integrated security is used. Standard security is being used for the site database, it displays sms_serv as the SQL Server account. This is the SQL Server account you created in Chapter 2 to access the site database.
Administrators and Domain Users.
No services on the site server use this account to run.
Administrators and SMSInternalCliGrp.
The SMS client components on the Windows NT client computer connect to the SMS site systems using the SMS Client Connection account.
The SMS Client Connection account, SMSClient_S01.
This account is used when SMS_Executive services, running on servers other than the site server, need to connect to the site server to transfer files.
Administrators and Domain Users.
The SMS_NT_Logon_Discovery_Service on the domain controller uses this account to connect to the site server to transfer data discovery records (DDRs).
No, there is no need for concern.
First, the site server should be physically secured from user access (in a locked room). Next, the Windows NT account policies prevent the user from improperly accessing the SMS site server directory structure.
If a user could physically log on to the site server, NTFS permissions would prevent the user from running the SMS Administrator console. Further, the user would need permissions to access the data through the WBEM namespace. Finally, the SMS Provider would prevent the user from accessing any objects to which they do not have rights. By default, the user would have no rights.
Each group should install the SMS Administrator console on local Windows NT Workstation computers.
Windows NT global groups should be created for each administrative group.
Appropriate users should be added to each Windows NT group.
SMS security objects should be created for each group for the appropriate objects.
For each group custom SMS snap-ins should be created that present the appropriate SMS objects.
The installation routine is attempting to access network resources that the client computer user does not have the rights to access. If a program requires administrative permissions and network access, the program should be configured to use the Windows NT Client Software Installation account. This is done by selecting the `Use Windows NT client software installation account' checkbox on the program's Environment tab. This option is found under a package listed below the Packages node.
The user account and password specified in the SMS Administrator console has not been created in the NetWare user account database.
The MSSQLServer service is not running on the SQL Server. If all of the SMS services are stopped, connection to the site database will be successful.
The SMS SQL Monitor process and the Trigger Manager thread.
SQL Monitor is installed on the computer running SQL Server. In this situation, SQL Server must be located on a computer other than the site server.
1) Restore SITECTRL.CT0 from a previous backup. 2) Run PREINST /DUMP to rebuild a site control file from the site database.
The `truncate log on checkpoint' option is disabled for tempdb. Enable this option so that the transaction log does not grow out of control.
You have two choices:
1) Restore the SMS registry keys and site control file that were saved with the database. This restores the system to its configuration when the backup was run.
2) Reset the site through SMS setup, which will synchronize the database with the current SMS registry and site control file.
If a Windows NT/2000 domain controller is part of a domain that is defined using the Windows Networking Logon Discovery method or the Windows Networking Logon Installation method, SMS will automatically install it as a logon point. If a NetWare server is enabled using the NetWare Bindery Logon Discovery method, the NetWare NDS Logon Discovery method, the NetWare Bindery Client Installation method, or the NetWare NDS Client Installation method, then the logon point will automatically reinstall. If the NetWare server does not appear using these discovery or installation methods, add it through the SMS Administrator console.
SMS_EXECUTIVE, SMS_SITE_COMPONENT_MANAGER, SMS_SQL_MONITOR, and SMS_NT_LOGON_DISCOVERY_AGENT
SMS_NETWORK_DISCOVERY and SMS_WINNT_SERVER_DISCOVERY_AGENT.
If the instructions in "About This Book" are followed, the size of the SMS installation drive (drive D:) is approximately 2GB or larger.
Someone has enabled a status filter rule that logs events to the Windows NT Event Viewer Application log. Find and disable the status filter rule in the details pane of the Status Filter Rules node that is logging events to the Windows NT Event Viewer Application event log.
The SMS Executive is a process that runs many threads appearing in the SMS Service Manager. When the SMS Executive is stopped, so are all of the threads run by the SMS Executive.
The SMS site namespace is stored in the WBEM repository, not the site database. Therefore, even though the SQL Server running the site database was stopped, the namespace is still available. Object instances, however, are stored in the site database. Therefore, you must first start the SQL Server running the site database before accessing this information.
The HealthMon Client Agent must be installed on all Windows NT/2000 computers that will be monitored by HealthMon.
There are a number of reasons why a secondary site installation fails. Two possible causes are that the service account used to install the secondary site server does not have enough rights to the secondary site server. This account must be granted administrative privileges to the secondary site server and be granted the `Logon as a service' advanced user right to complete the installation. Another cause for a secondary site server installation failure is a lack of disk space or the fact that there are no partitions formatted to NTFS. Review the SMS_BOOTSTRAP.log on the computer targeted for the secondary site server installation.