@abbodi1406, I just wanted to shout out a huge Thank You! Your KMS_VL_ALL is intelligent, yet simplistic and very reliable. Keep up the great work. Myself and many others have a lot of respect for you. Your work is very much appreciated.
Feedback: Just installed the daily task and onlogon task on my second desktop and the tasks were set up as expected. However, it took three reboots before any reactivation took place. Any idea why it did not reactivate on the first attempt?
My guess? timed out because of tunmirror failing to re-up the packets. Like I said, we'll need to wait for CODYQX4 to finish his project. He actually tunes the code a bit. We're still working on the first method. Even the jean_phile service uses the same basic handling. Of course if CODYQX4's version doesn't fix it for you, when it comes out, then your computer probably sucks too much to avoid the activation timeout. You've not listed what kind of computer/os/hardware you're trying to use, but I'd guess that it's not up to par.
Virtual: all windows, office 2010 / 2013 h t t p://forums.mydigitallife.net/threads/41010-KMSEmulator-KMS-Client-and-Server-Emulation-Source/page173?p=844636&viewfull=1#post844636
Hardware: Pentium Core 2 Duo 2.53 GHz; 4 GB RAM; Software: Win 8.1 Enterprise x64; Office 2013 x32 Does that 'suck too much', or what?
I don't think that's the right way of going about this. The mediastatus gets flipped on when in use. Are you setting the ip address of the adaptor to 10.3.0.1 255.255.255.0 before starting the service?
Hi, appreciate any help, I activated office 2013 but I get error 0x4004F040 "product was activated but owner should verify the products use rights". Is this something to be concerned about?, can it be corrected?, o just leave it as it is, Found the answer myself: (from MS) 'Product was activated but the owner should verify the Product Use Rights' informational warning (error 0x4004F040) When you run the command cscript ospp.vbs /act on an Office client, you receive the error 0x4004F040 and the error description text is "The Software Licensing Service reported that the product was activated but the owner should verify the Product Use Rights." If the 'License Status' value in the Ospp..vbs output is LICENSED, then your Office license is correctly established and this error can safely be ignored.
And x86 can 'see' 4 GB RAM? Max 3 GB if my poor memory serves me right, so how would that be any better?
Just some info on this: If you want to see full output remove ( >nul 2>&1) from script if you want to see only errors just remove 2>&1 as it will display errors in that command line. i.e., Action - remove ( >nul 2>&1) result - can see ALL messages from command. Action - remove ( 2>&1) only result - can ONLY see errors and NOT success messages.
It's about how fast it runs, not how much memory it uses. The extra ram doesn't really get used much. Literally the only time I've seen a program use more than 1GB of ram is when I export indexes to the install.esd recovery compression format that win8.1 included with dism. Some behemoth-like super-multi-threaded and highly memory intensive beast-like program like that would actually take use of the extra memory. Every other program on the planet will not. Games typically use about 700mb of ram. Web browsers use like 100-300 depending on how much stuff is going on. When you actually calculate what you can do without slowing your computer down to a crawl, and the benefit of having 1 extra gb of ram, it's kind-of a no-brainer. Just as a tip, most programs take use of the x86 Large Address Aware flag, but there is a Program called Large Address Aware 2.0.4, where you can check the LAA flag box on a lot of x86 programs to allow them to use more memory. They frequently don't use more memory anyway, but it's a neat little thing you can use for situations where a program would theoretically use a TON of ram, and you would prefer it to use a gig more. I wish I could articulate more clearly about why it's better to use x86 for older systems, but I guess I'm just terrible with arguing points. My main point is that x86 is MUCH faster on sub-par systems. A good rule of thumb is that if your system is not at least 4-core and has ddr3 1600 ram or greater, don't use x64 win8.x
It's not the only VPN driver out there. You could try using other drivers using the methods we use if yours is not installing or being used correctly. You could even probably try an old tap driver. Maybe an old tap0801 would work better... Maybe a VMware VPN driver would work better. Try installing a different VPN driver and using "route print" to locate the name for the set ip line and see if you can sub out one that works.
KMSAuto Net v1.0.3 How to setup the KMSAuto Net v1.0.3 for automatically run & activate Windows 8.1 Pro VL & Office 2013 VL every 25 days without connection to the internet?
Thanks for your scripts. For my personal use, I redirect all the echo commands to a file and added time stamps. I also schedule the script on the 1st and 15th day of each month via the task scheduler. On my desktop PC connected via Ethernet, it takes about 5 seconds to setup tunemirror and 4 seconds to setup kmsserver. On my 3 laptop PCs connected via WIFI, tunemirror is ok after about 90 seconds and kmsserver after about 10 seconds.
I think you can add ipconfig /renew >nul 2>&1 before timeout /t 3 /nobreak >nul 2>&1 "KMS Client.exe" %port% %kmsip% Windows81 >nul 2>&1 to Refresh network settings. This can avoid the computer can not find 10.3.x.x kms server.
dos AutoKMS_VL_ALL-6.0.4b work with enterprise?? i made a enterprise aio x86 and x64 and added the $oem$ .then tested it with VMware Workstation. but its not activated.
Sorry guys, I've got a bit lost amongst the auto re-activation posts, it's not so important for me but anyway I'm posting my feedback from testing it with abbodi1406's new Sever Service scripts... 01: Ran 1-Tap-Adapter.cmd 02: Ran 2-KMS-Service+TunMirror.cmd 03: Ran Create-Task.cmd Manually edited the task and changed to 'At logon'. Removed Win key (slmgr.vbs -upk), watermark appears on desktop (non activated). Reboot. Command prompt window on desktop, wait a few secs for it to go (security suite is loading) - F5 to refresh desktop, watermark goes, Windows has been activated (checked with slmgr.vbs). Removed Win key and rebooted several times, activates at every reboot and activation expire time has increased - all working fine. Obviously I'd only set the task like that for testing. Whether connected or disconnected the results were always the same - always re-activated upon reboot. Code: Check Expiry... --------------------------- Windows Script Host --------------------------- Windows(R), Professional edition: Volume activation will expire 19/05/2014 07:36:30 AM --------------------------- OK --------------------------- Uninstall Key - Reboot - Check Expiry... --------------------------- Windows Script Host --------------------------- Windows(R), Professional edition: Volume activation will expire 19/05/2014 11:35:13 AM --------------------------- OK --------------------------- Uninstall Key - Reboot - Check Expiry... --------------------------- Windows Script Host --------------------------- Windows(R), Professional edition: Volume activation will expire 19/05/2014 11:37:47 AM --------------------------- OK --------------------------- Uninstall Key - Reboot - Check Expiry... --------------------------- Windows Script Host --------------------------- Windows(R), Professional edition: Volume activation will expire 19/05/2014 11:52:47 AM --------------------------- OK --------------------------- Edit: Reversed the procedure for uninstall... 01: Deleted task. 02: Ran 2-KMS-Service+TunMirror.cmd 03: Ran 1-Tap-Adapter.cmd Everything cleaned up fine. Well done again abbodi1406