Re: MS04-040 command line ambiguous

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: KevinG (keving02_at_hotmail.com)
Date: 12/07/04

  • Next message: apex52: "Received field under advertisement status" 
    Date: Tue, 7 Dec 2004 10:07:15 -0600

    What it was saying was that for the SMS deployment specific patch you use
    /q:a /r:n. For the OS (win2k or XP) specific patches, you use /quiet
    /norestart. I agree it's kinda confusing. I'd love to see standardization
    on this.

    Kevin

    "Rory Niland" <RoryNiland@discussions.microsoft.com> wrote in message
    news:D0D421C3-388F-43DC-90E7-A578F2CB529F@microsoft.com...
    >
    > used /q:a /r:n for WinXP clients and now works ok .. go figure
    >
    > any chance you guys could standardise these switches and stop messing
    > about.
    >
    >
    > "Rory Niland" wrote:
    >
    >> Taken from : http://support.microsoft.com/kb/889410
    >>
    >>
    >> "Usage information
    >> To use the SMS deployment package, specify the following command-line
    >> command in DSUW:
    >> IE6.0sp1-KB889293-SMS-Deploy-KB889410-x86-ENU.exe /q:a /r:n
    >>
    >> The SMS deployment package uses the recommended command-line switches for
    >> SMS deployment to install the security updates silently without
    >> restarting
    >> client computers. For the Windows 2000 and Windows XP security updates,
    >> the
    >> /quiet /norestart command-line switches are used. For the Windows NT 4.0
    >> security update, the /q:a /r:n command-line switches are used. These
    >> command-line switches are part of the script logic in the SMS deployment
    >> package. These command-line switches cannot be changed."
    >>
    >>
    >> First you say use : /q:a /r:n then you say use /quiet /norestart if
    >> using
    >> 2000/XP - why did you put the "/q:a /r:n" in the usage instructions and
    >> then
    >> qualify it after.
    >>
    >>

  • Next message: apex52: "Received field under advertisement status"

    Relevant Pages

    • Re: Printing panoramas
      ... Standardization not just in printing has helped get Windows the market share it has today. ... Superior marketing and monopolistic practices are what got Microsoft the market share it has today. ... And by the way, that market share is dropping, while Mac and Linux are on the increase. ... Most of the software applications in Windows use the same or very similar Print Dialog Box so if you do a File Print in one application and then from another you see basically the same thing. ...
      (comp.graphics.apps.gimp)
    • Re: Printing panoramas
      ... Standardization not just in printing has helped get Windows the market share it has today. ... Superior marketing and monopolistic practices are what got Microsoft the market share it has today. ... And by the way, that market share is dropping, while Mac and Linux are on the increase. ... Most of the software applications in Windows use the same or very similar Print Dialog Box so if you do a File Print in one application and then from another you see basically the same thing. ...
      (comp.graphics.apps.gimp)
    • Re: Join me in my fight against PCs
      ... There is a lot of standardization in the parts between a Mac and a PC. ... running more than Windows XP...you should be able to run any PC operating ... On the hardware level, with nothing more than the chips ...
      (comp.sys.mac.advocacy)
    • Re: Join me in my fight against PCs
      ... There is a lot of standardization in the parts between a Mac and a PC. ... running more than Windows XP...you should be able to run any PC operating ... On the hardware level, with nothing more than the chips ...
      (comp.sys.mac.advocacy)
    • Re: Why Lisp is too hard for me to use
      ... Windows benefited from the standardization and contributed ... >> Microsoft had for such a long time. ... You've obviously not spent enough time writing software for the Win32 ...
      (comp.lang.lisp)