Answered by:
SCCM child site configuration.

Question
-
Hi All,
We have SCCM 2007 sp1 central site code CNT and also another primary site SNS reporting to parent central site.
We want to deploy new primary site for new location and it should report to central site.
What are the best way to create addresses and how to verify everything working perfect.
Thanks in advance.Monday, March 15, 2010 10:02 AM
Answers
-
Hi,
I don't think there is a best practice for creating addresses. the address settings depends on how you want to control traffic/bandwidth. When you create the relationship, you can monitor/verify the process by looking at these log files on both servers.
Sender.log
Despool.log
hman.log
If there are any errors related to permissions etc,. then they will be written to those log files.
Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products- Proposed as answer by Garth JonesMVP Monday, March 15, 2010 11:48 AM
- Marked as answer by Eric Zhang CHN Monday, March 29, 2010 7:15 AM
- Marked as answer by Eric Zhang CHN Monday, March 29, 2010 7:15 AM
Monday, March 15, 2010 10:27 AM
All replies
-
Hi,
I don't think there is a best practice for creating addresses. the address settings depends on how you want to control traffic/bandwidth. When you create the relationship, you can monitor/verify the process by looking at these log files on both servers.
Sender.log
Despool.log
hman.log
If there are any errors related to permissions etc,. then they will be written to those log files.
Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products- Proposed as answer by Garth JonesMVP Monday, March 15, 2010 11:48 AM
- Marked as answer by Eric Zhang CHN Monday, March 29, 2010 7:15 AM
- Marked as answer by Eric Zhang CHN Monday, March 29, 2010 7:15 AM
Monday, March 15, 2010 10:27 AM -
Hi Kent Agerlund,
Thanks for your reply.
Which articles should I refer before doing implementation.Monday, March 15, 2010 12:32 PM -
Monday, March 15, 2010 12:42 PM
-
Hi Torsten,
Thanks for your reply.
Well, I created site address on primary site. Example like CNT,
But it is showing CNT - (unknown) even this site code exists for central site.Monday, March 15, 2010 2:51 PM -
That's fine (if you're connected to the primary child site). But: the address should show fine if you're connected to the central site.Monday, March 15, 2010 3:12 PM
-
Well, What about the collections for every collection there should be a locked should appear on the collections.
But this lock does not appear on the collections of primary site. More over the manuall created collections at central site also missing from primary site (child site).
Where to check and troubleshoot...Monday, March 15, 2010 4:03 PM -
See the logs that Kent mentioned.
Monday, March 15, 2010 5:53 PM -
What exactly I should look for can you tell me in detail. On Central Site: In Senders.log this error. There is no exsisting connection Win32 Error=5
Tuesday, March 16, 2010 10:42 AM -
That's "access denied". Have you added the appropriate account to each site to site connection group http://technet.microsoft.com/en-us/library/bb632850.aspx?
Tuesday, March 16, 2010 10:46 AM -
HI Torsten,
I have added computer as well user account on both central and primary site local SMS site to site connection group.Tuesday, March 16, 2010 12:06 PM -
Hi Torsten,
Today I came and check. I check on primary site (child site) the locked icon appeared but in custom collections example like symantec clients created in central showing approved computer in primary site (child site) I cannot see same approved computers.
When I check the site status of primary site ( child site). I warning message below.
SMS Active Directory System Discovery Agent reported errors for 5 objects. DDR's were generated for 0 objects that had errors while reading non-critical properties. DDR's were not generated for 5 objects that had errors while reading critical properties.
I query the component SMS_AD_SYSTEM_DISCOVERY_AGENT, It was stop I try to start no luck.Wednesday, March 17, 2010 1:37 PM -
Are there any clients assigned to the central site? If so: they won't show up at the primary child site (because discovery and inventory data only flows up in a hierarchy).
SMS_AD_SYSTEM_DISCOVERY_AGENT will only be running when the scheduled discovery task is active (see adsysdis.log).Wednesday, March 17, 2010 1:48 PM -
Yes Clients are ssigned to the central site and approved.
But from primary site, In All Systems collection I can see all the computer but no site code. Assigned Client No.Wednesday, March 17, 2010 2:19 PM -
That depends on the configuration of your discovery methods.
They will show up as "client: no" if they are not assigned to but discovered by that site.Wednesday, March 17, 2010 3:34 PM -
Hi Torsten,
I need to know why the set parent site on the new child site is grayed out? before i created the relationship between the parent (existing sccm server which would be decomissioned later) and child (new sccm server due to hardware move) i installed the asset intelligence sync role and there was a complaint that i cannot attach with that role on so i deleted the role did the attachment. after a while of no activity between the parent and child, i removed the relationship by setting the child back to central site and clicked ok, i then reinstalled the role...when i went back to check the settings on the child server i discovered that the relationship had not been broken. so i tried to remove the asset intelligence role from the child site server without success. i then went to the parent site and was able to uninstall the role from the console there. however the set parent site on the child server is still grayed out.
here is my question, would it continue to be grayed out or is there a workaround that cos soon as the replication is finished, the clients would be re-assigned and i plan to break the relationship. kindly help.
thanks.
Tuesday, May 11, 2010 4:26 PM -
hello anybody there?Wednesday, May 12, 2010 10:30 AM