Amanda, by 'agent enrolment' do you mean it fails to install or appear in bladelogic console?
If fails to install then have you reviewed the windows\temp\rscd-install.log?
If fails to appear in blade, has Update Server Properties been run? Is the agent started on the system? If not started, rscd.log should have the cause.
the appserver needs to be able to resolve the hostname of the server. also - what version of bsa is this? in some versions of BSA we did not alter the windows firewall policy so port 4750 may be blocked.
I was able to figure out that a secondary permissions job was stopping the agent from installing.
Sent from my iPhone4