RE: problem attaching child site to parent.
- From: Sherry Kissinger [MVP-SMS] <mofmaster@xxxxxxxxxxxxx>
- Date: Tue, 1 Apr 2008 15:49:01 -0700
I don't "think" that publishing of the FQDN into AD would be related to
setting up the parent-child relationship. You could always extend AD schema
to have that error go away.
Nothing in the sender.log? I would assume that if something is trying to
link up you'd see errors in there.
Another thought... did these 2 sites ever have a previous parent/child
relationship? or the same site code was used previously for another site?
Perhaps there is historical info. At this point, if I were you, I'd burn a
Microsoft call on troubleshooting this.
--
Standarize. Simplify. Automate.
"Joshua" wrote:
I found this error..
Systems Management Server cannot update the dNSHostName property for the
existing object "cn=SMS-MP-AHT-MEM0SMS01T" in Active Directory. This
property is used to publish fully qualified host names in Active Directory.
Possible cause: The Active Directory schema has not been extended with
latest version of the SMS Active Directory classes and attributes.
Solution: Ensure the schema has been extended with the latest version of the
SMS Active Directory classes and attributes. The schema can be extended with
the tool "extadsch.exe" from the SMS directory on the SMS Site server that
reported this message.
"Sherry Kissinger [MVP-SMS]" wrote:
That is pretty much it... creating the sender addresses on each site to the
other, verify the computer accounts have rights to the other server, then set
the primary site.
If you look at either log files on the child primary, or check Site Status
messages in the console--anything in there giving you a clue?
--
Standarize. Simplify. Automate.
"Joshua" wrote:
I did set the parent site from there. I feel like there is something I am
missing. I have been unable to find complete directions on how to connect a
child site to a primary site. Everything just reads to set the primary site
and then it starts
working from there. I have had to do more research to learn about creating
the addresses and adding the computer accounts to the sitetosite connections
groups.
Do you know of any more thorough instructions? I am still new to SMS, the
person who used to manage it left and I inherited it.
"Sherry Kissinger [MVP-SMS]" wrote:
On the to-be-child primary, in the Console, Site Hierarchy, right-click the
sitecode/properties, does it show the to-be-central Primary site code there?
Did you "Set Parent Site" from there yet?
--
Standarize. Simplify. Automate.
"Joshua" wrote:
I have setup another primary site and I want to make it a child site to
another primary site. I have created the addresses for each system, I have
add the computer accounts for each computer in the other's sitetosite group.
I still do not see the child site show up under the hierarchy for the primary
site. What am I doing wrong?
- Prev by Date: Re: Setting up a Terminal Server (TS) for multiple Console users
- Next by Date: Re: SMS Client Installation Files
- Previous by thread: Re: SP3 Upgrade: Errors: 1020 (MP), 4951 (MP), 2302 (DP),
- Next by thread: Re: problem attaching child site to parent.
- Index(es):
Relevant Pages
|
Loading
