SMS 2.0 - Client Services won't install on secondary site BDC's

spikey · May 19, 1999

we are having dreadful problems with SMS2.0. Particularly cannot remote control secondary sites that are BDC's. Also the task SMSExec.exe is running at 50-80% every few minutes, basically destroying the performance of our PPRO/P2 350 servers. 
 
All secondary sites are connected via 64k Frame circuits and running NT4.SP4 and some SP5. 
 
as yet we cannot find any faith in SMS2.0 !!!!! 
 
HEEEELLLP !!!!

Trunk · May 26, 1999

We also had some problems with Remote control installing on some of our servers when we upgraded from SMS 1.2 to 2.0. On these servers, we found that a registry setting was preventing the 2.0 Remote Control from installing. 
 
On the servers in question, we would go to the following registry key: 
HKEY_LOCAL_MACHINE/Software/Microsoft/SMS/Client/Configuration/SMS 1.2 Client Migration 
 
The value "Overall 1.x migration status" would show as Pending or Failed. We changed the value to "Done". 
 
We then closed the registry editor, and went to our Client Access Point (CAP_XXX) and in the clicomp.box\remctrl\i386 directory, we ran remctrl.exe to manually install the Remote Control.

Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

SMS 2.0 - Client Services won't install on secondary site BDC's

spikey

MIS

Trunk

MIS

Similar threads

Part and Inventory Search

Sponsor