- Использование сборщика журналов Windows Server Essentials Use the Windows Server Essentials Log Collector
- Сбор сведений о среде Environment information collected
- Собираемые сведения о службах Services information collected
- Службы сервера Server services
- Службы сетевых компьютеров Network computer services
- Сбор сведений из журналов и реестров Logs and registry information collected
- Сведения из журналов и реестра сервера Server logs and registry information
- Сведения из журналов и реестра компьютеров сети Network computer logs and registry information
- Журналы компьютеров, которые работают не под управлением ОС Windows Logs for computers that do not run a version of the Windows operating system
- FTP Log Files
- Overview
- Compatibility
- Setup
- Windows Server 2012 or Windows Server 2012 R2
- Windows 8 or Windows 8.1
- Windows Server 2008 R2
- Windows 7
- Windows Server 2008 or Windows Vista
- How To
- How to configure logging options for an FTP site
- Configuration
- Attributes
- Child Elements
- Configuration Sample
- Sample Code
Использование сборщика журналов Windows Server Essentials Use the Windows Server Essentials Log Collector
Область применения: Windows Server 2016 Essentials, Windows Server 2012 R2 Essentials, Windows Server 2012 Essentials Applies To: Windows Server 2016 Essentials, Windows Server 2012 R2 Essentials, Windows Server 2012 Essentials
При устранении неполадок, связанных с компьютером, у представителя службы поддержки пользователей Майкрософт могут попросить вас собрать журналы с серверов, компьютеров в сети или с помощью сборщика журналов Windows Server Essentials. When you are troubleshooting computer issues, a representative from Microsoft Customer Service and Support may ask you to gather logs from servers, computers on the network, or both by using the Windows Server Essentials Log Collector.
Сборщик журналов копирует журналы программ, событий и прочую информацию среды в единый ZIP-файл по указанному адресу. The Log Collector copies program logs, event reviewer logs, and related environment information into a single zip file at a specified location. Сборщик журналов можно запускать непосредственно c сервера или любого компьютер сети, а также через удаленное подключение к компьютерам. You can run the Log Collector directly from the server or any computer on the network, or by using a remote connection to the computers.
Сборщик журналов не проводит анализ сетевых проблем и не вносит изменения в настройки серверов или компьютеров сети. The Log Collector does not analyze network issues or make changes to any server or computer on the network. Дополнительную информацию об устранении сетевых неполадок см. в справочной документации по вашему серверу. For information about how to troubleshoot network issues, see the Help documentation for your server product. В этом разделе Компьютеры в сети, отличные от сервера, называются сетевыми компьютерами. In this guide, the computers on your network, other than your server, are called network computers.
Чтобы установить и запустить сборщик журналов, выполните шаги, описанные в следующих разделах. To install and run the Log Collector, perform the steps in the following topics:
Сбор сведений о среде Environment information collected
Для каждого компьютера сети или сервера, указанного вами, сборщик журналов собирает следующие сведения о среде и помещает их в файл журнала коллекции: For each network computer or server that you specify, the Log Collector gathers the following environment information and places it into the log collection file.
Версия операционной системы Operating system version
Изготовитель и описание ЦП CPU manufacturer and description
Объем памяти и ее выделение Memory amount and allocation
Сетевые адаптеры, связанные с TCP/IP Network adapters that are bound to TCP/IP
Языковой стандарт Locale
Конфигурация хранилища Storage configuration
Сведения о файле узла Host file information
Журналы событий, включая события приложений, системные события, события Windows Server и Media Center Event Logs including Application, System, Windows Server and Media Center
Сообщения диспетчера управления службами Service Control Manager messages
События перезагрузки и Центра обновления Windows Reboot events and Windows Update events
Системные ошибки и ошибки приложений System Errors and Application Errors
Собираемые сведения о службах Services information collected
Службы сервера Server services
Служба резервного копирования Windows Server клиентского компьютера Windows Server Client Computer Backup Service
Поставщик службы резервного копирования Windows Server клиентского компьютера Windows Server Client Computer Backup Provider Service
Поставщик устройств Windows Server Windows Server Devices Provider
Управление доменными именами Windows Server Windows Server Domain Name Management
Реестр поставщика службы Windows Server Windows Server Service Provider Registry
Поставщик параметров Windows Server Windows Server Settings Provider
Служба UPnP-устройств Windows Server Windows Server UPnP Device Service
Поставщик средств удаленного администрирования Windows Server Windows Server Remote Web Access Administration Provider
Служба работоспособности Windows Server Windows Server Health Service
Служба хранения данных Windows Server Windows Server Storage Service
Служба SQM Windows Server Windows Server SQM Service
Службы сетевых компьютеров Network computer services
Поставщик службы резервного копирования Windows Server клиентского компьютера Windows Server Client Computer Backup Provider Service
Служба работоспособности Windows Server Windows Server Health Service
Реестр поставщика службы Windows Server Windows Server Service Provider Registry
Служба SQM Windows Server Windows Server SQM Service
Сбор сведений из журналов и реестров Logs and registry information collected
Для каждого указанного компьютера сети или сервера сборщик журналов собирает следующие сведения из журналов и реестра от сервера и компьютеров сети: For each network computer or server specified, the Log Collector gathers log and registry information from the server and network computer as follows.
Сведения из журналов и реестра сервера Server logs and registry information
Журналы серверных продуктов, с \Микрософт\виндовс сервер\логс Server product logs, from
Запланированные задачи Scheduled tasks
Журналы API установки Setup API logs
Журналы центра обновления Windows Windows Update logs
Файл оповещений о работоспособности Health Alerts file
Файл сведений об устройствах Devices Info file
Файл журнала архивации сервера Server Backup Log file
Файл журнала Panther Panther Log file
Разделы реестра из Registry keys, from
\\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server \
Сведения из журналов и реестра компьютеров сети Network computer logs and registry information
Журналы продуктов для сетевого компьютера в \Микрософт\виндовс сервер\логс Network computer product logs at
Файл оповещений о работоспособности в \Микрософт\виндовс сервер\дата Health Alerts file at
Журналы центра обновления Windows Windows Update logs
Журналы API установки Setup API logs
Сведения о запланированных задачах Scheduled tasks info
Разделы реестра от \ \ HKEY_LOCAL_MACHINE \Софтваре\микрософт\виндовс Server Registry keys from \\HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Windows Server \
Журналы компьютеров, которые работают не под управлением ОС Windows Logs for computers that do not run a version of the Windows operating system
Сборщик журналов не собирает файлы журналов с компьютеров, которые работают не под управлением ОС Windows. The Log Collector does not gather log files from computers that do not run a version of the Windows operating system. При использовании компьютеров, работающих под управлением ОС, отличной от Windows, вручную скопируйте следующие файлы журналов в ту же папку, где хранятся файлы сборщика журналов: For non-Windows computers, manually copy the following log files to the same location where you are storing the Log Collector files.
Library/Logs/Windows Server.log Library/Logs/Windows Server.log
Библиотека/журналы/Крашрепортер/панель запуска — (копирование всех файлов панели запуска- . Crash) Library/Logs/CrashReporter/LaunchPad- (copy all of the LaunchPad- .crash files)
Библиотека/журналы/Диагностикрепортс/панель запуска — (копирование всех файлов панели запуска- . Crash) Library/Logs/DiagnosticReports/LaunchPad- (copy all of the LaunchPad- .crash files)
FTP Log Files
Overview
The element is used to configure the activity logging options for an FTP site.
For example, you can enable or disable logging, specify the categories of information to store in the log file, and change the directory where the log file is stored. You can also use the element to control how often IIS creates a new log file based either on log file size or time interval and the maximum size (in bytes) that a log file can become.
Unlike Web sites that can use the IIS, NCSA, or W3C format for log files, the FTP 7 service only stores log files in W3C format.
You can define the categories of information that IIS logs by editing the logExtFileFlags attribute. The default values are Date , Time , ClientIP , UserName , ServerIP , Method , UriStem , FtpStatus , Win32Status , FtpSubStatus , ServerPort , Session , and FullPath .
Compatibility
Version | Notes |
---|---|
IIS 10.0 | The element was not modified in IIS 10.0. |
IIS 8.5 | The element was not modified in IIS 8.5. |
IIS 8.0 | The element was not modified in IIS 8.0. |
IIS 7.5 | The element of the element ships as a feature of IIS 7.5. |
IIS 7.0 | The element of the element was introduced in FTP 7.0, which was a separate download for IIS 7.0. |
IIS 6.0 | N/A |
The FTP 7.0 and FTP 7.5 services shipped out-of-band for IIS 7.0, which required downloading and installing the modules from the following URL:
With Windows 7 and Windows Server 2008 R2, the FTP 7.5 service ships as a feature for IIS 7.5, so downloading the FTP service is no longer necessary.
Setup
To support FTP publishing for your Web server, you must install the FTP service. To do so, use the following steps.
Windows Server 2012 or Windows Server 2012 R2
On the taskbar, click Server Manager.
In Server Manager, click the Manage menu, and then click Add Roles and Features.
In the Add Roles and Features wizard, click Next. Select the installation type and click Next. Select the destination server and click Next.
On the Server Roles page, expand Web Server (IIS), and then select FTP Server.
To support ASP.Membership authentication or IIS Manager authentication for the FTP service, you will need to select FTP Extensibility, in addition to FTP Service. .
Click Next, and then on the Select features page, click Next again.
On the Confirm installation selections page, click Install.
On the Results page, click Close.
Windows 8 or Windows 8.1
On the Start screen, move the pointer all the way to the lower left corner, right-click the Start button, and then click Control Panel.
In Control Panel, click Programs and Features, and then click Turn Windows features on or off.
Expand Internet Information Services, and then select FTP Server.
To support ASP.Membership authentication or IIS Manager authentication for the FTP service, you will also need to select FTP Extensibility.
Click OK.
Click Close.
Windows Server 2008 R2
On the taskbar, click Start, point to Administrative Tools, and then click Server Manager.
In the Server Manager hierarchy pane, expand Roles, and then click Web Server (IIS).
In the Web Server (IIS) pane, scroll to the Role Services section, and then click Add Role Services.
On the Select Role Services page of the Add Role Services Wizard, expand FTP Server.
Select FTP Service.
To support ASP.Membership authentication or IIS Manager authentication for the FTP service, you will also need to select FTP Extensibility.
Click Next.
On the Confirm Installation Selections page, click Install.
On the Results page, click Close.
Windows 7
On the taskbar, click Start, and then click Control Panel.
In Control Panel, click Programs and Features, and then click Turn Windows Features on or off.
Expand Internet Information Services, and then FTP Server.
Select FTP Service.
To support ASP.Membership authentication or IIS Manager authentication for the FTP service, you will also need to select FTP Extensibility.
Click OK.
Windows Server 2008 or Windows Vista
Download the installation package from the following URL:
Follow the instructions in the following walkthrough to install the FTP service:
How To
How to configure logging options for an FTP site
Open Internet Information Services (IIS) Manager:
If you are using Windows Server 2012 or Windows Server 2012 R2:
- On the taskbar, click Server Manager, click Tools, and then click Internet Information Services (IIS) Manager.
If you are using Windows 8 or Windows 8.1:
- Hold down the Windows key, press the letter X, and then click Control Panel.
- Click Administrative Tools, and then double-click Internet Information Services (IIS) Manager.
If you are using Windows Server 2008 or Windows Server 2008 R2:
- On the taskbar, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
If you are using Windows Vista or Windows 7:
- On the taskbar, click Start, and then click Control Panel.
- Double-click Administrative Tools, and then double-click Internet Information Services (IIS) Manager.
In the Connections pane, expand the server name, and then go to the site where you want to configure logging.
In the Home pane, double-click FTP Logging. — In the Log File Rollover section, click Select W3C Fields.
Select the fields for your log files, then click OK.
Under Directory, specify the path where the log file should be stored. The default is %SystemDrive%\inetpub\logs\LogFiles.
In the Log File Rollover section, specify the following options:
Schedule: to create new log file that are based on one of the following values:
- Hourly: a new log file is created each hour.
- Daily: a new log file is created each day.
- Weekly: a new log file is created each week.
- Monthly: a new log file is created each month.
Maximum file size (in bytes): to create a new log file when the file reaches a certain size (in bytes). The minimum file size is 1048576 bytes. If this attribute is set to a value less than 1048576 bytes, the default value is implicitly assumed as 1048576 bytes.
Do not create a new log file: there is a single log file that will continue to grow as information is logged.
Select Use local time for file naming and rollover to specify that log file naming and time for log file rollover uses the local server time. When this is not selected, Coordinated Universal Time (UTC) is used.
Click Apply in the Actions pane.
Configuration
Attributes
Attribute | Description |
---|---|
directory | Optional string attribute. |
Specifies the logging directory, where the log file and logging-related support files are stored.
The default value is %SystemDrive%\inetpub\logs\LogFiles .
true if logging is enabled; otherwise false.
The default value is true .
true if the a new log file is created based on local time; otherwise, false for Coordinated Universal Time (UTC), which was previously called Greenwich Mean Time (GMT).
Note: Regardless of the setting, the time stamp for each W3C Extended Logging log record is UTC-based.
The default value is false .
Specifies the categories of information that are written to either the log file (when you use W3C Extended log file format) or to the ODBC data source during logging events for a site. The logExtFileFlags attribute can be one or more of the following values. If you specify more than one value, separate them with a comma (,).
The default values are Date , Time , ClientIP , UserName , ServerIP , Method , UriStem , FtpStatus , Win32Status , FtpSubStatus , ServerPort , Session , and FullPath .
Value | Description |
---|---|
BytesRecv | Log the number of bytes that the server received. The numeric value is 8192 . |
BytesSent | Log the number of bytes that the server sent. The numeric value is 4096 . |
ClientIP | Log the IP address of the client that made the request. The numeric value is 4 . |
ClientPort | Log the port of the client that made the request. The numeric value is 33554432 . |
ComputerName | Log the name of the server on which the log file entry was generated. The numeric value is 32 . |
Date | Log the date on which the activity occurred. The numeric value is 1 . |
FtpStatus | Log the FTP status code. The numeric value is 1024 . |
FtpSubStatus | Log the sub-status code of the FTP error. The numeric value is 2097152 . |
FullPath | Log the full relative path. Note: This may be different URI that the client requested, which is logged by setting the UriStem flag. The numeric value is 8388608 . |
Host | Log the virtual host name, if there is one. The numeric value is 1048576 . |
Info | Log extended debugging information, if there is any. The numeric value is 16777216 . |
Method | Log the requested action. For example, USER , PASS, etc. The numeric value is 128 . |
ServerIP | Log the IP address of the server on which the log file entry was generated. The numeric value is 64 . |
ServerPort | Log the server port number that is configured for the site. The numeric value is 32768 . |
Session | Log the unique identifier for the FTP session. This is useful for analyzing session activity in your logs. The numeric value is 4194304 . |
SiteName | Log the Internet service name and instance number for the site. The numeric value is 16 . |
Time | Log the time in Coordinated Universal Time (UTC), at which the activity occurred. The numeric value is 2 . |
TimeTaken | Log the length of time taken for a request to be completed. The time taken is recorded in milliseconds. The numeric value is 16384 . |
UriStem | Log the Universal Resource Identifier (URI) stem information, which is the target of the action. Note: This shows the URI steam exactly as the client requested, which may not be the full relative path. For the full relative path, use the FullPath flag. The numeric value is 256 . |
UserName | Log the name of the authenticated user who accessed your server. Anonymous users are indicated by a hyphen. The numeric value is 8 . |
Win32Status | Log the Windows status code. The numeric value is 2048 . |
Specifies how often the FTP service creates a new log file. The period attribute can be one of the following possible values.
The default value is Daily .
Value | Description |
---|---|
Daily | Create a new log file daily. The numeric value is 1 . |
Hourly | Create a new log file hourly. The numeric value is 4 . |
MaxSize | Create a new log file when a maximum size is reached. The maximum size is specified in the truncateSize attribute. The numeric value is 0 . |
Monthly | Create a new log file monthly. The numeric value is 3 . |
Weekly | Create a new log file weekly. The numeric value is 2 . |
Specifies the verbosity for FTP logging.
The default value is LogSuccessful,LogError,LogInfrastructure .
Value | Description |
---|---|
LogError | Specifies that errors will be logged. The amount of data actually logged also depends on the setting of LogInfrastructure flag. The numeric value is 2 . |
LogInfrastructure | Specifies that all FTP commands and low-level data channel activity will be logged. For example, the logs will contain entries for DataChannelOpened, DataChannelClosed, PORT/EPRT, PASV/EPSV, if the LogInfrastructure flag is set. The numeric value is 4 . |
LogSuccessful | Specifies that successful activity will be logged. The amount of data actually logged also depends on the setting of LogInfrastructure flag. The numeric value is 1 . |
Specifies the maximum size of the log file (in bytes) after which to create a new log file. This value is only applicable when MaxSize is chosen for the period attribute. The minimum file size is 1,048,576 bytes. If this attribute is set to a value less than 1,048,576 bytes, the default value is implicitly assumed as 1,048,576 bytes.
The default value is 20971520 .
Child Elements
Configuration Sample
The following configuration example shows an FTP with custom logging options that specify that infrastructure commands will not be logged, log files will be rotated on a daily basis, and the additional debugging option has been added to the default fields.
Sample Code
The following examples illustrate enabling logging for an FTP site, configuring the log file directory for an FTP site for a specific path, and specifying daily log file recycling.