From the mailbag today comes the question of what do we call our domain name... and he wasn't talking about the .local issue mind you [which we should always do] but rather that internal box name so that should partnerships split, firms explode..whatever.. you weren't stuck with a inner netbios/domain name that just drove the customer crazy to the point that they were willing to flatten the box to get it off of there.
Personally I agree. The only caveat I would say to calling the entire fleet of your servers something like SBSServer is an issue that cropped up after SBS 2003 sp1 where if you had named your servers identical for all those in your control, the monitoring emails would get a bit confusing:
But yeah...naming that server something that you won't be asked to wipe off the face of the earth later is probably wise...
The titles of the performance and usage reports include the server name rather than the organization name
After you install SP1 for Windows SBS, the organization name is replaced with the server name in the title of the performance report and the usage report.
If you prefer to see the organization name in these reports, you can change the RegisteredOrganization entry in the registry.
Caution:
Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
To change the RegisteredOrganization registry entry
Click Start, click Run, type regedit in the Open box, and then click OK. Registry Editor opens.
Navigate to and click the following registry subkey:HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer
In the details pane, double-click RegisteredOrganization.
Enter your organization name in the Value data field, and then click OK.
Click File, and then click Exit to close Registry Editor.