Hi Dave,
I did nothing too complicated, just created a VLAN on the controller (IP NAT inside enable), create a DHCP pool for that VLAN in the controller, and assign that VLAN to clients.
This "workaround", if it could be named like that, just NAT all the traffic on that VLAN to controller's IP address, so this is only a workaround. Two possbile solutions are:
1.- Configuring all the IP parameters in a static way for Playbooks (you have the BB support link to justify this)
2.- To use network devices (like Aruba's, etc.) internal DHCP servers. (But this will only work if you can turn off the Win2008 Scope, and I guess you can't do that as you don't have access to the servers)
As I stated before the environment was:
Aruba Controller and APs
WPA2 SSIDs (PEAP and EAP-TLS)
Windows 2008 DHCP server
This would be enough to convince your customer that this is a BB - DHCP issue.