How to set Remote Desktop policies in Win10

On 1 Sep 2020 at 11:58:23 BST, "Wolffan" wrote:

On 01 Sep 2020, Chris wrote
(in article ):

On 31 Aug 2020 at 19:04:33 BST, wrote:

On 31 Aug 2020, mechanic wrote
(in article ):

On Sun, 30 Aug 2020 20:05:09 -0700, Norm Why wrote:

Hi,

I use a WinXP device to access Win10 PCs. Win10 lists errors in "Event
Viewer". How do I set 'native mode' on Win10. Details please. I wouldn't
ask
here if it was easy to find on the web.

Thanks.

It's your choice, but any reasom why you're stuck in 2001?

1 he’s using Service Pack 3, which was released in 2008

2 around here we have a few XP machines because the talk to large,
expensive,

hardware which have problems with later versions of Windows. Hardware
support

is a major reason for keeping old systems alive. We have devices which cost
$150,000 and more which won’t work if they can’t be accessed from a NT 4
to XP system, support was cut off at Vista. Sooner or later we’ll have to
replace that hardware, but it won’t be from _those_ vendors.

3 We also have ancient software which won’t run on newer systems. Software
support is another major reason to keep old systems alive. No, we don’t
see
a reason to ‘upgrade’ at the cost of hundreds of thousands when the old
system is working. Again, sooner or later we’ll have to replace the
ancient
software, but that time is not now, not while we still have XP-capable
machines.

If it ain’t broke, don’t fix it.

We have those too, but they are *not allowed* on the network or at the very
least firewalled from the internet. XP *is* broken as WannaCry amply
demonstrated and should be treated as such.

The majority of WannaCry victims were Win 7 and 8 machines which weren’t
patched and whose users din’t take security seriously. The Register has a
series of articles describing just how bad things were at the NHS prior to
WannaCry slapping them.

You don't need to tell me. My partner worked for the NHS prior to 2017 and the
situation was dire. Machines rarely on the same network, therefore
necessitating the us of USB sticks. Files or services only being available on
some machines and few controls on remote access of sensitive information.

Frankly, there should have been wholesale sacking of
senior management, especially senior IT management, after that debacle.

Yep.




I honestly think vendors of these super expensive machines should be
obligated
to keep their software current and working on newer versions of Windows.
They
know these machines can have long lifespans so should plan appropriately.
It's
not that they can't, it's that they won't.

Yep. Which is why we’ll be buying elsewhere.

Good luck. It's common practice.

On Tue, 1 Sep 2020 14:20:29 -0000 (UTC), Chris wrote:

XP *is* broken as WannaCry amply demonstrated and should be
treated as such.

The majority of WannaCry victims were Win 7 and 8 machines which weren¢t
patched and whose users din¢t take security seriously.

These statements are not mutually exclusive, by the way.

On Tue, 01 Sep 2020 06:58:23 -0400, Wolffan wrote:

[snip]
Which is why we¢ll be buying elsewhere.

Just out of interest, who's "we" in your posts, by the way?

On 01 Sep 2020, mechanic wrote
(in article ):

On Tue, 01 Sep 2020 06:58:23 -0400, Wolffan wrote:

[snip]
Which is why we’ll be buying elsewhere.

Just out of interest, who's "we" in your posts, by the way?

the company.

On Tue, 01 Sep 2020 18:20:01 -0400, Wolffan wrote:

On 01 Sep 2020, mechanic wrote
(in article ):

On Tue, 01 Sep 2020 06:58:23 -0400, Wolffan wrote:

[snip]
Which is why we¢ll be buying elsewhere.

Just out of interest, who's "we" in your posts, by the way?

the company.

And you're responsible for purchasing decisions?

On 02 Sep 2020, mechanic wrote
(in article ):

On Tue, 01 Sep 2020 18:20:01 -0400, Wolffan wrote:

On 01 Sep 2020, mechanic wrote
(in article ):

On Tue, 01 Sep 2020 06:58:23 -0400, Wolffan wrote:

[snip]
Which is why we’ll be buying elsewhere.

Just out of interest, who's "we" in your posts, by the way?

the company.

And you're responsible for purchasing decisions?

nope. I do have input into IT purchasing. The actual users have been
screaming for years about being forced to use XP. Management points out that
the machines still work, and will as long as we have XP-capable computers.
Even a newer computer with XP in a VM will do, and no, it doesn’t have to
be a newer _Windows_ computer. XP running in VMware on a Xeon box is way
faster than XP running natively on a 2005-vintage Pentium. Activation could
be a problem, but there are ways around that, too.

We’ll be having XP around for a long time, even after all of the actual old
machines have died. And we’ve still got a few spare XP machines, with
actual licenses, which were in use elsewhere and were retired and replaced by
newer machines there because _those_ machines weren’t required to talk to
ancient hardware or software. As old XP machines die they are replaced by
spares or by XP running in a VM.

Note that Hyper-V sometimes does Very Strange Things(â„¢) if you put XP on
it. Just sometimes, and not in a predictable way, just often enough to annoy.
Why, it’s almost as if Microsoft doesn’t want to support XP on _anything_
any more.