Hi, I have recently moved our database server to a SQL Cluster following all provided documentation. Kerberos authentication has been enabled on the cluster and SPN's have been setup. For a couple of weeks things were ticking along nicely but I am now getting Site System Status messages against the SCOMPRODSQL-A server every hour as follows: SMS Site System Status Summarizer still cannot access storage object "\\SCOMPRODSQL-A\D$\SMS_SCCM" on site system "\\SCOMPRODSQL-A" The server specified is the inactive node on the cluster, so the disk is not mounted here. There are no errors on the active node within SCCM. The drive for the database is \\SCOMPRODSQL-B\G$\SMS_SCCM and this looks fine. My question is why is it trying to connect to D$, and why am I getting these errors - I would not expect to be able to connect to the disk on this server but this did not cuase errors for the first couple of weeks of operation. Any help would be greatly appreciated. ThanksAndrew

Hi, D$ is that a clusterdrive? -- Cheers,Kenneth Bess Forum: http://www.systemcenterforum.netBlog: http://www.systemcenterblog.net "AC76" wrote in message news:5d2c43f4-bf28-46a5-a104-80a494267704... Hi, I have recently moved our database server to a SQL Cluster following all provided documentation. Kerberos authentication has been enabled on the cluster and SPN's have been setup. For a couple of weeks things were ticking along nicely but I am now getting Site System Status messages against the SCOMPRODSQL-A server every hour as follows: SMS Site System Status Summarizer still cannot access storage object "\\SCOMPRODSQL-A\D$\SMS_SCCM" on site system "\\SCOMPRODSQL-A" The server specified is the inactive node on the cluster, so the disk is not mounted here. There are no errors on the active node within SCCM. The drive for the database is \\SCOMPRODSQL-B\G$\SMS_SCCM and this looks fine. My question is why is it trying to connect to D$, and why am I getting these errors - I would not expect to be able to connect to the disk on this server but this did not cuase errors for the first couple of weeks of operation. Any help would be greatly appreciated. ThanksAndrew Bess, Kenneth - http://www.systemcenterblog.net - http://www.systemcenterforum.net

Hi, D$ is that a clusterdrive? -- Cheers,Kenneth Bess Forum: http://www.systemcenterforum.netBlog: http://www.systemcenterblog.net "AC76" wrote in message news:5d2c43f4-bf28-46a5-a104-80a494267704... Hi, I have recently moved our database server to a SQL Cluster following all provided documentation. Kerberos authentication has been enabled on the cluster and SPN's have been setup. For a couple of weeks things were ticking along nicely but I am now getting Site System Status messages against the SCOMPRODSQL-A server every hour as follows: SMS Site System Status Summarizer still cannot access storage object "\\SCOMPRODSQL-A\D$\SMS_SCCM" on site system "\\SCOMPRODSQL-A" The server specified is the inactive node on the cluster, so the disk is not mounted here. There are no errors on the active node within SCCM. The drive for the database is \\SCOMPRODSQL-B\G$\SMS_SCCM and this looks fine. My question is why is it trying to connect to D$, and why am I getting these errors - I would not expect to be able to connect to the disk on this server but this did not cuase errors for the first couple of weeks of operation. Any help would be greatly appreciated. ThanksAndrew Bess, Kenneth - http://www.systemcenterblog.net - http://www.systemcenterforum.net

Hi, D$ is that a clusterdrive? -- Cheers,Kenneth Bess Forum: http://www.systemcenterforum.netBlog: http://www.systemcenterblog.net "AC76" wrote in message news:5d2c43f4-bf28-46a5-a104-80a494267704... Hi, I have recently moved our database server to a SQL Cluster following all provided documentation. Kerberos authentication has been enabled on the cluster and SPN's have been setup. For a couple of weeks things were ticking along nicely but I am now getting Site System Status messages against the SCOMPRODSQL-A server every hour as follows: SMS Site System Status Summarizer still cannot access storage object "\\SCOMPRODSQL-A\D$\SMS_SCCM" on site system "\\SCOMPRODSQL-A" The server specified is the inactive node on the cluster, so the disk is not mounted here. There are no errors on the active node within SCCM. The drive for the database is \\SCOMPRODSQL-B\G$\SMS_SCCM and this looks fine. My question is why is it trying to connect to D$, and why am I getting these errors - I would not expect to be able to connect to the disk on this server but this did not cuase errors for the first couple of weeks of operation. Any help would be greatly appreciated. ThanksAndrew Bess, Kenneth - http://www.systemcenterblog.net - http://www.systemcenterforum.net

Hi Andrew, The reason why you are getting the error is because ConfigMgr. has installed files on the D$ and the drive is not any longer available. When working with a SQL cluster you can configure the no_sms_on_driver.sms file. This file will prevent ConfigMgr. files from being installed on specific drives. Have a look at this article - http://www.myitforum.com/articles/18/view.asp?id=11946 Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

Thanks Kent, That looks like it is the issue - I thought these were only relevent for DP's! I have added the no_sms_no_drive.sms file to all other drives now - what do I need to do for these changes to be picked up to clear the errors? Cheers

All drives are clustered except C$. The database is on G$. What I am thinking I need to do is: 1. Move the config manager files to C$ on both clustered servers.2. Put no_sms_on_srive.sms on all the clustered drives. Can someone confirm that this is the best resolution and confirm how I go about 1. safely. Can I literally copy the folder from cluster drive to C: and edit the file location for the Service in the registry...or is it too much to hope for it to be this simple? Thanks again,Andrew

Hi all, If anybody could advise me regarding my previous comment that woulod be appreciated. Thanks in advance, Andrew

Hi, This issue is not yet causing me any live issues, and is unlikely to as the drive will be available when we failover, but it is messy. Can anyone advise as to how I can move these site systems from D$ (and G$ on active node) to C$. Thanks

AC76, Did you ever get this fixed? I have a similar environment. It doesn't appear to be causing any real issues, the error messages in Site System Status are just warnings... but I was wondering if you were able to fix the problem? I think this might be "by design" and no real problem exists...

AC76, Did you ever get this fixed? I have a similar environment. It doesn't appear to be causing any real issues, the error messages in Site System Status are just warnings... but I was wondering if you were able to fix the problem? I think this might be "by design" and no real problem exists...