It´s right because it´s key dependent. If you enter a Pro key during the installation, it will be Pro, if you enter an Enterprise key, it will be Enterprise, if Education key..... Just checked with someone who installed this as Enterprise without an issue using an Enterprise key.
Makes sense. Thanks for confirming. I'm going to check on my end and see that the image deployment works with ConfigMgr.
Note that there has been a period of a few days for RS3 with no builds between the last non-final build and the final one. Therefore, given the analysis that has been done in this thread, it's impossible to know for sure whether this is final or not. If you don't have first-hand information, only time will tell. Now the blog post is a little ambiguous in saying "Again, we are in the phase of checking in final code to prepare for the final release." Checking in final code doesn't imply it has to be compiled into a new build, it could also mean zero day fixes that will roll out later in a patch. And final release is not equal to final build. Still, a delta of .1 is a little odd, because this has not happened before in a final build (AFAIK) except for the "RS3 anomaly".
Yes, that is why I think they will just release a new delta patch if any fixes are needed (and to remove the Insider branding) on the release day. Just like it was done for 16299.1, where 16299.15 became the final RTM on release day. So it should most likely be safe to installed 17133.1 right now, then just get the cumulative patch on release day...
@dabugen; thx but not working here; enterprise and education keys show as invalid. will try the download all option ..
@ashoktvm The script needs to download files, could it be that your firewall is blocking it? I overlooked this at first too, once I gave connection permissions, everything went smooth. Also make sure to put the script into a directory without spaces, like c:\temp\win10setup
yes it downloaded all the files and I didn't need to do anything it started by itself and gave me this error message
thx qt15. i already tried that one. keys from there worked on FCU.. doesn't look like edu or ent is included in the uup files.. ?
@ashoktvm What is the exact error? Have you executed the whole thing in a directory without spaces? @robsinbc Still have not got around to install my customized ISO, but as soon as I do, I will report back.
Maybe the insider program servers are still considering this build as an insider build and dealing with it on this basis and they just need to turn off something in the insider servers or change the servers settings for this build from insider to stable without having to release a patch. Something like changing the update servers from insider to stable for an insider build after it officially become RTM .
That message is something local though (on your hard drive), so this will need a patch on your system. But that is how they did it with RS3 already too, 16299.1 was the last "insider" build, then a cumulative patch was released which brought it to 16299.15 and that was the RTM As for the Enterprise, I have just read it again on my German Forum that they have made it Enterprise just by the key and showed me the installed version that showed "Enterprise". I will report back how it goes for me and what exactly needs to be done.
The exact error message is " Error work script.". > the the file i downloaded is created in such a way that it creates all the folders needed when i click on create ISO
"Nope" = sure, because I had done it exactly that way 16299 was on, then I (manually) installed the first cumulative update to 16299.15. Not sure what he refers to, but it´s exactly like I did it ;-)