"Can not perform non-interactive scan if AU is interactive-only"

Got WSUS clients not reporting back to the server.

Found this in the WindowsUpdate.log

"Can not perform non-interactive scan if AU is interactive-only"
I think I have the GPO stuff right. (I can see in GPresult that the right
info is there) and in the windows update log it shows the server and group
membership.

Ideas?

"C-Guy" <> wrote in message
news:49C46F6B-B185-4850-BD8C-...
> Got WSUS clients not reporting back to the server.
>
> Found this in the WindowsUpdate.log
>
> "Can not perform non-interactive scan if AU is interactive-only"
> I think I have the GPO stuff right. (I can see in GPresult that the right
> info is there) and in the windows update log it shows the server and group
> membership.

But something isn't configured correctly or the WUAgent wouldn't be balking
at performing the scan.

If this is an x86 machine, please run the Client Diagnostic Tool and post
the results; otherwise, restart the Automatic Updates service and post the
log entries from WindowsUpdate.log for the Service Startup activities..



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

So after some playing it turns out to be a policy we are pushing which is
turning off AU.

So: Question is, of the 4 choices...

Automatic
Download and let me chose
Notify but don't install.
Turn off.

Which do I want my domain policy specifying? (If I want it to be invisible
to the end user.)

I'd put it on Automatic but I want to specify deployment times on the WSUS
server..not the client.

What do you think the 'best practice' is in this regard?

_

"Lawrence Garvin [MVP]" wrote:

> "C-Guy" <> wrote in message
> news:49C46F6B-B185-4850-BD8C-...
> > Got WSUS clients not reporting back to the server.
> >
> > Found this in the WindowsUpdate.log
> >
> > "Can not perform non-interactive scan if AU is interactive-only"
> > I think I have the GPO stuff right. (I can see in GPresult that the right
> > info is there) and in the windows update log it shows the server and group
> > membership.
>
> But something isn't configured correctly or the WUAgent wouldn't be balking
> at performing the scan.
>
> If this is an x86 machine, please run the Client Diagnostic Tool and post
> the results; otherwise, restart the Automatic Updates service and post the
> log entries from WindowsUpdate.log for the Service Startup activities..
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"C-Guy" <> wrote in message
news:C700D3AB-38CF-4219-AB77-...
> So after some playing it turns out to be a policy we are pushing which is
> turning off AU.

It happens more often than you might think. :-)


> So: Question is, of the 4 choices...
>
> Automatic
> Download and let me chose
> Notify but don't install.
> Turn off.
>
> Which do I want my domain policy specifying?

Well, first, you probably do not want to set this value at the *domain*
level.

Servers, ideally, should be configured to use "Notify but don't install", so
that installations can be supervised during a maintenance window when
installations can be performed and the server restarted.

Workstations, normally, are configured to use "Automatic", so that updates
can be installed without any requirement of user interaction at all.

Of necessity, then, this configuration requires at least two GPOs -- one
with AUOption=3 and another with AUOption=4.

> I'd put it on Automatic but I want to specify deployment times on the WSUS
> server..not the client.

Severe misconception! You do not, and cannot, specify deployment times on
the WSUS Server. The only things you can do at the WSUS Server are:

1. Approve updates -- which will permit the detection and downloading of
content, all of which will normally occur within the 22 hours following the
time the approval is posted.

2. Specify a deadline, which is the No Later Than time that an update will
be installed, provided the update has not been installed from the several
methodologies that would be available before the deadline is reached (e.g. a
Scheduled Installation for workstations; a User Initiated installation for
workstations; an Admin initiated installation for servers).

> What do you think the 'best practice' is in this regard?

The above represents what is commonly accepted "best practice" at this time.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin