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!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

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

Status
Not open for further replies.

spikey

MIS
May 19, 1999
1
GB
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.<br>
<br>
All secondary sites are connected via 64k Frame circuits and running NT4.SP4 and some SP5.<br>
<br>
as yet we cannot find any faith in SMS2.0 !!!!!<br>
<br>
HEEEELLLP !!!!
 
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.<br>
<br>
On the servers in question, we would go to the following registry key:<br>
HKEY_LOCAL_MACHINE/Software/Microsoft/SMS/Client/Configuration/SMS 1.2 Client Migration<br>
<br>
The value "Overall 1.x migration status" would show as Pending or Failed. We changed the value to "Done".<br>
<br>
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.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top