If all my offices had DHCP from their ISP, zero-touch provisioned would become more of a reality. Until then, I'm still involved in IAP/RAP deployments. It's honestly much easier to convert each IAP-to-RAP, set enet0, then ship it off. The device is plug-and-play once it reaches the remote office.
Our installers already have a couple of wireless devices and a tool that measures the signal strength of each access point.
That's a good idea. Very basic tool, but can be very helpful for verifying RSSI. I typically use the inSSIDer on my Android for quick signal testing.
What percentage of the Airheads community are installers?
<-- Architect, configuration, installer, troubleshooter
Relative to other wireless products, how installers feel about deploying Aruba devices?
I don't have any experience with other vendors, but most of my installs local or remote are fairly painless. My issues are more operational.
In order to minimize delays in deployment, what are some other tools that an installer should have in his toolkit?
In addition to what you said, packet capturing software w/capturing device is a must. My favorite lately is WildPackets OmniPeek w/Wildpacket 3x3 wifi adapters. Alternatively, an IAP-225 configured to send packet captures to my laptop.
Are there any additional diagnostic tools/software that you would like included within the controller (mobility or virtual)?
I'm very happy with being able to send AP packet captures directly to my computer in Wireshark or OmniPeek format in realtime. This is a great feature. There is an option to send the unencrypted client traffic from the controller to a destination as well, but for some reason it only shows traffic from the client you're tracking, it does not show traffic to that client. If I had it my way, I'd be able to see to/from traffic for the client I'm doing the packet capture of.