Flash player not detected. Click here to install flash.
« 1 2 3 4 5 »

Win-ning friends in the workplace and hoping you hate group policy

Subject: General Tech | May 23, 2017 - 03:08 PM |
Tagged: microsoft, Win 10, enterprise

Microsoft is continuing with their policy of self inflicted hurdles for Enterprise adoption of Windows 10.  We have known for a while that Group Policy no longer works as expected on the new version of Windows and today The Inquirer posted more exact information this particular issue.  A security researcher locked down a machine using Group Policy settings and found that even with policies in place to prevent certain protocols and services, the machine continued to attempt connections.  The most damning proof of all was on a machine set to extreme security, with all but connections to Microsoft Update blocked, that still happily attempted to connect to advertising servers.  The marketshare of Win 10 devices in the workplace does not look to be on the rise any time soon.

IC180010.gif

"On Monday, we revealed that a security researcher had used a packet sniffer to show that many settings designed to prevent access to the internet were being ignored with connections to a range of third party servers including advertising hubs."

Here is some more Tech News from around the web:

Tech Talk

 

Source: The Inquirer
Subject: Motherboards
Manufacturer: MSI

Introduction and Technical Specifications

Introduction

02-board.jpg

Courtesy of MSI

The MSI Z270 Gaming Pro Carbon board features a black PCB with carbon fiber overlay covering the board's heat sinks and rear panel cover. MSI also liberally sprinkled RGB LED-enabled components across the board's surface and under the board for an interesting ground effects type look. The board is designed around the Intel Z270 chipset with in-built support for the latest Intel LGA1151 Kaby Lake processor line (as well as support for Skylake processors) and Dual Channel DDR4 memory running at a 2400MHz speed. The Z270 Gaming Pro Carbon can be found in retail with an MRSP of $174.99.

03-board-profile.jpg

Courtesy of MSI

04-board-flyapart.jpg

Courtesy of MSI

MSI integrated the following features into the Z270 Gaming Pro Carbon motherboard: six SATA III 6Gbps ports; two M.2 PCIe Gen3 x4 32Gbps capable ports with Intel Optane support built-in; an RJ-45 Intel I219-V Gigabit NIC; three PCI-Express x16 slots; three PCI-Express x1 slots; a Realtek ALC1220 8-Channel audio subsystem; integrated DVI-D and HDMI video ports; and USB 2.0, 3.0, and 3.1 Type-A and Type-C port support.

05-military-class-v.jpg

Courtesy of MSI

To power the Z270 Gaming Pro Carbon motherboard, MSI integrated a 10 phase (8+2) digital power delivery system dubbed Military Class V. The Military Class V integrated components included Titanium chokes, 10 year-rated Dark capacitors, and Dark chokes.

06-rear-panel-flyapart.jpg

Courtesy of MSI

Continue reading our preview of the MSI Z270 Gaming Pro Carbon motherboard!

Manufacturer: The Khronos Group

The Right People to Interview

Last week, we reported that OpenCL’s roadmap would be merging into Vulkan, and OpenCL would, starting at some unspecified time in the future, be based “on an extended version of the Vulkan API”. This was based on quotes from several emails between myself and the Khronos Group.

Since that post, I had the opportunity to have a phone interview with Neil Trevett, president of the Khronos Group and chairman of the OpenCL working group, and Tom Olson, chairman of the Vulkan working group. We spent a little over a half hour going over Neil’s International Workshop on OpenCL (IWOCL) presentation, discussing the decision, and answering a few lingering questions. This post will present the results of that conference call in a clean, readable way.

khronos-officiallogo-Vulkan_500px_Dec16.png

First and foremost, while OpenCL is planning to merge into the Vulkan API, the Khronos Group wants to make it clear that “all of the merging” is coming from the OpenCL working group. The Vulkan API roadmap is not affected by this decision. Of course, the Vulkan working group will be able to take advantage of technologies that are dropping into their lap, but those discussions have not even begun yet.

Neil: Vulkan has its mission and its roadmap, and it’s going ahead on that. OpenCL is doing all of the merging. We’re kind-of coming in to head in the Vulkan direction.

Does that mean, in the future, that there’s a bigger wealth of opportunity to figure out how we can take advantage of all this kind of mutual work? The answer is yes, but we haven’t started those discussions yet. I’m actually excited to have those discussions, and are many people, but that’s a clarity. We haven’t started yet on how Vulkan, itself, is changed (if at all) by this. So that’s kind-of the clarity that I think is important for everyone out there trying to understand what’s going on.

Tom also prepared an opening statement. It’s not as easy to abbreviate, so it’s here unabridged.

Tom: I think that’s fair. From the Vulkan point of view, the way the working group thinks about this is that Vulkan is an abstract machine, or at least there’s an abstract machine underlying it. We have a programming language for it, called SPIR-V, and we have an interface controlling it, called the API. And that machine, in its full glory… it’s a GPU, basically, and it’s got lots of graphics functionality. But you don’t have to use that. And the API and the programming language are very general. And you can build lots of things with them. So it’s great, from our point of view, that the OpenCL group, with their special expertise, can use that and leverage that. That’s terrific, and we’re fully behind it, and we’ll help them all we can. We do have our own constituency to serve, which is the high-performance game developer first and foremost, and we are going to continue to serve them as our main mission.

So we’re not changing our roadmap so much as trying to make sure we’re a good platform for other functionality to be built on.

Neil then went on to mention that the decision to merge OpenCL’s roadmap into the Vulkan API took place only a couple of weeks ago. The purpose of the press release was to reach OpenCL developers and get their feedback. According to him, they did a show of hands at the conference, with a room full of a hundred OpenCL developers, and no-one was against moving to the Vulkan API. This gives them confidence that developers will accept the decision, and that their needs will be served by it.

Next up is the why. Read on for more.