Archive for the ‘2008 R2’ Category

Error Message: “Server Administrator is unable to launch using default Internet browser.”

August 19, 2014 1 comment
  • System Notes: Dell PowerEdge T310, Windows Server 2008 R2 Standard, Dell OpenManage Server Administrator 7.2.0

On a Dell PowerEdge T310 server, running Windows Server 2008 R2 Standard, when trying to start a local default installation of Dell OpenManage Server Administrator from a new account logon, we received an error message stating “Server Administrator is unable to launch using default Internet browser.”


OpenManage Error

It turns out that one of the administrator accounts had installed a secondary browser on the server for a specific purpose, then removed it.  This caused the program associations for Internet browsing to be incomplete.  To correct this, go into the Control Panel, go to Default Programs, then select Set your default programs.  Click on Internet Explorer from the Programs list and click on the Set this program as default option at the bottom of the window.  After that, Dell OpenManage Server Administrator should launch normally.

Additional Notes:
We only tried the above solution with Internet Explorer, but there is no reason it should not work with another browser.



Backup Exec 2010 R3 System Upgrade from Windows Server 2003 R2 to Windows Server 2008 R2

February 9, 2013 Leave a comment
  • System Notes: Backup Exec 2010 R3, Windows Server 2003 R2 Standard, Windows Server 2008 R2 Standard

Lately, I have been doing a lot of work upgrading older Windows servers from the 2003 R2 version (both 32 and 64 bit versions) to 2008 R2 (and soon probably 2012 once I get some more testing/learning time in with it).  One of the servers I had to upgrade was running Backup Exec 2010 R3, which was being used to backup other servers in a local domain to an internal RAID array.

The operating system upgrade was no problem, but moving Backup Exec and all of its data was going to be more complicated.  I primarily followed this Symantec Support article (TECH129826), while also referring to this (TECH67768).  The second article is much more comprehensive, but comes with the caveat that it is really only for moving Backup Exec between servers using the same operating system versions.

All data moved over correctly, and as far as Backup Exec was concerned, there were no differences between the two servers, from a job and history perspective.  The only problem I ran into was that I had to create a new temporary backup job and connect to each one of the remote servers that were being backed up by the existing backup jobs (via a Backup Exec Remote Agent).  This prompted Backup Exec to ask if I wanted to add each remote server to the “trusted favorites list,” which I did.  Before I figured out I needed to do this, my backup jobs were failing with authentication errors.

Additional Notes:

I was reusing the same hardware for my upgrade, and did not have to change the paths of the Backup-To-Disk folders that Backup Exec was using.  This simplified things greatly.  If you are using Backup-To-Disk folders with disk locations that are going to change, keep in mind that you will have to re-add each of them to the Backup Exec configuration, then also do a scan and an inventory on each as well before they can be used.

Windows Server 2008 R2 Active Directory Schema Update

September 15, 2012 Leave a comment
  • System Notes: Various Domain Controller Hardware, Windows Server 2008 R2 Standard

Recently, I have completed several Active Directory domain upgrades for various organizations.  Everyone seems to finally be moving away from Windows Server 2003 and to Windows Server 2008 R2.  For reference purposes, or for those who are curious, below are sample outputs from one of the upgrades, for the various schema upgrade commands.  This is the main online article I referenced for these routines.

  1. adprep /forestprep
  2. adprep /rodcprep
  3. adprep /domainprep

Additional Notes:

The example Active Directory schema update was for a domain running the Windows Server 2003 R2 schema extensions.  The adprep /rodcprep is not strictly required, but I generally do it regardless of whether or not the client is currently using Read-Only Domain Controllers, as those will then be a future option with no additional Active Directory preparation required.