Decomming BES5
We currently have a BES5 / BES12 hybrid and BES5 is now longer needed. I cannot find any documentation on decommisioning BES5, can anyone help with the steps?
Thanks! |
Re: Decomming BES5
just turn it off or uninstall it
remove port 3101 on firewall call it a day unless you want to remove the service account too but most use the same one for BES 12 also How to decommission a BlackBerry Enterprise Server or component and remove it from the BlackBerry Administration Service console |
Re: Decomming BES5
Yeah, done that but BES12 is now complaining about not being able to talk to the BES5 servers. We can't add or edit any users..
2016-12-20T13:14:36.484+0000 - CORE {dirSyncProcessor-thread-1} admin.directory.management|core [{}] - WARN QuarantineException caught, quarantine data due to java.lang.IllegalStateException: com.blackberry.enterprise.shadowing.bbc.client.Bbc ClientException: java.net.SocketTimeoutException: connect timed out com.rim.platform.workflow.io.runner.QuarantineExce ption: java.lang.IllegalStateException: com.blackberry.enterprise.shadowing.bbc.client.Bbc ClientException: java.net.SocketTimeoutException: connect timed out at com.rim.platform.workflow.errorhandler.impl.Defaul tErrorHandler.handleRetry(DefaultErrorHandler.java :94) at com.rim.platform.workflow.errorhandler.impl.Defaul tErrorHandler.handle(DefaultErrorHandler.java:80) at com.rim.platform.workflow.io.runner.WffErrorHandle rRunner.run(WffErrorHandlerRunner.java:74) at com.rim.platform.workflow.io.runner.WffErrorHandle rRunner.run(WffErrorHandlerRunner.java:25) at com.rim.platform.workflow.io.runner.ActivityDelega teRunner$ProxyRunnerAdapter.run(ActivityDelegateRu nner.java:50) at com.rim.platform.mdm.core.service.workflow.RestEas yThreadLocalHandoff.run(RestEasyThreadLocalHandoff .java:39) at com.rim.platform.workflow.io.runner.ActivityDelega teRunner.run(ActivityDelegateRunner.java:41) at com.rim.platform.workflow.io.runner.ActivityDelega teRunner.run(ActivityDelegateRunner.java:16) at com.rim.platform.workflow.io.runner.WorkflowContex tRunner.run(WorkflowContextRunner.java:85) at com.rim.platform.workflow.io.runner.WorkflowContex tRunner.run(WorkflowContextRunner.java:32) at com.rim.platform.workflow.io.runner.factory.BasicR unnerFactory$1.run(BasicRunnerFactory.java:186) at com.rim.platform.workflow.executor.impl.SimpleThre adManager$ExecuteNextDispatcher.run(SimpleThreadMa nager.java:203) at java.util.concurrent.Executors$RunnableAdapter.cal l(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker( Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run (Unknown Source) at java.lang.Thread.run(Unknown Source) |
Re: Decomming BES5
Was BES 5 integrated into BES12, i.e. did you just have one Web Console to manage BES12 and BES 5?
|
Re: Decomming BES5
Hi, all sorted here's the not very helpfully named KB that helped:
How to decommission Services for devices running BlackBerry OS 7.1 and earlier in BlackBerry Enterprise Service 12 |
Re: Decomming BES5
Great, thanks for letting us know. I have not seen this KB before.
|
All times are GMT -5. The time now is 06:34 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.