RE: [NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

Not going to happen. It’s going to require new processors. Everything being released is a mitigation, not a “fix”. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Ed Ziots Sent: Tuesday, January 9, 2018 4:27 PM To: ntsysadm@lists.myitforum.com Subject:

RE: [NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

You need the a/v registry key in order to get the patch via MU/WU to start with. The other two (for servers) are only needed if you are running Hyper-V in Win10. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael Leone Sent: Tuesday, January 9,

Re: [NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

On Tue, Jan 9, 2018 at 5:08 PM, Mike wrote: > For CVE-2017-5754 [rogue data cache load] you are good as the PCID line > doesn't impact security. > For CVE-2017-5715 [branch target injection] you need a > microcode/BIOS/firmware update. > > The Windows patch is

Re: [NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

Got similar like yours The results didn't changed until after running the Dell Command Update (which installed "Installed Management Engine Components Installer") and installing the BIOS update for the Dell Optiplex, the new result is [cid:ecc93508-926d-4802-a560-def9c99546d7]

Re: [NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

On Tue, Jan 9, 2018 at 4:53 PM Art DeKneef wrote: > What systems are you seeing this with? You seem to be bouncing back and > forth between servers and clients making it confusing to follow. > Not at all. As the post says, I'm asking about workstation OSes, Win10 and Win

Re: [NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

For CVE-2017-5754 [rogue data cache load] you are good as the PCID line doesn't impact security. For CVE-2017-5715 [branch target injection] you need a microcode/BIOS/firmware update. The Windows patch is installed *Windows OS support for branch target injection mitigation is present: True*

RE: [NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

What systems are you seeing this with? You seem to be bouncing back and forth between servers and clients making it confusing to follow. For servers Microsoft has stated to help protect servers you need: 1. Apply the Windows OS system update released on Jan. 3, 2018. 2. Make

Re: [NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

It would be nice if intel and amd released.processor or bios.firmware update to.fix the flaw.once and all. On Jan 9, 2018 2:24 PM, "Michael Leone" wrote: > Here's something (more) I am confused about. Suppose I have Win 7 and Win > 10 workstations, and I have properly

Re: [NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

I've already issued the registry entries, so it looks like this: Speculation control settings for CVE-2017-5715 [branch target injection] Hardware support for branch target injection mitigation is present: False Windows OS support for branch target injection mitigation is present: True Windows

Re: [NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

Interesting. Can you post the output of the Get-SpeculationControlSettings command? On Tue, Jan 9, 2018 at 3:12 PM, Michael Leone wrote: > On Tue, Jan 9, 2018 at 3:00 PM, Mike wrote: > >> You only need the Registry entries on Server versions. >>

Re: [NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

On Tue, Jan 9, 2018 at 3:00 PM, Mike wrote: > You only need the Registry entries on Server versions. > You do need hardware support to protect against CVE-2017-5715. > > Run the Get-SpeculationControlSettings PowerShell command to get the > details. >

Re: [NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

You only need the Registry entries on Server versions. You do need hardware support to protect against CVE-2017-5715. Run the Get-SpeculationControlSettings PowerShell command to get the details. https://gallery.technet.microsoft.com/scriptcenter/Speculation-Control-e36f0050 On Tue, Jan 9, 2018

[NTSysADM] Are the Meltdown/Spectre reg keys needed for workstations?

Here's something (more) I am confused about. Suppose I have Win 7 and Win 10 workstations, and I have properly patched the OS. Do I *also* need to issue the 2 (or is it 3) registry entries? I *thought* the registry entries were only for servers, but I have seen other statements that say that the

[NTSysADM] RE: Surface and rdp small display

Here is a manifest file that is working on my Book that is on Anniversary. Be sure to make the reg edit in the link I sent previously and reboot. It also works for Outlook and the old versions of Photoshop, just need to rename it and drop it in the right directory. From:

[NTSysADM] RE: Surface and rdp small display

I told him it was time for the bifocals. He told me his private life was none of my business? lol From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Andrea 'ML' Suatoni Sent: Tuesday, January 9, 2018 11:20 AM To: ntsysadm@lists.myitforum.com Subject:

[NTSysADM] RE: Surface and rdp small display

Well, I don't know if it fits in your environment, but due to that precise DPI issue I've switched to mRemoteNG as RDP client when I started using a Surface, and it works perfectly. No more Lilliputian remote desktops since then. Andrea From: listsad...@lists.myitforum.com

[NTSysADM] RE: Surface and rdp small display

Yeah. Doesn't play nice from a surface. Applied the hotfix to the destination workstation. Rebooted. Not I think I am going into the display settings on the Surface and reducing them from 2billionx1billion (exaggerated). Down to 1280x800 or something reasonable. This seems to be playing nice.

[NTSysADM] RE: Surface and rdp small display

Ugh. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Kennedy, Jim Sent: Tuesday, January 9, 2018 9:57 AM To: ntsysadm@lists.myitforum.com Subject: [NTSysADM] RE: Surface and rdp small display Notice: This email is from an outside source. Please do

[NTSysADM] RE: Surface and rdp small display

*Disclaimer, have never used a Surface so unsure of screen size. Have you changed the Display configuration within the RDP session itself to a higher resolution? That normally increases the screen size of the RDP session. Click on Show Options before connecting

Re: [NTSysADM] Surface and rdp small display

Windows 10 using the RDP app from the Store? If so you can try playing around with the scaling settings in that app. On Tue, Jan 9, 2018 at 9:45 AM, David McSpadden wrote: > I have been reading and applying hotfixes to my CFO’s surface but the RDP > session is so small he

[NTSysADM] RE: Surface and rdp small display

You need a manifest file, however I believe MS blew that up in the Anniversary edition. http://pocketnow.com/2016/01/25/hidpi-scalling-in-windows-10 From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of David McSpadden Sent: Tuesday, January 9, 2018 9:46 AM

[NTSysADM] Surface and rdp small display

I have been reading and applying hotfixes to my CFO's surface but the RDP session is so small he cannot use his Surface to remote into his workstation in the office. What should I be really doing to fix this? David McSpadden Systems Administrator Indiana Members Credit Union P: 317.554.8190|