hello, I used this tool (really great, good job) to convert a version Retail in VL, the first installation is OK. I was testing and I had problems to uninstall (not related to this tool) but now when I try to install I have a problem with activation, I red stripe at the top of Word, Excel indicates that version is not activated I have to again convert Retail => VL? thanks EDIT: may be an activation problem, I used EZ-activator, the first time (for the licence key) how to remove all traces of activation?
Finally download fr_office_professional_plus_2010_with_sp1_x86_x64_dvd_730410.iso and used the channel switch, all is OK but the final iso file is not created with the new name !! Extract hte iso file and launched setup.exe, ask me for a licence number !! I think the convertion to VL was not ok !! If anyone could help ?? Thanks in advance.
Ok it shouldn't as for a key, if it does than it's retail. Did it actually create the iso? Cause if so the conversion should be ok too, if the conversion fails it doesn't write the iso. The question however is if you have converted both x64 and x86 installers. The setup in the root always calls the x86 installer, if you want to install x64 you have to run the setup in the x64 folder.
Thanks for help, in fact the final iso is never created. The original iso is fr_office_professional_plus_2010_with_sp1_x86_x64_ dvd_730410.iso i downloaded from the links here. So I do not understand !!
OOOH wow, I missed that it's an sp1 iso. Can you tell me how it's made? Are there updates (extracted from sp1) in the updates folder? If not than probably the cab archive itself is updated, which means I have to give the switcher a huge update to support sp1.
That's true but I think they did change something else too. At least the proplus edition now also contains Lync, while the RTM didn't. So lync is also in the cab files -> cab files canged -> digital signature at the end of the file also changed. I don't know if the signature matters for installation, but apearantly something goes wrong. Maybe the xml files are changed too. Products other than proplus might still work though. But I didn't have time to check things out yet.
Of course it's not hard to support it, if the xml or cab files are different than the rtm ones than I just need to handle the sp1 versions of the same products as separate things. So like proplus rtm and standard rtm are different things, I'd need to handle proplus rtm and proplus sp1 as different things too. It's easy to do, I only need 1 extra check to make sure that if both rtm and sp1 versions are added, only the sp1 version remains cause it has a higher priority. And my checks are indeed more specific I think cause I check for every file that I change if it exists. I don't know how conversion works when office is already installed, but for the installer each product has different files. In the xml files for example there's not just a line where retail needs to be changed to volume (actually there is), but also some file hashes. Each product has different hashes so they must be changed for that specific product. This means I always need to check which specific product I'm changing, while your method uses some universal switch I think?