Quote:> Rebuilt my SMS server. Previously was NT 4.0, sp6, SQL 7.0 member
> server. Now is 2k, SQL 2k. Able to bring database back online.
> Prior to my rebuild, I disabled logon and discovery, stopped NT logon
> and SMS executive services on BDCs and removed associated registry
> keys. How do I get the BDCs to start acting as CAPs and logon points
> again? My original configuration had each of the install and
> discovery methods turned on and after the rebuilt they remained like
> that. Do I need to disable and re-enable the logon and discovery
I am rebuilding an SMS Server that is a CAP, Distribution Point (1 GB
Size), and Software Source point (1GB Size) for all SMS packages. My
goal is to get the new server back up and running as quickly as
possible. My site is a child site, but the software source holds
packages for both the parent and child. There is another CAP and
Distribution point in my site until the new server gets back up and
I would like to restore the package adminstrative share (smspkge$) and
the CAP_(SITE Code) directory from backup to get it up and running
quicker. I'm not sure what registry entries go along with it and if
that will cause me grief.
Or, should I do it through the SMS snap in and let it take longer.
Will client systems react to the new CAP differently if it's the same
Anyone do the same process and have feedback ?