IORRT - The Official Office 2010 VL Rearm Solution

yes, c works, rearms perfectly, resets total minutes of Grace and keeps the same rearm count.

I don't. I found it, but I can't find the task...
I'll translate what I get in my IORRT when I do C:

(...first part I can't see, ran too fast)
Operation concluded with success.
Operation concluded with success.
Office Software protection Platform initiating
Office Software protection Platform initiated with success
Microsoft Office rearm successful.
SUCCESS: Scheduled task "IORT" eliminated with success.
SUCCESS: Scheduled task "IORT" created with success.
The syntax of the name of the file, directory or label of the volume is incorrect.
Microsoft <R> Windows Script Host version 5.8
Copyright <C> Microsoft Corporation 1996-2001. All rights reserved.

Entry error: It is not possible to find script file "C:\Windows\system32\OSPP.VBS".
IORT 10-12-2010 19:32:00
Ready
Press any key to return to the main menu

When I ask the status (d) it only says the same as above from "The syntax of the name of..." to the end.

Rearms are the same - status according to Toolkit:
---------------------------------------
SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c
LICENSE NAME: Office 14, OfficeProPlus-KMS_Client
LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel
LICENSE STATUS: Grace Period
Last 5 characters of installed product key: H3GVB
REMAINING GRACE: 30 days (43184 minute(s) before expiring)
---------------------------------------

yes, always

Could it have anything to do with portuguese win7 software? something in the name of things? supposedly it is only portuguese for the reader, the "original codename" is always as in english software, as can be used in command prompt (? that's its name in english right?) isn't it?

 

@timesurfer I see ospp.vbs is directing itself to system32.

I get the folder for it (the install path), but you have to cd /d to that variable to call ospp.vbs otherwise it looks in system32 for it

Did you change IORRT as it worked when I wrote my last edit of it.

 

Hi
Yes I was using 1st post version, at least it's 1.9 too.... I don't remember if I DL from elsewhere... I might have...
I was trying to use Task Scheduler to make IORRT run and autoselect c everytime the PC starts, with privileges, in the background, and closing in the end... I am using the IORRT.bat (not the IORRT 1.9.bat), that seems to do the C option alone, is that ok?

 

I personally tested the Hybrid in AutoRearm by running the startup task manually and seeing if it reset the daily time, and I'd already known restore/rearm worked. All I did was put the functions for task in it and reset the daily at the end of the program.

 

Errors don't matter.
I finally found the IORRT and Hybrid... I'm ashamed to confess I didn't really know how to look for it, though that I had to go through each of the smaller directories, but the tasks were in the library directory, that also contains the rest... I'm really new for this.
So I hope the error is meaningless... One problem though, I'm using PC in battery mode right now, I often do... it doesn't let it work if it is in not AC connected... Could you fix it? It's only unticking 2 options in "conditions" tab in properties, but everytime it recreates the task process during rearm it resets those options... also there is no tick in highest privilege execution, I don't know if it will run that way...
I might do the new task anyway with those definitions...

 

Just for information, my created task works perfectly so the errors are no problem nor the problem of the IORRT/Hybrid tasks. Just scheduled to run IORRT.bat on startup and given time, independently of energy source, and using highest privileges.

THANK YOU SOOOOOOO MUCH, timesurfer and cody!!! You saved my work!

 

C:\windows\AutoRearm folder has exe and backups in subfolder. It thinks on its own because it uses the classes and toolkit code/functions, just uses a loop to apply them in this specific way. I learned of the rearm technique because I backup Office when messing with it and I did rearm testing and found rearms restored when restoring backup. I just built a loop and if statements around calls to the needed functions and AutoRearm was born out of the toolkit in 5 minutes with assurance the code worked since it's gone through all the toolkit testing and betas. I haven't heard a bug report from 2.0.1 yet and I don't count KMS errors. The one confirmed bug in 2.0 i fixed was AV created.

One person said the Key Checker crashed but I could not reproduce it and only had one report so just noted it for now.

I think IORRT vs Autorearm equal out as the way we handle things efficiency wise counter balance (and everything else is the same). The fact that I don't restore or rearm unless needed saves it but when a restore is needed it determined so by rearming so it would be like a second or two slower than IORRT because it would rearm(fail)-restore-rearm vs restore-rearm.

I think its a stable solution but I had an idea for mine to make it even more flexible. As you are aware you can have multiple versions of Office 2010 installed. I got MAK activation before the key died on Pro Plus. If I wanted to AutoRearm/IORRT Visio/Project (I don't have them installed now but used to) it would knock out the MAK activation as rearm rearms everything.

It is possible to rearm products individually though. The OSPPC.dll (which is not figured out) can rearm by passing a SKUID (you see it in Check Activation Status) and rearm just that product. If you look back to rearm guides for old betas you'll see you had to use OSPPRUN to get and pass a SKUID to rearm one product and do it for all of them.

This adds flexibility but it also complicates things as well. I rely on the rearm count being constant for all apps as there is no way out there to make it otherwise currently. If we made individual rearm possible (which I want to add to toolkit) we'd have to check each product's rearm count. If I could get that call working (I think Daz might look at it) I can get the rearm count per SKUID. I'd likely add it to activation status and nuke the "Available" button. Probably would move rearm to license management so it could use the selector and it would make sense since a non-IORRT/AutoRearm is not activation anyway.

Basically what I want from OSPPC.dll is:
1.Get Rearm Count
2.Individual Rearm
3.Uninstall License (this could let me test some new tricks as this is effectively an uninstall as far as license database is concerned)
4.GetInstalledSKUIDs (Would make the Getting Office Config in EZ-Activator way more efficient)

PS: Do you have the ospprun.exe?

EDIT: The above DLL stuff turned out to be absolutely worthless and not what I expected.

 

OK I got that OSPPRUN.

I think if I can script to that file from C#, I will add the features based on OSPPRUN until we can figure out how to do it ourself.

Right now I want to see what happens when you uninstall licenses.

 

Right now the battle is calling it from C# and getting the output. I'm gonna ask on Mixed Coding but I just learned how to pass input to an external app so that is a good thing.

 

No just the OSPPRUN.exe. If you look in the Calling a DLL Help thread I posted, that is a list of commands.

Basically OSPPRUN.exe does the DLL or OSPPSVC talking as we don't know how to do so ourself. I'm using it since I can test features and simply replace OSPPRUN with the needed code whenever necessary.

Right now I'm working on Uninstall Licenses. I have a way to pass the SKUs I have hardcoded, to get some code, and pass that code/id to get a different code/id. Dump the last IDs all into the UninstallLicense function of OSPPRUN and it uninstalls your slics. I manually removed ProPlus Academic MAK. I'm trying to see how office behaves when I manipulate licenses as it may be possible to reset rearms or escape notifications brick if they uninstall clean without OSPPSVC keeping record. Office Uninstall removes them but some people get grace and some people get notifications on reinstall of office.

The fact I have new tools and functions of OSPPSVC I could not achieve with WMI (Which has much more than ospp.vbs) gives me more power over office and lets me test and break and fix things to see how office responds so I learn more about it.

 

I've thought maybe leftover reg keys as the tokens + OSPP stuff that get backuped in the hive file both get nuked.