Is there a way to suppress the generation of these messages while using SMS SP1 schema ?
First option is, tell SMS to not publish to AD. By default it is configured to publish to AD. It’s on the Advanced tab of the Site Properties dialog box. This is not the best option.
Second you could create a status filter rule to filter out this specific error until you can update the schema.
This is the better solution and we recommend you upate the schema when possible to obtain this FQDN support.
- Carl
