Questions, questions

Discussion in 'Update Services' started by josh lacroix, Jul 20, 2005.

  1. josh lacroix

    josh lacroix Guest

    1-I just deployed my new SWUS and i am very impressed. I did see some
    complications, i couldn't see all my systems..some Xp and some 2000 sp 4. On
    the 2000's i updated the Update client software and with in 30 secs, i could
    see them. The Xp's were a little harder to figure out...For some reason
    because they were all cloned using ghost, i changed the SID and bang, worked
    fine. Why would this only affect XP, all my systems are cloned from ghost.

    2-The computers showing, are those real time? Most likely not, so if i
    delete a computer, how long does it take to it be purged from the computer

    3-In my to do list, i have 1 update that says it needs to be approved, yet
    when i follow the link, nothing comes up.

    4-How would i setup my IIS so i could see in real time all the computers
    connected to me?I went into my performance manager but what shoould i add?

    5- I though i could also see a internal web interface to the windows update
    by hitting http://servername/selfupdate

    but i can;t see anything. I do see it in my IIS manager websites.
    josh lacroix, Jul 20, 2005
    1. Advertisements

  2. josh lacroix

    Asher_N Guest

    It is not real time. Computers report on a schedule. default is every 17-
    22 hours. It's pseudo-random. The effect is to have computers report at
    different times. AFAIK, you must delete them manually.

    You can't

    There is no internal website. The selfupdate folder conytains the code
    required by the ws to update the the WU client.
    Asher_N, Jul 20, 2005
    1. Advertisements

  3. Perhaps because the XP master image had previously been connected to Windows
    Update or SUS?

    Or perhaps because the installation of the WUA on the Windows 2000 reset the
    They are near real time, Josh. Every 22 hours (minus a random offset of
    1-20%), each client reports in to the WSUS server and scans to see if there
    are any new updates to be downloaded and installed. So I say near real time
    because under normal circumstances, everything reported on the WSUS server
    is current as of the most recent 24 hours. Since Windows update management
    is really a once-a-month process under normal operation -- having data no
    older than 24 hours is pretty near real time.

    You can make it even more 'near real time' by reducing the default detection
    interval to as low as 1 hour. Note, however, there really is no functional
    benefit to making this adjustment, and in large network environments it can
    actually have negative performance effects on your network and WSUS server.
    Yeah... this is an Exchange update that doesn't filter properly. Set your
    filter options for All Update, All Approvals, and synced Any Time, and then
    scan through the list for "not approved" updates and/or updates for
    At this point, I don't know that there's a way to do it. WSUS apparently
    does provide some PerfMon counters, but nobody's really dug into them (at
    least from what's been reported here). Also realize that the actual
    "connection" between the client and the WSUS server is web-service based,
    and fairly transitory in terms of time length and frequency, so it many not
    even be feasible to produce a functional list of "connected" clients.

    Which brings us back to the 'near real time' data of /reporting/ clients
    that WSUS provides on the console.
    No, there is no user-purposed web interface ala Windows Update. The
    selfupdate service is merely some ASP.NET code and a CAB file that's
    downloaded and installed on the client.
    Lawrence Garvin, Jul 21, 2005
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.