Re: Installation Error MS04-028 Scan Tools on NT4 Site Server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Adam Welker [MSFT] (adamwel_at_online.microsoft.com)
Date: 11/03/04

  • Next message: Jeremy Byrne: "multiple users on Administrator Console"
    Date: Wed, 3 Nov 2004 11:00:58 -0800
    
    

    The KB should have been updated with steps to manually install this tool on
    NT4, but I've copied them here.

    Extract Files

    1) Run the downloaded setup bundle SMS_MS04028ScanTools.exe - it
    will extract its content into folder "SMS_MS04028ScanTools"

    2) From a command line, browse to the location of the created
    folder and run the command "MS04-028SCAN-ENU.EXE /x C:\PkgSource"

    3) Delete the following files:

    %LICENSE_FN%

    %LICENSEHTM_FN%

    %PRINTHELPER%

    %SETUP_UTIL%

    %WELCOME_NOTEFN%

    Uninstal.EXE

    UninstObj.exe

    The following files should remain:

    Advertisement.dll

    AdvtResourceDll.dll

    License.txt

    MS04-028UpdInventRelNotes.htm

    msxml3.tmp

    msxml3a.tmp

    msxml3r.tmp

    products.xml

    scan.ini

    ScanConfig.xml

    ScanHlpr.dll

    ScanWrapper.exe

    SMSReport.MOF

    SWUDefine.MOF

    UpdateScan.exe

    UpdateScan.xml

    Create Collection

    4) From the SMS Admin Console on the NT4 server, create a collection
    named "MS04-028 Scanner" and populate the collection with a test machine
    (for testing purposes before deploying across the enterprise).

    Create Package

    5) From the SMS Admin Console, create a package with the Name
    "MS04-028 Scanner"

    6) Under the Data Source tab, select "This package contains source
    files" and set the Source Directory to the "PkgSource" folder created in
    step 2.

    7) Create program "MS04-028 Scanner". Use a command line of
    "ScanWrapper.exe /cache" and set to "run whether or not user is logged on".
    Use the default settings for the remaining properties.

    8) Create another program "MS04-028 Scanner (expedited)". Use a
    command line of "ScanWrapper.exe /cache /kick" and set to "run whether or
    not user is logged on". Use the default settings for the remaining
    properties.

    9) Create a distribution point for the package.

    10) A number of fields in the scan.ini file need to be edited and added.
    Here is an example scan.ini prior to editing:

    [Agent]

    Name=Security Update Tool (MySiteCode)

    Type=MBSA

    [Package]

    ID=<Put Package ID here>

    Name=Security Update Tool

    Program1=Security Update Tool (MySiteCode)

    Command1=s_scan.exe /s /cache

    Program2=Security Update Tool (MySiteCode) (expedited)

    Command2=s_scan.exe /s /cache /kick

    Here is an example of the correctly edited scan.ini file using the names
    listed in these steps. The package ID can be found under Package Status in
    the System Status. In this example, the Package ID is "JOK00001":

    [Agent]

    Name=MS04-028 Scanner

    Type=MS04-028

    PatchAge=20

    PackageAge=30

    [Package]

    ID=JOK00001

    Name=MS04-028 Scanner

    Program2=MS04-028 Scanner (expedited)

    Command2=ScanWrapper.exe /cache /kick

    Program1=MS04-028 Scanner

    Command1=ScanWrapper.exe /cache

    11) After editing the scan.ini file, update the distribution points and
    verify the correct scan.ini file is copied to the package share.

    12) Create advertisement called "MS04-028 Scanner" to advertise package
    "MS04-028 Scanner" to the collection created in step 4 using the program
    "MS04-028 Scanner". Set the advertisement with a recurring schedule every
    7 days.

    -- 
    Adam Welker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    "Franz Schenk" <franz.schenkNOSPAM@fititNO-_SPAM.ch> wrote in message 
    news:eV9SCsOvEHA.612@TK2MSFTNGP15.phx.gbl...
    > Can't install the MS04-028 Scan Tool on a NT4 SP6a SMS 2.0 SP5 Primary 
    > Site
    > Server: Getting an error "The procedure entry point
    > getsystemwindowsdirectorya could not be found in the dynamic link library
    > kernel32.dll"
    >
    > kernel32.dll was probably replaced by some security updates, was created 
    > at
    > November 18th, 1999 and modified on July 25th, 2003.
    >
    > According the documentation, the MS04-028 scan tool should be supported on
    > SMS 2.0 site servers on NT4 SP6a servers. thanks all in advance for any
    > help!
    >
    > Franz
    >
    >
    > 
    

  • Next message: Jeremy Byrne: "multiple users on Administrator Console"

    Relevant Pages

    • Re: Installation Error MS04-028 Scan Tools on NT4 Site Server
      ... The SMS MS04-028 scan tool is supported on NT4, ... named "MS04-028 Scanner" and populate the collection with a test machine ... Create Package ... Name=Security Update Tool ...
      (microsoft.public.sms.admin)
    • Re: Slackware 9.1 - getting HPPSC1210 to work
      ... I have managed to get the scanner part working. ... Again, I have downloaded it, converted to TGZ and installed. ... > would suppose had to be installed by the hpoj package ... ... > solution (package doesn't include it, can't compile from source, mmmm). ...
      (comp.os.linux.hardware)
    • Re: On the death of teTeX
      ... incremental package updates available if there were an update tool for ... updates and install them, much as yum does on FC or presumably apt ... Define a subset of the TeX Live TEXMF tree to get something ... | like the MikTeX package manager mpm would be needed to install ...
      (comp.text.tex)
    • Re: On the death of teTeX
      ... incremental package updates available if there were an update tool for ... updates and install them, much as yum does on FC or presumably apt ... It's called MikTeX package manager mpm and has ... Define a subset of the TeX Live TEXMF tree to get something ...
      (comp.text.tex)
    • Re: cannot detect scanner
      ... If the latest drivers for the scanner are for XP, my guess is one, either ... operating system for which the original package was designed. ... then install the updated drivers. ...
      (microsoft.public.windowsxp.accessibility)