I'm attempting to install a two-node SQL cluster over a Windows Cluster. The windows cluster is up and running and all set. When I run the SQL Server installation wizard, on the Data Directory screen, when using an SMB share, I type \\FS\BBDB, I get the error message reading that the setup account needs to SESECURITY privilege in the target file server.
Now, simple enough, right? Problem is, the setup account DOES have sesecurity privilege already. Not only that, but, the setup account is also:
-A domain admin
-An enterprise admin
-A local admin in both the source and the target machines
-Has full rights to both the share, as well as the NTFS folder
-It also has all the following rights per accesschk sys internals utility:
SeSecurityPrivilege
SeBackupPrivilege
SeRestorePrivilege
SeSystemtimePrivilege
SeShutdownPrivilege
SeRemoteShutdownPrivilege
SeTakeOwnershipPrivilege
SeDebugPrivilege
SeSystemEnvironmentPrivilege
SeSystemProfilePrivilege
SeProfileSingleProcessPrivilege
SeIncreaseBasePriorityPrivilege
SeLoadDriverPrivilege
SeCreatePagefilePrivilege
SeIncreaseQuotaPrivilege
SeUndockPrivilege
SeManageVolumePrivilege
SeImpersonatePrivilege
SeCreateGlobalPrivilege
SeTimeZonePrivilege
SeCreateSymbolicLinkPrivilege
SeChangeNotifyPrivilege
SeInteractiveLogonRight
SeNetworkLogonRight
SeBatchLogonRight
SeRemoteInteractiveLogonRight
SeIncreaseWorkingSetPrivilege
-UAC is deactivated in the target file server. Not only I brought the lever down all the way, but also I edited the registry to actually disable it.
So, what gives??? Help much appreciated. I'm stumped here.
The whole environment is running on Windows Server 2012 R2 Datacenter servers, all fully patched. Attempting to install SQL Server 2012 Enterprise, and yes, I do accept the updates to install setup files when asked.
rferreira