Victor Lyuboslavsky

When we shipped Windows MDM, we did not plan, design, or QA the WlanXml profile, so this is a StoryBug (TM).

@marko-lisica Yes, Fleet couldn't verify because we don't have special logic for comparing this type of profile. This is similar to the ADMX-backed profile type which I recently added verification...

Yes, we should try to uncover other config scenarios and make sure we handle them. We don't have to fully verify each scenario, we just need to recognize it. For...

Yes, if profile status is failed, Fleet will try sending it again only once.

@nonpunctual This issue was mentioned `customer-person`'s call. This issue only fixes the validation issue with the WlanXml profile. By validating it correctly, Fleet should not try to resend it. The...

@marko-lisica A few questions. 1. Since the expiration date cannot be configured, do we want to add an environment variable to disable renewal? Maybe `FLEET_SERVER_NDES_SCEP_RENEWAL_DAYS`, where 0 would mean disabled....

> > Since the expiration date cannot be configured, do we want to add an environment variable to disable renewal? Maybe FLEET_SERVER_NDES_SCEP_RENEWAL_DAYS, where 0 would mean disabled. This will also...

> * Add validation to make sure `CN` field in NDES SCEP profile includes `$FLEET_VAR_NDES_SCEP_RENEWAL_ID` This implies that renewal is always enabled.

> > > * Add validation to make sure `CN` field in NDES SCEP profile includes `$FLEET_VAR_NDES_SCEP_RENEWAL_ID` > > > > > > This implies that renewal is always enabled....

> @getvictor I think to make this simpler for now, let's skip this. I think we won't close doors for later. We can always add this? ok