Re: SMS 2.0 and SMS 2003 Running at same time in same domain.

Tech-Archive recommends: Speed Up your PC by fixing your registry


Different sms versions can perfectly coexist in one domain, even
identical versions have no problem working in the same domain. So
bringing down sms 2.0 will probably not resolve much.

With the very basic errors you are giving us it is difficult to tell you
how to solve everything. (You can right-clock on these components and
click show messages; All to have more detailed errors.

Sms Site component mgr & sms hierarchy manager probably complain that
they cannot create an object in Active Directory. Assuming you have
extended the AD Schema you would have to do the following to resolve
this. Make sure you give your site server account (advanced security) or
sms service account (standard security) full control permissions on the
systems container. For more info check the AD Publishing white paper.

http://www.microsoft.com/smserver/techinfo/productdoc/default.asp

For the other errors I would have to see the actual error messages to
take a stab at them.

Kim Oppalfens
MVP SMS
In article <7480713A-063A-4F59-B43D-D0474D163B8D@xxxxxxxxxxxxx>,
Jon@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> I have just installed SMS 2003 in a domain that is already running SMS 2.0. I
> am trying to push the client out. Will I will I be able to do this or do I
> need to bring down the SMS 2.0 server first. SMS has built the collections
> and everything from the domain is showing up, but I can not deploy the
> client. Here are some of the error messages I recieve listed below.
>
> I will be bringing the SMS 2.0 Server down at the end of the week. My
> question basically, is will this solve my problem????
>
> Critical Errors
> -SMS_CLIENT_CONFIG_MANAGER
> -SMS_MP_CONTROL_MANAGER
> -SMS_SITE_COMPONENT_MANAGER
>
> Warning
>
> -MS_NT_USER_GROUP_DISCOVERY_AGENT
> -SMS_NT_USER_DISCOVERY_AGENT
> -SMS_HIERARCHY_MANAGER
>
> Please help!
>
> Thanks
> Jon
>

--
Kim Oppalfens
SMS MVP
.

Relevant Pages

  • Re: After reinstallation
    ... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
    (microsoft.public.sms.setup)
  • Re: Adv Client with Workgroup Computers
    ... I was trying to use the SMS tools from the SMS server to initiate harware ... Inv for example the account is a domain account but the Client PC is in a ... Is there a procedure for installing the ADV client localy on a workgroup ... I have manually added to the WINS server. ...
    (microsoft.public.sms.admin)
  • Re: After reinstallation
    ... I guess what you say is that my server is running fine, but I should not expect client push to work. ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... "Todd Hemsell" wrote: ...
    (microsoft.public.sms.setup)
  • Re: 4912: Cannot update the already existing object. Need some he
    ... Also, as far as the client pointing to the wrong server, you should use SMS ... SP3 client through a logon batch file. ...
    (microsoft.public.sms.admin)
  • Re: Installation of Client
    ... SmsDetectDowngrade_ErrorMessage = A newer version of the SMS ... Advanced Client is already installed ... I also manually added the WINS information into the WINS server that both ... cannot get the client to properly install. ...
    (microsoft.public.sms.setup)