New
#90
It let me install Word Mobile, in "Read only mode". To edit and save an Office 365 subscription is required.
It let me install Word Mobile, in "Read only mode". To edit and save an Office 365 subscription is required.
Agree, all that stuff should really be hidden until upgraded to Win Pro :)
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.
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!