Event ID: 8003 Master Browser derp

short synopsis: disable the Computer Browser service on the offending PC.

“Event Type: Error
Event Source: MRxSmb
Event ID: 8003
Event Category: None
Description:
The master browser has received a server announcement from the computer XXX that believes that it is the master browser for the domain on transport NetBT_Tcpip_XXX-. The master browser is stopping or an election is being forced.“

This is simply a network configuration error and nothing more, so don't panic.  It's actually a fairly common error when you've got networked computers.  Frankly, I wouldn't consider it an error as an error states something is broke.  Think of this as an argument between children,  "This other computer thinks it's the Master browser, but I want to be!"

What's going on is Windows networking services, specifically MRxSmb, is having a difficult time trying to decide which computer should maintain this master browser list.  This browser list service provides a list of computer sharing resources in and on the domain.  Think of it as a list provided to workstations that can view network resources within your network neighborhood.

The first thing you need to take into consideration is: Is this a dedicated server on the network or are you running another machine with a Domain Controller?

Let's say it's a dedicated server on the network, then go to the machine specified in the event viewer text that is believing it is the Master Browser for the domain.
go into control panel->administrative tools->services then click on the Computer Browser option, click stop.

(what is? Computer Browser service - http://support.microsoft.com/kb/188001)

Also, double-check the registry settings by making sure the IsDomainMaster to False at:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters\IsDomainMaster

 If you're running a Domain Controller, which you should ideally use as the "master browser", go to each of your workstations and disable the Computer Browser service. In addition, to ensure you've told your workstations not to search for a master browser, you can run a command line utility: BROWSTAT STATUS.  This tells you whether browsing is active, how many servers are on the domain, and what their names are.

This will resolve your issue.  However, as a disclaimer, only make registry edits if you are completely sure of what you are doing.  Also, after you make these changes, it is always in your best interest to reboot the machine.  If you are still having issues, you've either done something wrong, else your computers are not on the same subnet.

Understanding CALs

CALs, or Client Access Licenses, are often a confusing matter.  I've been working with them ever since I got started in IT, however, not until recently have I had a full understanding of when and where you'd use a CAL.  Not to mention, there are different types of CALs which add to the confusion.

Let me break down a few things for you:
-What's a CAL
-What CAL do I use?
-When not to use a CAL.

CAL,  a client access license. 
When you buy or manage a Windows server, it'll be licensed to end users or to businesses.  The CAL gives you rights to connect to a server, or server application. Most editions of server or a specific service, come with some CALs already.  This allows the software to be used by either a few users or a few computers.  The more users/computer, the more CALs required.  Think of it this way, one CAL per concurrent connection.

There are two types of CALs; a device and a user. 
User CALs allow one user to connect to a server or service.  Any user can connect, however, only one user may utilize the CAL at any given time.  Let's say you have SQL Enterprise 2k8 w/ a 5 CAL, then 5 users can utilize that service at the same time.

Device CALs allows one device to connect to the server or service.  Connections are limited by device, rather than user.  So if you have a lot of users and a small amount of devices, utilizing CALs for each of those devices is more cost-effective.

Core CALs, are special CALs offered by Microsoft via corporate licensing.  Core CALs include CALs for Microsoft Windows Server, Exchange, Systems Management Server, and Sharepoint.  Think of it as a suite of CAL offerings to license basic server components across your computers.  Less overhead equals less management of your CALs.  So if you're going to utilize many Microsoft services, look into Core CAL licensing.

Lastly, when don't you need a CAL?  When your users access the server anonymously or when they require privacy via authentication.  You do not need to add CALs for users who are authenticating.  If you are gearing your server or services for customers and not internal-employees, you'll want to utilize an External Connector.  An EC allows an unlimited number of outside users to access a server or service.  However, EC's should only be considered when you have a large customer-base because they are rather expensive.  If you have a smaller external user-base, CALs are a much more cost-effective solution.

SQL 2k8 R2 upgrade head scratch

Performing an upgrade for any service or application should be an easy task, right?  Well in the instance of SQL server upgrades, sometimes it isn't.  The process hasn't been as concise as I'd like, however, here are two issues I've frequently run across and their quick fixes.

1)  Cannot install SQL Server 2k8 upgrade due to SQL 2k5 Express tools still existing.  

But I don't even have 2k5 express tools installed?  Talk about a head scratcher...

Two quick work arounds:

-Remove the registry key at: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90

 else, you can simply rename this key/export the key to a different registry folder.  I would suggest rename it something to the sorts of "old" or "previous".

If you are still receiving the SQL 2k5 Express Tools is installed prompt as I was:

-Do you have RedGate backup installed?  

If so, uninstall SQL Search 1 as this RedGate application seems to have an instance of the express tools installed.

2) Reporting Services:  Check whether report server is correctly configured, the database server is running and you have permissions to access the database.

If during the install it will not let you proceed because reporting services is not configured you will have to run:

  -All Programs > Microsoft SQL 2008> Configuration Tools > Reporting Services Configuration Manager

After connecting to the server go through the list on the left as follows:

Service Account – Use Built-in Account and Local System. Click apply if it is highlighted or go on to the next on, if not.

Web Service URL – Just click the Apply button if it is highlighted.  Skip to the next if its not.

Database – If the fields are populated below and the Apply button is grey'd out, you can skip and go on to the next setting. If not, you will have to select Change Database> Choose existing > Select the ReportServer database. If it does not exist, then Select Create new report server database and accept default until done.

Report Manager URL - Just click the Apply button if it is highlighted.  Skip to the next if its not.

All remaining options can be skipped. When done just Exit.

If you cannot get passed the connection screen using Windows Integrated security, change to SQL Authentication with

User: "user"

Pass:"password"

Should be able to proceed at this point and complete the upgrade.

These seem to be the most common errors and annoyances you'll encounter when upgrading SQL Server 2k8 R2.  With a little patience and logic, hopefully you've resolved any head scratching issue you may have stumbled upon during this process.