Windows 10: Microsoft Releases Windows 10 S ISO to Developers, Education Customers

Not sure why the "Get Office" App is there? It doesn't work at all, I clicked the Install Office 365 and get a "The thing your looking for isn't here". I was wanting to install Outlook, trying to install that all by itself gets the same message. Of the preinstalled Office Apps, only OneNote appears to work? Clicking Excel, PowerPoint, and Word from the Start Screen gets that same "The thing your looking for isn't here" message. The tiles for Excel, PowerPoint, and Word only show up on the Start Screen. They are not listed in All Apps or in Settings > Apps & features. They are just place holders to install those Apps. That fail when you try to do it. So, it would appear, no way to run Office? That isn't going to fly if this is meant for students?

 

That is weird behavior. On the other hand, Office is not a Store App so you should not try make that work until you have upgraded to Windows Pro. Office is not intended to be run on Windows S. *Smile

If I understand correctly, the education part is intended as educational apps coming from Windows Store. Office is just a collection of document manipulation editors and does not fall into the educational app category at all but rather into the productivity category. I think the idea here is that a School has it's own Office servers, the students run Edge browser and manipulate their documents using office online editors.

 

It let me install Word Mobile, in "Read only mode". To edit and save an Office 365 subscription is required.

 

The thing is though, why put the tiles there for Excel, Word and PowerPoint if they won't work and can't be installed from those tiles? IMHO, they have a few kinks to work out.

 

Agree, all that stuff should really be hidden until upgraded to Win Pro *Smile

EDIT: Schools however create a model installation, configure that and then capture all that to some deployment server and finally deploy the working image to all computers they want Windows with this configuration to be installed on. Everything can be configured. No point in making installations for weeks, when you can just click one button and all computers are ready to go within an hour.

 

Since I am quite certain I understand what Windows 10 S is and how it differs from Windows 10 Pro or the other editions, I see no point in personally testing it any further. I know what limitations a strict policy brings to the table.
Only thing I could test, is making a model machine with some configuration, capture that to a server and then have a few computers (or VMs) where I use PXE boot to deploy the image and see how goes. Then maybe modify my model machine and force push the new image to the already working machines.

But I see no point in doing this either, as I could do it with any Windows edition, and they all work the same. The whole Installing, configuring, capturing, deploying process is the same for all the latest Windows editions. Nothing special about this.

 

Yeah, imaging will be the way to go. I'm logged in with my Microsoft ID instead of my Office 365 account. I may setup a second user account with that and see if it changes anything?

 

Added my Office 365 Account to my existing account but still can't edit in Word. I had to add the office 365 account to that App in its settings. Then I got a "you've been upgraded message. This may be old news to some of you but its all new stuff for me.

 

Just a few little hints from TF members in this thread, and some help from Microsoft docs:

Windows 10 S manufacturing overview | Microsoft Docs

- and Windows 10 S in manufacturing mode can be made to work almost like Pro:





Once all modifications are made, manufacturing mode is removed and the image can be deployed to the users.

As you can see, the Command- and Power- shells seem to work ok, and Superfly's ShowkeyPlus works where they wouldn't in 10 S before

Portable Win32 applications work fine - even old Word 97 and Excel 97 run from across network, but installing stuff from online like Chrome seemed to be a no-no. Downloaded Office 2007 fileformatconvertors.exe threw up the warning:





and the contents of the .exe had to be extracted from the exe using 7-zip, and then the O12conv.msi runs fine from within the extracted folder.

If you don't muck about with this edition, as I did above, it should behave perfectly as an Insider testbed, since it is locked down, and no extraneous rubbish should seep in (unless perhaps Internet Explorer is used, and people are careless with emails). However it is clinically sterile.

If It were widely used, it might encourage a better range of serious useful Windows Store utilities - which are still woefully poor for the most part.

But I agree with Slice' when there's no real interest in using this version for testing in its sterile form, and it's easy to deploy.

One other thing though:
Dism is DISMally slow mounting and unmounting wimfiles for modification. Wimlib-Imagex is much faster!

 

Had no issues in enabling manufacturer mode, makes this S edition quite interesting. It most definitely adds an additional layer of security; as an admin I can prepare the image, install software and deploy, being sure no user can tamper with it *Smile

I am starting to like the S edition!

 

Okay, just fired up a test drive.
This thing seems to take longer to install than a regular pro edition...





I got the "just a moment" screen like a hundred times (just an exag)...

 

My graphics driver (ASUS GTX 1070) got installed automatically during installation...