Migration of Blackberry users from domino to Exchange

This article describes the main steps for migrating BlackBerry smartphone user accounts from a BlackBerry Enterprise Server in one mail platform environment (IBM Lotus Domino, Novell GroupWise, or Microsoft Exchange) to a BlackBerry Enterprise Server running on a different mail platform.  The process outlined in this article accomplishes this scenario by using the BlackBerry Enterprise Server migration kit. The kit includes a permanent Server Routing Protocol (SRP) Identifier and an Authentication Key that replace the existing SRP Identifier and Authentication Key already in use.  An SRP Identifier can be used on a BlackBerry Enterprise Server for any mail platform.

The BlackBerry Enterprise Server migration kit will also allow the client access licenses (CALs) from the current BlackBerry Enterprise Server to be used on the new BlackBerry Enterprise Server during the migration of BlackBerry smartphone users.


Complete the following steps:

Install the BlackBerry Enterprise Server software for the new mail platform on a separate computer using the SRP Identifier and Authentication Key provided in the migration kit and the same CALs that are currently used in the BlackBerry Enterprise Server on the current mail platform.

Remove the BlackBerry smartphone user accounts from the BlackBerry Enterprise Server in the current mail platform environment (Domino).

Delete all data from the BlackBerry smartphones. For instructions, see knowledge base article KB02318.

Add the BlackBerry smartphone user accounts to the new BlackBerry Enterprise Server in the new mail environment (Exchange)

Unable to login to Lync from Blackberry Device

Problem:

Recently i faced this issue, where the error says "Someone is connected to the account from another computer"


Verified the article here, but it didn't solve the issue, as we are already running on Blackberry Enterprise Server 5.0 SP3 MR8.

It is a known issue with Blackberry Enterprise Server.

Resolution:

Once i have restarted the Blackberry Collaboration Service the issue got fixed and user is able to login to Lync from blackberry device.

To fix the issue permanently in your environment, you need to upgrade to BES 5.0 SP4

Bulk user creation in Blackberry Enterprise Server

In most organizations, we would already have a list of users present in our messaging environment (or in Active Directory). Instead of adding a single user at a time—which in a large organization could take up valuable time—we can create a .csv file and import a batch of users. When we carry out the import of users, we can specify:

The names of the groups we want to add the users to
Details about activation such as type of activation, password, and expiry times
E-mail address
Which Blackberry Enterprise Server instance to join, denoted via the SRP ID
For the purpose of this lab, we are going to create a .csv file that will create and add six users to our group called Sales Team. Set each one up with a default activation password of 'password', which has an expiry time of 40 hours.

1. Open up Notepad.

2. Add the following column headings, each separated on one line with a comma:
E-mail address
SRP ID
Group names
Activation password operation
Activation password
Activation password expiry
For each user, specify their e-mail address, the SRP ID for the BlackBerry Enterprise Server instance we want to join, and the group name—in our case it will be "Sales Team". We will set the activation password operation for all users to specify, the activation password for all users will be "password", and the expiry time will be 40, denoting 40 hours before the password expires. Your text file should look similar to the following screenshot

3. Save the file as a normal .txt file, if created in a notepad.

4. Within the BlackBerry Administration Service, navigate to the BlackBerry solution management section.

5. Expand User and select Create a User, then select Import new users.

6. Browse to the text file we created previously and select Continue.

7. Once the import is finished, you will see the message stating the following users have been created and e-mailed the activation password we set in our CSV file, as shown in the previous screenshot of the CSV file.

8. In the CSV import file settings, we can—under Activation Password Operation—choose to type the following keywords, which would have alternative effects on the user activation method:
Generate: This would automatically generate and e-mail an activation password to the users
None: It will just create the user account

9. We can also check to ensure that the six users are added to the Sales group.

10. Click on Manage groups, select Sales Team, and then select View group membership.

Blackberry Enterprise Server Installation 5.0 for Exchange

Step-by-Step guide to install the Blackberry Enterprise Server for Microsoft Exchange



Verify you have completed the preinstallation tasks as per the Blackberry Enterprise Server Installation and Configuration Guide.

This installation process assumes that you want to install the Blackberry Configuration Database on a computer that is separate from the computer that is separate from the computer that hosts the Blackberry Enterprise Server.

This installation process installs all of the Blackberry Enterprise Server components on a single computer. In a production environment, you might choose to install some Blackberry Enterprise Server components on separate computers.


1. Log in to computer using a Windows account that has the proper permissions. This account runs the Blackberry Enterprise server services.
2. On the Blackberry Enterprise Server Installation media, double-click Setup.exe
3. In the Blackberry Enterprise Server Installation dialog box, click Continue Installation.
4. In the License agreement dialog box, perform the following actions:

In the User name field, type your user name
In the Organization field, type the name of your organization.
In the Country/Region drop-down list, click the name of your country or region.
In the License agreement section, read the license agreement
If you want to accept the license agreement, select I accept the terms in the license agreement.
5. Click Next
6. In the Setup type dialog box, select I would like the installation process to create a Blackberry Configuration Database.
7. Click Next
8. In the Setup options dialog box, in the Components section, select all of the check boxes for the Blackberry Enterprise Server components.
9. Click Next
10. In the Apache License dialog box, perform the following tasks:
Read the license agreement.
If you want to accept the license agreement, select I accept the terms in the license agreement.
11. Click Next
12. In the CPL license dialog box, perform the following tasks:
Read the license agreement
If you want to accept the license agreement, select I accept the terms in the license agreement.
13. Click Next

14. In the Preinstallation Checklist dialog box, read and verify the information. Click Next
15. In the Database options dialog box, select Use a Microsoft SQL Server database installed on another computer.
16. Click Next
17. In the Accounts and folders dialog box, perform the following actions:
In the Windows account information section, in the Password field, type the password for the windows account that you use to install the Blackberry Enterprise Server
In the Blackberry Enterprise Server section, in the Name field, type the name of the Blackberry Enterprise Server that you want the Blackberry Administration Service to display
18. Click Next
19. In the Summary dialog box, verify that the information is correct.
20. Click Install
21. Click Yes when the installation process requests that you restart the computer
22. After the computer restarts, log in to the computer using the windows account that you used in Step1
23. In the Database Information dialog box, perform the following actions:
In the Microsoft SQL Server name field, type the name of the database server that the Blackberry Enterprise Server can use
In the Blackberry configuration Database name field, type the name of the Blackberry Configuration Database.
24. Click Next
25. Click Yes when the installation process requests that you create a new database.
26. Click Ok when the installation process confirms that the database was created successfully.
27. In the Advanced database options dialog box, click Next to accept the default values.
28. In the CAL and SRP information dialog box, perform the following actions:
In the Key field, type the name of the Blackberry Client Access License key.
In the Host Name field, type the address for the Blackberry Infrastructure.
In the Port Number field, type the port number for the Blackberry Infrastructure.
To verify the connection to the Blackberry Infrastructure, click Verify
29. Click Next
30. In the Microsoft Exchange Server dialog box, perform the following actions:
In the Microsoft Exchange Server field, type the name of the Microsoft Exchange server.
In the Mailbox field, type the name of the administrator that has the appropriate permissions.
Click Check Name.
Click Apply.
Click Ok
31. In the Application extensibility settings dialog box, perform the following actions:
In the Pool name field, type an FQDN to create a Blackberry MDS Integration Service pool
In the Blackberry MDS Application Repository name field, type the name of the Blackberry MDS Integration Service Database.
Verify the default values for the port numbers.
In the Default administrator credentials field, in the Password and Confirm fields, type a password that you can use to manage and publish applications.
In the Default publisher credentials field, in the Password and Confirm fields, type a password that you can use to manage and publish applications.
32. Click Next
33. Click Yes when the installation process requests that you create a new database.
34. Click OK when the installation process confirms that the database was created successfully.
35. In the Monitoring service dialog box, if you want to use the same database server that the Blackberry Configuration Database uses, in the Database Name field, type the name of the Blackberry Monitoring Service database.
36. Click Next
37. Click Yes when the installation process requests that you create a new database.
38. Click OK when the installation process confirms that the database was created successfully.
39. In the instant messaging settings dialog box, perform the following actions:
In the Blackberry Collaboration Service drop-down list, click the name of the instant messaging system that you want to use.
In the Host field, type the host name of the instant messaging server.
In the port field, type the port number for the instant messaging server.
If applicable, select either HTTPS or HTTP
40. Click Next
41. In the Administration Settings dialog box, perform the following actions:
In the Pool Name field, type an FQDN that the setup application can use to create the Blackberrry Administration Service web address
In the New Password and Confirm password fields, type the password for the SSL certificate that the Blackberry Administration Service uses for authentication with browsers.
42. Click Next
43. In the LDAP settings dialog box, perform the following actions:
In the LDAP server URL field, type the URL of the LDAP server that host the Blackberry device users using the following format:
ldap://computer_name:port, where computer_name is the DNS name of the LDAP server and port is the port number that the LDAP server listens for connections on (by default, port 389)
In the LDAP search base field, type the distinguished name of the search base URL for the area of the directory tree that contains the Blackberry device users.
In the LDAP user name field, type the name of the administrator account that has permissions to log in to and search the LDAP server. You can type the name for the administrator account as the login name, also known as the name of security account manager (for example, besadmin)
In the LDAP password field, type the password for the administrator account that has permissions to login to search the LDAP server.
44. Click Next

45. In the Advanced administration settings dialog box, if you want to use Blackberry Administration Service authentication, perform the follwing actions:
  In the New password field, type a password for the Blackberry Administration Service administrator account.
In the Confirm password field, retype the password.
46. Click Next
47. In the Start Services dialog box, click Start Services.
48. Click Next. If you installed the Blackberry Administration Service, the setup application waits until the Blackberry Administration Service services are running before the setup application continues.
49. In the Console addresses dialog box, copy the web addresses for the Blackberry Enterprise Server components and paste them into a document for future reference. You can use the web addresses to log in to the Blackberry Enterprise Server components that you installed.
50. Click Close

Congratulations, you have completed this task!

How to change the Recipient Scope

What is a Recipient Scope ?

Recipient scope is the specified portion of Active Directory hierarchy that the Exchange Management Console (EMC) and the Exchange Management Shell uses for recipient management. When you set the recipient scope to a specific location within Active Directory, you can view and manage all recipients stored in that location, including all the containers under it.

The EMC and Shell always start with the recipient scope at the domain-level of the computer that is running the management interface. Neither the user account that's being used nor the Exchange servers being managed has bearing on the default value of the recipient scope.

How to change the Recipient Scope from EMC

In the console tree, click Recipient Configuration.
In the action pane, click Modify Recipient Scope.
In Recipient Scope dialog box, select one of the following options:
View all recipients in forest   Click this button to work with all recipients in the forest. To use a specific global catalog server, select the Global Catalogcheck box and then click Browse. In Select Global Catalog, select the global catalog server that you want to use. If you don't specify a global catalog server, Exchange automatically selects an available one. 

View all recipients in specified organizational unit   Click this button to work with all recipients in a specific organizational unit (OU) and all OUs under it. Click Browse, and then, in Select Organizational Unit, select the OU that you want to use.

To use a specific domain controller, select the Recipient Domain Controller check box. If you don't specify a recipient domain controller, Exchange automatically selects an available one.
Click OK.

How to change the Recipient Scope from EMS

Set-AdServerSettings -ViewEntireForest $true

If you would like to use a specific GC while using EMS, you add a parameter "PreferredGlobalCatalog"

Set-AdServerSettings -ViewEntireForest $true -PreferredGlobalCatalog NameoftheGC.Domain.com

Unable to save the host file

Default location for hosts file is "C:\Windows\System32\drivers\etc"

While working on the installation of Blackberry Enterprise Server on Windows Server 2008 R2, i have encountered an issue where i am unable to modify the hosts file on the server.

While troubleshooting found that there is a local administrator account on the system and with the same name another account exists on the domain.

After deleting the local administrator account which is the duplicate of the account which exists on the domain, the issue is solved.

Finally i am able to modify and save the content on hosts file.

How to determine if my Windows 7 is 32-bit or 64-bit

You can use one of the method mentioned below to determine whether your Windows 7 is 32-bit or 64-bit

Method 1

1. Right Click on "Computer"
2. Properties
3. A windows opens where it mentions 32 or 64 bit
4. If nothing is mentioned, most of the time it's a 32-bit version

Method 2

1. Click the Start button
2. Control Panel
3. System
4. Maintenance
5. System
6. Under system tab you can find the type of the system: 32 or 64 bit

Method 3

1. Go to C:\
2. The presence of this folder shows that it is a 64 bit system
3. C:\Program Files(x86)

Method 4

1. Open Command Prompt
2. Type the below command
wmic os get osarchitecture
3. It will return the output as below 
OSArchitecture
64-bit

Method 5

1. Open Command Prompt
2. Type the below command for a quick output
echo %Processor_Architecture%
3. It will return the output as below for 64-bit
AMD64

Method 6

1. Open Command Prompt
2. Type the below command
SystemInfo | "System Type"
3. It will return the output as below for 64-bit
System Type: x64-based PC

Blackberry Installation Errors

During installation of Blackberry Enterprise Server 5.0.3, I have encountered an error "Error Initializing System". This is a known issue in Blackberry Setup application.

When you run the setup application for the second time and the setup application cannot connect to the Blackberry Configuration Database, the setup application displays the "Error Initializing system" error message and does not permit you to change the Blackberry Configuration Database information.

In order to fix the problem, follow the below steps.

Click Start -> Run
Type Regedit
Perform one of the following actions

If you are running a 32-bit version of windows, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server.

If you are running a 64-bit version of Windows, navigate to 
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Research In Motion\BlackBerry Enterprise Server.

Remove the Database key.
Perform one of the following actions:

If you are running a 32-bit version of Windows, navigate to 
HKEY_CURRENT_USER\SOFTWARE\Research In Motion\BlackBerry Enterprise Server.

If you are running a 64-bit version of Windows, navigate to HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\Research In Motion\BlackBerry Enterprise Server.

Remove the Database key.
Restart the setup application.

How to get the individual user information from the Blackberry MAGT Log Folder

When you need to get the details of the user information from the MAGT log file, then you  can copy the log file in C:\ and open command prompt type the below command to get the output of the user blackberry messaging agent information from the MAGT which has all users information.

find /n /i "Firstname.lastname@domain.com" C:\BESServer_MAGT_04_20130109_0001.txt> C:/user.txt

Exchange Server 2013 Gotchas

Exchange Server 2013 reached RTM a couple of months ago and has since reached General Availability (GA).
In my personal opinion, Exchange 2013 RTM is not ready for prime time. Microsoft made a decision to release all of Wave 15 (Office desktop applications and servers) at the same time; as well as release Windows 8, Windows RT, and Windows Server 2012 at the same time. I think this decision was seriously flawed. It is obvious that the products were not complete at RTM (witness Windows 2012 and Windows 8 having 300 MB of patches between RTM and GA, and Exchange 2013 not supporting any interop with prior versions of Exchange at either RTM or GA). It is easy to conclude that the RTM dates were artificially imposed.
I have prepared a class on Exchange 2013 for one of my clients and part of that class was to discuss the limitations associated with Exchange 2013 RTM when compared to Exchange 2010 SP2. Note that the rest of the class discussed many of the new features and capabilities that have been added to Exchange 2013. So... the story is not all bad.
But as a summary of my opinion, Exchange 2013 RTM is not ready for prime time. Right now, it can only be installed in a green-field environment (that is, an environment where Exchange did not previously exist), so it is a safe bet that the Exchange team agrees with that as well. We can hope that some updates will quickly come out to address some of the current deficiencies.
This list is by no means exhaustive. And, as always, whether a particular issue is important to your organization requires you to evaluate your environment.

OWA

• Help -> About is gone
• It's very slow.
• No S/MIME support
• No Public Folder support, either for legacy public folders or modern public folders.
• No distribution list moderation
• No way to move the reading pane
• Built-in spell-check is gone. IE 10 provides spell-check natively, but earlier versions of IE do not. A third-party add-in or an alternate browser is required.
• Other things are gone; don't waste too much time looking for them.

Client Connectivity

• No BES support
• ...on a related note (and likely the primary reason BES is not yet available), the CDO/MAPI download is not yet available for Exchange 2013.
• Outlook 2003 is no longer supported.
• Direct MAPI access to the Exchange server is no longer supported. RPC/HTTP (Outlook Anywhere) is required.
• Outlook now reports that the server is it connected to is <<guid>>@<<active-directory-domain>>. This is intentional, if misguided.

Installation and Architecture

• Cannot uninstall individual roles from a server, must uninstall all of Exchange
• Install is painfully slow
• The Hub Transport role is gone. There is now a Front End Transport service on CAS servers and Mailbox Transport services on Mailbox servers.
• The Unified Messaging role is gone. There is a now a Unified Messaging Call Router service on CAS servers and a Unified Messaging service on Mailbox servers.
• The CAS consists of three pieces: CAFE' (Client Access Front End), which proxies all end-user protocols to the appropriate mailbox server (completing the decoupling of the MAPI endpoint started in Exchange 2010) and handles Outlook Web App; FET (Front End Transport) which proxies SMTP protocols to the mailbox server and is responsible for TLS setup; and Unified Messaging Call Router.
• After an installation or an upgrade, services not starting is an endemic problem. You will likely need to increase ServicesPipeTimeout on your Exchange servers.
• Documentation is minimal at best
• Deployment and sizing guidance is non-existent.
• Cannot be installed along with Exchange 2007 or Exchange 2010
• Exchange 2013 Edge server is not available
• Forefront Protection for Exchange is gone
• For both Exchange 2010 and Exchange 2013, applying updates can often screw up the winrm configuration. If you get errors in EMS or EAC regarding "The WS-Management service cannot process the request", try this first:
  
  winrm quickconfig
  iisreset
• Since you cannot interop with legacy public folders in RTM, if you need an Organizational Forms Library, you must create it yourself. To create an Organizational Forms Library:
  
  1. Create "Organizational Forms Library" folder under the Eforms Registry:
  
  New-publicfolder "Organizational Forms Library" -path "\non_ipm_subtree\Eforms Registry"
  
  2. Set the locale ID for the Org Forms Library:
  
  Set-PublicFolder "\non_ipm_subtree\Eforms Registry\Organizational Forms Library" -EformsLocaleID EN-US
  
  It is no longer necessary to set the PR_URL_NAME property.

Exchange Management

• The Exchange Management Console is gone as is the Exchange Control Panel. They are mainly replaced by the Exchange Administration Center (EAC); which is completely web based.
• If you are attempting to use EAC with IE 10, you need KB2761465 (released on December 11, 2012).
• The Exchange Best Practices analyzer is no more.
• The Exchange Mail Flow Troubleshooter is no more.
• The Exchange Performance Troubleshooter is no more.
• The Exchange Routing Log Viewer is no more.
• The EAC does not provide a preview (or an after-view for that matter) of the PowerShell it executed.
• Antispam and antimalware is crippled compared to earlier releases
  
  The E15 AV does not offer a quarantine
  The E15 AS does offer a quarantine (for the administrator, not per-user)
• Antispam cannot be managed from the Exchange Administration Center; it must be managed using PowerShell in the Exchange Management Shell
• Kerberos Constrained Delegation (KCD) is not supported for OWA
• This isn't new, but should be reinforced: DO NOT TURN OFF IPV6. Microsoft does not perform any testing to determine the effects of disabling IPv6. Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. See http://technet.microsoft.com/en-us/network/cc987595.aspx.
• System Center Data Protection Manager (DPM) version required for backups of Exchange 2013 is SC DPM 2012 SP1

Mailboxes and Databases

• Mailbox sizes MAY appear to increase substantially when moving a mailbox to an Exchange 2013 mailbox server. In Exchange 2010 and before, only select properties of a particular mailbox item were assigned as part of the mailboxes diskspace allocation, causing under-reporting. Now, all item properties for a particular mailbox item are assigned to the mailboxes disk space allocation. However, some items in Exchange 2013 are now compressed which were not before. This can lead to a reduction in reported and allocated diskspace. So, prediction is basically impossible. Just be aware that it may happen.
• Corrupt PropertyTags during a mailbox move are common. Using (Get-MoveRequestStatistics -IncludeReport <<alias-name>>).Report.Failures you can find the rule or message that is causing the problem and remove it.
• Changes made to improve Office 365 and hybrid deployments had an unintended consequence (this is my conclusion). When you are performing impersonation (e.g., to open a different user's mailbox via EWS), you should always impersonate using the email address.
• As a corollary, it is recommended that the account UPN match the primary email address.
• In a change that you won't know about until you need to know it - MRS Proxy is not enabled by default in Exchange 2013. Use Set-WebServicesVirtualDirectory to enable it.
• Clean-MailboxDatabase is gone
  
  Update-StoreMailboxState is designed to replace it
  Requires that you know the guid of the deleted mailbox
  No on-premises cmdlets allow you to find those out!
• Get-LogonStatistics is non-operational. The cmdlet is still present, but it doesn't work.
• Exchange 2013 Enterprise Edition supports only 50 mailbox databases instead of the 100 supported in Exchange 2010
• MRM 1.0 (Messaging Record Management - Managed Folders) is non-operational on Exchange 2013 mailbox servers. The cmdlets are still present, and will affect down-level servers (which you can't use right now), but they don't work with Exchange 2013 servers.
• Moving mailboxes using the migration wizard in EAC can generate large amounts of log files for the database which hosts the arbitration mailbox. Use New-MoveRequest instead.
• In a positive change, Office Filter Packs are no longer required. There is a new search technology used in all Wave 15 (Office 2013) products and it knows how to search all the Office file formats. This also includes the PDF format, so a separate iFilter installation for PDF is no longer required.
• When using Database Availability Groups (DAGs) on Windows Server 2012, you must manually create the Cluster Network Object (CNO) and provision the CNO by assigning permissions to it.
• While Windows Server 2012 provides support for large sectors (4 KB), Exchange 2013 does not support large sectors. Emulation of large sectors (512 E) is supported provided that all database copies are on 512 E.
• The above statement is, in general, true. Additional capabilities of Windows Server 2012 are not supported by Exchange Server 2013. This specifically includes but is not limited to Hyper-V Replica.

Exchange 2013 Guides

Using the Exchange Administration Center In this guide, you’ll become familiar with some of the organization management tasks you can perform by using the new Exchange Administration Center. 1. Deploying an Exchange Mailbox...

http://officeignitelabs.cloudguides.com/Exchange%20Labs.htm?goback=%2Egde_4151518_member_203363031

How to get the list of user accounts created from a certain date till the latest from a DC

 OS: Windows Server 2008 R2

      Login to Domain Controller which is Windows Server 2008 R2

    Open Powershell and import the module active directory

      Set the date variable as the start point from which you want to search till the latest

It will query for the users which are created after 1^st Jan 2013

Note: Date Time Format (Year, Month, Date)