RE: Secondary Site Installation

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



ok, I guess these are only created with the push method.
Does it just show as pending in the Central site.

You might need to add the client machines manually to the site server groups
and the SQL groups.
I know if you tell sMS to uninstall the secondary and try again it creates
all kinds of mess. You then have to find all the ccr and ddr and get rid of
them

check the inboxes\ddm.box\data.col
do you have a file: [secondarsitecode]qry.ncf
If you open this file with notepad you should see the settings
Check your hman.box\pubkey.
Is there a key file for the secondary.
Check the sender log from the central site and see if you have 53 or 3 or 5
errors (unable to connect)

Can you get to the \\server\sms_site and the cap share?

--
-----------------------
http://sms-hints-tricks.blogspot.com/


"spg7752" wrote:

Matthew,

Neither file exists on the root of the drive where SMS is installed. All I
have is CAP_AL1, SMS and WUTemp for directories. There are 4 tmp files
however.

Steve

"Matthew Hudson" wrote:

SMS_BOOTSTRAP.log
SMSSETUP.LOG
they should be in the root of the drive you installed to...

--
-----------------------
http://sms-hints-tricks.blogspot.com/


"spg7752" wrote:

Matthew thanks for the infomation. It has been 5 hours since the secondary
was installed. Still have not seen it on the primary in the hierarchy. I
went to the SMS directory on the secondary. Do you mean the install.map
file. The SMS logs directory does not have a install.log.

"Matthew Hudson" wrote:

Go to the drive on the secondary and look at the sms intall log. If you are
sending it over the network it will take a while. It will trickle down and
then intstall a service to complete the installation. I have see it take up
to 2 hours for the whole thing. I was forced to restart the secondary at the
end to make it appear in the central site. If the secondary is on a virtual
machine it will take 2x as long.


--
-----------------------
http://sms-hints-tricks.blogspot.com/


"spg7752" wrote:

Recently I did a clean install of SMS 2003 sp1. The primary has been up and
running for 3 days. Today I install the first of 4 secondary site servers.
It has been serveral hours since the installation. I am still not seeing the
secondary site from the SMS admin console on the primary site server in the
hierarchy. I have done this in the past with our previous SMS 2.0 sp5
environment. The secondary site showed up relatively quickly. The
installation was done from the SMS 2003 sp1 CD on the secondary site server.
Any ideas would be greatly appreciated.

Steve
.



Relevant Pages

  • SMS 2003 Rollout
    ... One central site server for site server ... no user would be assigned to this central site. ... As AD team rolls out AD, I will implement SMS. ... I am debating between client push or logon ...
    (microsoft.public.sms.setup)
  • Client Installation Method
    ... One central site server for site server ... no user would be assigned to this central site. ... As AD team rolls out AD, I will implement SMS. ... I am debating between client push or logon ...
    (microsoft.public.sms.admin)
  • Re: DRW says "Could not execute the test"
    ... logon client installation has not been enabled on the site. ... the clients assigned to the site are SMS 1.2 clients. ... database is running on SQL version 7.0 SP3 or higher. ... SMS EXECUTIVE service is running on the site server, ...
    (microsoft.public.sms.setup)
  • Re: Client Installation Method
    ... > One central site server for site server replication purpose only, no user would be assigned to this central site. ... assign them to the sms site with which they have the best connection. ... Client push installation would make it much more automated than login ...
    (microsoft.public.sms.admin)
  • Re: Installation of a Secondary Site
    ... You could do an installation initiated from an sms cd, ... initiate the installation from within the sms admin console. ... > I installed SMS 2.0 on a site server at the main office. ...
    (microsoft.public.sms.admin)