try this 1. 1. create a folder C:\Office 16. then extract the iso to the folder. 2. open cmd as admin, type C:\Office 16\setup.exe /configure configuration32.xml. enjoy...until 1 Dis 2014.
akshay1189, VL version activating process is same as for Office 2013 with offline MAK keys. Retail version of 365 could be converted to 2013 (any edition) by inputting appropriate key and activating online/by phone with retail key.
It is available from online installer that could be grabbed from the same folder in baidu as for VL version of 16 Beta. Check out post #105 (You need OfficePreview_v1.05c.zip file)
I'm not sure if I get your point entirely, but to me it sounds like you're making things more complicated than they actually are. IMO, Office 365 is just not sufficient because it only refers to the subscription-based product, whereas Office 16 refers to both the standalone and subscription-based one, and as long as Microsoft is not going to ditch the desktop for the cloud version, we should go by codenames rather than licensing models when we talk about what's next in the pipeline.
I guess it will be more FAT.. 2 new features crippled saving on HHdisk functions (but cloud) more expensive MS ... they will do it
So, I'm trying to install and im getting an error: We hit an issue trying to uninstall your previous Office version. so I uninstalled it manually but I'm still getting that error even after a reboot....
To be clear on that. Is there any Microsoft technical report on that codename as the name for the present Office? The fact that it is still bearing Office 365(not Office 2010,etc in nature but 365) not Office 16 makes it more of 365 than 16. And, somebody just called it Office 2016 above. The nomenclature is a bit confusing.
I've added a section for Office 2016 into the repo but for now I'm going to wait before doing much else. This build is an internal and they are very different from the public releases because click2run uses a virtualized thing to make it all work if I remember correctly. At any rate seeing as this is not a public build which can have relevant information in terms of licensing the best we could do is have a quick look but in all seriousness I would just skip this one. I'm going to wait until I see a public beta. Sorry guys.