RE: SMS and Dameware

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: JRM (JRM_at_discussions.microsoft.com)
Date: 09/30/04 

Date: Thu, 30 Sep 2004 05:49:04 -0700

Mark,

Also check under Site Settings | Client Agents | Remote Tools Client Agent.
There is a check box that is 'do not install remove control components for
advanced clients running Windows XP, Windows Server 2003, or later'.

Obviously, if this box is checked - it won't install the remote tools for
XP. The reason for this is that you can just use RDC or remote assistance on
XP.

We have both DameWare and just got SMS, so we are following the same path
you are. The main reason for us is that it is easier to control who has
rights to remote control system X, and we can get reporting on it. So far
we've had no problems using both at once.

I hope that helps.

Jason

"Mark Morrell" wrote:

> Hello
> We are running Dameware NT Utilities (latest version) on a W2K domain.
> Would like to change over to SMS 2003.
> I am doing all this on a test bed.
> All machines have the latest patches/upgrades/service packs available
> The 2000 boxes (servers or workstations) don't seem to have any problem with
> both Dameware and SMS.
> The XP pro boxes (with or without SP2) do everything except remote tools.
> Says remote control agent not found.
> And yes, I turned off the new XP firewall.
> The XP box worked fine until I loaded the dameware client on it.
> I used the remove agent tool for the dameware client, still nothing.
> Also, we still have a few NT boxes around.
> SMS sees them, but won't load anything on them.
> I checked dameware's pages, no help.
> Haven't found anything in the knowledge base.
> I can keep the dameware running for the NT machines until we can upgrade
> them (but don't really want to).
>
> Any ideas how to clear out dameware so SMS remote tools will function on XP?
> Any ideas how to get the NT machines to load the client?
>
> Thanks

Relevant Pages

  • Re: Client installed but not recognized as install in the SMS MMC
    ... Have you enabled the client agents on the site server? ... the remote tools the box for Do not install on Windows XP and Windows Server ...
    (microsoft.public.sms.setup)
  • Re: Remote tools client agent.
    ... the control panel applet on the client, however, client A doesn't show ... > for the machines you can't connect remote tools to, ... >> can't after the install. ... And the fact that you can't remote control ...
    (microsoft.public.sms.admin)
  • openssh 3.5p1: PATCH
    ... - sftp transaction logging ... control over whether the client can execute chmod, ...
    (comp.security.ssh)
  • Asp.net Important Topics.
    ... ASP.NET server controls contained within the page. ... A custom server control is ... can also perform validation using client script. ... Where does the Web page belong in the .NET Framework class hierarchy? ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: XPe PXE RDP minimum config?
    ... Certificate Request Client & Certificate Autoenrollment ... Common Control Libraries Version 5 ... Shell Core Registry Data ... It is Minlogon image with fully capable RDP client running. ...
    (microsoft.public.windowsxp.embedded)