Please post what is written to the device log while the installation is taking place. You can monitor the device console from the Organizer window in Xcode. Open Xcode and select Window -> Organizer then select Console under your device.
Based on your description I can think of three things that may have caused this:
OTA Over SSL
The device attempting to install the app is running iOS 7.1 and the manifest.plist and ipa are not being served over SSL. Please keep in mind that iOS 7.1 now requires OTA installations to take place over a secure https connection.
Signed with Incorrect Profile
If the device log contains "Unable to preflight application" then the application was most likely not signed appropriately. You can verify that you are indeed using the correct mobile provision by following the steps from this answer: https://stackoverflow.com/a/18642782/1144060
- Take your IPA file, rename it to have a .zip extension.
- Unzip this file and open the Payload directory in Finder.
- Right click your application and click Show Package Contents.
- Find the file embedded.mobileprovision, and open this file in a text editor (like TextEdit).
If the embedded.mobileprovision contains an entry for ProvisionedDevices then you are signing with an Ad Hoc or development profile and not with your enterprise profile.
Missing Private Key
Unless the enterprise certificate is managed by Xcode (e.g. you created the enterprise certificate from within Xcode) it is likely that Xcode does not manage it in the same way it manages your other profiles.
Our build machine has multiple ADC accounts configured in XCode 5. When attempting to initialize a new build environment I exported the profiles and imported them into the new build environment. The enterprise certificate and key were not created by one of the accounts registered in Xcode. The enterprise certificate and key were not transferred.
On your macbook open Keychain Access.app and selected the Certificates Category on the lower left. Your enterprise certificate will be shown in relation to the private key. Select both of them and then select File... -> Export. Enter a password to protect the p12 file.
Copy the resultant p12 file (Named Certificates.p12 by default) to your mac pro and double click the file to import it into your default keychain using Keychain Access.app