cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Windows agent deployment policy update issues

Hello

 

A large number of our agent deployments to Windows machines using sccm end up needing manual fixing due to policy timing out on the first update.

 

SCCM pushes the agent,  schedules and all beacons are included. The first run of policy update fails with time out and will continue to fail until run manually by an administrator. 

 

Anyone else seeing policy issues like this in the environment?

(6) Replies

Hi @rwiltshire 

does the error also occurs if the agent is installed manually, but uses the same account for installation as SCCM and the same installation parameters as SCCM. Could you please post your agent configuration file or tell us the settings you're using. Is the agent client able to reach the beacon IIS ManageSoftRL site (https://[BEACONSERVER]/ManageSoftRL/) ?

my basic settings are

Thanks and Best,

Dennis

The same error with policy occurs manually as well if policy is installed at the time of agent install. Typically running policy manually fails once then kicks into gear. This occurs deploying one agent or 10 or 100 at the same time. 

 

I'll take a look at the other options you have included to see if these can help bring our success rate up. The ignore policy error option might be a great hint. 

 

Thanks

Hi,

One suggestion is by deploying Flexera Agents in smaller chunks sequentially.

After the initial deployment, a Flexera Agent will try to download the policy from the Beacon that you specify in the deployment configuration file immediately.

Assuming that you push 10,000 Flexera agents to client computers using SCCM in a single batch, after completing the installation, the 10K agents will try downloading the policy simultaneously. Your Beacon(s) most likely will be overwhelmed by the number of simultaneous requests.

This will result in a time out error on the agents that are not getting a response from their Beacon in time.

Hi,

You can check also this thread https://community.flexera.com/t5/FlexNet-Manager-Forum/FNMS-Inventory-Agent-Deployment/td-p/96439/page/4 

You can create a custom package which will deploy o custom policy and you can schedule the policy updating time and also multiple beacons. I implemented a package like this and solved a lot of issue like network ports are closed at the deployment time or one package for all beacons. 

Our team recently updated the installation scripts to include all beacons and schedule. Even with this the policy ends up timing out and the agent does not report up inventory right away. 

The policy success is flakey but we have not discovered if the error is network, iis related or agent related.

We find the error occurring in small batches. Our agents are deployed at build time for servers so the number is really low most of the time.