Re: Remote problem - ldwmnt.dll faulting module

Found this in the help file. Microsoft didn't happen to mention this did
they? Thanks again.

When you configure settings on the Advanced tab, the previously installed
clients do not automatically receive the new settings. For example, you might
want to change the default compression method, or the default remote access
protocol. New clients that install the Remote Control Client Agent receive
the new settings, but clients that have already installed Remote Tools do not.

To update all clients to the new settings, you can use either of two methods:

Disable Remote Tools in the SMS Administrator console, wait for all clients
to recognize the change and uninstall the Remote Control Client Agent, and
then enable Remote Tools in the SMS Administrator console.
Make the changes you want on the Advanced tab, wait for the changes to
replicate from the site server to all of the clients, and then distribute a
software package to all collections of clients that already have the Remote
Control Client Agent installed. The package updates the Remote Tools client
settings for all targeted clients.
The first method is easy, but might not be suitable for many networks
because of the brief loss of Remote Tools functionality. The second method
does not require any loss of functionality, but is not as simple to perform.
If you use software distribution, the package you create contains the
instruction to run %windir%\MS\SMS\Clicomp\Remctrl\Rchwcfg.exe (%windir%
denotes the Windows folder on the client) with a command line parameter of
install. This will cause a Remote Tools client component to recognize the
changes made on the Advanced tab and update the client settings.



"firemanf29" wrote:

>
> Microsoft Support said this was an issue with the Compression setting in
> the Remote Tools Client Agent. Change as follows:
>
> Site Hierarchy - (Site) - Site Settings - Client Agents
> Remote Tools Client Agent
> Advanced Tab
> Change "Default compression for remote control:" from "Automatically
> Select" to "Low (RLE)" and Click Apply then OK. Then change could take
> up to 25 hours to update online clients.
>
> Hope this Helps.
>
> Scott
>
>
>
> --
> firemanf29
> ------------------------------------------------------------------------
> Posted via http://www.mcse.ms
> ------------------------------------------------------------------------
> View this thread: http://www.mcse.ms/message1627756.html
>
>
.

Relevant Pages

  • Windows Update Server question/problem
    ... the clients Windows Update was set to ... DOWNLOAD, notify but do not install. ... I can make no changes to these settings on the client. ...
    (microsoft.public.windows.server.sbs)
  • Re: Vista - User Directory
    ... service "owns" the data and the clients just use/update it. ... even create a shared folder, who you wish to allow to share it, etc., etc.) Alternatively, ... So the user-specific settings remain (simple things like what printer to use, ... we install and run fine on Vista/7. ...
    (microsoft.public.vc.mfc)
  • Re: Windows Update Server question/problem
    ... am running the SBS Update Services. ... the clients Windows Update was set to ... notify but do not install. ... I can make no changes to these settings on the client. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant i have define any secondary client installation type?
    ... Client Install Type or Settings for Remote Tools? ... don't want to ask and set a different policy in the admin console. ...
    (microsoft.public.sms.admin)
  • Re: Should WSUS force clients to install updates?
    ... I ended up uninstalling/reinstalling WSUS, checking all possible settings. ... from a command line and now the client says Option 4 Scheduled Install. ... So it apears that the clients are not picking up the needed setting to ...
    (microsoft.public.windows.server.sbs)
Loading