Good... At the present time I'm wrapping up and killing bugs. At this point I do not anticipate needing to change any major coding. It should be able to hold together for an extended period of time. By the numbers I have Nova 12.1 Prototype 3 had about 1000 lines of code in it. At this point we are looking at about 1550 lines of code given scripts removed, added, or consolidated. This is gonna be fun.
Well in other news I'm slowly inching along to a final release. Only issue it took forever to fix all the bugs / audit the code. The good news is that support list is going to remain intact after a good amount of code tweaks. I did finally get a 2nd RC build online with quite a few more fixes here and there. Overall I'm happy even though my eyes want to bleed from all the fixing. The reason it was a pain in the neck was that the SetupComplete had to be completely rewritten. Most of the existing code was just not good enough as I wanted to add more features that are only available in powershell 3.0. That being said I alas do feel sorry for my laptop which has been chugging through Virtual Machines like an alcoholic.
Ok after a good amount of bug killing and satisfying my simple curiosity. I have started to update the Original Post to include the changes coming to the final build of Nova 12.1. We are going to see some radical changes like being able to install all the programs bundled into it without those programs actually being on the ISO. This is made possible by using a downloader that grabs all the software from their respective sites they originate from. Lastly after trying out the live install script on Windows XP because I was curious it worked out better than I hoped for. I was able to make it happen and made a few changes to make this fully possible with a new RC build that I called RC 2.0 while the ones before it were called RC 1.0 and RC 1.1. The good news is that the bugs are getting less and less serious as I squash more of them.
Given the amount of time required to test this fully. I'm just going to start posting nightly builds because effectively I'd have to test this 3 times on the full support list (excluding Windows XP). It would just take too long so it will be easier to just get people to test it for me Nova 12.1 Prototype 6 (4.29.2016) Nova 12.1.exe Full copy of the pack that can be used on anything aka full support list. Nova 12.1 - Online.exe Lite copy of the pack that will download programs during install using setup updater script. Additionally this will only work on Powershell 3.0 Operating systems. This means Windows 7 or newer so legacy operating systems such as Windows XP / Windows Vista will not work.
What's the script look like? I mean I have my own way to do the install using the MSP silent install method.
The way I did the Office Installs is that I used the xml bootstrapper. This is loaded into the setup via command line aka powershell. For the purposes of Licensing I am not going to integrate this into Nova. Nova is a legal means to load programs into an ISO / OEM. Office.xml Spoiler <!-- Office 2016 Pro Plus --> <Configuration Product="ProPlus"> <Display Level="Basic" CompletionNotice="No" SuppressModal="No" AcceptEula="Yes" /> <USERNAME Value="." /> <USERINITIALS Value="" /> <COMPANYNAME Value="." /> <PIDKEY Value="" /> <Setting Id="AUTO_ACTIVATE" Value="0" /> <Setting Id="SETUP_REBOOT" Value="Never" /> <INSTALLLOCATION Value="" /> <OptionState Id="ACCESSFiles" State="Local" Children="force" /> <OptionState Id="EXCELFiles" State="Local" Children="force" /> <OptionState Id="XDOCSFiles" State="Local" Children="force" /> <OptionState Id="LyncCoreFiles" State="Local" Children="force" /> <OptionState Id="OneNoteFiles" State="Local" Children="force" /> <OptionState Id="OUTLOOKFiles" State="Local" Children="force" /> <OptionState Id="PPTFiles" State="Local" Children="force" /> <OptionState Id="PubPrimary" State="Local" Children="force" /> <OptionState Id="GrooveFiles2" State="Local" Children="force" /> <OptionState Id="VisioPreviewerFiles" State="Local" Children="force" /> <OptionState Id="WORDFiles" State="Local" Children="force" /> <OptionState Id="SHAREDFiles" State="Local" Children="force" /> <OptionState Id="TOOLSFiles" State="Local" Children="force" /> </Configuration> Project.xml Spoiler <!-- Project 2016 --> <Configuration Product="PrjPro"> <Display Level="Basic" CompletionNotice="No" SuppressModal="No" AcceptEula="Yes" /> <USERNAME Value="." /> <USERINITIALS Value="" /> <COMPANYNAME Value="." /> <PIDKEY Value="" /> <Setting Id="AUTO_ACTIVATE" Value="0" /> <Setting Id="SETUP_REBOOT" Value="Never" /> <INSTALLLOCATION Value="" /> <OptionState Id="PROJECTFiles" State="Local" Children="force" /> </Configuration> Visio.xml Spoiler <!-- Visio 2016 --> <Configuration Product="VisPro"> <Display Level="Basic" CompletionNotice="No" SuppressModal="No" AcceptEula="Yes" /> <USERNAME Value="." /> <USERINITIALS Value="" /> <COMPANYNAME Value="." /> <PIDKEY Value="" /> <Setting Id="AUTO_ACTIVATE" Value="0" /> <Setting Id="SETUP_REBOOT" Value="Never" /> <INSTALLLOCATION Value="" /> <OptionState Id="VISIOFiles" State="Local" Children="force" /> </Configuration> PowerShell Office install method $office = "/config main.xml" $visio = "/config visio.xml" $project = "/config project.xml" cd OfficeSetupDir start-process "setup.exe" -ArgumentList "$office" -wait start-process "setup.exe" -ArgumentList "$visio" -wait start-process "setup.exe" -ArgumentList "$project" -wait