Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Patch Manager > Report Now vs Detect Now

Report Now vs Detect Now

Table of contents
Created by Craig O’ Neill, last modified by MindTouch on Jun 23, 2016

Views: 38 Votes: 1 Revisions: 4

Overview

This article provides information on the difference between the Report Now and the Detect Now commands in Patch Manager.

Environment

All versions of Patch Manager

Detail

Here are some important points to keep in mind when using/detectnow and /reportnow.

The
/reportnowfunction is only processed when:

  1. There are completed events to report to the WSUS server.
  2. The WUAgent is IDLE.


The WUAgent always automatically executes a reporting event approximately 20 minutes after the completion of all other pending activities.
The purpose of the
/reportnow parameter is to immediately expire that 20 minute delay.

When executing a script with these two commands in immediate succession (or issuing them from the command line immediately following one another), the reality is that the
wuauclt /reportnow invocation actually does nothing at all.

The proper way to use these two commands(or tasks from Patch Manager) is to first launch the
wuauclt /detectnow task, and then WAIT for the completion of the detection event. Typically, this could take a couple of minutes, but on a healthy, fully patched system, it may complete in a matter of seconds.

Once the WUAgent is idle, then executing
wuauclt /reportnow will cause the call to the ReportingWebService to occur immediately, rather than waiting for the built-in 20 minute delay.

 

Last modified
01:17, 23 Jun 2016

Tags

Classifications

Public