In 3 days your system will try to activate - without success obviously - and you still have 27 days and 5 rearms.
So it's working as it should? And i will not be subjected to some kind of "block" of my os after those 3 days ? Another question: what will happen when i'll run out of the 5 "rearms" ?
Yes, you have no problems. And 5 rearms of 30 days is half a year. After that you reinstall IR5 to start from new - or better, a OEM key has probably leaked by then and a BIOS loader can be installed. Sorry - disregard the last sentence. It is nonsense: You have Enterprise I was thinking of WHS 2011. But you can activate using KMS.
Thanks again Troels! So, at this time, there isn't a valid keygen for the enterprise edition? If i "downgrade" my version from the enterprise one to the ultimate or the professional, will i find a valid key, or nothing will change ?
There's no "downgrade" from enterprise, it's a common misunderstanding. Enterprise and Ultimate have the same features, the difference is the Licensing, Enterprise -> KMS, Ultimate -> OEM SLP. This basically means that Ultimate can be permanently activated, and KMS needs reactivation every 180 days.
There is bug in enterprise whereas some see that 3 days and some see actual days remaining Maybe try Daz's WATfix ...lol
Thanks! Just want to say THANKS for this awesome utility! It worked perfect on my Windows Home Server 2011 w/ SP1 installed. NOTE: I was accessing the server via MSTSC, and when the server rebooted, it did not come back up. I went to the server and there was an error message, something about the repair function not supported with this version of Windows (or something like that), and asking to enter local and keyboard (I think). I just selected NO and restarted, logged in, and everything was fine. I then ran Trilogy 2.1.cmd, selected Rearm, and BAM, 30 more days instead of 6. Thanks again.
Please reupload the last version of IR4. I have repeatedly tried to use Trilogy on two PC's with Windows 7 Ultimate (one SP1 and one not), and it fails on both of them. It also seems needlessly complicated. For example I can run "slmgr.vbs -rearm" manually when I need to or I can create my own task to do it if I want. I just need something to reset the trial period when the number of rearms is up. The old ReARM4.exe was simple and worked fine (at least on my non-SP1 PC). Unfortunately I no longer have a copy of it, and I don't know if it works on WIndows 7 SP1.
Thanks! Well I tried it multiple times on each PC with no luck. It is also difficult to troubleshoot because the CMD file spawns extra BAT and VBS files and then deletes them along the way. What it should really do is just reset the trial period and then give the user the option whether to use "slmgr.vbs -rearm" or not.
Dude it is fine. It is not difficult to troubleshoot because of the .vbs or .bat files! It is difficult to troubleshoot because you gave exactly ZERO information as to what is NOT working....lol What changes did you make. Not one person has had problems with IR5 regarding the vbs [/B file. IR4 and IR5 work exactly the same. It should not give user option since IR4/5 was designed to be automatic not manual! If you want to rearm "early" the use the "rearm" option like IR4/5 has always had! Also if you'd read the first post it says explicitly that Trilogy supports all UPDATES and SP's...lol Another thing! IR5 is not endlessly complicated. It's actually much better with way more error checking and communications for the user. IR4 also had manual "rearm" just like IR5 does...lol The task for IR4/5 is exactly the same as does it run automatic and silent and cannot interfere in anyway shape or form as it runs only every 30 days! @Team Trilogy Please don't support IR4 as it was killed when I started development of Trilogy. Notice this user not only lost his copy of IR4 although he'd need it to rearm manually and reinstall but he gave ZERO information as to what was wrong then blamed it on same stuff IR4 does so let's not pm IR4 to anyone before fully troubleshooting IR5. This is how we learn Thanks
It's not fine. It doesn't work. I tried it multiple times on each PC. It messed my non-SP1 PC up so badly that I couldn't even run slmgr.vbs any more because it said the key was missing. I finally gave up and hosed that OS installation and did a clean SP1 installation for that PC. On my SP1 PC, I had to manually rearm it a couple of times until it would finally say it was genuine. The bad news is that I only have one rearm left. I didn't make any changes. However in trying to go over your CMD file I did notice that you used a program called wpeutil which isn't on either of my PC's. It doesn't appear to come with stock Windows 7, but I don't know if it is the cause of the problem. You need to change that to "not two people" because I did have these problems. The old ReARM4.exe is what I used before, and I had no problems with it except it was inconvenient since you had to boot to recovery mode to run it.
In looking over the CMD file I think I found the problem. Neither of my PC's ever entered recovery mode despite the fact that the BAT file should have run "reagentc /boottore". My recovery directory is not on drive C:. Do you think that is the problem?
It does work your OS is borked! IR4/5 is the only hack that never messes with system files except maybe KMS activators and of course Daz loader ...lol Again your OS is having probs not IR4/5...lol wpeutil is how in RE it restarts auto because I wanted it to be as auto as possible Don't need to not going to...lol There is not better method to rearm just use Daz but have better attitude with his team reagentc /boottore is how it boots auto into RE...lol Open cmd prompt and type Code: reagentc /enable If you want further support to find ACTUAL problem have better attitude towards MDL dev's In end IR4/5/Trilogy is massively tested and working with higher success first time than any solutions
The OS on my PC's were not borked until I ran your CMD file on them. No my OS had no problems until I ran your CMD on them. Neither OS was expired either. I simply ran your CMD file because I wanted to reset the rearm count. Except neither of my PC's ever entered RE mode. Both of my PC's use the standard Windows 7 boot menu, but Windows 7 is not the only OS choice in the list. I can manually choose RE mode, but your CMD file did not triigger it. You need to if you want to be accurate. But I can see that is not a priority with you or your work. I looked that up and saw that, but it did not work. It was already enabled on my PC's as verified by "reagentc /info". It was obviously not tested enough.
Not sure but he's blaming a lot when it's exactly same code! Also he said it messed up his system which IR4/5 has never done...lol If he is beginner he needs to let us know instead of shooting blanks into the dark with what he thinks is wrong ...lol Let's see if that code I gave him fixes his ability to boot into Re auto Code: reagentc /boottore IR4/5 doesn't bork OS but beginners sometimes in their "inexperience" bork their OS...lol Then you have something installed on your system your not telling us? Accurate enough to have 99.9% success...lol I support more solutions than almost anybody so wrong again ...lol So tested that it is phenomenally known world wide for over an year now with nearly 100% success except for people who don't care to work with Team Trilogy ...lol Good luck I'll Team Trilogy help you if they want to ...lol
No, they were not preactivated. They were installed from the stock Windows 7 release and SP1 release ISO's linked from torrents on the MDL website. The only unsual part is that the OS isn't installed on drive C/the first SATA drive, and it's not the only OS in the boot menu. I used no loaders or other cracks on them. I simply used ReARM4.exe whenever my rearm count was 0. The only mistake I made was "upgrading" to the Trilogy CMD version.