I am quite new to big fix and have been searching for an easy way to do this but cant seem to find the answer, so really need some help.
I have found a query by brolly33 that finds the logon server, but wanted to know how i could use that information to run some macafee installations.
Query is
q: if exist value “LogonServer” of keys “Volatile Environment” of keys of key “HKEY_USERS” of registry then value “LogonServer” of keys “Volatile Environment” of keys of key “HKEY_USERS” of registry as string else “Not Logged On”
a: \logonserver
How can I then use this answer to add to a installation script
The easiest way to do it is to use the software distribution wizard to package up your McAfee folder and then use the resulting Task to install McAfee on whichever systems that you target.
Hi Ben, havnt used the wizard before, but had a quick look through it, and it looks like there is only an option to grab the package from a central location, however i have 150 remote sites and wanted to pull the installation files from a server on each site, like the logon server, cutting down on the WAN traffic. Hopefully without creating 150 tasks.
A simple task like the below works a treat, if there was only a way for the task to substitute dc1 for the local logon server each and every time
It is technically possible to try have the agent use the files on a share, but the key problem is that the agent runs as the SYSTEM account and doesn’t have access to the share (here is more info: http://support.bigfix.com/cgi-bin/kbdirect.pl?id=1249).
One of the benefits of BigFix is that it distributes the packages through relays for you and so as long as you have designated a relay in your remote sites, you can deploy packages very easily through BigFix and minimize the WAN traffic (each relay will cache the files for you automatically). It would all be done with one Task.
Have you set up the relays yet (which you should in any case)? If so, distributing this package through the software distribution wizard still sounds to me like the easiest approach (the alternative is to use the RunAsCurrentUser approach or the NullSessionShare approach that are outlined in that KB article above).