| | Re: BES Transporter
I've tried twice now, the only difference being the group and policy assignments being left as default during the second transport. I read on another forum that this had allowed a transport when the assignment had resulted in MigrationCompletePending.
I also receive the following warnings in the BBET log:
SWITCH_SERVICE is still pending, device may be out of coverage
SET_IT_POLICY is still pending, device may be out of coverage
While going through the transporter logs I noticed my destination BES shows up as [188.8.131.52] when Programs lists it as 5.0.4 MR1; could the mismatch cause this or is it just how the versions are displayed?