jhanemaaijer
Posts: 7
Score: 0 Joined: 2/5/2002 Status: offline
|
It took me a while but I did resolve it by running the following steps In short I removed the clusternode temporarily from the cluster and forced a site reset. In detail: - Moved all the cluster resources to (one of) the other cluster node(s).
- Evict the clusternode from the cluster. This was the clusternode with the SCCM components op the cluster drive installed. steps to evict a cluster node: http://technet2.microsoft.com/windowsserver/en/library/f43e533a-e693-4995-a7ee-1d34583125141033.mspx?mfr=true
- Make sure that the no_sms_on_drive.sms file was added on every cluster disk.
- Restart the SCCM server. (More success for a site reset, otherwise you could encounter a hanging SMS_CLIENT_CONFIG_MANAGER)
- Reset the SCCM site with the option to Modify SQL Server configuration. Change nothing. After that I checked the sitecomp log to see the reinstallation of all the SCCM components on all SCCM component servers. Note that this affect the entire site and also the component services on the SCCM server itself, MP server, fall back point server, scup server, report server etc. Some servers require a restart after reinstallation. You will see temporarily warnings and errors in the site status. Make sure to give SCCM some time after a site reset to reinstall the components. Check the sitecomp log for the progress.
- After a while the Site Database server and component server comonents were removed from SCCM for the evicted cluster node.
- Searched the registry of the evicted cluster node to remove some entries pointing to SMS_<servername>. (I saw two pointers).
- Removed the SMS_<servername> files from the cluster disk.
- Rejoined the clusternode to the cluster (see http://technet2.microsoft.com/windowsserver/en/library/f43e533a-e693-4995-a7ee-1d34583125141033.mspx?mfr=true).
- After a while, when the Site component Manager has run, SCCM reinstalls the SCCM components on the added clusternode and added the clusternode to the site systems. (You can manually trigger the Site component Manager if you don't want to wait).
- Checked the SCCM site status to check of all components were running as they should.
< Message edited by jhanemaaijer -- 11/22/2007 9:02:16 AM >
|