Microsoft today delivered a new Windows 10 build that includes changes designed to address long-standing complaints about the operating system’s update practices.
Testers—those registered with the Windows Insider program and on its “Fast” release track—were handed build 15002 today. Dona Sarkar, the Microsoft software engineer who serves as the public face and voice for Insider, called 15002 “a BIG update” in a post to a company blog that spelled out a slew of changes.
Among them are several related to how Microsoft updates the OS.
Users can now pause updates for up to 35 days, although it was unclear which updates can be postponed.
All Insiders can put updates on pause, but when the feature goes live with the next upgrade to all customers, the switch will not be offered to consumers running Windows 10 Home. Instead, the option will be available only in the more expensive—and largely business-oriented—Windows 10 Pro, Windows 10 Enterprise and Windows 10 Education.
Microsoft has made a habit of providing the most update and upgrade flexibility to users of Pro, Enterprise and Education; Windows 10 Home users, for example, are required to adopt updates as soon as the Redmond, Wash. company serves them up.
Sarkar did not elaborate on which updates would be delayed by the new pause; Microsoft did not reply to requests for clarification.
But if security updates are among those put on pause, the option would address complaints from some business customers who have argued that there should be a way to postpone patches from landing on their PCs. IT administrators using a patch management system, such as Microsoft’s Windows Server Update Services (WSUS) and System Center Configuration Manager (SCCM), or a third-party product like Shavlik Protect, already can delay updates.
Some administrators regularly delay patching as a kind of quality control, assuming that any problems will be uncovered by others, then fixed by Microsoft.
However, organizations that rely on Microsoft’s Windows Update or Windows Update for Business services have not had a delay option for security updates: The pause feature, if it applied to patches, would serve that purpose.
Also in build 15002 is the addition of an ethernet-based Internet connection to those which Windows 10 monitors as “metered.” Previously, only connections based on a Wi-Fi network or cellular data—a link to the Internet from a smartphone, for instance, including one that’s been set to serve as a Wi-Fi “hotspot” for a nearby PC—could be metered.
Because some customers rely on a capped connection where every downloaded byte is tallied by their ISP (Internet service provider), Windows 10 will forgo downloading most updates—including security patches—until it recognizes a non-metered connection or is told that one is present. The idea: Delay large downloads that would exhaust the month’s supply of allowed data until the user is in a location— a public hotspot, say—where the Internet can be accessed without penalty.
Windows 10 Home users have exploited the metered connection setting since the OS’s mid-2015 launch as one way to postpone forced updates and upgrades. However, those whose ISPs delivered a connection via ethernet—cable companies typically use ethernet between the modem and PC—could not, until build 15002, employ that trick.
The changes and additions in build 15002 will be included in the next major upgrade, flagged as “Windows 10 Creators Update.” Microsoft has not yet set a release date for the upgrade, but clues uncovered last year hinted at a March launch .

© Source: http://www.infoworld.com/article/3156186/microsoft-windows/microsoft-lets-some-windows-10-users-hit-pause-on-updates.html
All rights are reserved and belongs to a source media.

Bridging the gap between development and the infrastructure teams is the deployment specialist. These days, the job is often titled DevOps specialist, indicating how these two worlds are being merged. You can see how this role started in » Anatomy of a Software Development Role: Deployment. »
Image source: https://www.flickr.com/photos/wocintechchat/25926827581/
Author: WOCinTech Chat
A: The goal here is to get the candidate to articulate what source control conditions should be met before a full build. For instance, there may be a requirement that third-party analysis tools be run before a build can be performed or scheduled. A candidate may also suggest that, in some cases, before code can be checked in for a build, it might need a code review.
Image source: https://www.flickr.com/photos/onepointfour/6310364447/
Author: Dustin Gaffke
A: A candidate should recognize that scheduled builds work well when there are a large number of developers on the team who may cause overlapping builds to happen (or to need to be prevented). On-demand builds are appropriate for projects with fewer developers, and when it makes sense for developers to iterate on each other’s work several times a day.
Image source: https://www.flickr.com/photos/dafnecholet/5374200948/
Author: Dafne Cholet
A: A candidate’s answer should include how production data is moved to the QA environment on a schedule. They should mention how the data is partitioned, so only some of the data comes back to the QA environment, and how the data is anonymized where that is required.
Image source: https://pixabay.com/en/glass-water-ice-cubes-drink-cold-1206584/
Author: ColiN00B
A: Environments should have barriers preventing them from talking to one another, so that the production system doesn’t use services from the developer workstations or the integration environments.
Image source: https://www.flickr.com/photos/arthur-caranta/3007271737/
Author: Arthur Caranta
A: Configuration is tricky to manage because the developer adds new configuration options to the software, and each environment has its own configuration files. A candidate should discuss that, typically, there is a merge process to create final configuration files out of parts that are solution-specific as well as some which are environment-specific.
Image source: http://m23.sourceforge.net/PostNuke-0.750/html/gfx/network_diagram.png
No author listed, from m23.sourceforge.net
A: The answer can be MSI, ZIP, or any suitable mechanism. The intent of the question is to identify the packaging mechanisms that the candidate is familiar with and has used.
Image source: https://www.flickr.com/photos/bods/2286095630/
Author: Andrew Bowden
A: Smoke tests are designed to quickly indicate a successful or failed deployment. The answer here should include automated or semi-automated execution of smoke tests, and a candidate should identify the kinds of tests that should be used to quickly assess whether or not the deployment was successful.
Image source: https://www.flickr.com/photos/centophobia/3457073907/
Author: Centophobia
A: A typically overlooked process is what happens when the build fails to deploy to an environment. Understanding the steps that are taken—and that there are ways to recover—is the key to this question.
Image source: https://www.flickr.com/photos/campuspartyeurope/7858311034/
Author: Campus Party Europe in Berlin
A: Generally, test environments are deprovisioned because there are a maximum number of environments that can be active at any one time—or because a time limit has expired. Conditions may dictate that users are notified before an environment is recycled.
Image source: https://www.flickr.com/photos/rhysasplundh/5202454842/
Author: Rhys A.
A: Because builds should be signed—and impossible to produce a version of the software not created on the build server—keeping the certificates and private keys restricted is important. However, developers need to be able to build the software for their testing. The response should discuss how a candidate can build for themselves while only the build server creates official builds.
Image source: https://pixabay.com/en/privacy-policy-keyboard-security-510731/
Author: succo
Bridging the gap between development and the infrastructure teams is the deployment specialist. These days, the job is often titled DevOps specialist, indicating how these two worlds are being merged.
Your name/nickname
Your email
Subject
(Maximum characters: 1200). You have characters left.

© Source: http://www.developer.com/mgmt/slideshows/ten-deploymentdevops-interview-questions-you-should-know.html
All rights are reserved and belongs to a source media.

Things are all change at Yahoo. The sale of the company to Verizon appears to be going ahead — despite a series of setbacks along the way, including a high-profile data breach — for $4.83 billion, and when the deal does go through, Marissa Mayer will step down from the board.
While many news reports today state that Yahoo is now called (or will be) Altaba, this is not strictly true. Verizon is not buying Yahoo in its entirety; a 15 percent stake in Alibaba and a 35.5 percent stake in Yahoo Japan will live on as an investment company going under the new name of Altaba Inc. Details of the changes are revealed in an SEC filing.
Yahoo’s filing to the Securities and Exchange Commission shows that when the Verizon deal completes — subject to the necessary regulatory approval — existing board members David Filo, Eddy Hartenstein, Richard Hill, Jane Shaw, Maynard Webb, and Marissa Mayer will step down from their positions. There is no suggestion, at this stage, that Mayer will resign her role as CEO.
It’s fair to say that the Yahoo we have come to know is dead. Signaling this, the SEC filing states:
It goes on to say:
At most, it is a division rebranding.
We don’t yet know exactly what plans Verizon has for Yahoo, but we can expect to see the existing search engine, webmail and other services integration into AOL (owned by Verizon) products. It expected that the Yahoo name will live on as this is something that has already been indicated by AOL. The deal with Verizon is expected — barring any further hiccups — to be finalized in the first quarter of this year.
Image credit: jejim / Shutterstock.com

© Source: http://feeds.betanews.com/~r/bn/~3/x5YY5-Hlbf8/
All rights are reserved and belongs to a source media.

The Investigatory Powers Act 2016 — better known to many as the snooper’s charter — faced massive public criticism in the run-up to becoming law at the end of 2016 for the privacy-invading powers it affords the UK government to gather data about internet usage.
Towards the end of the year, the European Court of Justice ruled that the «general and indiscriminate retention» of internet data and communication is illegal, potentially threatening the Investigatory Powers Act. Now the human rights group Liberty is launching its own legal attack on the Act, asking for a High Court judicial review of the bulk surveillance powers that have been voted into law.
The campaign group says that the Act goes too far, adding its voice to increasingly loud calls for the legislation to be amended or repealed. Of particular concern is the fact that the Act allows for the collection of data about any internet user, regardless of whether they are suspected of wrong-doing. Liberty director Martha Spurrier says:
Taking on the government has the potential to be an expensive affair, and Liberty is hoping to crowdfund its legal challenge. On its website the group says:
Specifically, Liberty is seeking to test the legality of four powers brought in by the Investigatory Powers Act:
The government says that it intends to » vigorously defend these vital powers».
Image credit: focusimage / Shutterstock

© Source: http://feeds.betanews.com/~r/bn/~3/n2vlfgwPipk/
All rights are reserved and belongs to a source media.