Blackberry KB03112: BES 5.0: How to move the BlackBerry Configuration Database to a new Microsoft SQL Server instance

Last modified: 05-05-2015
Environment
  • BlackBerry Enterprise Server 2.1 to 5.0 SP4
  • BlackBerry Enterprise Server for Office 365
  • Microsoft SQL Server 2000 SP3 to 2012
  • Microsoft SQL Server Desktop Engine (MSDE)
Overview

Confirm that the Database version is compatible with the Microsoft SQL Server version before moving the BlackBerry Configuration Database to a new Microsoft SQL Server instance. Refer to compatibility matrix at:

BlackBerry Enterprise Server Compatibility Matrix

The BlackBerry Enterprise Server services must be stopped during the process described in this article.

Note: In a Microsoft Exchange environment, complete the tasks using the BlackBerry Enterprise Server service account unless otherwise stated.

Complete the following tasks to move the BlackBerry Configuration Database to a new Microsoft SQL Server instance:

Task 1: Prepare the new Microsoft SQL Server
Task 2: Back up the BlackBerry Configuration Database
Task 3: Restore the BlackBerry Configuration Database
Task 4: Configure the BlackBerry Enterprise Server

Task 1 - Prepare the new Microsoft SQL Server

Note: Complete this task using an account with administrator access to the new Microsoft SQL Server. Microsoft SQL Server 2005 or 2008 requires the following server role permissions:
System Administrator, Database Creator.

Step 1: Assign the appropriate permissions based on the applicable environment

Microsoft SQL Server 2000 to 2012

  1. Open Enterprise Manager (Microsoft SQL Server 2000) or Microsoft SQL Server Management Studio (Microsoft SQL Server 2005 to 2012).
  2. Go to Microsoft Server Group > <SQL_Server_name> > Security.
  3. Right-click Logins and select New Login.
  4. From the General tab, click the double quotation marks ( "" ) button.
  5. From the Global Address List, select the name of the BlackBerry Enterprise Server service account.
  6. Click Add, then click OK.
  7. On the Server Roles tab, select Server Administrators and Database Creators.
    Note: In BlackBerry Enterprise Server 4.1, the System Administrator role is needed for role-based administration.
  8. Close Enterprise Manager (Microsoft SQL Server 2000) or Microsoft SQL Server Management Studio (Microsoft SQL Server 2005 to 2012).

Microsoft SQL Server Desktop Engine (MSDE)

  1. Log in to the new Microsoft SQL Server.
  2. Right-click My Computer, and click Manage.
  3. Expand Local Users and Groups.
  4. Select Groups and then click the Administrators group.
  5. Click Add.
  6. Type the name of the BlackBerry Enterprise Server service account and then click Check Name.
  7. Click OK.
  8. Close the Computer Management window.
  • Step 2: Turn on the correct server protocols based on the applicable environment

Microsoft SQL Server 2008 to 2012 Express or Microsoft SQL Server2008 to 2012

  1. Click Start > Microsoft SQL Server 20xx > Configuration Tools > SQL Server Configuration Manager.
  2. Expand SQL Server Network Configuration.
  3. Select the Microsoft SQL Server instance that will be used for the BlackBerry Configuration Database.
  4. If necessary, turn on the TCP/IP and Named Pipes protocols.
  5. If a protocol is turned on in the previous step, restart the Microsoft SQL Server services.

Microsoft SQL Server 2005 Express or Microsoft SQL Server 2005

  1. Click Start > Microsoft SQL Server 2005 > Configuration Tools > Microsoft Server Configuration Manager > Microsoft Server 2005 Network Configuration.
  2. Select the Microsoft SQL Server instance that will be used for the BlackBerry Configuration Database.
  3. If necessary, turn on the TCP/IP and Named Pipes protocols.
  4. If a protocol is turned on in the previous step, restart the Microsoft SQL Server services.

Microsoft SQL Server Desktop Engine (MSDE) or Microsoft SQL Server 2000

  1. Click Start > Run.
  2. Type svrnetcn.
  3. Click OK. The Microsoft Server Network Configuration Utility opens.
  4. Make sure that TCP/IP and Named Pipes are both listed as protocols that have been turned on.
  5. Close the Microsoft Server Network Configuration Utility.
  6. If a protocol is turned on in step 2, restart the Microsoft SQL services.

Step 3: Make sure that the SQL Server Agent service is running

Note: This step only applies to BlackBerry Enterprise Server  4.1.7 and earlier. BlackBerry Enterprise Server 5.0 and later no longer relies on the SQL Server Agent service for maintenance procedures.

Note: The SQL Server Agent service is not available for Microsoft SQL Server Express editions. If running Microsoft SQL Server 2005 Express or Microsoft SQL Server 2008 Express, see KB14017.

  1. Open the Windows Control Panel, then open Administrative Tools > Services.
  2. Make sure that the SQL Server Agent service is started for the instance and that the Startup type is set to Automatic.
  3. Close the Services window.

Step 4: Update the BlackBerry Configuration Database schema

Important: If the BlackBerry Enterprise Server software was installed to create a blank BlackBerry Configuration Database on a new Microsoft SQL Server instance, do not perform the following steps, because the schema has already been updated.

Note: If you are running BlackBerry Enterprise Server 5.0, CreateDB.exe is recommended, but not necessary to run prior to restoring the database backup.

  1. Download the installation package for the version of the BlackBerry Enterprise Server that is being used.
  2. Extract the contents of the installation package.
  3. Copy the Database folder to the new Microsoft SQL Server.
    Note: The default location of this folder is C:\Research In Motion\BlackBerry Enterprise Server 4.x.x\Database
  4. Go to the Database folder and open the BESMgmt.cfg file in a text editor, such as Notepad.
  5. Locate the DB_NAME=BESMgmt or (DATABASE_NAME=BESMgmt) line depending on the version of the upgrade and then make sure that the name specified matches the BlackBerry Configuration Database name.
  6. If using a named instance of Microsoft SQL Server, change the SERVER=local line to SERVER=<SQL_Server_Name>\< instance_name>.
  7. Close the file, and Save the changes.
  8. From a command prompt, navigate to the Database directory.
  9. Type createdb.exe BESMgmt.cfg and press Enter.
  10. After the command has finished executing, close the command prompt.

Task 2 - Back up the BlackBerry Configuration Database

Note: When backing up the BlackBerry Configuration Database, complete the steps based on the applicable environment.

Microsoft SQL Server 2000 to 2012

  1. Open Enterprise Manager (Microsoft SQL Server 2000) or Microsoft SQL Server Management Studio (Microsoft SQL Server 2005 or 2008).
  2. Right-click the BlackBerry Configuration Database (for example, BESMgmt).
  3. Select Backup Database.
  4. Click Add to specify the Directory Name and File Name.
  5. Click OK to accept the settings.
  6. Click OK again to start the backup process.
  7. Close Enterprise Manager (Microsoft SQL Server 2000) or Microsoft SQL Server Management Studio (Microsoft SQL Server 2005 or 2008) when the process is complete.

Microsoft SQL Server Desktop Engine (MSDE)

  1. From a command prompt, type osql -E and press Enter.
    Note: If logging in to a named instance of the Microsoft SQL Server, use the following command syntax to log in: osql -E -S <SQL_Server_name>\<instance_name>
  2. Type the following commands in the specified order:
    1. backup database <BlackBerry_Configuration_Database_name> to disk = 'C:\<BlackBerry_Configuration_Database_name>.bak'
    2. go
    3. quit
  3. Close the command prompt.

Task 3 - Restore the BlackBerry Configuration Database

There are two methods available to restore the BlackBerry Configuration Database and each are dependent upon the applicable environment:

  • Restore the BlackBerry Configuration Database from a backup
  • Detaching and re-attaching the BlackBerry Configuration Database files.

Restore database method for Microsoft SQL Server 2000 to 2012

  1. Open Enterprise Manager (Microsoft SQL Server 2000) or Microsoft SQL Server Management Studio (Microsoft SQL Server 2005 to 2012).
  2. Right-click the Databases (for example, BESMgmt).
  3. Select Tasks>Restore Database.
  4. Click From Device and browse for the .bak file.
  5. Select Options and ensure Overwrite the existing database is selected.
  6. Click OK to accept the selection.
  7. Close Enterprise Manager (Microsoft SQL Server 2000) or Microsoft SQL Server Management Studio (Microsoft SQL Server 2005 to 2012) when the process is complete.

Detach and re-attach database method for Microsoft SQL Server 2000 to 2012

  1. Open the Control Panel, and open Administrative Tools > Services.
  2. Stop each service that has a name that begins with BlackBerry.
  3. Log in to the existing Microsoft SQL Server.
  4. Open Enterprise Manager (Microsoft SQL Server 2000) or Microsoft SQL Server Management Studio (Microsoft SQL Server 2005 to 2012).
  5. Right-click the BlackBerry Configuration Database name.
  6. Select All Tasks, and click Detach Database for Microsoft SQL Server 2000 or for Microsoft SQL Server 2005 or 2008, select Tasks and click Detach.
  7. Close Enterprise Manager (Microsoft SQL Server 2000) or Microsoft SQL Server Management Studio (Microsoft SQL Server 2005 to 2012).
  8. Go to the Microsoft SQL Server Data directory and copy the MDF and LDF files.
    Note: The default path is C:\Program Files\Microsoft SQL Server\MSSQL\Data\ and the default filenames are BESMgmt.mdf and BESMgmt.ldf.
  9. Log in to the new Microsoft SQL Server.
  10. Open Enterprise Manager (Microsoft SQL Server 2000) or Microsoft SQL Server Management Studio (Microsoft SQL Server 2005 to 2012).
  11. Right-click the BlackBerry Configuration Database name.
  12. Select All Tasks, then click Detach Database for Microsoft SQL Server 2000 or for Microsoft SQL Server 2005 select Tasks and click Detach.
  13. Move the files that were copied in step 8 to the Microsoft SQL Server Data directory.
  14. When prompted to overwrite the files, click Yes.
  15. In Enterprise Manager (Microsoft SQL Server 2000) or Microsoft SQL Server Management Studio (Microsoft SQL Server 2005 or 2008), right-click the Database folder, then click All Tasks.
  16. Select Attach Database for Microsoft SQL Server 2000 or for Microsoft SQL 2005 to 2012 right-click the Database folder and select Attach.
  17. Select the MDF file to attach, then click OK.
  18. Close Enterprise Manager (Microsoft SQL Server 2000) or Microsoft SQL Server Management Studio (Microsoft SQL Server 2005 to 2012).

Restore database method for Microsoft SQL Server Desktop Engine on a Microsoft SQL Server having the same directory structure

  1. Copy the BlackBerry Configuration Database backup to the C:\ path of the new Microsoft SQL Server.
  2. From a command prompt, type osql -E and press Enter.
    Note: When logging in to a named instance of the Microsoft SQL Server, use the following command: osql -E -S <SQL_Server_name>\<instance_name>
  3. Type the following commands in the specified order:
    1. restore database <BlackBerry_Configuration_Database_name> from disk = 'c:\<BlackBerry_Configuration_Database_name>.bak' with recovery, replace
    2. go
    3. quit
  4. Close the command prompt.

Restore database method for Microsoft SQL Server Desktop Engine on a Microsoft SQL Server having a different directory structure

  1. Copy the BlackBerry Configuration Database backup to the C:\ path of the new Microsoft SQL Server.
  2. From a command prompt, type osql -E and press Enter.
    Note: When logging in to a named instance of the Microsoft SQL Server, use the following command: osql -E -S <SQL_Server_name>\<instance_name>
  3. Type the following commands in the specified order:
    1. restore database <BlackBerry_Configuration_Database_name> from disk =
      "C:\<BlackBerry_Configuration_Database_name>.bak" with move
      "<BlackBerry_Configuration_Database_name>_data" to
      "<new_path>\MSSQL\Data\<BlackBerry_Configuration_Database_name>.mdf", move
      "<BlackBerry_Configuration_Database_name>_log" to "<new_path>\MSSQL\Data\<BlackBerry_Configuration_Database_name>.ldf"Note: To determine the logical file names <BlackBerry_Configuration_Database_name>_data and <BlackBerry_Configuration_Database_name>_log for the BlackBerry Configuration Database, complete the following steps:

      1. On the Microsoft SQL Server hosting the BlackBerry Configuration Database, open a command prompt and type the following command:
        OSQL -E or OSQL -E -S <SQL_Server_name>\<instance_name>
      2. Type the following commands in the specified order, pressing Enter after each command:
        exec sp_helpdb <BlackBerry_Configuration_Database_Name>
        go
        The two logical file names for the BlackBerry Configuration Database are BESMgmt_data and BESMgmt_log.
      3. Close the command prompt.
    2. go
    3. quit
  4. Close the command prompt.

Detach and re-attach database method for Microsoft SQL Server Desktop Engine

  1. Open the Control Panel, and open Administrative Tools > Services.
  2. Stop each service that has a name that begins with BlackBerry.
  3. Log in to the existing MSDE Server.
  4. From a command prompt, type osql -E and press Enter.
    Note: When logging in to a named instance of the Microsoft SQL Server, use the following command: osql -E -S <SQL_Server_name>\<instance_name>
  5. Type the following commands in the specified order:
    1. exec sp_detach_db @dbname = "<BlackBerry_Configuration_Database_name>"
    2. go
    3. quit
  6. Go to the Microsoft SQL Server Data directory and copy the MDF and LDF files.
    Note: The default path is C:\Program Files\Microsoft SQL Server\MSSQL\Data\ and the default filenames are BESMgmt.mdf and BESMgmt.ldf.
  7. Move the files that were copied in step 6 to the new Microsoft SQL Server.
  8. Log in to the new MSDE Server.
  9. From a command prompt, type osql -E and press Enter.
    Note: When logging in to a named instance of Microsoft SQL Server, use the following command: osql -E -S <SQL_Server_name>\<instance_name>
  10. Type the following commands in the specified order:
    1. exec sp_detach_db @dbname = "<BlackBerry_Configuration_Database_name>"
    2. go
    3. quit
  11. Move the files that were copied in step 6 to the Microsoft SQL Server Data directory. When prompted to overwrite the files, click Yes.
  12. From a command prompt, type osql -E and press Enter.
    Note: If logging in to a named instance of Microsoft SQL Server, use the following command syntax to log in: osql -E -S <SQL_Server_name>\<instance_name>
  13. Type the following commands in the specified order:
    1. exec sp_attach_db @dbname = "<BlackBerry_Configuration_Database_name>"
    2. @filename1 = "C:\Program Files\Microsoft SQL Server\MSSQL\Data\<BlackBerry_Configuration_Database_name>.mdf",
    3. @filename2 = "C:\Program Files\Microsoft SQL Server\MSSQL\Data\<BlackBerry_Configuration_Database_name>.ldf"
    4. go
    5. quit
  14. Close the command prompt.

Task 4 - Configure the BlackBerry Enterprise Server

To configure the BlackBerry Enterprise Server to connect to the new BlackBerry Configuration Database, complete the following steps:

For BlackBerry Enterprise Server for Office 365

Note: BlackBerry Enterprise Server for Office 365 does not have a change database option like previous versions.

  1. Manually update the BESMgmt database with the new SQL instance name by running the following Transact-SQL command against the BESMgmt database:
    UPDATE DatabaseServer SET Name = 'SQLServer\SQLInstance'
    Where SQLServer\SQLInstance is the SQL server and SQL instance information for the new destination SQL server.
  2. Then continue with following KB18129 that explains the configuration and connect process for BlackBerry Enterprise Server 5.0.

For BlackBerry Enterprise Server 5.0

BlackBerry Enterprise Server 5.0 does not have a change database option like previous versions. KB18129 explains the configuration and connect process for BlackBerry Enterprise Server 5.0.

For BlackBerry Enterprise Server 4.0 to 4.1

  1. On the BlackBerry Enterprise Server, click Start > Programs > BlackBerry Enterprise Server > BlackBerry Server Configuration.
  2. On the Database Connectivity tab, click Change Database.
  3. In the Change Database Wizard, specify the new Microsoft SQL Server name and the existing BlackBerry Configuration Database name.
  4. Complete the wizard. Make sure that the Start Services check box is selected and click Finish.
  5. Open Administrative Tools > Services and make sure that all of the BlackBerry Enterprise Server services started successfully.
    Note: The BlackBerry Database Consistency Service might be unavailable, this is normal.
  6. Open BlackBerry Manager and make sure that the correct database is set up by completing the following:
    1. For BlackBerry Enterprise Server 4.0
      1. Right-click BlackBerry Manager, and click Properties.
      2. Select the Properties tab and verify that the Microsoft SQL Server information and BlackBerry Configuration Database name are correct.
    2. For BlackBerry Enterprise Server 4.1
      1. Go to Tools > Options > Database and verify that the Microsoft SQL Server information and BlackBerry Configuration Database name are correct.
      2. Verify that all of the BlackBerry smartphone user accounts appear on BlackBerry Manager.
      3. If there is a remote BlackBerry Manager, make sure to check the settings from step 6.
      4. Test email message flow from the BlackBerry smartphone.
      5. For BlackBerry Enterprise Server 4.1, install the database notification system.
        Note: This is only required in smaller environments running a maximum of 3 BlackBerry Enterprise Server instances.
      6. Copy the RimEsp.dll file to the C:\Program Files\Microsoft SQL Server\MSSQL\Binn folder on the new Microsoft SQL Server.
      7. In Microsoft Query Analyzer, go to the Database\DBInstallScripts\SQLServer\4.1 folder on the installation media.
      8. Open the NotifyInstall.sql file and replace <_databasename> with the name of the BlackBerry Configuration Database.
      9. Run the script.
  7. Verify that the Microsoft Query Analyzer displays the following message:  Function dbo.xp_RIM_xxxx registered
Additional Information

When moving from a Microsoft SQL Server Desktop Engine (MSDE) server instance to a full Microsoft SQL Server instance on a separate computer, see KB04039 for information on how to increase the mail agent limitation on the BlackBerry Enterprise Server.

If receiving an error that the BlackBerry Configuration Database is in use, complete the following steps:

  1. Remove all the BlackBerry smartphone user accounts from the BlackBerry Configuration Database by typing the following commands at a command prompt:
    1. OSQL -E
    2. use master
    3. alter database <BlackBerry_Configuration_Database_name> set single_user with rollback immediate
    4. go
    5. use <BlackBerry_Configuration_Database_name>
    6. go
    7. exit
  2. Detach the BlackBerry Configuration Database by typing the following commands at a command prompt:
    1. OSQL -E
    2. use master
    3. sp_detach_db @dbname = <BlackBerry_Configuration_Database_name>
    4. go
    5. exit
  3. Attach the BlackBerry Configuration Database by typing the following commands at a command prompt:
    1. OSQL -E
    2. use master
    3. exec sp_attach_db @dbname = "<BlackBerry_Configuration_Database_name>",
    4. @filename1 = "C:\<Path_to_database_file>\<BlackBerry_Configuration_Database_name>.mdf",
    5. @filename2 = "C:\<Path_to_transaction_log_file>\<BlackBerry_Configuration_Database_name>.ldf"
    6. go
    7. exit
      Note: The default path is C:\Program Files\Microsoft SQL Server\MSSQL\Data and the default filenames are BESMgmt.mdf and BESMgmt.ldf.

Windows Updates to avoid: Adware to promote Windows 10: KB3035583

On Windows 7 SP1 and Windows 8.1, you might recently have got the update KB3035583. It installs folders and functions to promote the launch of Windows 10 and of course, it calls home to do that.

See more details in this article.

Luckily, you can un-install this update, or, if you have not installed it already, hide it in the "recommended updates" screen.

If you are on Windows 7 and don't plan to upgrade to Windows 8.1 or Windows 10 you can also uninstall:

KB2952664
KB2990214
KB3068708

Windows: Schannel error 40 and Internet Explorer

When I needed to access a secure page (HTTPS) from Internet Explorer 11 on a Windows 2008 R2 server, I always got a "Page cannot be displayed" error. I could, though, access that page from another machine or another browser on the same server.

Looking in the Event Viewer I saw:

Log Name: System
Source: Schannel
Date: 05.01.2015 12:11:58
Event ID: 36887
Task Category: None
Level: Error
Keywords:
User: SYSTEM

Description:
The following fatal alert was received: 40.

Schannel error 40 means: SSL3_ALERT_HANDSHAKE_FAILURE

So I checked with SSL Labs which Ciphers my browser offers:

https://www.ssllabs.com/ssltest/viewMyClient.html

It looks like it was offering very old ciphers first

TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_RC4_128_SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
...

I checked the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Cryptography\Configuration\Local\SSL\00010002

It contained exactly the same old ciphers first!

So I looked at a Windows 7 client that was working and saw that there were the newer and more secure ciphers listed first:

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521
...

I copied the Registry entry of the working machine to the server, rebooted the server and - Bingo - I could now access the web page.

ESXi 5.5: How to install an update via SSH

Download the current update (i.e. ESXi 5.5 Update 2) from MyVMWare. For HP Servers, download the special HP Version. Download the .zip file, not the .iso file.

Copy the .zip file to the datastore via vSphere client.

Login to ESX via SSH

Run the command

esxcli software vib update -d "/vmfs/volumes/datastore1/Install/VMWare-ESXi-
5.5-U2-HP/VMware-ESXi-5.5.0-Update2-2068190-HP-5.77.3-Nov2014-depot.zip"

Reboot VMWare ESXi

Apple iOS8: How to download iOS updates manually

If you need to download the Apple iOS manually, do the following. Go to:

http://www.ipswdownloader.com

Choose the hardware model (e.g. iPad4 (GSM)

Then download the .ipsw file (this can be 2GB in size or more).

Place this file in the following directory (that's for Windows 7):

C:\Users\UserName\AppData\Roaming\Apple Computer\iTunes\iPad Software Updates

When you connect your iOS device to your computer and start iTunes, you can directly load the update.

Apple iOS 8: How to factory reset a locked iPad or iPhone

If you forget your device passcode or PIN, there is no way to get into it again. You have to do a factory reset of the device. For that, you need iTunes and a USB cable to connect your device to your PC.

Find below the steps to recover your handheld:

Important: These steps will wipe (delete) all your data and settings from your device.

  1. Remove all cables from your device.
  2. Switch your device off by holding the Standby button and swiping to the right.
  3. Hold the home button and connect your handheld to a running iTunes. Keep holding the home button until the "Connect to iTunes" logo appears on the device.
  4. In iTunes, click "Restore".
  5. In iTunes, click "Restore and Update".
  6. If you are shown an iOS Update screen, click "Next".
  7. On the License Agreement, click "Agree".
  8. iTunes now downloads the latest iOS software and puts your device in "Recovery Mode".
  9. The update and factory reset can take up to an hour.

Windows Active Directory: How to move the FSMO Roles via the GUI

All 5 FSMO roles of Active Directory can be moved via script, but lets see how it works via GUI (MMC):

RID Master, Infrastructure Master, and PDC Emulator

  1. Login to the target DC via RDP
  2. Open "AD Users and Computers"
  3. Right-click the Domain and choose "Operations Masters..."
  4. Choose the appropriate tab
  5. Click "Change..."
  6. Click "Yes" to confirm

Schema Master

Make sure you are member of the "Schema Admins" group. Being in the "Enterprise Admins" group is not enough!

  1. Login to the source DC via RDP
  2. Open "AD Schema"
  3. Right-click "Active Directory Schema" and choose "Change Active Directory Domain Controller"
  4. Choose the target DC
  5. Right-click "Active Directory Schema" and choose "Operations Masters..."
  6. Click "Change..."
  7. Click "Yes" to confirm

Domain Naming Master

  1. Login to target DC via RDP
  2. Open "AD Domains and Trusts"
  3. Right-click "Active Directory Domains and Trusts" and choose "Change Active Directory Domain Controller"
  4. Choose the target DC
  5. Right-click "Active Directory Schema" and choose "Operations Masters..."
  6. Click "Change..."
  7. Click "Yes" to confirm

Windows Active Directory: Who holds the FSMO Roles?

The easiest way to find out which Active Directory Domain Controller holds the FSMO roles is the following:

  • Open a CMD box
  • Type netdom query fsmo
  • The output is something like

    C:\Windows\system32>netdom query fsmo

    Schema master               DC1.ad-domain.local
    Domain naming master      DC1.ad-domain.local
    PDC                         DC1.ad-domain.local
    RID pool manager            DC1.ad-domain.local
    Infrastructure master       DC1.ad-domain.local

    The command completed successfully.

Windows: How to elevate the Command Prompt to System Rights

Have you ever tried to configure something on a windows system as Administrator and still got a permission denied?

While the Administrator is powerful, he still can't do everything. There is an account that is even more powerful, it is called SYSTEM. So how could you run something as SYSTEM? Here is how:

  • Start a command prompt as Administrator
  • From Sysinternals, download psexec.exe and put it on the C: drive
  • In the command prompt, navigate to the directory with psexec.exe
  • Run "psexec.exe -i -s cmd.exe" (without the quotes)
  • Now a second command prompt opens with SYSTEM privileges
  • Type "whoami" to confirm that you are SYSTEM

Be careful as with these rights, you can easily destroy a system.

HP ILO: Configure it via ESX

When you can't access HP ILO via Web Console anymore (e.g. because you have configured the IP address wrongly or enabled DHCP by accident), there is a possibility to configure the ILO IP settings via ESX.

Login to the ESX vSphere Client

Make sure that SSH is running on ESX (ESX host > Configuration > Security Profile > Services > Properties, Start SSH if it is not started)

Download Putty on the Windows machine where the vSphere Client runs. Start Putty.exe and use the IP address of the ESX host to login.

After you have entered the user name (root), it takes a while for the password prompt to be shown. Wait and then enter the password.

cd /opt/hp/tools

Export the current config: ./hponcfg -w /tmp/ilo_config.txt

Now, copy this file to the Windows machine (for example with WinSCP).

Open it with WordPad and change the following lines:

<IP_ADDRESS VALUE = “10.10.10.20″/>
<SUBNET_MASK VALUE = “255.255.255.0″/>
<GATEWAY_IP_ADDRESS VALUE = “10.10.10.1″/>
<DHCP_ENABLE VALUE = “N”/>

Copy it back to the ESX host (overwrite existing file)

./hponcfg -f /tmp/ilo_config.txt

Let the ILO restart.

You should now be able to login to ILO via the Web Console.