Scripting and FBWF

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1138
    Avatarcola007
    Member
    • Total Post: 2
    • Newbie

    Hello,

    I’m fairly new to the Thin Client technology and have been working with Wyse V90Ls for about a month now. I’ve successfully installed and configured WDM 4.5.3 and have started to learn Wyse’s scripting language.

    I’m attempting to install McAfee Antivirus 8.5i with EPO and I’d like to push that out through a script in WDM. I can get the application installed and running for the most part, my concern comes in when trying to exclude the virus definitions from the Write Filter.

    It it my understanding that the Write Filter exclusions cannot be added when the Write Filter is disabled (red) – and I have confirmed this by attempting it manually. When the WDM Scripts are run, the device reboots and disables the filter, thereby stopping my ability to script any exclusions with the McAfee, or any other package. Is there any way around this using WDM scripting?

    I’ve tried creating a test script to exclude an existing directory from the Write Filter on a test V90 and the results were as I expected – it did not work.

    Any suggestions will be greatly appreciated! Please let me know if any more information is needed.

    #12701
    AvatarNeo
    Member
    • Total Post: 8
    • Newbie

    You should be able to run command lines through the WDM script or, worst case, push down a batch file that you can execute with the command lines in it. They proper syntax is the key. What you want is:

    fbwfmgr /addexclusion c: directory path

    Make sure there is a space between the volumename (c: in this case) and the slash that starts your path statement.

    In a WDM script it would look something like this:

    EX “fbwfmgr /addexclusion c: directory path”

    I have not tested this last so I don’t know for sure if it will work.

    #12734
    Avatarcola007
    Member
    • Total Post: 2
    • Newbie

    Neo, thanks for the suggestion.

    I tried scripting it through a WDM script and it did not appear to work.
    I’m trying to figure out how to completely automate the install in one, or at most two packages. The systems have not been joined to the domain (yet) so I’m not sure what the best method of deploying a batch file to them would be in order to add the exclusions.

    I’ve contacted Wyse in regards to this and my rep suggested running fbwfmgr /enable and then adding the exclusions but I think that would require a reboot inbetween enabling the filter and adding the exclusions, effectively putting me back in the same situation.

    I’ve got a few months experience doing VB scripting and I have WMI enabled on the terminals so I should be able to accomplish the task, just not in the desired method.

    I’m going to try out enabling the filter then adding the exclusions without a reboot and see what happens.

    Any other suggestions in the mean time will be greatly appreciated.

    Thanks!

    #12737
    AvatarNeo
    Member
    • Total Post: 8
    • Newbie

    I think I see your problem now.

    Try pushing your batch script down with WDM and setting the Runonce key to run the script on the next reboot. This should get around the issue of FBWF not being enabled while you push out the WDM script.

    You will need to put a reboot at the end of your batch script though because the exclusions do not take effect until the reboot following being added to the list.

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