CHI-LTD
asked on
Blackberry 10 Server install
I have installed this all is working fine (as i can register with usb lead via Web desktop manager) apart from wireless activations. I suspect that it is because of the recent port changes on MDS during install.
I assume we simply need to open up port 3101 still, nothing else?
Can anyone link the recent changes to the the MDS install as i cannot find it?
Thanks
I assume we simply need to open up port 3101 still, nothing else?
Can anyone link the recent changes to the the MDS install as i cannot find it?
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Unsure of routing service? What/where is this?
I have installed BDS and MDM only.
No, i have already ran through this kb and changed the ports during install.
I have installed BDS and MDM only.
No, i have already ran through this kb and changed the ports during install.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
right, so we need to setup the router even if we dont have a dmz?
Yes. They just make it so you can put it in the DMZ if you would prefer.
ASKER
Yes, i need a blackberry router on the BDS 10 server? If so that could be the problem then. i have re-ran the installer (not installed UDS) and can't see any option for blackberry router...
Sorry. I just saw this. I will get a screen shot up loaded.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ah, well i dont get this screen!!!!!!
bds.jpg
bds.jpg
Are you running it on a box that already has BDS installed? It has to be installed on a separate system (or VM).
ASKER
yes all on one box...
really, thats annoying..
So will this resolve my OTA registrations???
really, thats annoying..
So will this resolve my OTA registrations???
It should, although without being familiar with everything in your environment I cannot guarantee that fact. I know you you need it to function correctly.
ASKER
can it be installed on the bes5 server?
No. It would conflict with the BES 5 router. None of the BDS features and services can be installed on a system running previous versions of BES.
ASKER
so i need this part of BDS for OTA activations but cannot install it on the same server?
I stand corrected. While verifying the answer to your question. I did find a KB where you can configure it to use your existing BES router service.
http://btsc.webapps.blackberry.com/btsc/viewdocument.do?externalId=KB29748&sliceId=2&cmd=displayKC&docType=kc&noCount=true&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl
http://btsc.webapps.blackberry.com/btsc/viewdocument.do?externalId=KB29748&sliceId=2&cmd=displayKC&docType=kc&noCount=true&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl
However, you would need to eventually stand up a stand alone router if you eventually decommission your BES 5.0 environment.
ASKER
strange thing is im sure i have already tried this... Will give it another go
Did you get this working through your 5.0 BES?
ASKER
In short no. Its a bit odd though. We now have activesync up and running on the exchange side. If we setup activesync the playbook can talk to exchange and it sets up the email and prompts for work/balance area.
Still unable to register OTA and have got the BES5 server and port number in the BES10 BDS side of things.
The next thing im looking at now is building a new VM for the BES10 router...
Still unable to register OTA and have got the BES5 server and port number in the BES10 BDS side of things.
The next thing im looking at now is building a new VM for the BES10 router...
Are the Playbooks Wi-Fi only? The ones we have are, so they work over the internal network to activate.
ASKER
No, i have the newer 3g one that doesn't rely on wifi/bridge...
Just read that the devices OS needs to be at v2.1 for OTA activations. Our is at 2.0.1.668...
Just read that the devices OS needs to be at v2.1 for OTA activations. Our is at 2.0.1.668...
ASKER
Got the router installed on another VM and configured BDS to use that server for routing.
Not had chance to test it properly though.
Also found playbook 3g cannot activate OTA with v2.0. Must be v2.1 to register...
Not had chance to test it properly though.
Also found playbook 3g cannot activate OTA with v2.0. Must be v2.1 to register...
ASKER
i assume this isn't the issue as the port changes are local, and is probably firewall related?