SMS issue

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

SMS issue

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003 >> SMS issue

Page: [1]

Message

<< Older Topic Newer Topic >>

SMS issue - 2/12/2008 11:07:10 PM

jper

Posts: 53
Score: 0
Joined: 4/18/2007
Status: offline

Hi guys---- somedays ago we had to change the machine's name of all our machines (2000 more or less)...
So, we desinstalled the sms client before the change, change the name and later on we installed the sms client again...
For example:
Before machine name: ing12f4
Actual name: ing12f401
We had to change by company's politic...

But I have one trouble.... in the sms server I am getting the next error:

The kerberos client received a KRB_AP_ERR_MODIFIED error from the server ing12f401$. The target name used was cifs/ing12f4.Domain_name. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (Domain_name), and the client realm. Please contact your system administrator.

But we erased or disabled the before machine account...

The sms server is an windows 2003 sp2 and I have sms 2003 sp2.

Thanks a lot for your help.
Regards,

Post #: 1

RE: SMS issue - 2/13/2008 12:12:42 AM

pwstrain

Posts: 122
Score: 9
Joined: 3/11/2007
From: Danville, Illinois
Status: offline

Did you remove the client from the domain and re-add it by joining it to a workgroup, renaming, and re-joining the domain?
Or did you just rename the client?

_____________________________

My Personal Blog
My Technical Blog

(in reply to jper)

Post #: 2

RE: SMS issue - 2/13/2008 3:36:44 PM

jper

Posts: 53
Score: 0
Joined: 4/18/2007
Status: offline

We followed this steps, in this order:
1. Desinstall the sms client on the machines
2. Get out the machine from the domain (we puted them in one workgroup)
3. Change the machine name to the new accoring the company's politics
4. Add the machine to the domain:

With the same user account
Move the new machine's account to the corresponding OU
Either disable or erase the old machine´s account

5. Install the sms client

(in reply to pwstrain)

Post #: 3

RE: SMS issue - 2/18/2008 6:35:41 AM

peter.e

Posts: 24
Score: 0
Joined: 11/21/2006
Status: offline

Hello!

Are there any other reasons why this error could be appearing? We have lots of these errors in the event log.

Thanks,
Peter

(in reply to jper)

Post #: 4

RE: SMS issue - 2/18/2008 7:44:54 AM

eschloss

Posts: 616
Score: 25
Joined: 9/7/2004
From: Cincinnati
Status: offline

By that procedure, the client is probably using the same SMS ID it was using before. Uninstalling the sms client does not delete the smscfg.ini in the windows directory. If you turn around and re-install the client with that file still there, it will use the previous SMS ID and appear to be the same machine to SMS.
Try stopping the CCMEXEC service, deleting C:\windows\smscfg.ini and then restarting the CCMEXEC service and see if that helps.

(in reply to peter.e)

Post #: 5

RE: SMS issue - 2/18/2008 3:40:34 PM

jper

Posts: 53
Score: 0
Joined: 4/18/2007
Status: offline

Hi !
I have one question why only some machines are doing it and why not all ?? And of course in all the machines we did the same...
We have some customers that have some custumers that use their user accounts in diferents machines, could be it another reason why are happening it ???

So, why could be the method to do the tasks that I mencioned before???
Thanks a lot !

(in reply to eschloss)

Post #: 6