maybe this has been explained somewhere already, apologies. the ir5.bat deletes the WPA tree from the registry as it seems? there are 21 lines each with the same key and then 5P-x with x running from 0 to some letters. What are these? edit1: ok, copied IR5.bat into my system drive C. rebooted, went into RE, arrived at X:windows/system32 prompt. This seems like where my system drive is located when doing a dir cmd. typed X:IR5 and get a 'not recognized as internal or external cmd' message. tried a few other combinations (c:ir5.bat, c:ir5, and same with x). no luck... edit2: searched around a little. it actually turns out that F is the system drive in my case. Drive X contains program files, users, windows and a setup.exe file (must be hidden system partition). The F drive contains the above including serverfolders and the ir5.bat I copied earlier. now command works. rebooting, bottom right on screen reports non genuine as expected when back to main OS screen. Running manual package (install), installs product key and message pops up with 'product key installed successfully' at the same time the non genuine label bottom right disappears. another window pops ups with detailed licensing info. license status: initial grace period, 30 days remaining, remaining windows rearm counts 5. !! it works. Genius ! it successfully turned my pristine 22 day grace period with 3 rearms into a 'genuine' 30 with 5 rearms a note to those for which it fails at the RE level, need to search for your system drive. probably depends on number of drives installed (in my case 5). a note to myself: this probably means that trilogy 2.4 works perfectly fine as well. just need to find the system drive when in RE. edit3: it seems that this procedure breaks the dashboard connection from clients to the server (certificate issue?) (note, launchpad with shared folders is not affected, but backup and dashboard withing the launchpad are). Uninstalling the WHS2011 Connector software and reinstalling fixes the dashboard connection and all recent backups on the server are still present. However, the backup from the launchpad reports "no previous backups". So the rearm works but it resets the backup service for clients to 0. But restoring from backups before rearm still works ok. I don't think this is a big deal. edit4: ok, just checked my other clients and they seem to be fine. The dashboard works without a problem and backup reports all backups including the ones before rearm. It doesn't reset backups to 0. Maybe the one above just needed a reboot, not sure.
Thanks for testing. The whole reason I did MPC was that RE has problems finding system partition sometimes. No other reason. We agreed that this was not IR5 problem but again RE. Glad it worked for you and you can use IR5 just like normal to rearm, get status and uninstall. Again RE only affects install not task install or anti-nag install I was just wondering if manual rearm could detect as it was rearming what was previous wallpaper and it's location and put it back. Maybe it is in log I dunno
That was the easiest part but your welcome anyhow. Seems with a little help I've become a supporter/developer of software hacks. I didn't used to be this way. I must have nothing else to do Thanks everyone for being good friends during this time And for helping me with this project So with the release of the MPC we should have an easier time with troubleshooting/support of IR5 1. No more partition software problems like with acronis, etc that affect automatic boot into RE 2. No more problems with placement/detection of IR5.bat in system drive by RE
Trilogy need supporters/testers and people who read this thread ...lol Yea new 5.5 support for non-MDL version
OK, clean install Windows 2008 Enterprise R2 fully updated and latest Trilogy 2.5 keeps booting in System Recovery.