SMS 2003 SP3 MP 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 2003 SP3 MP 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 2003 SP3 MP issue

Page: [1]

Message

<< Older Topic Newer Topic >>

SMS 2003 SP3 MP issue - 5/6/2008 11:27:49 AM

dholiway

Posts: 6
Score: 0
Joined: 7/18/2007
Status: offline

We currently a migrating our SMS server from older hardware to newer hardware. When we set up the new server we created a new site for it. The old SMS was SP1 the new was SP3. Both server were set as Primary sites and had all components configured, and each had there own site code When we started migrating the clients from one site to another we upgrade the old server to SP3 and made it a child of the new server. All the clients migrated to the new server with no problem. Now I have removed the boundaires from the old server and added them to the new server, it now appears that none of the clients are able to locate the new server. When you use the auto discover feature on the client, it automatically finds the old site code, instead of the new site code. Everything appears to be running normally on the new server. Even if you use the auto discovery on the new server it will locate the old server.

The CCMEXEC.log on the server shows this:
Request failed: 501 Not Implemented CcmExec 5/6/2008 11:14:53 AM 6344 (0x18C8)
Request failed: 501 Not Implemented CcmExec 5/6/2008 11:16:03 AM 3976 (0x0F88)
Request failed: 501 Not Implemented CcmExec 5/6/2008 11:17:43 AM 3976 (0x0F88)
Request failed: 501 Not Implemented CCMEXEC 5/6/2008 11:20:35 AM 2584 (0x0A18)
HandleRemoteSyncSend failed (0x80040231). CCMEXEC 5/6/2008 11:20:35 AM 2584 (0x0A18)
CForwarder_Sync::Send failed (0x80040231). CCMEXEC 5/6/2008 11:20:35 AM 2584 (0x0A18)
CForwarder_Base::Send failed (0x80040231). CCMEXEC 5/6/2008 11:20:35 AM 2584 (0x0A18)
Request failed: 501 Not Implemented CcmExec 5/6/2008 11:20:57 AM 2584 (0x0A18)

The locationservices.log shows that it is querying AD and finding information that both servers exist and is setting the MP as the wrong server.

The clientlocation.log appears that it is bounce back between servers as the MP. And the current issue is that any packags that are set to run will not run because it is unable to find the DP to get them, mostly becuase it is looking at the wrong MP.

Any help would be greatly appreciated,

Thanks,
Dewayne

Post #: 1

RE: SMS 2003 SP3 MP issue - 5/6/2008 11:36:52 AM

kpandey

Posts: 124
Score: 2
Joined: 4/23/2007
Status: offline

Few Questions to understand the problem

1. Did the new server is named as the old server .

2. Did you assign the permission to System Management Container with the new hardware

As the Security rights on the system managment container identify the computer system account with the GUID . The new hardware would not share the nold GUID. It is always better to remove the old or obselete secuirty rights given to the old hardware and assign the proper rights to the new server however what your hman components says does it record any error which says the <SMS Server Name > Does not able to update the information to AD ????

(in reply to dholiway)

Post #: 2

RE: SMS 2003 SP3 MP issue - 5/6/2008 11:41:39 AM

dholiway

Posts: 6
Score: 0
Joined: 7/18/2007
Status: offline

The servers have have different names, though only a slight different SMS and SMS1. Also when I extended the schema i verifed that I gave the new server permsisions to the Systems Management container.

Should I remove the listing from the Systems Mangement container that refer to the old server. In looking at it, it list information for both servers?

Thanks for the fast reply,
Dewayne

(in reply to kpandey)

Post #: 3

RE: SMS 2003 SP3 MP issue - 5/6/2008 4:02:39 PM

kpandey

Posts: 124
Score: 2
Joined: 4/23/2007
Status: offline

Few Things to double check before you remove the old server name from the security rights

1. The security rights should have to the folder as well as to the child folder .

2. Check component status specially for the two components

a) SMS Hierarchy Manager
b) SMS Component Manager

(in reply to dholiway)

Post #: 4

RE: SMS 2003 SP3 MP issue - 5/6/2008 4:46:46 PM

dholiway

Posts: 6
Score: 0
Joined: 7/18/2007
Status: offline

To answer your questions:

1. Security rights are granted to the folder and all child folders.

2. And for both servers, parent and child, both have no errors or warnings on the two listed components.

(in reply to kpandey)

Post #: 5

RE: SMS 2003 SP3 MP issue - 5/6/2008 10:02:32 PM

bmason505

Posts: 1939
Score: 100
Joined: 1/23/2003
From: Minneapolis, MN
Status: offline

What about the SLP? Maybe delete the entry in AD and restart your SLP or the site component manager on the SLP.

_____________________________

Brian Mason
MCSA\MCSE\MS MVP - SCCM
Wells Fargo
http://www.miscusergroup.org/

(in reply to dholiway)

Post #: 6

RE: SMS 2003 SP3 MP issue - 5/7/2008 6:38:05 AM

kpandey

Posts: 124
Score: 2
Joined: 4/23/2007
Status: offline

It Make sense to remove the old slp and restart as it would cause the client to locate the new MP . May be your slp indicating towards the old mp hence the clients coming up with old site code .

(in reply to bmason505)

Post #: 7

RE: SMS 2003 SP3 MP issue - 5/7/2008 8:20:39 AM

phaustein

Posts: 859
Score: 32
Joined: 3/21/2005
From: Washington, DC
Status: offline

Is the child site (old server) still have its own clients? I would unregister the old server's MP from AD and remove any entries in AD that refer to the site and related boundary entries. Depending upon if you have additional sites, I would go as far as to unregister all the MP's and remove any remaining entries in AD, except for the SLP and re-register the MPs. Do you have more than 1 SLP configured in the hieracrchy? I have found that if more than one exists and you have overlapping subnets that systems will find the wrong site.

_____________________________

Hope this helps.
Paul

(in reply to kpandey)

Post #: 8

RE: SMS 2003 SP3 MP issue - 5/7/2008 11:11:45 AM

smacpherson

Posts: 17
Score: 0
Joined: 4/25/2007
Status: offline

From the ccmexec error, I would verify that the SMS Advanced client is functioning properly on the new server. A fix or reinstall of the client may resolve it. I would also look into the afforementioned. I might also test a force client install from the new server to some testing computers to refresh the client on them to see if that would change what server their looking at.

(in reply to phaustein)

Post #: 9

RE: SMS 2003 SP3 MP issue - 5/7/2008 11:30:27 AM

dholiway

Posts: 6
Score: 0
Joined: 7/18/2007
Status: offline

Thanks to everyone for the suggestions, the issue with both server listed in AD appears to have been the problem. With the old server removed, it appears that everything is functioning normally.

Thanks again,

Dewayne

(in reply to smacpherson)

Post #: 10