Cluster Setup for Sccm 2007 R2
- From: J Wolfgang Goerlich <jwgoerlich@xxxxxxxxx>
- Date: Thu, 12 Feb 2009 03:15:33 -0800 (PST)
Hello,
What steps are involved in setting up Sccm to run off a SQL cluster?
I have Sccm 2007 R2 installed on a Windows Server 2008 Enterprise 32-
bit OS (Sccm3). There is a SQL 2005 server (Mscs1-isg\isg) installed
on a fail-over cluster (Mscs1) running on two Windows Server 2003
Enterprise 64-bit computers (Db4 and Db5). The SQL resource runs on
Db5. Sccm3 reports errors that it cannot reach the site components on
Db4 (see below for full text).
I have added the SPNs for the cluster and cluster resources. I have
also set Sccm3 as a member of Db4\Administrators and
Db5\Administrators.
In the Sccm admin console, I see Db4 and Db5. Both are set to host the
roles: ConfigMgr component server, ConfigMgr site database server,
ConfigMgr site system. I do not see the clustered SQL server instance
(Mscs1-isg\isg).
What steps am I missing? Any setup or troubleshooting advice
appreciated.
J Wolfgang Goerlich
Severity Error
Type Milestone
System SCCM3
Component SMS_SITE_COMPONENT_MANAGER
Message ID 1050
SMS Site Component Manager could not create the SMS server components'
installation directory "O:\SMS_SCCM3" on site system "\\DB4" or set
the correct permissions on the directory. The operating system
reported error 67: The network name cannot be found. Possible
cause: The destination drive is full. Solution: Make more space
available on that drive. Possible cause: The site system is not
exporting the default drive letter shares, such as "\\DB4\C$", "\\DB4\D
$", and so on. Solution: You might have disabled the default drive
letter shares for security purposes. SMS requires these shares. Please
re-enable these shares using the Windows NT Disk Administrator.
Possible cause: The site system is turned off, not connected to the
network, or not functioning properly. Solution: Verify that the site
system is turned on, connected to the network, and functioning
properly.
Possible cause: SMS Site Component Manager does not have sufficient
access rights to remotely administer the site system. Solution:
Verify that the Site System Connection accounts are properly
configured to allow SMS to remotely administer the site system.
Possible cause: Network problems are preventing SMS Site Component
Manager from properly accessing the site system. Solution:
Investigate and correct any problems on your network.
Severity Error
Type Milestone
System SCCM3
Component SMS_SITE_COMPONENT_MANAGER
Message ID 1031
SMS Site Component Manager failed to reconfigure site system "\\DB4"
to receive SMS server components.
Solution: Review the previous status messages to determine the exact
reason for the failure. SMS Site Component Manager cannot reinstall
any SMS server components on this site system until the site system is
reconfigured successfully. SMS Site Component Manager will
automatically retry this operation in 60 minutes. To force SMS Site
Component Manager to immediately retry this operation, stop and
restart SMS Site Component Manager using the SMS Service Manager.
Severity Information
Type Milestone
System DB4
Component SMS_SITE_SYSTEM_STATUS_SUMMARIZER
Message ID 4701
SMS Site System Status Summarizer still cannot access storage object "\
\DB4\O$\SMS_SCCM3" on site system "\\DB4". The operating system
reported error 2147942467: The network name cannot be found.
Possible cause: The site system is turned off, not connected to the
network, or not functioning properly. Solution: Verify that the site
system is turned on, connected to the network, and functioning
properly.
Possible cause: SMS Site System Status Summarizer does not have
sufficient access rights to connect to the site system and access the
storage object. Solution: Verify that the Site System Connection
accounts are properly configured to allow SMS to connect to the site
system and access the storage object.
Possible cause: Network problems are preventing SMS Site System Status
Summarizer from connecting to the site system. Solution: Investigate
and correct any problems on your network. Possible cause: You took
the site system out of service and do not intend on using it as a site
system any more. Solution: Remove the site system from the list of
site systems used by this site; this list appears under Site Systems
in the SMS Administrator console.
Possible cause: You accidentally deleted the storage object or took
the storage object out of service.
Solution: The SMS components will eventually detect that the storage
object no longer exists on the site system and will either recreate it
or choose a new storage object. Monitor the status messages reported
by other SMS components to verify that this occurs properly.
.
- Prev by Date: Task Sequence Media has errors - Running Sequence from SCCM works
- Next by Date: SCCM 2007 and Novell clients
- Previous by thread: Task Sequence Media has errors - Running Sequence from SCCM works
- Next by thread: SCCM 2007 and Novell clients
- Index(es):
Relevant Pages
|
