Package Issue

  • This topic is empty.
Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #346
    Avatarrigs
    Member
    • Total Post: 12
    • Regular Joe
    • ★★

    Gents,

    I have S90 XPe device, on Rapport 4.4.1, executing a small program Ive put together that runs Microsofts qfecheck program to check for installed MS patches, then map a drive to server, and then write the output back to a file on a server share ( written in Wise Package Studio ). I end up with a file the name of the Thin Client asset ( eg abc1234.log) with all the installed QFEs listed in a txt based .log file.
    I have added this as a Rapport package, and all the rsp does is copy the EXE local, run it, then delete file and end.
    The program runs perfectly as standalone on the device,( from my USB Stick) when logged in as an Admin, but fails when sent as a Rapport Package.
    Im using basic “Net Use” commands, to map to server.

    Does someone have any reasonable explanation for this ?


    Text=*** Map a drive to Server using Admin acct

    Execute Program
    Pathname=cmd.exe
    Command Line=/c net use p: \serverpatch_reports /user:Administrator password

    Text=*** Run QFE Check, with output directed to P:
    Execute Program
    Pathname=%sys32%qfecheck.exe
    Command Line=/l:p: /v/q

    #9282
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    Assuming it runs OK from the batch file run from the terminal can you post the Rapport script as it may be an error there. The script may look like this:


    CO=XP
    CF=4000
    LU

    SF “QFE_updatebatchfile.cmd” “Z:batchfile.cmd”
    EX “Z:batchfile.cmd” “+”

    EL


    Now, as a side issue. I would not recommend updating every patch this way. Why? Many of them are not required as parts of the OS are missing and you could be patching something that does not exist. Also these patches fill the flash at an alarming rate.

    If you go to Wyse.com on the main downloads page you can subscribe to an email where Wyse vet every MS release and if its an issue repackage it as small as possible into a Rapport package you can load up and push out. Also Wyse email you when this is done so you don’t have to remember to check.

    Now this is not to say you can’t do what you are setting up but check the patches you are pushing and don’t fill the flash. Also consider firewalling the units and maybe on a separate VLAN.

    Cheers,
    -TT

    #9283
    Avatarrigs
    Member
    • Total Post: 12
    • Regular Joe
    • ★★

    here is rsp….as I said, its very basic.
    Im only patching with released Wyse patches…..this process is for reporting purposes only ….

    [Version]
    Number=runreport
    Description=Runs qfecheck and directs out to Server
    OS=XP
    Category=Other

    [Script]
    ;
    ;DATE: 16 Mar 2007
    ;
    ;Prepared and Written by me
    ;
    ; This package is for use on XPe builds with SP2 only. It will fail
    ; on other builds.
    ;
    ;


    ; Check Operating System, Check SP level and Confirm free space
    ;


    CO “XP”
    CV “c:windowssystem32ntoskrnl.exe” “>=” “5.1.2600.2622”
    CF “C” “5000”
    ;
    ;


    ; No Lockout
    ;


    ;LU
    ;


    ; Copy over the update files
    ;


    SF “Crunreport.exe” “c:runreport.exe”

    ;
    ;


    ; Execute the update file
    ;


    EX “c:runreport.exe” “+”
    ;
    ;


    ; Local Pause
    ;


    LP “10”
    ;
    ;;


    ; Delete the file
    ;


    DF “c:runreport.exe”

    #9284
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    Cool, I assumed you were going to run the patches, as a report only this is cool.

    It looks OK to me, I am assuming the script runs with no errors on the Rapport console? Throw a script with a text out put or pop up near the end of the Rapport script to test this. Also try not mapping the drive and dump the results of qfecheck.exe to the Z: drive to see if this is the issue. Once you narrow down the problem it should be easy to fix.

    If this is the case is it possible that you have a problem with the batch file running as system? This would explain why it works when you run it as admin.

    Post back your results,

    Cheers,
    -TT

    #9295
    Avatarrigs
    Member
    • Total Post: 12
    • Regular Joe
    • ★★

    Just cant seem to get the device to connect back to the server. Will see if a”null share” is the way to go.

    Cheers.

    #9341
    Avatarrigs
    Member
    • Total Post: 12
    • Regular Joe
    • ★★

    Aborting this project, cant get it to work.

    I would like to be able to provide reports to my customer showing what level of patches my S90s have.
    If anyone has any cool suggestions for patch reporting…Im listening.

    #9342
    Avatarrigs
    Member
    • Total Post: 12
    • Regular Joe
    • ★★

    Basically …

    How do I query the rapport mdf file, to find the QFEs listed on a device ?

    Cheers.

    #9345
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hmm, nice challenge.

    You could simply do a package report from Rapport and dump this to a spread sheet.

    Also the Rapport DB is a SQL database so you can connect to it and write a select statement for packages starting with HF*.

    This would give you what Rapport thinks went to the devices but you want to know what successfully deployed.

    Let me ponder on this … 8)

    #9362
    Avatarrigs
    Member
    • Total Post: 12
    • Regular Joe
    • ★★

    Any update on this ?

    #9363
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    Have you tried to use the MSBSA (MS baseline security analyzer) to scan the devices? This may give you a list of all the patches installed on each device. It will report many missing but this is not important as it compares to a full PC, main this is you should get a good consolidated report,

    Cheers,
    -TT

    #9364
    Avatarrigs
    Member
    • Total Post: 12
    • Regular Joe
    • ★★

    Its not so much the tool Im having problems with, its writing the results back to my Server that is proving hard.

    Whether MBSA or QFEcheck, I still have to write back to the server… and on these very locked down S90 devices, thats the stumbling block.

    Cheers.

    #9366
    Avatarkaraziel
    Member
    • Total Post: 74
    • Back Stage Pass
    • ★★★★

    way to stretch my brain

    if you can get the results on the device
    why not send the results to a file matching the unique machine name of each device and sending that back to the WDM FTP server.

    That way you can send one script to all the devices and have each create a unique file to review. You could even save as .csv and merge into a larger xls spreadsheet.

    Is there an output option from the application run here: EX “c:runreport.exe” “+” ? You could then add a line like this to create unique filename:

    EX “copy c:QFE_results.txt c:%computername%.txt”
    GF “c:%computername%.txt %computername%.txt”
    DF “c:%computername%.txt”
    DF “c:QFE_results.txt”

    *NOTE I haven’t tested this at all, its just a possible example you might consider. Its relying on the system variable %computername% to create the unique filenames.

    -k

Viewing 12 posts - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.