I believe his daily task uses my original task re-creation concept as I did with IR5/IORRT so that daily at same time last activated does new daily task get created at that exact moment hence new daily task is re-created at same time activation is done or at boot for office So really with Trilogy's IORRT it never gets past the 179/180th day although rearm concepts work within 30 day time frame...lol
Well it still sets the 24 hour trigger when it runs, but there is now just one task instead of when we needed 2. My code allows for multiple trigger creation, unlike the exe used in batch, so I have one task with 2 triggers. But it works the same in practice. I effectively keep it from counting down assuming nothing has changed that would lead to activation failure (like AV or the user has changed office so that the PID in use no longer works, which the latter is fixed by running EZ-Activator).
Well it still sets the 24 hour trigger when it runs, but there is now just one task instead of when we needed 2. My code allows for multiple trigger creation, unlike the exe used in batch, so I have one task with 2 triggers. But it works the same in practice. I effectively keep it from counting down assuming nothing has changed that would lead to activation failure (like AV or the user has changed office so that the PID in use no longer works, which the latter is fixed by running EZ-Activator). EDIT: Connection crapped out and caused a double post.
Hmm crappy connection leads to the dark side Banned for not deleting second post So you have combined daily and startup in one task that when run uses the auto re-creation task concept at time task runs...lol Impressive... I haven't been watching your tasks as closely as I should have
everything is back to normal, had to delete it manually from C:\Windows\System32\Tasks because I didn't see AutoKMS in the list. Probably it was from the repair install
Making progress on the next tool. I have to decide on some UI stuff so I'd like to ask. Currently I'm working in the Office 2010 Toolkit UI as is, and added 2 buttons. One for windows, one for Office. Whatever is applied decides whether something like the activate button applies to office or windows. However this is inconsistent, as the License Files and Key Checker dictate that based on the comboboxes. Also some functions will never have a Windows equivalent. There will not be a windows channel changer. I'm thinking of making a selector that will spawn a window for either office or windows, so the windows one wouldn't have office only functions and I could change the UI in a way that worked best for both (it is difficult to combine them in such a way that makes sense for both. I plan to move the EZ-Activator button to the Activation tab, which would be 100% the same except for no AutoRearm on Windows, and add more information on the Main Tab. @Bosh I'll mess with it some more and see how it goes.
Yeah, 99% of the windows code is buried in OTK and not used. Basically make a UI for Office stuff and another UI for Windows, but bundled together to have one app to download. I have a launcher that can create a window, basically I make a different window for windows and luanch that instead. I am working on windows EZ-Activator now (it will handle KMS but be simpler than office given some things can't be done or are unneeded). I still need to write windows backup code, which shouldn't be too hard. PS:Notice that AutoKMS activates windows and you can install/uninstall windows keys if you select them. All Activation tab functions have working windows functions but you cannot trigger them in OTK. But they are there and have been for a while.
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.