HOWTO: Create two software configurations for different versions of an application

Products

• BlackBerry® Enterprise Server for IBM® Lotus® Domino®
• BlackBerry® Enterprise Server for Microsoft® Exchange
  

---

Environment

• BlackBerry® Enterprise Server version 4.1 SP6 for Microsoft® Exchange
• BlackBerry® Enterprise Server version 4.1 SP6 for IBM® Lotus® Domino®
  

---

Overview

When creating a software configuration on the BlackBerry Enterprise Server you receive the following error:

Multiple instances of the following applications were found. Please remove all but the desired version to enable the applications for configuration.

---

Cause

The issue occurs when trying to create a software configuration for an application that has multiple versions created for different BlackBerry smartphones. For example, the BlackBerry® Client for use with Microsoft® Office Communications Server 2007 v2.2 is designed for the BlackBerry® Storm™ Series only. The BlackBerry Client for use with Microsoft Office Communications Server 2007 v2.1 is designed for BlackBerry smartphones that do not use the SurePress™ touch screen.

---

Resolution

Use the following process to create a second shared folder within C:\Program Files\Common Files:

1. Open My Computer and select the drive that hosts the BlackBerry Enterprise Server (C:\ by default).
2. Double-click on Program Files, then Common Files.

   Note: A folder must be created that uses the same folder structure as the Research In Motion folder.

3. Create a folder called RIM in the Common Files folder, then copy the AppLoader folder from the Research In Motion folder to the RIM folder.
4. To share the RIM folder, complete the following steps:
   1. Right-click on the RIM folder, then select Sharing and Security.
   2. Select Share this folder.
   3. Click Apply.
   4. Click OK.
5. Create a folder within the RIM folder called Shared, then create a folder called Applications within the Shared folder.
6. Copy the .cod and .alx files for the second application to the new Applications folder
7. Open a command prompt by clicking Start >Run, type cmd, then click OK.
8. Go to the directory within the RIM folder (for example: cd C:\Program Files\Common Files\Rim\AppLoader).
9. Run the command loader.exe/index.
10. In BlackBerry Manager, click the Software Configurations tab.
11. In the Common Tasks menu, select Add New Configuration. In the Configuration Name field, type a name for the configuration.
12. Click Change to input the Universal Naming Convention (UNC) path to the shared folder.
13. Type \\\.
14. Application Software should appear in the window, expand the window to see the new software configuration.

HOWTO: View Composer - How to Delete Orphaned Protected Entities in vCenter

View Composer enables the use of linked clones with View Manager in order to reduce the amount of storage needed per VM. It does this by coping the parent VM + snapshot into a protected VM or entity. This VM is protected so it can’t be deleted in vCenter to ensure an admin doesn’t accidentally delete the VM which users may be referencing.

The correct way to manage these protected VM’s isn’t within vCenter, it’s in View Manager. When a linked clone enabled pool is created, recomposed, or deleted this updates the protected entity accordingly. In some cases it may be necessary to manually unprotect and remove the protected entity in vCenter. SVICONFIG.EXE is included with View Composer to assist with this. Located under “C:\Program Files\VMware\VMware View Composer\SviConfig.exe” this command will unprotect any View Composer related protected entity.

Here is how to unprotect the host folder and any entities it may contain:

1. On the vCenter/View Composer server launch Start –> Run –> CMD
2. Browse to “C:\Program Files\VMware\VMware View Composer”
3. Type the command below replacing the default information with specific information for your environment.
“SviConfig -operation=UnprotectEntity -VcUrl=https://my.vc/sdk -Username=User1 -Password=123 -InventoryPath="/My Datacenter/vm/MyReplicaFolder" -Recursive=True”

OR

"SviConfig -operation=UnprotectEntity -VcUrl=https://vcenter/sdk -Username=domain\username -Password=password -InventoryPath="/DataCenterName/vm" -Recursive=True"

The second will unprotect all VMs in the specified data center.

If this is successful it will return a confirmation of any entities unprotected. Now it will be possible to use vCenter to delete the newly unprotected entity.

Source: http://blogs.vmware.com/view/2009/01/view-composer-how-to-delete-orphaned-replicasource-entries-in-vcenter.html

HOWTO: Removing a standard (replica) connection server from a cluster of connection servers

To remove a replica:

1. Uninstall the connection server and ADAM instance from the server that you want to remove from the cluster.
   1. Click Control Panel > Add or Remove Programs.
   2. Remove VMware View Connection Server and Adam Instance VMwareVDMDS.
      
      
2. Refer to Remove View Manager Entry in the Command Line Tool for View Manager document for full details on how to use the vdmadmin.exe tool to remove the reference to the now redundant replica in the ADAM database.
   
   Here is an example of the command:
   
   "C:\Program Files\VMware\VMware View\Server\bin\vdmadmin.exe -S -r -s "
   
   Note: This step is not mandatory, but it clears the removed Connection Server from the Admin UI.