Dark Developments Where Knowledge Meets Power

15Aug/120

BlackBerry Express – Migration to a new server

Posted by Dark#Basics

BlackBerry Express - Migration to a new server

It's quitte easy to migrate a running BES installation. This is my check-list when preforming a BES migration.

Step1: Move Blackberry Operations

1. Download and install all BES pre-requirements on the new server.
2. Make sure that the besadmin has all permission it needs on the different mailboxes, throtteling, etc.
3. Install BES on the new server but redirect the configuration to the old BES during installation.
4. Move the Blackberry users to the new server using the webinterface.

Step2: Move configuration Database

1. Install SQL Express on the new server or create a new instance and make sure BESADMIN is able to logon to the new SQL instance. Enable TCP/IP and Named Pipes on the instance.
2. Disable all BES related services on the old server. Backup the old configuration database using the SQL Management Tools.
3. Disable all BES related services on the new server. Update the new BES Configuration Database. This is done by running createdb.exe BESMGmt.cfg. The files are located in the Database folder of the installation media. Make sure that the appropriate settings are made in the BESMgmt.cfg file.
4. Restore the BES Configuration database on the new server, make sure that Overwrite existing database is checked.
5. Change the configuration database setting on the new server. This is done by running the setup again and updating the Database Information Screen with the new instance name.
6. Start all services again on the new server.

btsc.webapps.blackberry.com/btsc/viewdocument.do?externalId=KB12304&sliceId=2&cmd=displayKC&docType=kc&noCount=true&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

btsc.webapps.blackberry.com/btsc/viewdocument.do?externalId=KB03112&sliceId=2&cmd=displayKC&docType=kc&noCount=true&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

btsc.webapps.blackberry.com/btsc/viewdocument.do?externalId=KB18129&sliceId=2&cmd=displayKC&docType=kc&noCount=true&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

Filed under: BES No Comments
15Aug/121

VMware- ESX Image Builder CLI

Posted by Dark#Basics

VMware- ESX Image Builder CLI

When installing ESX(i) on different vendor platforms you'll get confronted with warnings related to drivers. In my case it was a Dell R720 and during the installation of ESX I got the message "no network adapters found".
The only option is to build your own custum ESX image and inserting the correct NIC drivers.

1. Download the latest ESXi build from the patch page from VMware. my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vmware_vsphere/5_0#product_downloads

2. Next download the approriate driver software from the driver depot. my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vmware_vsphere/5_0#drivers_tools
Note: In my case I needed the net-tg3 drivers.

3. Extract all the files so that you can access them with vCLI. You can download vSphere CLI from my.vmware.com/web/vmware/details/vcli41/ZHcqYmRoaCpiZHRAag== .

4. Next, start your PowerCLI session and import the software depots using the “Add-EsxSoftwareDepot” cmdlet.  Import all the software depots you have downloaded.

Select All Code:
1
2
Add-EsxSoftwareDepot C:\vmware\ESXi-5.0.0-20120604001-standard.zip
Add-EsxSoftwareDepot -DepotURL "C:\vmware\net-tg3.zip"

5. After the software depots have been imported the next step is to create an image profile using the “New-EsxImageProfile” cmdlet. There are two ways to create a new image profile, you can create an empty image profile and manually specify the VIBs you want to add, or you can clone an existing image profile and use that as your starting point.

Select All Code:
1
New-EsxImageProfile -CloneProfile "ESXi-5.0.0-20120604001-standard" -Name "CustomISO" -AcceptanceLevel CommunitySupported

6. Next, you use the “Add-EsxSoftwarePackage” to add VIBs to your image profile.

Select All Code:
1
Add-ESXSoftwarePackage -ImageProfile CustomISO -SoftwarePackage net-tg3

7. After adding the VIBs you need the next step is to export the image profile. You can export the Image Profile as a software depot (.zip) or as an ISO file (.iso).

Select All Code:
1
2
3
Export-EsxImageProfile -ImageProfile CustomISO -ExportToIso -FilePath C:\vmware\CustomProfile.iso
 
Export-EsxImageProfile -ImageProfile CustomISO –ExportToBundle -FilePath C:\vmware\CustomProfile.zip

blogs.vmware.com/vsphere/2012/04/using-the-vsphere-esxi-image-builder-cli.html

communities.vmware.com/message/2069580