In BHOLD Core -> Model -> Users, I am receiving a Warning - "{Requested registry access is not allowed.}" As per release notes, I have updated CoreWebPath in: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\bhold\FIM and DomainName, BFSSManageAttributeRoles, BFSSTimer, BFPCTimer in: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\bhold\b1Core I am not aware of any other required modifications. I have tried modifying the permissions on the bhold key & have had a poke around using procmon, but I can't see any glaringly obvious issues. Anyone know how to fix this? Matt

To resolve this, give the BHOLD Core Service account read permissions on the following Node: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\bhold\Attestation Matt

Matt, did this actually work? I see the same issue after installing the BHOLD core on the Home/BHOLD attributes/BholdAttributes page when I try to change the BHOLD system attributes NoHistory, MoveorgunitToSameorgtype, Days between ABA run and Start hour of ABA run. I was able to work around it by giving the account running B1Service (usually "b1user") "Full Control" of either HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\bhold or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\bhold\b1Core, but this doesn't seem right. I haven't found any other reference to "{Requested registry access is not allowed.}" except yours.

Matt, did this actually work? I see the same issue after installing the BHOLD core on the Home/BHOLD attributes/BholdAttributes page when I try to change the BHOLD system attributes NoHistory, MoveorgunitToSameorgtype, Days between ABA run and Start hour of ABA run. I was able to work around it by giving the account running B1Service (usually "b1user") "Full Control" of either HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\bhold or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\bhold\b1Core, but this doesn't seem right. I haven't found any other reference to "{Requested registry access is not allowed.}" except yours. Hi Laurin I resolved the issue you mentioned above in the same way by giving the b1user account full permissions on the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\bhold key. One could play around with reducing the permissions to achieve "least privilege" but the service account deffinitely needs at least write permissions here to be able to update the registry. I have not had time to do this yet but intend to do so in my test lab when I get the chance. I do find it strange that this is not automatically configured during install but it seems this is just one of many bugs in the MS release of BHOLD.Regards Lance Laurens Datacom Systems