SCCM 2007 R2 Secondary Site

I have installed a server as a secondary site SCCM servers by copying the SCCM files to this server and running it locally.
I have installed and configured WebDAV and IIS and done the necessary configurations.
However the server hasnt appeared under my primary site server in the SCCM console.

Is there something (logs etc., ) I need to check to see why it hasnt appeared as a secondary site in spite of waiting for 3 days?
tedcbeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nagendra Pratap SinghDesktop Applications SpecialistCommented:
Just copied the files? Any guide/book for the steps you took?

Try installing this from the main server. It will transfer like 500 MB data and will install in a few mins after that.
0
MaxSoullardCommented:
Hi

You can check the following logs:
Despool.log    -    Records incoming site-to-site communication transfers.
Sender.log    -    Records files that are sent to other child and parent sites.

It could be a public key issue, check the site below:

http://technet.microsoft.com/en-us/library/bb693690.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tedcbeAuthor Commented:
Thank you npsingh123 and MaxSoullard for your suggestions.

I have done the following so far

1. SCCM 2007 with SP2 files copied to the local server and installed
2. SCCM 2007 R2 copied to the local sever and installed
3. Install IIS and Web Dav and configure it
4. Checked if AD Schema is extended to SCCM 2007 by looking in the Systems Management container within AD Users and computers.
5. Checked sender.log on the primary server which shows the following

04/09/2013 09:42:31      Instruction file = D:\Program Files (x86)\Microsoft Configuration Manager\inboxes\schedule.box\tosend\0000D123.I1t      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:31      Checking for remote file \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.PCK      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Checking for remote file \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.SNI      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Checking for remote file \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.TMP      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Attempt to create/open the remote file \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.PCK      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Created/opened the remote file \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.PCK      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Attempt to create/open the remote file \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.PCK      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Created/opened the remote file \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.PCK      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Sending Started [D:\Program Files (x86)\Microsoft Configuration Manager\inboxes\schedule.box\tosend\0000D123.Piv]      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Attempt to write 1024 bytes to \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.PCK at position 0      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Wrote 1024 bytes to \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.PCK at position 0      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Attempt to write 349 bytes to \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.PCK at position 1024      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Wrote 349 bytes to \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.PCK at position 1024      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Sending completed [D:\Program Files (x86)\Microsoft Configuration Manager\inboxes\schedule.box\tosend\0000D123.Piv]      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Attempt to create/open the remote file \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.TMP      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Created/opened the remote file \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.TMP      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Attempt to create/open the remote file \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.TMP      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Created/opened the remote file \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.TMP      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Sending Started [D:\Program Files (x86)\Microsoft Configuration Manager\inboxes\schedule.box\tosend\0000D123.I1t]      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Attempt to write 396 bytes to \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.TMP at position 0      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Wrote 396 bytes to \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.TMP at position 0      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Sending completed [D:\Program Files (x86)\Microsoft Configuration Manager\inboxes\schedule.box\tosend\0000D123.I1t]      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Renaming remote file \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.TMP to \\SRSCCM08.centra.local\SMS_SITE\214UNCE1.SNI      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Rename completed [\\SRSCCM08.centra.local\SMS_SITE\214UNCE1.TMP]      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Sending completed successfully      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Retrieved the snapshot for priority 0, there are 0 files in the snapshot.      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Retrieved the snapshot for priority 1, there are 0 files in the snapshot.      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Retrieved the snapshot for priority 2, there are 0 files in the snapshot.      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Retrieved the snapshot for priority 3, there are 0 files in the snapshot.      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:32      Retrieved the snapshot for priority 4, there are 0 files in the snapshot.      SMS_LAN_SENDER      112568 (0x1B7B8)
04/09/2013 09:42:36      We have 0 active connections      SMS_LAN_SENDER      3492 (0x0DA4)
04/09/2013 09:42:36      Checking for sending capacity.  Used 0 out of 5.      SMS_LAN_SENDER      3492 (0x0DA4)
04/09/2013 09:42:36      Connecting to D:\Program Files (x86)\Microsoft Configuration Manager\inboxes\schedule.box\outboxes\LAN.      SMS_LAN_SENDER      3492 (0x0DA4)
04/09/2013 09:42:36      Retrieved the snapshot for priority 0, there are 0 files in the snapshot.      SMS_LAN_SENDER      3492 (0x0DA4)
04/09/2013 09:42:36      Retrieved the snapshot for priority 1, there are 0 files in the snapshot.      SMS_LAN_SENDER      3492 (0x0DA4)
04/09/2013 09:42:36      Retrieved the snapshot for priority 2, there are 0 files in the snapshot.      SMS_LAN_SENDER      3492 (0x0DA4)
04/09/2013 09:42:36      Retrieved the snapshot for priority 3, there are 0 files in the snapshot.      SMS_LAN_SENDER      3492 (0x0DA4)
04/09/2013 09:42:36      Retrieved the snapshot for priority 4, there are 0 files in the snapshot.      SMS_LAN_SENDER      3492 (0x0DA4)

The site did not appear within Site management under the primary site so I tried to install the secondary site from the main server as suggested by npsingh123 but have had an egg times for the last week or so under the Site Management section for this Secondary site.

I was under the impression that you have to manually exchange public keys within sites if AD schema is not extended for SCCM 2007 (which is not the case).

Any help on getting this working will be very much appreciated
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Nagendra Pratap SinghDesktop Applications SpecialistCommented:
Have you added the computers to other computers local admins?
0
tedcbeAuthor Commented:
I have added the Central site sever computer account to the local admin of the secondary site server.
0
Nagendra Pratap SinghDesktop Applications SpecialistCommented:
You have to do the reverse too.

add sec's computer account to primary's local admins.

Please try to locate a guide. I tried to find one but now most guides are on SCCM 2012.

Also, for an environment with Pri + Sec you should have a book to start with. SCCM is the most complex software I have seen.
0
tedcbeAuthor Commented:
It turned out be a public key issue. I was under the impression that if the AD Schema is extended to SCCM 2007, the process will take place automatically.
After I manually exchanged the keys as mentioned in the technet article, the process completed successfully. Thank you MaxSoullard.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Applications

From novice to tech pro — start learning today.