Hi @mbartosh -
Is this a policy action? Did you create it prior to the upgrade to v10? If so, you may need to re-start the policy using the he latest Fixlet 2305 in BES Support, where you’ll see that they added code to deal with the change in the prefix:
// prefix name of the tag files
if {((parameter "ClientVersion" of action) starts with "10.0")}
parameter "Prefix" = "hcltechsw.com-BigFix_"
else
parameter "Prefix" = "ibm.com_IBM_BigFix_"
endif
As far as I know, there was no notice given by HCL that this had happened.
In my case, once I discovered the issue, I re-ran the whole tag generation process. I don’t know if this was necessary or not. You may want to open a support case with HCL to work through the issues.
