Hi Cody, I just thought I would throw in my 2 cents worth. I think you should create a seperate tool for Windows. The existing tool is pretty busy right now with tabs and buttons and I am sure that 95% of the people who use it don't understand most of the options, but it's that EZ Activate button that saves them. If you add more buttons and tabs I believe it is going to be way too complicated for the average Toolkit User. Further, most of the Windows people currently activate via the Daz Loader or the OEM BIOS method. I would bet that (just a wild guess here) 80+% of your Users would be getting the tool just for Office. So looking forward to the maintenance effort, every time you released a new version because of Windows changes all the Office Users would download the tool just to have the latest one. And speaking of maintenance I think it would also be far easier to maintain and test two seperate tools. No one knows what M$FT is going to come up with for Windows 8 or the next version of Office and having the Windows and Office functions comingled has got to make coding and testing more difficult. Finally, the tool is pretty big right now, so splitting out Windows will make an individual download smaller, or at least keep it from growing. I lived in Montana for years so I understand what it's like to live with a really crappy connection. Incidentally, thank you for all the hours you have put in. There are a lot of people out here who are thankful for your tool but never take the time to let you know.
The windows tool would be a separate UI so as not to bundle, and as long as I don't add OEM stuff, 99% of the windows code is the same as office, so the changes and impact are minor. As long as MS stays with SPP/OSPP then my tool code will change very little, as I use their WMI calls for just about everything.
EZ-Activator in the windows tool will check that, and all other activation functions are fine any way it goes. I removed functions in the windows ui that won't exist, like channel changer. License Tab would only come back if I added OEM Slics, which I don't want to do as it is a lot of effort.
Exactly, it would be a lot of work for nothing, and why add all those slics and keys and not have a loader of my own to use them? I'm mostly doing this to make KMS for Windows more accessible and manageable, as you have great control over office but little over windows. Also, EZ-Activator is the fix when something makes office change so the current AutoKMS PID fails, but there is nothing for windows. Basically the windows tool would be the key tab, activation tab, and backup tab, made to work on windows.
If it is needed, otherwise no. I've never worked with a windows activation backup but it is easier than office since there is no registry dumps needed or registration. I'm the only one who has an Office Backup that will work if converted EZ-Activator style and work on a different architecture. The activation stuff works but if it is converted, office won't auto fix the registry. I take the users Registration key and create copies for the other architectures and no one else does this. I don't have to do any of that for windows. One thing has me wondering, for all Windows backup devs:Why are you guys backing up the pkeyconfig.xrm-ms? Not 100% sure about windows but some people think you need that, and you usually don't. The only time it is needed is in frankenbuilded cases like the first Office RTM Hack (BETA MAK Restoration). I notice every tool I've tried so far, from old to Josh Cell' new tool all save that file. I already have the code to get the key from registry for Windows (just a matter of changing the registry path from my office code, which I open sourced) and likewise applies to the tokens code (just a different folder path). I basically make a copy of office, gut out the registry stuff, and change the paths and class references in the code from Office to Windows, a few minor changes and I have a Windows backup.
I don't remember PMR's backup tool needing reboot If true wonder if there is solution in this like IORRT/AR Daily or at boot...lol With one task with multiple triggers of course
It just does the tokens but not the registry, so rearm tricks don't work, as rearms are stored in the registry. Note that I can do tokens only restore of office, but you get the rearm count from before the restore. The WPA key you destroy in IR5 is like the OfficeSoftwareProtectionPlatform key in Office, only office locks out if you delete that.
I want to do just one task in IORRT to simplify Shouldn't be to hard to update IORRT? And your approaching a new solution title
Not sure how to add multiple triggers via batch, or if you even can via the schtasks.exe. But you'd need to be able to do that to make one task in batch, or find a separate batch tool that could do that. It gets harder that you could probably use an XML but would break XP compatibility and my ability to detect IORRT, given XP can't use them. Maybe you could manually create the single task my modding my AutoKMS task, then getting whatever files/registry you need, and use those to install the task.
Hello CODYQX4, I try the version 2.2.3, but when I check the status in ACTIVATION / LICENSING FUNCTIONS, to check the status of my Office. version 2.2.3 show an error. you can see the follow pick show that office is ok. but when I go down in INFORMATION CONSOLE, this version show this information and Office Toolkit say that I have install OFFICE 2010 RETRAIL CHANNEL, when I only have install VOLUMEN VERSION. the error say: LICENCE DESCRIPTION: Office 14 RETRAIL channel LICENCE STATUS: Unlicensed ERROR 0xC004F014 BUT, in version 2.2.2 When I check the license status, this version only show me that I have a Volumen Channel, this version dont´t show that I have install RETRAIL, when I don´t have any retrail. I´m sorry for my poor english, but I expect that I explain this problem well. Thanks CODYQX4
You have verbose check enabled, which all those unlicensed are is things you don't have a key active for them, verbose is to check if license installs got screwed up.