Configuration profile changes not taking affect on some existing machines

[bbot]

I made changes to a configuration profile and set it to distribute to all machines.

100% of Newly added machines are getting the changes, but it seems like machines that had the policy before are not getting updated.

Currently it is set at a user level, changes were made 3-4 weeks ago.

[bbot]

Nevermind, Casper got back to me.

Thank you for reaching out about this! My sincere apology to hear that we are having issue pushing configuration profile to client device that are set to User-Level.

Currently we have a known bug case open (D-008182) for this issue. Our Developer are aware of the issue and is working for a fix. We do however have a workaround fix for this issue. Below is the workaround steps:

1. Clone the already existing user-level Configuration Profile but DO NOT click Save yet.
2. Make changes to the cloned user-level Configuration Profile.
3. Now we can save the changed cloned user-level Configuration Profile.
4. Delete the old original user-level Configuration Profile

Please give the above workaround steps a try and let me know of the result!

Thank you and have a wonderful day!

Best regards,

[jhalvorson]

@brandobot Which version(s) of CasperSuite does this bug apply to?

[bbot]

@jhalvorson 9.65. I just did a google search on that bug number, appears to have been an issue as early as January this year.