Client errors after renaming server...
I have renamed the server and promoted it to a DC as well. These are theonly two functions the server performs. I have uninstalled SCE and reinstalled after the name change and dcpromo. Now that I have renamed the server I get errors from some clients as follows: _______________________ Source OpsMgr Connector Event ID 21006 Description The OpsMgr Connector could not connect to [OLDSERVERNAME]:5723 The error code is 11001L(no such host is known.) Please verify there is a network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination. _______________________ Source OpsMgr Connector Event ID 21001 The OpsMgr Connector could not connect to MSOMHSvc/[OLDSERVERNAME.domain.com] because mutual authentication failed. Verify the SPN is properly registered on the server and that, if the server is in a separate domain, there is a full-trust relationship between the two domains. _______________________ Source OpsMgr Connector Event ID 20057 Failed to initialize security context for target MSOMHSvc/[OLDSERVERNAME.domain.com] The error returned is 0x80090303(The specified target is unknown or unreachable). This error can apply to either the Kerberos or the SChannel package. _______________________ Clearly it is because I have changed the name of the server, but I am unsure of how to correct this. I only have a few clients correctly connecting and reporting, but all remaining are experiencingthis issue Thanks for any help you can offer.
December 7th, 2007 1:43pm

Hi, You need to reinstall all agents. Also, make sure the GPO and the security group SCE creates refers to the new installation. Bjrn Axll MVP - Advisec AB http://blog.advisec.com
Free Windows Admin Tool Kit Click here and download it now
December 8th, 2007 11:50am

Hi, Thanks for Bjrn Axll's inputs. Also, I would like share some additional information with you. These symptoms can occur when the servicePrincipalName (SPN) for the management server's HealthService is not registered or is not registered correctly. The HealthService SPNs should be as follow: MSOMHSvc/FQDNMSOMHSvc/COMPUTERNAME Please perform the following steps on the SCE server: 1. Install Windows Support Tools in the Server 2003 resource kit.2. Open a command line. Run the command: setspn L servername3. Check whether there are any duplicated SPNs on the MSOMHSvc.4. If you find duplicate SPNs, remove it by run the command: setspn D MSOMHSvc/FQDN computername and then restart the OpsMgr service. For example, if you find duplicate SPN like this MSOMHSvc/OPSMGRFA, run command with setspn D MSOMHSvc/ OPSMGRFA opsmgrfa. 5. You may have to purge Kerberos tickets on affected agents. You can do this by rebooting agents or by using klist.exe. Klist is included in the Windows Server 2003 Resource Kit Tools, you can find it at below: Windows Server 2003 Resource Kit Toolshttp://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en 6. To purge tickets using klist, run the following command: klist purge Then, press y to confirm deletion of each ticket. After you purge tickets, restart the OpsMgr Health Service.I hope it helps.-----------------------------Sincerely,Guozhen WangMicrosoft Online Community Support
December 10th, 2007 1:19am

Thank you both for your help. It is greately appreciated. I have reinstalled the agents, helper objects,and copied the certs to the clientsmanually. Here is the latest from my event viewer. _________________________ Source: Health Service Modules Event ID: 31876 Data item returned no information for parameter '$Data/Property[@Name='SupportsDiskQuotas']$' This usually indicates that the query is incorrect. One or more workflows were affected by this. Workflow name: Microsoft.Windows.Client.2000.LogicalDisk.Discovery Instance name: CLIENTNAME.DOMAIN.com Instance ID: {FB09CB15-8DD4-B2C9-90CE-C48202AD8A32} Management group: SERVERNAME_MG _________________________ Once again thank you for the help -Jeff Swim
Free Windows Admin Tool Kit Click here and download it now
December 10th, 2007 3:57pm

Hi Jeff Swim, Thanks for your update. The new issue you are facing was noticed in the following article: Windows Client Operating System Management Pack Guide for Operations Manager 2007http://download.microsoft.com/download/7/4/d/74deff5e-449f-4a6b-91dd-ffbc117869a2/OM2007_MP_WinCliBase.doc It is a known issue, and have no workaround in this release of SCE. And it is under investigating, please wait for the coming SP1. By the way, may I know if your issue of renaming server had been resolved? If the problem still happens, please feel free to let us know. We will be happy to provide further assistance. Thanks.-----------------------------Sincerely,Guozhen WangMicrosoft Online Community Support
December 11th, 2007 1:13am

Related to your error of: Event ID 21006 Description The OpsMgr Connector could not connect to [OLDSERVERNAME]:5723 The error code is 11001L(no such host is known.) Please verify there is a network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination. We ran into this error today and had nothing to do with changing server names, but instead was related to people following instructions that we made and copy/paste server name into the field with extra spaces. This actually (surprisingly) keeps these spaces and will cause it to not work. So, I had to Modify the installation and remove the trailing spaces and then redo MOMCertImport and then restart the HealthService and this quickly fixed the problem. I did not find anyone else online that mentioned this, so hopefully it helps someone else as it is really difficult to catch :)
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2011 2:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics