RE: Failed upgrade to SCCM

When you only see 2 actions, that generally means that the client cannot
contact a Management Point to obtain policies. Troubleshooting can be
complex; there are different paths to take if you've extended AD or not.

A couple places to start:
- in SMS Toolkit 2 is "MP Troubleshooter", use that to see if the MP itself
is OK
- check logs on the client; what MP is it trying to contact (if any?)
- Are you 100% sure that's the correct site code? For example, Advanced
clients cannot belong to a secondary site code--it has to be the primary site
code. If you inadvertently put in the secondary site code, change it to the
Primary site code.
--
Standarize. Simplify. Automate.


"Chris" wrote:

Sorry for the long post, I just wanted to get as much detail in as possible.

I recently started the upgrade our SMS 2003 SP3 Server to SCCM. Our setup is
a single site / server with one child site although the child site had
recently failed so I removed it from the SMS Console before starting the
upgrade. The SQL Server is a remote server that is shared with other
applications.

The prerequisite checker passed for everything except inactive clients and
SQL Server security mode and as we require the SQL server to be in SQL &
Windows Authentication mode we cannot change this. I started the
installation and everything seemed to be going well until the very end where
everything completed successfully except "Install management point" and (I
think) "Install site control manager" with status "Unknown" I pressed finish
and attempted to open the ConfigMgr Console however it hung on loading.

I have tried re-running the upgrade again however it now pops up an error
message saying it cannot deinstall SMS components from the server in the
failed child site that was removed. If I ignore that, it continues on
however fails at "Install SMS provider components".
I have done plenty of reading and the error points to either WMI or SPN's
however if either of these were an issue, wouldn't it have picked it up
during the original failed install? I have double checked the SPN's and
re-registered WMI components however SCCM will not reinstall. After a couple
of failed upgrade attempts, I tried the Site Repair Wizard however it has
started returning a Provider Load Error so it does look like WMI, I'm just
not sure what caused WMI to fail after the first upgrade attempt.

I'm done with trying to recover this install so I need to know what my
options are for recovering the Site with our existing data? Can I uninstall
the single site completely and then reuse our existing SQL database with a
fresh SCCM installation. I have SQL backups from both before and after the
upgrade so I could even return to SMS if I had to. Unfortunately, I
discovered after the fact that we don't have any backups of the SMS Site
server itself as the previous IT guys had never installed the backup agents
on the server.

Thanks in advance,
Chris

.

Relevant Pages

  • Re: Fax on Terminal Server from SBS2K3
    ... please make sure the Fax service is installed on the TS server. ... you can try the steps below to install Shared Fax Client: ... 248340 Installing and Using Programs in Windows 2000 Terminal Services ...
    (microsoft.public.windows.server.sbs)
  • RE: Fax monitor incoming + outgoing calls?
    ... The detail steps to install share fax client as follows: ... Start server management console, locate Client Computers node, click ... To the folder redirection GPO issue: ... How to stop Folder Redirection in Windows Server 2003 and in Windows 2000 ...
    (microsoft.public.windows.server.sbs)
  • RE: No Client or Server Desktop Access Through RWW SBS 2003 SP2
    ... The SBS server is running SP2. ... However I don't know if the client computers do. ... To successfully install SBS 2003 SP1, ...
    (microsoft.public.windows.server.sbs)
  • Re: Fax on Terminal Server from SBS2K3
    ... activity logging in the shared fax in the server box. ... Microsoft CSS Online Newsgroup Support ... Follow the wizard to install Shared ... you can try the steps below to install Shared Fax Client: ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Fax Sharepoint Routing
    ... Business Server 2003 and click "Change/Remove", ... If the Fax Services component was original installed by using the SBS ... Install fro the Fax Server component. ... And then we should push the shared fax client application from server to ...
    (microsoft.public.windows.server.sbs)