Unique OrgName != Friendly Org Name = Trouble

I was helping with a problem where they were getting a 401 on plug-ins that were running fine on other systems.  Turns out there's a bug where if your Friendly org name is not equal the Unique Org Name you will get a 401 error.

This occurs when you use the CreateCrmService to retrieve an instance of the CRMService  from the plug-in context.  Internally when the CRM server sets up the service object instance the friendly name is used in stead of the uniquename.  If those are different you will get a 401 error just as if you supplied any invalid organization name.

There's a post in the CRM forums where Peter one of the tech writers explained the problem in greater detail as well as a couple of options for the work around.  Read the forum post here.

Since you can change your friendly name, I'm more in favor of the first suggested option to work around the problem which is basically make your Friendly org name the same as your Unique Org Name.  This can be done in deployment manager - you have to disable the organization first, and then you can use the Edit Organization option.