I thought I read that adding a task to update the client configuration could help, but now I'm not sure if that's what we need for enforcing the blockout.
I'm a bit confused about the differences between options C and D. Both seem to deal with restricting communications, but I can't recall which one specifically addresses the blockout.
This is a tricky one. I'm not entirely sure which option is the best way to enforce the agent blockout. I'll need to review my notes and maybe even look up some documentation to make sure I get this right.
Okay, let me think this through step-by-step. I need to find where the agent settings are configured and look for an option to enforce a blockout at startup. I think option B or D might be the right approach.
Ah, I remember learning about this in class. I believe the answer is option D - configuring the target agent settings to disable communications at startup and adding a blackout period.
Hmm, I'm a bit unsure about this one. The options seem to cover different areas of the agent configuration. I'll need to carefully read through each one to determine the correct procedure.
That makes sense too. I guess we need to carefully read the options and choose the one that best fits the procedure for enforcing the agent blockout at system startup.
Haha, I bet the developer who wrote this question is a real comedian. 'Randomize next configuration update time'? What is this, a game of chance? I'll have to go with option B, it seems the most straightforward.
I disagree, I believe the correct answer is B. Enforcing an agent blockout at startup seems more related to configuring the Symantec Management Agent Package install task.
I'm going with option C. Configuring the downloads tab under global agent settings to use bandwidth throttling and restrict 'Agent communications for a set time at startup' sounds like the best way to handle this.
Option D makes the most sense to me. Configuring the target agent settings, under the blockouts tab to 'disable communications at startup' and adding a blackout period seems like the logical way to enforce an agent blockout.
I think option B is the correct answer. Configuring the advanced tab on the Symantec Management Agent Package install task to 'Enforce an agent blockout at startup' seems like the most direct way to ensure the enforcement of an agent blockout at system startup.
Candra
3 months agoIn
3 months agoDevon
3 months agoColeen
4 months agoLawrence
4 months agoLeana
4 months agoPaz
4 months agoDenise
4 months agoJonell
5 months agoVincenza
5 months agoAlpha
5 months agoYoko
5 months agoStephaine
5 months agoDorothea
5 months agoElouise
1 year agoCordelia
1 year agoMuriel
12 months agoElza
12 months agoFranchesca
1 year agoMarci
1 year agoMartha
1 year agoMarvel
11 months agoWayne
11 months agoMaryln
11 months agoEun
1 year agoElouise
1 year agoGlenna
1 year agoXuan
1 year agoSamira
1 year ago