Jump to content

Recommended Posts

Posted (edited)
So to get this right, Enterprise will have Edge but can't be updated?

You're 50% there. :)

 

The Enterprise edition, like almost all editions of Windows 10, will include Edge and keep it up-to-date by default but if you switch one or more computers to the special Long-Term Servicing Branch - designed primarily for mission critical devices such as hospital PCs - those devices will only receive security and hotfixes from that point on.

 

... the reason Microsoft won't provide Edge to Enterprise users on LTSB is because the company expects to roll out new features and feature updates to Edge on a regular basis, as both Gartner and Microsoft officials note. That means it would be kind of pointless to include the evolving Edge browser if it's not going to be updated.

 

Computers running the Enterprise edition of Windows 10 that are NOT on the Long-Term Servicing Branch will continue to receive new features including updates to Edge.

 

In a school environment, the LTSB would be perfect for computers that run the cashless catering tills, heating system, digital signage or kiosk-type devices since they will still receive security updates each month, but not updates that add new features.

 

The article below explains how the different update branches work.

 

https://blogs.windows.com/business/2015/01/30/windows-10-for-enterprise-more-secure-and-up-to-date/

 

Many consumers today expect their devices to receive ongoing feature updates without having to take an action. However, we understand that businesses require more control in how updates are delivered, and at what pace.

 

For example, systems powering hospital emergency rooms, air traffic control towers, financial trading systems, factory floors, just to name a few, may need very strict change management policies, for prolonged periods of time. To support Windows 10 devices in these mission critical customer environments we will provide Long Term Servicing branches at the appropriate time intervals. On these branches, customer devices will receive the level of enterprise support expected for the mission critical systems, keeping systems more secure with the latest security and critical updates, while minimizing change by not delivering new features for the duration of mainstream (five years) and extended support (five years). On Long Term Servicing branches, customers will have the flexibility to deliver security updates and fixes via Windows Server Update Services (WSUS) which allows full control over the internal distribution of updates using existing management solutions such as System Center Configuration Manager or to receive these updates automatically via Windows Update.

 

We also learned from customers that while having control of mission critical environments is important; they also have many end user devices that are not necessarily mission-critical. Managing those devices as mission critical systems results in significant, unnecessary costs and complexity, while additionally depriving business users of access to the latest functionality. Many IT organizations have told us they would like to get out of the business of managing end-user devices. They are looking for ways to keep devices up to-date with more discretion than simply treating them the same way they treat consumer devices.

 

To that end, we are introducing a new approach for business customers, which we are referring to as the Current branch for Business. By putting devices on the Current branch for Business, enterprises will be able to receive feature updates after their quality and application compatibility has been assessed in the consumer market, while continuing to receive security updates on a regular basis. This gives IT departments’ time to start validating updates in their environments the day changes are shipped broadly to consumers, or in some cases earlier, if they have users enrolled in the Windows Insider Program. By the time Current branch for Business machines are updated, the changes will have been validated by millions of Insiders, consumers and customers’ internal test processes for several months, allowing updates to be deployed with this increased assurance of validation. Enterprises will be able to decide if they want to receive updates automatically via Windows Update, or via WSUS to have control through management tools over how the updates are distributed in their environments.

Edited by Arthur
  • Thanks 1
Posted
bit the bullet and shoved it on as a dual boot on a suite pc here (yes im not very busy) might have to try a fresh install on a vm as well as it gave me the option to sign-in with an office 365 account. It did after first boot though not allow me access to any settings lol

 

well don't do that. If you install windows 10 to a native boot vhd you cant upgrade it to the next version it just basically downloads the update and says computer says no on you. Was such a sensible way to test it on a pc without upsetting anyone and its what ive done in the past with windows 8.1

Posted
I was planning on deploying a trolley of wireless ssd based notebooks with Windows 10 on them, but frankly I'm a bit disappointed with our testing of Windows 10.

 

I like the boot speed, GUI and general feel of 10, but its got the same baggage as 8.1 - i.e the stupid metro apps that clog it up.

 

And the biggest problem? Joined to the domain means really long initial login times. 10 minutes for a first login, you've got to be kidding! - but its setting up all of the metro stuff - imagine this on a wireless laptop!

 

So we'll be sticking with 7 for this summer, until we can make 10 work properly.

 

Snap,

 

Weve been forced intto have 8.1 on some windows tablets as they wont do 7.

 

What a nightmare they are, weve split of the profiles so 7 and 8.1 arnt sharing and done a few other tricks but they are so slow logging in. Never delete the profiles as well so if doesnt have to recreate.

Cant seee it changing as it never did with 8.1, surely they know about the login time.

 

Win 7 was slower than xp but still ok but 8/8.1 was unacceptable.

 

Ive got staff moaning that some old machines take a minute to login in windows 7.

Posted
Does this mean the existing keys work fine or would we have to put some more in?

Not sure to be honest, although if I find out I'll post the details in this thread.

Posted
Does this mean the existing keys work fine or would we have to put some more in?

 

Thanks

 

I believe what it tends to mean is that the KMS Host Service has been expanded to support Windows 10's backend, and Windows 10 keys. So you will have to put in keys for Windows 10.

Posted
I believe what it tends to mean is that the KMS Host Service has been expanded to support Windows 10's backend, and Windows 10 keys. So you will have to put in keys for Windows 10.

That would make the most sense. I guess we'll have to wait until next month to get the actual product keys.

Posted

We've had good experience with W8.1 on tablets and that's spurring me on as W7 is getting a bit long in the tooth and is not as secure. Fine on our network, but the staff take their laptops home to their insecure networks and pick up all sorts of crap. The worst thing about the Dell tablets are the docks, which are just cr*p.

 

I'm draft planning on migrating all the laptops to W10 Pro with an HD swap to SSDs at the same time, starting in late summer. I also have to setup encryption to meet the new EU Data Regulation so would rather do it all at once if possible. We'll use MDT and deploy it with Office 2013, which we're already using. Testing proper will ramp up when the Volume License version of W10 Pro becomes available and I can put the image into MDT.

  • 4 weeks later...
Posted
I will be looking to use MDT as well to deploy Windows 10 this summer. I'm just hoping there will be a GPO to manage the apps as there was never a nice way of doing it on Windows 8 via a server.
Posted
I installed the ADK, converted a pro iso to Enterprise this afternoon and had it deployed within an hour this afternoon. Made a default user.v5 profile and... Perfect. I've never known a Windows upgrade to be so painless. (No I'm not going to deploy the unofficial iso!)
Posted

HI Guys

 

I know i'm late to this post however, what are people doing with staff laptops? We have a number of schools with staff who have laptops with them over the summer. They often have admin rights on the laptops but i really dont want them installing Windows 10!

 

I'm interested in what people are doing about this?

Posted

I've called as many in as I could for the summer break. These will receive an SSD and will have Windows 10, Office 2013, BitLocker encryption etc. installed on them. As soon as I have the W10 Pro image for MDT, I can make a start. The rest will be trickle-fed to us in September and we'll get through them. All of our machines will receive W10, including the classroom suites, Smartboard PCs and staff tablets.

 

Any staff who do their own W10 installation will just have it wiped and imaged by us, anyway.

Posted
Are people going to go for the enterprise version or education one?

 

It makes practically no difference what so ever, so unless there is a pressing need for the long term servicing branch we will likely use the education version.

Posted
It makes practically no difference what so ever, so unless there is a pressing need for the long term servicing branch we will likely use the education version.

 

Bitlocker isn't in the education version.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...