Crystal Reports for SMS Readme

by

Crystal Services

Installing Crystal Reports for SMS

Runtime File Requirements

Runtime Agreement License

Technical Support Information

Using Sample SMS Reports

SMS Reports by Crystal


INSTALLING CRYSTAL REPORTS FOR SMS

1.	Change your active directory to the \reports\disk1 directory on the Systems Management Server CDROM.

2.	From the Windows Program Manager, select the File|Run command.

3.	When the Run dialog box appears, type: setup and then select OK or press Enter to call up the installation program.

4.	Once the installation is complete, simply double click the Crystal Reports for SMS icon.

If you have any problems running Crystal Reports, check for hints in the Crystal Reports Help file. Most of the configuration problems you may run into are covered in this file. There will be icons created in Program Manager Systems Management Server for Crystal Reports, Crystal Reports for SMS Help, Crystal Reports for SMS Readme, ODBC Setup and ODBC Administrator.

When you are installing Crystal Reports there will be a file created called CRWSETUP.LOG.  This file logs all of the information regarding the installation.  If you have a problem with the installation please have the information from this file ready when you contact Crystal Services' Technical Support Department.


RUNTIME FILE REQUIREMENTS

File Requirements:

As a registered user of Crystal Reports for SMS, you are allowed to distribute a runtime version of the Crystal Reports print engine with your applications at no charge. The following is an overview of runtime requirements:

For all applications

The following files must be included on a distribution disk, regardless of the application it accompanies:

File

Description

CRPE32.DLL

Interface to the print engine

COMDLG32.DLL

Help with printer selection, etc.

CRXLAT32.DLL*

* You need to include this file only if you are going to use the ToWords(x) or ToWords(x, #places) functions in your reports.

Database specific requirements

The following files are necessary for their respective databases. If your application will not be reporting on one or more of these databases, then do not include the files for those databases.

ODBC

Include the following files if your application will be using ODBC:

ODBC32.DLL

Microsoft ODBC DLL

ODBCCP32.DLL

Microsoft ODBC Install DLL

ODBC.INI

Microsoft ODBC INI

ODBCINST.INI

Microsoft ODBC Install INI

P2SODBC.DLL

Crystal's ODBC DLL

NOTE: You must ship ODBC.INI files that are configured appropriately for the database(s) your application is using. You do this using the ODBC Admin program, ODBCADM.EXE  The ODBC.INI file must point to the location in which your ODBC drivers will be installed.

Export specific requirements

If your application will give your users the ability to export their reports, you must include files from the following list appropriate to the export options provided:

Format DLL's

u2fcr.dll

Crystal Reports format

u2fdif.dll

DIF (Data Interchange Format) format

u2frec.dll

Record format

u2frtf.dll

Rich Text Format (RTF)

u2fsepv.dll

Comma separated values format

u2ftext.dll

Text format

u2fwks.dll

Lotus 1-2-3 format

u2fxls.dll

Excel format

Destination DLL's

u2ddisk.dll

Disk file destination

u2dmapi.dll

MAPI format (Microsoft Mail)


RUNTIME SOFTWARE LICENSE

Permission is granted to the original purchaser of this Runtime package, under Crystal Services' copyright, to reproduce and distribute exact copies of the Runtime software, and to modify, reproduce and distribute the sample applications, made from the original disks in this package (or a set of backup copies made directly from them), provided that:

Such copies are distributed for the purpose of executing specific-purpose application programs written using an authorized copy of Crystal Reports.

The user will remain solely responsible to anyone receiving such copies for any support, service, upgrades, technical or other assistance, and such recipients will have no right to contact Crystal Services for such services or assistance.

The Runtime program will not be altered, disassembled, decompiled or reverse-engineered.

Crystal Services provides no warranty at all other than the Limited Warranty provided in this package to the original purchaser.  The purchaser will indemnify and hold Crystal Services harmless from and against any claims or liabilities arising out of its use, reproduction or distribution, and the use by the recipients of copies made hereunder.

The permission granted herein is solely for the purpose of using the Runtime program and custom applications to execute specific-purpose application programs written using an authorized copy of Crystal Reports. The user is not authorized to include the Runtime program or custom applications in any general-purpose report writing and/or database querying product, or in any product that is otherwise generally competitive with Crystal Reports Pro.

If you wish to distribute copies of the Runtime software or custom application on other terms, please contact Crystal Services directly.

NOTE:  Please check the manual of your development tools to see if there are additional tool-specific requirements.


Technical Support

Before contacting Technical Support make sure you have registered your copy of Crystal Reports and have the following information ready:

•	what version of Crystal Reports you are using

•	what type of data are you using

•	how many versions of CRPE32.DLL are on the system, their locations, file sizes, and dates

•	listing of files in the CRW, WINNT35\System32, report, and database directories

•	if possible, a file sorted by file extension, creating by  typing:

dir /oe > filename.dir

Crystal Services provides On-line (modem), fax, CompuServe and telephone support:

On-line	(604)662-8298

If you have a modem On-line support is the most convenient and effective way to solve your problems.  To use it, go to the Help menu and choose Technical Support.  Fill in the details on your problem and Attach any relevant files.  To transmit, Click on the Connect button. Your request is electronically sent to the Crystal Reports Technical Support Server and is immediately given an Id #..  Telephone charges are minimal as the connection time to the Server is brief.

A Technical Support Representative will review your request and send you a response. Check for a response by going to the Help, Technical Support and Clicking on Connect. Updated information on all outstanding requests is immediately transmitted back to you. If your problem is still outstanding, a reply such as "requires liaison with the Crystal R&D team in progress"  will be provided.

NOTE:  You do not require any communications software to use On-line support. The software is built in - all you need is a modem!

Fax	(604) 681-7163

To prepare your fax request, go to the Help menu, choose Technical Support and fill in the details on your problem. Print the form and fax it Crystal Services.  Note that this form provides valuable information that often contributes to the resolution of your problem.

CompuServe	CompuServe address 72223,2632

Please leave CompuServe messages on the MSBASIC forum in the Third Party area with the word CRYSTAL in the title.  That way other users can benefit from the answer.  You may find that the answer to your problem is already there!

Telephone	(604) 669-8379

Make sure that Crystal Reports and the problem report are both loaded.


USING SAMPLE REPORTS

Crystal Reports for SMS comes with a number of ready-to-run reports. In order to use Crystal Reports with Systems Management Server, you must first create the views in the database that are used to access the data.  Please read Appendix I in the Systems Management Server Administrator's Guide for information on creating the views before using Crystal Reports.

To configure your machine to run those reports:

1.	Double-click on the ODBC Setup icon in the Systems Management Server group.

2.	Install the "SQL Server" driver.

3.	Add a data source for "SQL Server" ensuring the Server, Network Address, Network Library and Database Name are set correctly. The Database Name should reference the same database for which the SMS views were created.

4.	Double-click on the Crystal Reports for SMS icon in the Systems Management Server group.

5.	Open one of the provided SMS reports in Crystal Reports.

6.	From the Crystal Reports menu, select the Report|Refresh Report Data command.

7.	When prompted for the data source name, provide the data source that was created in step 3.


SMS Reports by Crystal

The following reports were created from the SMS sample database with name, SMS.

Report: 	dup_ips.rpt

Title: 	Computers With Duplicate IP Addresses

Description: 	Links vIdentiifcation with vNetwork to list computers that have duplicate IP addresses.

SQL query:

SELECT

vNetwork.IP_Address0, vIdentification.Name0, vIdentification.Site0, vIdentification.Domain0

FROM

SMS.dbo.vNetwork vNetwork, SMS.dbo.vIdentification vIdentification

WHERE

vNetwork.dwMachineID = vIdentification.dwMachineID

Report: 	latescan.rpt

Title: 	Late Scan Report Computers Not Scanned in Past 10 Days

Description:	Links vIdentification with vWorkstationStatus to list computers that have not been scanned in the past 10 days.

SQL query:

SELECT

vWorkstationStatus.LastHWScan, vWorkstationStatus.LastSWScan, vIdentification.Name0, vIdentification.Site0, vIdentification.Domain0

FROM

SMS.dbo.vWorkstationStatus vWorkstationStatus,

SMS.dbo.vIdentification vIdentification

WHERE

vWorkstationStatus.dwMachineID = vIdentification.dwMachineID

Report: 	netcard.rpt

Title: 	Network Card in Use By Domain By Site

Description:	Links vIdentification to vNetcard to list information about which network cards are in use by domain by site.

SQL query:

SELECT

vIdentification.Name0, vIdentification.Site0, vIdentification.Domain0, vIdentification.LogOn_Name0, vNetcard.Manufacturer0, vNetcard.IRQ0

FROM

SMS.dbo.vIdentification vIdentification, SMS.dbo.vNetcard vNetcard

WHERE

vIdentification.dwMachineID = vNetcard.dwMachineID

Report: 	os_type.rpt

Title: 	Operating Systems in Use By Domain

Description:	Links vIdentification to vOperating_System to list what operating systems are used by the computers in each domain.

SQL query:

SELECT

vIdentification.Name0, vIdentification.Domain0, vIdentification.SystemRole0, vOperating_System.Version0, vOperating_System.Operating_System_Name0, vOperating_System.Installation_Date0

FROM

SMS.dbo.vIdentification vIdentification, SMS.dbo.vOperating_System vOperating_System

WHERE

vIdentification.dwMachineID = vOperating_System.dwMachineID

Report: 	path.rpt

Title: 	Path Environment Variables By Domain By Site

Description:	Links vIdentification to vEnvironment to list the PATH values for each computer by domain by site.

SQL query:

SELECT

vEnvironment.Value0, vEnvironment.Environment_String0, vIdentification.Name0, vIdentification.Site0, vIdentification.Domain0, vIdentification.LogOn_Name0

FROM

SMS.dbo.vEnvironment vEnvironment, SMS.dbo.vIdentification vIdentification

WHERE

vEnvironment.dwMachineID = vIdentification.dwMachineID AND (vEnvironment.Environment_String0 = 'Path' OR vEnvironment.Environment_String0 = 'PATH')

Report: 	personal.rpt

Title: 	Personal Computers By Domain

Description:	Lists Personal Computer information from the vIdentification view.

SQL query:

SELECT

vIdentification.Name0, vIdentification.Domain0, vIdentification.NetCardID0, vIdentification.SystemRole0, vIdentification.SystemType0

FROM

SMS.dbo.vIdentification vIdentification

WHERE

vIdentification.SystemType0 <> ''

Report: 	processr.rpt

Title: 	Processor Type by Domain

Description:	Links vIdentification to vProcessor to display what processors are being used by each computer in each domain.

SQL query:

SELECT

vIdentification.Name0, vIdentification.Domain0, vIdentification.SystemRole0, vProcessor.Processor_Name0

FROM

SMS.dbo.vIdentification vIdentification, SMS.dbo.vProcessor vProcessor

WHERE

vIdentification.dwMachineID = vProcessor.dwMachineID

Report: 	services.rpt

Title: 	Status of Services By Domain By Site

Description:	Links vIdentification to vServices to list information about the status of services in the domain by site.

SQL query:

SELECT

vIdentification.Name0, vIdentification.Site0, vIdentification.Domain0, vServices.State0, vServices.Start_Type0, vServices.EXE_Path0, vServices.Start_Name0

FROM

SMS.dbo.vIdentification vIdentification, SMS.dbo.vServices vServices

WHERE

vIdentification.dwMachineID = vServices.dwMachineID

Report: 	software.rpt

Title: 	Software in Use By Domain

Description: 	Links vIdentification to vSoftware to list information about software packages in use by domain.

SQL query:

SELECT

vSoftware.Software_Name0, vSoftware.Date0, vSoftware.Path0, vIdentification.Name0, vIdentification.Domain0

FROM

SMS.dbo.vSoftware vSoftware, SMS.dbo.vIdentification vIdentification

WHERE

vSoftware.dwMachineID = vIdentification.dwMachineID

Report: 	space.rpt

Title: 	Free Disk Space of Personal Computers by Domain

Description: 	Links vIdentification to vDisk to list computers that are over 50% full.

SQL query:

SELECT

vDisk.Disk_Index0, vDisk.__Disk_Full0, vDisk.Free_Storage__MByte_0, vDisk.Storage_Size__MByte_0, vIdentification.Name0, vIdentification.Site0, vIdentification.Domain0, vIdentification.SystemRole0

FROM

SMS.dbo.vDisk vDisk, SMS.dbo.vIdentification vIdentification

WHERE

vDisk.dwMachineID = vIdentification.dwMachineID AND vDisk.__Disk_Full0 > 50

Report: 	upgrade.rpt

Title: 	Systems Ready for Windows 95 Upgrade

Description: 	Links vIdentification to vPC_Memory, vOperation_System and vProcessor to list computers that should be upgraded to Windows 95.

SQL query:

SELECT

vIdentification.Name0, vIdentification.Domain0, vIdentification.SystemRole0, vPC_Memory.Extended_Memory__KByte_0, vOperating_System.Version0, vOperating_System.Operating_System_Name0, vProcessor.Processor_Name0

FROM

SMS.dbo.vIdentification vIdentification,  SMS.dbo.vPC_Memory  vPC_Memory, SMS.dbo.vOperating_System vOperating_System, SMS.dbo.vProcessor vProcessor

WHERE

vIdentification.dwMachineID = vPC_Memory.dwMachineID AND vIdentification.dwMachineID = vOperating_System.dwMachineID AND vIdentification.dwMachineID = vProcessor.dwMachineID AND (vProcessor.Processor_Name0 = 'INTELPENTIUM' OR vProcessor.Processor_Name0 = 'INTEL PENTIUM' OR vProcessor.Processor_Name0 = '80486SX' OR vProcessor.Processor_Name0 = '80486DX' OR vProcessor.Processor_Name0 = '80486' OR vProcessor.Processor_Name0 = '80386' OR vProcessor.Processor_Name0 = '486SX-25' OR vProcessor.Processor_Name0 = '486DX-66' OR vProcessor.Processor_Name0 = '486DX')

Report: 	video.rpt

Title: 	Display Information By Domain By Site

Description: 	Links vIdentification to vVideo to show information about the computer and its display.

SQL query:

SELECT

vIdentification.Name0, vIdentification.Site0, vIdentification.Domain0, vVideo.Adapter_Type0, vVideo.Display_Type0, vVideo.Manufacturer0, vVideo.Bios_Date0

FROM

SMS.dbo.vIdentification vIdentification, SMS.dbo.vVideo vVideo

WHERE

vIdentification.dwMachineID = vVideo.dwMachineID