I’ll use fixlet ID 9800701 as an example here:
You’ll notice within the fixlet description, there are multiple tags that reference template files. They look something like this.
These will be removed and in cases where the contents of the template are still necessary, the contents will be placed directly into the fixlet.
You should not expect to see any visual differences in currently supported versions of BigFix console.
Templates like “1_0.txt” (http://sync.bigfix.com/bfsites/bessecurity_3409/1_0.txt), which will be removed, are only visible in much older versions of BigFix.
So the raw description from the above link would look something like this instead:
<!-- StartBESFixletMessage -->Microsoft has released a patch that fixes vulnerabilities in Exchange 5.0 NNTP Service and SMTP Service. An attacker could send a series of incorrect data to either service. In the case of the NNTP Service (TCP/IP port 119), it would cause the Server Information Store to fail. This could in turn cause other Exchange Services to fail and prevent users from connecting to their mail folders. In the case of the SMTP Service (TCP/IP port 25), it would cause the Internet Mail Service to fail, but would not affect other Exchange Services.
<b>Note: </b>Due to the complexity of this upgrade, installation of this patch must be completed manually.
<b>Note:</b> This Fixlet message does not have a default action. For more information on default actions, see BigFix KB #474.<!-- EndBESFixletMessage -->
<!-- StartFixletButtonArea -->
<!-- StartBESFixletPrelink -->Click <!-- EndBESFixletPrelink --><a href=“https://docs.microsoft.com/en-us/security-updates/securitybulletins/1998/MS98-007”>here<!-- EndBESFixletLink --></a><!-- StartBESFixletPostlink --> to view Microsoft Security Bulletin MS98-007.<!-- EndBESFixletPostlink --><!-- StartBESFixletPrelink -->Click <!-- EndBESFixletPrelink --><a href=“cid:Action2”><!-- StartBESFixletLink -->here<!-- EndBESFixletLink --></a><!-- StartBESFixletPostlink --> if you wish to remove this Fixlet message and mark it as fixed on affected computers. In doing so, you accept the risk of not closing this vulnerability on affected computers.<!-- EndBESFixletPostlink --><!-- EndFixletButtonArea -->