IORRT - The Official Office 2010 VL Rearm Solution

I'd prefer the old one as it lets you ensure you revert the user's system back to before IORRT if you uninstall, but since you restore EVERY single time before you rearm there isn't a difference.


@timesurfer

don't use DEL %SystemDrive%\ProgramData\Microsoft\OfficeSoftwareProtectionPlatform\IORRT.bat
it wiil never work on XP

do this
DEL "%ALLUSERSPROFILE%\Microsoft\OfficeSoftwareProtectionPlatform\IORRT.bat"

it works always that way. I posted it before. I am not sure why you are messing with it. The IORRT I posted yesterday only had Backup.hiv issue, and the above command except replace IORRT.bat with Backup.hiv.

I'll put it into mine and repost it as you guys are doing the wrong things over that Backup.hiv and inadvertantly reverting to stuff that will not work on XP.

I'll test it on XP.

I said mine worked on 32 on 64, you said it worked 32 on 32 (what OS?) and as it was said XP 64 is not supported.

 

Not really, what I was asking is this.

After an uninstall, the BACKUP.HIV that was created during the initial install of IORRT will be deleted. When we reinstall IORRT afterwards, we create a new BACKUP.HIV file during the install. Would it be of any advantage to not delete BACKUP.HIV when uninstalling and then checking to see if it is there before recreating BACKUP.HIV during a re-install?

 

@timesurfer: If I can make a suggestion I would try to add a service that autoruns that will reset the rearm and rearm every so often. Like rearm automatically in 25-30 days and reset the rearm automatically like every 2-3 months. I love your program even though I said I prefer a perminant activation. I just think that having an auto service would really help out.


Update: Oops, forgot it already had that lol. FACEPALM myself haha

 

His is rigged everyday whereas mine behaves more similar to that.

I wonder though what the preferred method is though?

 

@timesurfer since we do the task in our tools very differently (I use AutoKMS style for it which might not be the best way for Rearm). Maybe add a poll here to see what the perferred way is.

Your way: Execute daily and restore everytime then rearm.
Advantages:Simple and takes care of it even if never reboots
Disadvantages:Restore+Rearm is slower so the fact I put off the restore until needed makes the times restore isn't needed much faster. Also tied to a specific time (Mine set to midnight, if I stopped running my PC at midnight this would be an issue).

My way: Execute on boot, check grace, if less then 5 days rearm. If rearm fails then restore+rearm.
Advantages:Task not tied to a specific time. Faster because it rearms only when needed and restores only when needed.
Disadvantages:Lets the grace count down. If user leaves PC on for 30+ days (more likely than 180+) it expires. If user starts PC and is just above 5 days, and leaves it on for 5+ days, it expires.

Hybrid way (A bit of a combination):
Execute upon boot, then every 24 hours run it again. This allows the best of our scheduling methods. The fact that it is at boot then 24 hours after boot means the task does not get tied down to a specific time like midnight. I can't see any flaw in this schedule because we ensure it should not ever drop below 30 like you want and we use my boot method to determine the 24 hour mark so user doesn't install it at a weird time they normally turn their PC of plus the at boot saves them from killing their PC before your time hit, rebooting one month later and it being expired (because it wasn't the time yours set).

 

What do you think about that hybrid method? It seems the smartest and it trumps either of our current scheduler methods.

I just need to find out how to make that in XP.

I'll do some XP testing with my last code as I lost track of what you were doing because you changed some things that seem to have no realtion to the Backup.hiv (which I know will break XP).

So me and you confirm 32on32 and 32on64 Windows 7 (and Vista) work. That means 64on64 should work as well as 32on32 and 64on64 are basically the same.

I will test XP and that should ensure IORRT.bat is done. Use the next one I post in its entirety as it will have all the good fixes without the XP breaking mods.

 

I have seen tasks like this before. Effectively it would say triggered at boot, after triggered, run every 24 hours. I need to see if it can be made on XP and the command would automatically work forward.

I find one of the reasons to work on the IORRT as its getting the rearm concept out there. I made AutoRearm but it is dwarfed by the EZ-Activator which has been recommended and the main attraction of the toolkit. A lot of people probably DL'd BETA 3, got it working and left things alone, and those who updated probably never checked the readme or Activation Tab to see it there.

I tried a trick to beat the nags on Retail but it did not work. Only way I am aware of is convert to VL. I'll probably give the user the option to convert to VL upon install of it so they don't get nagged.

 

I just realized a way easier way to do things.

You guys are storing the tokens alongside the batch file and Backup.hiv and copying the whole folder then deleting the batch and hive file from the tokens file.

If I make IORRT store its stuff the way the toolkit does, you'd just copy a subfolder of IORRT to the tokens path and the Backup.hiv and IORRT.bat would never end up there in the first place. I'll make it do that and it will mean people can dump a toolkit backup there easily.

 

No there is still Systemdrive\IORRT

It will have a subfolder called Backup, which has two subfolders Files\Tokens, and Registry. The tokens.dat and Cache\Cache.dat goes inside tokens folder. Backup.hiv (now renamed OfficeSPPInfo.hiv) goes into the reg folder. You copy the tokens folder contents to the "%ALLUSERSPROFILE%\Microsoft\OfficeSoftwareProtectionPlatform" folder.

The backup follows the structure of an Office 2010 Toolkit Backup and this is how I do it. The IORRT.bat and Backup.hiv used to go into "%ALLUSERSPROFILE%\Microsoft\OfficeSoftwareProtectionPlatform", and you were deleting the batch there but not the .hiv. I now ensure neither go there in the first place. The only reason they got there is because you stored the tokens with them.

 

So Far I got XP support to work fully (I'm assuming nothing broke elsewhere). One problem with XP was that XP is too dumb to autocreate the folder you want to save hiv file to if it doesn't exist so I dealt with the new folder. adding <NUL to all the schtasks /query fix that line issue, and the backup.hiv and IORRT.bat never end up in that one folder to have to delete in the first place.

Everything works. I just want to see if I can figure out how to make that new task first.

 

Unfortunately the XP (and maybe Vista+) commandline is too dumb to create the task and I can't manually make it in XP.

I have a very good idea though.

We make a second task called IORRTStartup, this runs on boot and runs IORRT. IORRT task seems to regenerate the old IORRT (but fails on XP but I add delete then recreate), this would set the task time to the time they booted, and the original IORRT task would run with that to reset every 24 hours.

I just gotta test it first.