|
|
When I approve a new update(s) all the computers and groups show as no status, until they report back in. Is there a way to prevent the computers from changing their status? I just approved an update for the server group and all groups and computers now show up as having changed to no status. As of right now it will take a week plus for all the PCs to update their status.
|
|
"jpnels" <jpnels[ at ]discussions.microsoft.com> wrote in message news:3C30748E-F4A2-4D53-81FB-C1D9CE73D58B[ at ]microsoft.com...
[Quoted Text] > When I approve a new update(s) all the computers and groups show as no > status, until they report back in.
This is by design, and expected. The WSUS server has "No Status" on those updates vis a vis the client's status until the client reports that status. The client only reports status on updates approved for detection in WSUS 2.0
In WSUS v3, the client reports status on *all* updates, because *all* updates are approved for detection.
> Is there a way to prevent the computers > from changing their status?
That's like asking if there's a way to stop the moon from revolving around the Earth. The status is what the status is. You cannot change =truth=.
> I just approved an update for the server group > and all groups and computers now show up as having changed to no status. > As > of right now it will take a week plus for all the PCs to update their > status.
No.. it won't.. unless you have *serious* dysfunctions in your environment. Clients, by default, execute detections and reporting every 22 hours (minus a random offset). You should never have to wait more than 24 hours to have a full status update from all clients.
-- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....
|
|
Lawrence Garvin (MVP) wrote:
[Quoted Text] >> As of right now it will take a week plus for all the PCs to update >> their status. > > No.. it won't.. unless you have *serious* dysfunctions in your environment. > Clients, by default, execute detections and reporting every 22 hours (minus > a random offset). You should never have to wait more than 24 hours to have a > full status update from all clients.
That presumes that all the clients are powered up and connected to the network. In many environments this can't be taken for granted.
Harry.
|
|
"Harry Johnston" <harry[ at ]scms.waikato.ac.nz> wrote in message news:O$ptl6woHHA.208[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] >>> As of right now it will take a week plus for all the PCs to update their >>> status.
>> No.. it won't.. unless you have *serious* dysfunctions in your >> environment. Clients, by default, execute detections and reporting every >> 22 hours (minus a random offset). You should never have to wait more than >> 24 hours to have a full status update from all clients.
> That presumes that all the clients are powered up and connected to the > network. In many environments this can't be taken for granted.
Thus my note about "serious dysfunctions". If somebody is complaining because it'll take a week to update all their PCs, and the only reason is because they're powered down for days at a time.... well.... something is "dysfunctional".
And even if they're not powered up and/or connected to the network, from an admin perspective, I stand by the statement:
You should *never* have to wait more than 24 hours to have a full status update from all clients.
-- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....
|
|
Lawrence Garvin (MVP) wrote:
[Quoted Text] > And even if they're not powered up and/or connected to the network, from an > admin perspective, I stand by the statement: > > You should *never* have to wait more than 24 hours to have a full > status update from all clients.
We sometimes have to wait months, e.g., when a laptop is taken overseas. :-)
Harry.
|
|
"Harry Johnston" <harry[ at ]scms.waikato.ac.nz> wrote in message news:e0PhGkxoHHA.5084[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text] >> And even if they're not powered up and/or connected to the network, from >> an admin perspective, I stand by the statement: >> >> You should *never* have to wait more than 24 hours to have a full >> status update from all clients. > > We sometimes have to wait months, e.g., when a laptop is taken overseas. > :-)
No... you don't.
But you *choose* to. :-)
Notebooks are fully capable of being updated in Europe, Asia, and Africa, just like in North America.
-- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....
|
|
|