Microsoft Says Summer's Windows 10 Upgrade Fit For Business (computerworld.com)
Microsoft has moved Windows 10 August update to the Current Branch for Business release track, putting the "Anniversary Update" in the queue for automatic downloads and installation on enterprise PCs. From a report on ComputerWorld: The move will also set in motion a two-month countdown clock on support for the original mid-2015 version of Windows 10. "Windows 10 1607, also known as the Windows 10 Anniversary Update, has been declared as Current Branch for Business (CBB) and is ready for deployment," Michael Niehaus, a director of product marketing, said in a post to a company blog that used similar wording to the first upgrade to the CBB. In April, Microsoft moved the November 2015 upgrade to the corporate delivery track. Microsoft issued the Anniversary Update Aug. 2, even though its numerical designation of 1607 referred to July (07) of this year (16). The upgrade will be released in January through Windows Update, Windows Update for Business and Windows Server Update Services (WSUS), Niehaus said.
Does it involve removing the "telemetry" AKA spyware?
Just search for wsus server update windows 1607. After updating to 1607, it won't connect to the wsus server until you manually apply patches to the machine. I made that mistake of installing, but luckily I did a test run of only 10 computers.
Freedom of Speech only include discussion that are approved by the RIAA, MPAA and DMCA.
We were trialing a handful of Lenovo laptops running Windows 10 Enterprise. When the Anniversary update came, almost all of them got hosed. Most were recoverable after wasting a couple hours fiddling. One was so hosed that I gave up, reformatted the drive, and installed Windows 7 Pro.
It was that event that solidified my loathing for Windows 10. Microsoft cares more about siphoning your personal data now than putting out even a minimally viable product.
The Anniversary Update deleted the grub bootloader of my debian desktop when it was released a few months ago for desktop computers. I don't know if they fixed it since then.
As a sysad wrestling with 1607 at this very moment...
We don't choose what gets used, we're just the grunts in the field told to "Make it work".
People well above our pay grade make blind decisions and we end up paying for it.
I really wish Linux was more prevalent as an Enterprise desktop platform, but as long as people fear anything resembling change, it is what it is.
It's hard enough getting our aging data entry mooks to use Office 2010 without them falling over themselves, let alone Open Office/Libre.
The network guys at my job put in a rule at the gateway to prevent the Window 10 upgrade message from popping up in the first place. Not that any of the users have admin rights to upgrade Windows 7 to Windows 10 if they did click on the link.
So... the Windows versions before the one that isn't even coming out for half a year are not fit for business then?
That will be such a comfort for all the SMB's who were forced onto the current version, regardless of their wishes.
Why would anyone upgrade a single day before the long term extended support period ends in 2020?
I'm just kidding. I wouldn't touch Windows with YOUR ten foot pole.
Have gnu, will travel.
Well, at least we now know, or have always known, what Microsoft thinks of your business.
I agree, every time m$ chirps, I watch to see the comedy that forms the chorus.
Hyper-V??? on a desktop os?
Server 2016 is same base OS but with less UI and other stuff running. Now 2016 may have a newer Hyper-V core then windows 10.
In my experience, any shop with more than 10 users won't let you authorize ordering office supplies, let alone software, unless you are pretty high on the org chart.
Server 2016 is same OS base too. No thanks until MS hires a QA department back.
What I experienced this week; the update service crashed other services out of the blue without a clue, found out nic teaming doesn't work as expected after nic 1 was disconnected, losing connections from half the network, and DHCP loadbalancing made clients disconnect from the network often for several seconds.
Applause for Microsoft and their wondeful job of delivering a stable, high quality server OS with critical services to synchronise an administrator's email, documents and media files online and use XBox online services. *claps slowly*
home
Your job is to provide the right services for the rest of the company. If I need Photoshop or AutoCAD or Solidworks then frankly I don't give 2 shits about your religious ideological views on computer software development methodology or whether you abbreviate Microsoft with a $ sign because you don't like them. If you're not capable of doing the job of supporting the other people in the organization then you don't get the job.
If Linux was more prevalent, you probably wouldn't have a job.
Hate MS all you want, but if your job there is to fix these problems. No problems = no job. Stop trying to make your job redundant, you should be praising MS for keeping food on your table.
And no, you aren't paying for it, you're paid to deal with it.
It may seem like a subtle difference, but your paycheck says otherwise.
A little late for some quality karma whoring here but....
We have some NVR software for our IP cameras. I thought it would be a good idea to upgrade the VM running it to windows 10. Huge mistake.. I can't fsck'ing control when the damn things reboot. (This is 10 pro)
So I'm downgrading our NVR machines to win 7. Sorry MS, 10 works great on the desktop, my GPO objects mostly work, but this reboot thing is a HUGE issue.
Finally!
It's about time that they made that piece of shit fit to be used in the business environment since it's getting more difficult to get MS Windows 7.
Come on! Grandma tested it. Look Facebook loads just fine on her Acer. Go release server 2016 as we had 2 million testers and no telemetry of a single NIC teaming failure!
I know MS is bashed here often but server 2008 r2 thru 2012 r2 are actually Ok and .... RELIABLE. Yes you heard that. But without a QA department I do not know what to do when Server 2012 R2 goes EOL?
I hate being those old whippersnappers afraid of change that scatter the IT community, but with more Oracle like per core licensing of 2016 and this shitware with 10 I am afraid to move forward. If Windows 8.1 had a start menu for my users I wouldn't mind upgrading 7 to that when EOL hits soon.
But I will be fired if I deploy 10 or server in it's current state. I cannot have only 3 months to stop a feature update that breaks something??!! Worse cumulative security updates means I can't ever run legacy software and stay secure?? If one bad update from 2014 breaks a website ActiveX control I cannot have a cumulative update as it will break that control etc.
Time to think long and hard about my career as I will be fired anyway when I can't meet my 97.97% uptime required by my annual performance evaluation. Thanks Microsoft
http://saveie6.com/
I work for a 50,000+ employees company, and we're currently completing our Windows XP to Windows 7 upgrade...
So Windows 10? Maybe in 5 or 6 years?
Try it! Library of Babel