It combines all the input files into one iso which contains all the inputed installers. It can convert the activation channel of the input products from retail into volume or visa versa. It doesn't activate/crack the products, unless you do it yourself with an unattended file. It doesn't add any other crap to the installer.
Prerequirements: .net Framework 3.5
1.3.2 -> 1.4
- Added support for: Office Small Busines Basics
Office Single Image (integration only, there is no volume version)
Sharepoint Designer (integration only, this product doesn't require activation)
- It now stops when there's no supported product found in the input file. Previous versions would continue and make an empty iso.
- Preventive fix for language ids that don't have the typical XX-XX structure.
1.3.1 -> 1.3.2
- Fixed 3 bugs in the add additional files/folders option.
1.3 -> 1.3.1
- Excluded the dll of 7-Zip from the 7-Zip archive, just like it was with version 1.2. This ensures compatibility with x64 operating systems.
- Added Microsoft and 7-Zip to the credits list.
1.2 -> 1.3
- Added support for various products (see supported products).
- Switched to new 7-Zip 9.20.
- Included all files inside 7z archive, except for 7Z.exe which is needed for extraction.
- Previous versions detected only README.HTM files as readme files, and the language was determined using foldernames. This version checks all htm files to see if it's a readme file, and the language is detected using the contents of the file itself.
- Now also multilanguage installers and installers with multiple products are supported. This means you can reuse outputted files as input file, previous versions didn't support this.
- It takes up less diskspace, especially when many files are inputted.
- Cleaned up the code a bit.
1.1 -> 1.2
- Added support for Visio and Project Professional.
- It can now combine Visio, Project and Office installers into one iso.
- It can now combine different language installers into one multilanguage installer.
1.0 -> 1.1
- Fixed the problem that caused incompatibility with Windows XP and earlier.
- Office Professional Plus
- Office Standard
- Office Small Business Basics
- Office Single Image, this is Office Home and Student, Office Home and Business and Office Professional in 1 installer. (integration only, volume versions of this product don't exist)
- Project Professional
- Project Standard
- SharePoint Workspace*
- SharePoint Designer (integration only, this product does not require any form of activation)
For all these products both x86 and x64 and all languages are supported.
* These products are also available in the office suits like Office Professional Plus, but now also the separate versions are supported.
What it does
It combines all the input files into one iso which contains all the inputed installers. It can convert the activation channel of the input products from retail into volume or visa versa.
What it doesn't
It doesn't activate/crack the products, unless you do it yourself with an unattended file.
It doesn't add any other crap to the installer.
1) Input all the installers you want. Those can be exe files or iso images. Only trusted installers should be used, with unmodded files (original Microsoft installers, Wzor select editions and installers made by this program are ok). If you use installers with modded/corrupted files, this can result in a corrupted output installer. You can also add for example two x86 Visio installers with a different language, you will then have the choice between these languages during setup. (This requires the note at the bottom of the post!)
2) Choose one activation channel for all the output files, or check "Use advanced options". If you didn't check "Use advanced options go to step 5, otherwise proceed with step 3.
3) On the Advanced options tab select the desired activation channel for all inputted products.
4) If you want to add additional files or folders or want to make moddifications to the files then you can check "Add additional files/folders to the installer". This option will open an explorer window in the right directory before creating the output iso image.
Never give an already moddified input installer, if you want to make moddifications always use this option or do it afterwards.
5) Specify an output file.
6) Click "Start channel switching" and wait until you iso is created.
The output file is always an iso file. Why?
Because the exes are an sfx program followed by a regular cab file, but I think the files to extract from the cab are coded inside the sfx program. So when you add files to the installer, or when you switch the activation channel (which also renames files) the sfx program won't extract all necessary files.
The iso files are made exactly the same way as Microsoft made it's dual architecture MSDN iso: using cdimage 2.47 and the right commandline arguments so the iso is official-Microsoft-iso-like.
Why is the program 20MB in size?
For each product two xml files are really edited, so only those parts that are different are replaced. The cab files are only different in their signature, that's also just edited. The msi files however have so many differences it's undoable to only change that parts, so I 7zipped those files and included them in the app. That's why it's pretty big for what it does. But still downloading 20MB is better than downloading all the magebytes nefor replacing the folders manually. It wouldn't have been so big when I used CODYQX4's patches, but that's too late now.
If you don't trust this you can always extract the output installer and check the file hashes of the files inside, you'll see for yourself nothing unwanted is added and the files are genuine. The hash of the output iso won't match any hash of valid office installers, this is only because the timestamps of some files are different.
Note: Imagin you make for example an iso with both English and Dutch versions of Visio.
Now when the setup wizard is ran in English, setup forces you to install the English version (you can't uncheck it). You can still choose if you want to isntall the Dutch version also or not. Af cource if the setup is ran in Dutch it's the other way around.
The language the setup wizard uses is automatically determined from Windows' locale/language settings. This means an English version will always run the English setup, and you're forced to install at least the English version.
You can however force the setup to use a language, and this can be done in two ways: 1) Changing Windows' locale/language settings
2) Removing the Office.xx-xx folder (xx-xx is the language ID) for all languages, except the one from the language you want the setup running in. Setup will be forced to use this language simply because there is no other.
FOR METHOD 2 I NEED SOME TESTERS
If you want to test just make a multilanguage installer and leave only one Office.xx-xx folder there. It's best to leave a language that DOESN'T correspond your Windows settings, this way it's shure there won't occur errors using this method.