How to set Remote Desktop policies in Win10

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.

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.

I just used Remote Desktop to access a Win 10 system from an XP system and
I don't see any errors in Win 10's Event Log. What should I be looking for?

"Char Jackson" wrote in message
...
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.

I just used Remote Desktop to access a Win 10 system from an XP system and
I don't see any errors in Win 10's Event Log. What should I be looking
for?


Look for 'remote-desktop-services- and 'terminal-services-
You should see them in "Administrative Events".

My WinXP is WinXP Professional Version 2002, Service Pack 3. Maybe a better
WinXP version exists?

"Norm Why" wrote in message
...
"Char Jackson" wrote in message
...
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.

I just used Remote Desktop to access a Win 10 system from an XP system
and
I don't see any errors in Win 10's Event Log. What should I be looking
for?


Look for 'remote-desktop-services- and 'terminal-services-
You should see them in "Administrative Events".

My WinXP is WinXP Professional Version 2002, Service Pack 3. Maybe a
better WinXP version exists?

I should mention my WinXP machine is 32-bit. Maybe 64-bit is better?

On Sun, 30 Aug 2020 22:55:49 -0700, "Norm Why"
wrote:

"Char Jackson" wrote in message
.. .
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.

I just used Remote Desktop to access a Win 10 system from an XP system and
I don't see any errors in Win 10's Event Log. What should I be looking
for?


Look for 'remote-desktop-services- and 'terminal-services-
You should see them in "Administrative Events".

OK, thanks. I see a (harmless) warning letting me know that redirection of
USB devices is disabled by policy. That's not a problem for me and I'm
aware of the policy.

Are you seeing additional or different errors in your Win 10 event logs?
Does Remote Desktop work for you? If not, have you tried disabling the
option to "Allow connections only from computers running Remote Desktop
with Network Level Authentication"?

My WinXP is WinXP Professional Version 2002, Service Pack 3. Maybe a better
WinXP version exists?

No, you're about as up to date as possible, given that you're using XP. And
32 bit is also probably right where you should be with XP.

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?

On Mon, 31 Aug 2020 11:27:10 +0100, mechanic wrote:

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

The question mechanic asks is...
o What is on Windows 10 that he needs that's not already on Windows XP?

Those who haven't asked that question might be surprised by the answers.

o What can you do on Windows 10 that you can't do on Windows XP or Windows 7?
https://groups.google.com/forum/#!topic/microsoft.public.windowsxp.general/fJBY472ds3E
--
Almost all "new" versions of mature software are mere marketing promotions.

mechanic wrote:
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?

He's using an OS that lets him get work done.

It's a concept.

Windows 10 is just not daily driver material.
It's too busy doing its nails and washing its hair,
to care about anyone else.

Paul

On Mon, 31 Aug 2020 11:46:31 -0400, Paul wrote:

He's using an OS that lets him get work done.

I worked in the Silicon Valley for decades, much of it in software
marketing (among other startup endeavors) where I learned first hand how
desperate MARKETING is for a "new version" of software.

Much like they put "New Improved" on California egg cartons, it's almost
always simply a repackaging of the same old stuff (sometimes worse, as in
the case of the Windows 10 tiled menus compared to the XP cascade menu).

Besides...

Long ago we already asked the question, outside of the fact that Microsoft
won't support XP, what FUNCTIONALITY is in Windows 10 that hasn't already
been in every other Windows operating system for the past two decades.

We could barely scrape up anything that the later Windows does that the
earlier Windows already did.

Details he
o What can you do on Windows 10 that you can't do on Windows XP or Windows 7?
https://groups.google.com/forum/#!topic/microsoft.public.windowsxp.general/fJBY472ds3E

Similar story with MS Office:
o What useful functionality is in the newer Microsoft Office that isn't already in the older MSOffice 2007 Pro?
https://groups.google.com/forum/#!topic/microsoft.public.windowsxp.general/sKGer09EakA
--
In general, in my experience, most if not all "new" versions of mature
software are mere MARKETING shenanigans which only the ignorati fall for.

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.

Wolffan wrote:

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

Is there an issue with enabling/enforcing Network Level Authentication
between WinXP and Win10?

Is it even possible to patch WinXP for the CredSSP encryption oracle issue?

On Mon, 31 Aug 2020 14:04:33 -0400, Wolffan wrote:

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

Trouble is, it was broke, as many XP users (inluding many in the NHS
in the UK) found when WannaCry ran riot through their systems.

On 31 Aug 2020 at 19:04:33 BST, "Wolffan" 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.

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.

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

On Mon, 31 Aug 2020 14:04:33 -0400, Wolffan wrote:

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

Trouble is, it was broke, as many XP users (inluding many in the NHS
in the UK) found when WannaCry ran riot through their systems.

That’s why you keep XP machines on a subnet which can’t access the
Internet. Our XP machines are on their very own little network, no wireless,
optical drives and USB except for keyboard and mouse turned off in BIOS, no
floppy drives, one admin user which is not normally used, standard users with
restrictions so that any damage from malware is strictly limited. According
to El Reg, the majority of WannaCry targets at NHS were Winb 7, not XP.
https://www.theregister.com/2017/10/..._wannacry_says
_nao_report/

Quote:
______
"NHS Digital told us that the majority of NHS devices infected were unpatched
but on supported Microsoft Windows 7 operating systems."

Unsupported devices, those on XP, were in the minority of identified issues.
_______
Unquote.

What nailed the NHS was that they didn’t properly patch and didn’t take
proper security seriously.

We take security seriously.

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. Frankly, there should have been wholesale sacking of
senior management, especially senior IT management, after that debacle.


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.