Pull – although the server can send a “refresh” command to a client to have them check in with the server faster)
As of version 8, I believe the files can be downloaded by the client in advance, then run at whatever time is set in the action.
Files are actually copied to the client from a BES server or relay. No file servers or file shares are involved, and using a file server is generally not recommended.
Pull – although the server can send a “refresh” command to a client to have them check in with the server faster)
As of version 8, I believe the files can be downloaded by the client in advance, then run at whatever time is set in the action.
Files are actually copied to the client from a BES server or relay. No file servers or file shares are involved, and using a file server is generally not recommended.
(We are beginning to test BigFix now and there are no relays involved yet.)
As for #2, after the files are copied in advance, is the ‘Action’ triggered by the server or client?
I ask because if something were to happen and cause the server to be unavailable, will the ‘Action’ never be able to take place?
if the main BigFix server crashed and your clients had downloaded the actions and were all queued up, they would continue to run. For example, if the clients were taken off the network (a laptop for example) your actions would still run. Sames true for servers. Now, since the server is down, you’d have no way to know if they succeeded or not of course…
if the main BigFix server crashed and your clients had downloaded the actions and were all queued up, they would continue to run. For example, if the clients were taken off the network (a laptop for example) your actions would still run. Sames true for servers. Now, since the server is down, you’d have no way to know if they succeeded or not of course…
That makes sense, but just to be sure (have to have answers for management), If the actions were currently taking place, they would continue to run.
But, for example, if a server had an action to take place at 5pm and crashed at 4pm, would that action still be triggered/started? Or another way of asking, would the server send the date and time to start the install, along with the patch, to the client and then would the client begin the install at 5pm (assuming the server is still down)?
If you send the action at 3pm to start at 5pm, and the main BES crashes at 4pm, I’m 95% sure that the action will still run on the endpoint. However, you would need the download to occur before the server dies, or else it won’t successfully run at 5pm.