Microsoft Windows NT 4.0 Guide Manual de usuario descargar pdf (Pagina 27)

Microsoft

Windows Server

™

2003 White Paper

Windows NT 4.0 Server Upgrade Guide 22

A company is preparing to deploy Windows XP Professional to all desktop computers. The

organization is divided among three physical locations connected by high-speed data connections.

The organization uses the Active Directory service within a single domain, and has created an

organizational unit (OU) for each physical location (HQ, East, and West).

On Server1, the IT department creates a shared folder for storing all log files generated by

Collector, with the Universal Naming Convention (UNC) path \\Server1\Analyzer, and another

shared folder for storing the Collector executable, with the path \\Server1\Collector. The IT

department decides to use a logon script assigned through Active Directory to distribute and run

Collector. Because the three physical locations are represented by three separate OUs within the

domain, the organization decides to gather data by OU. To accomplish this, the IT department

adds the following lines to the logon script:

Copy \\server1\collector\collector.exe c:\

C:\collector.exe /O \\server1\analyzer /N /E HQ /CW

The first line of code copies Collector executable from the shared folder on Server1 to drive C on

the client computer. The second line of the code instructs Collector to do the following:

• Send log file output to the shared folder on Server1 that is specified for storing logs (using the /O

switch).

• Scan network drives that might be mapped (using the /N switch).

• Mark the data with an HQ designation for the HQ OU (using the /E switch).

• Wait five minutes before starting the collection.

The IT department can include similar lines for the logon scripts in the East and West OUs, with

the exception that the /E switch would define the OU name in each case

What Collector Does

Collector inspects all the applications installed on a computer and builds an inventory file in either

a compressed .cab format or an uncompressed .xml format. This information is then used by

Analyzer. The data can be gathered easily and quickly throughout the network when deployed

through mechanisms such as logon scripts. The goal of Collector is to provide a quick and easy

way to gather the inventory of systems running in the enterprise. This data is then used to find,

determine, and fix compatibility issues.

Note Make sure to install and inventory applications that you intend to run in the new environment but

that may not yet be running, so you can also verify compatibility with those new applications.

A sample file collected by Collector includes XML and looks similar to the following:

1 2 ... 22 23 24 25 26 27 28 29 30 31 32 ... 154 155

Sin comentarios

Microsoft Windows NT 4.0 Guide Manual de usuario Pagina 27