Hi all,

A few queries about the above config -

We are setting up a new E2k7 system with 2 front end CAS servers with NLB and 2 back end Mailbox servers in NLB config and doing CCR between them (no shared storage).

I was able to install SnapDrive 6.01 and create four LUN's (non shared dedicated) on each Mailbox server on two seperate SAN's for the mail stores & logs. No problem.

However as soon I rebooted and went to check the LUN's (which stayed connected) and create a new one I got a couple of errors (different on each system) - RPC server unavailable - Security package related error

Oddly I can expand existing LUN's OK via SD - so some functionality exists - just can't create a new LUN within SD.

I have had a suggestion to make sure the Windows Quorum Witness Disk should also be on the SAN - following Microsoft best practive I've created a small Quorum Witness Disk and share on a CAS server. Thats fine - still doesn't fix the RPC error (I can ping and access the admin share on the SAN from each mailbox server).

The most annoying thing is that none of these issues has cropped up with W2K3 and SD 4.2.1 - I'm following the same fundamental setup steps.

Given I'm not using shared storage clustering just CCR and NLB I want to discover the root of the SD errors - is it SD trying to be clever and insisting that for a Windows cluster you really need shared disks registered with the cluster administrator regardless of wether they're shared or not ? - just some weirdness with W2K8 and SD 6.01 ? - are there any gotchas with W2K8 and SD 6.01 that I need to be aware of ? I just noticed theres a DCOM exception for the W2K8 firewall on NOW - how come SD doesn't set this stuff up at install time ?

I want to eliminate the clustering ASAP issue because until I nail the problem the Exchange guys can't really proceed with the rest of the install. Particularly if I need to keep messing around with breaking and re-establishing the cluster to sort out an RPC error.

Thanks in advance, Raj.