Paul Williams [MVP]
2006-06-08 11:37:09 UTC
Afternoon all,
In the process of deploying SMS 2003 SP2 to a couple of small enterprises -
~5,000 clients each.
Anyway, we've hit a strange problem where the SMS client is failing on a
bunch of XP SP1 systems. Looking through the logs it is failing when trying
to install BITS. We tried a bunch of suggestions that we found in these
groups and none of them were working. We thought it might be an issue with
the Windows installer, so we got one of the desktop guys to install Windows
Installer 3.1 v2. Since this has been installed the CCMSETUP service won't
start, so we can't get to where we were before (MSI installation fails re.
BITS).
Standard SCM error - service didn't respond to the control in a timely
fashion.
Any ideas what's going on? The only change that I can see is the
installation of installer. We also had to rename the cryptography database
as that was corrupt and stopping the installer from installing.
To be sure, I removed the CCMSETUP folder and service (from the registry)
and initiated the push again (client push from management server) and the
same happens. I'm a couple of hundred miles from site and SMS v2 has
deinstalled, so can't remote control the box. I can RCONSOLE onto there,
which I've done and tried running \\sms\smsclient\i386\ccmsetup but that
didn't do much, and I can't run the MSI as I don't have interactive access
to the console -only CMD.
Any help or suggestions appreciated. This has stopped the rollout dead.
:-(
In the process of deploying SMS 2003 SP2 to a couple of small enterprises -
~5,000 clients each.
Anyway, we've hit a strange problem where the SMS client is failing on a
bunch of XP SP1 systems. Looking through the logs it is failing when trying
to install BITS. We tried a bunch of suggestions that we found in these
groups and none of them were working. We thought it might be an issue with
the Windows installer, so we got one of the desktop guys to install Windows
Installer 3.1 v2. Since this has been installed the CCMSETUP service won't
start, so we can't get to where we were before (MSI installation fails re.
BITS).
Standard SCM error - service didn't respond to the control in a timely
fashion.
Any ideas what's going on? The only change that I can see is the
installation of installer. We also had to rename the cryptography database
as that was corrupt and stopping the installer from installing.
To be sure, I removed the CCMSETUP folder and service (from the registry)
and initiated the push again (client push from management server) and the
same happens. I'm a couple of hundred miles from site and SMS v2 has
deinstalled, so can't remote control the box. I can RCONSOLE onto there,
which I've done and tried running \\sms\smsclient\i386\ccmsetup but that
didn't do much, and I can't run the MSI as I don't have interactive access
to the console -only CMD.
Any help or suggestions appreciated. This has stopped the rollout dead.
:-(
--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net