Hi, during our installation of our first Exchange Server 2007 Mailbox Server we hit a problem. We had to complete the installation of the active node with the command line setup. Everything works finde except for: We are not able to add a Public Folder Database, which is necessary for we do have "legacy" clients around. This is the error message when I try to configure SCM1 with a Publich Folder Database. Zusammenfassung: 2 Element(e). Erfolgreich: 0, Fehler: 1. Verstrichene Zeit: 00:00:00 Neue(r)/(s) publicsError Error:General Cluster error exception: The cluster ressource group for mailbox server 'Cluster1" could not be found. new-publicfolderdatabase -StorageGroup 'CN=First Storage Group,CN=InformationStore,CN=Cluster1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MyOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MyDomain,DC=local' -Name 'publics' -EdbFilePath 'E:\MDB\First Storage Group\publics.edb' Remark: This is a translation of the error from German. Setup stops and no database is set up. As a second error every time I open our Cluster server opject in Exchange Management Console I receive an error: --------------------------------------------------------Microsoft Exchange Error--------------------------------------------------------Following Error was reported while loading topology information: get-StorageGroupCopyStatusErrorError:The status of continuous cluster replication of a mailbox server, which is not local, could not be received. Server Cluster1 does not run on this cluster. --------------------------------------------------------OK-------------------------------------------------------- Any help would be highly appreciated. Cheers, Florian

Do you have any other net names in the cluster? Is the CMS the only resource in the Windows Cluster?

It sounds like 'Cluster1' is not really the cluster name. If you run a 'Get-MailboxServer' whatare the name(s) listed? Your SCC cluster mailbox server name should match with the Network Name listed if you look at the cluster group in Cluster Administrator. Does it say 'Cluster1' or something else? Lastly might be worth running BPA, it's good at picking out misconfiguration issues that cause this kind of thing. Cheers, Erik