Главная » 2014 Июль 19 » Microsoft Toolkit 2.5.2 Stable
Microsoft Toolkit 2.5.2 Stable | 12:30 |
[center] [/center] Microsoft Toolkit – многофункциональный KMS-активатор для операционных систем Windows Vista, 7, Windows Vista, 7, Windows 8/Server 2012, Office 2010/2013; Windows 8.1/Server 2012 R2, а так же Microsoft Office 2013 в этих операционных системах. Microsoft Toolkit - multifunctional KMS-activator for the operating systems Windows Vista, 7, Windows 8/Server, 2012, and Office 2010/2013. Includes a set of tools for managing licenses and activation. He can use the KMS-activated, even if you use a retail Retail license. So we get a single activator for modern products Microsoft. This is a set of tools and functions for managing licensing, deploying, and activating Microsoft Office and Windows. All output from these functions is displayed in the Information Console. All functions are run in the background and the GUI is disabled to prevent running multiple functions, as they could conflict or cause damage if run concurrently. The Microsoft Office Setup Customization Functions (Customize Setup Tab), AutoKMS Uninstaller (if AutoKMS is installed), AutoRearm Uninstaller (if AutoRearm is installed), Office Uninstaller and Product Key Checker work even if Microsoft Office or Windows is not installed/supported. For information about individual functions, read further. Settings: Microsoft Toolkit Settings KMS Options Tab: KMS Server/Port To Use: Allows you to set what KMS server and port should be used when attempting KMS activation. Unless you have a real KMS server or a network host running a KMS Emulator or Server you will want this set to 127.0.0.2. Whatever the numerical box says will be the used port. KMSEmulator will use this port but it must be open on your PC, or the process using it may be terminated. NOTE: The Office KMS Server/Port is used when activating Office based products and Windows KMS Server/Port when activating Windows based products. KMS PID To Use: Allows you to set what KMS Extended PID should be used by KMSEmulator when attempting KMS activation. Changing the PID can help fix persistent KMS activation failure or KMS failing Genuine Validation, but in most cases you want to leave this alone. You can pass a valid KMS PID, the string DefaultKMSPID to use a hardcoded default, or RandomKMSPID to generate a random string matching the KMS PID format. NOTE: The Office PID is used when activating Office based products and Windows PID when activating Windows based products. NOTE: You cannot change the KMS PID used for KMS Activation for KMS Servers. If a KMS Server fails Genuine Validation, this Setting will not help. Activate Using KMS Emulator: Uses KMS Emulator to perform KMS activation. Unless you have a real KMS server or a network host running a KMS Emulator or Server you will want this enabled. Delete KMS Host/Port After Run: Removes the KMS server name and port from the registry after KMS activation. Force Open KMS Port By Terminating Processes: Kill any processes using the KMS Port so you can run KMS Emulator on that port. NOTE: This is only performed if KMS Activation fails, allowing KMS Emulator to silently fail and a KMS Server Virtual Machine to be used. KMS Server Service Tab: KMS Port To Use: Allows you to set what KMS Port the KMS Server Service will listen on. Any clients using this service must use this KMS Port. KMS PID To Use: Allows you to set what KMS Extended PID should be used by this service when sending KMS activation responses to KMS Client applications. You can pass a valid KMS PID, the string DefaultKMSPID to use a hardcoded default, or RandomKMSPID to generate a random string matching the KMS PID format. Force Open KMS Port By Terminating Processes: Kill any processes using the KMS Port so you can run KMS Server Service on that port. License Display Tab: Show CMID: Shows your KMS Client Machine ID. You won't have one if you aren't using KMS and haven't requested activation. Show Unlicenses: Shows ALL possible product keys you can install, not just the ones you have installed. Showing this helps in troubleshooting. Paths Tab: AutoKMS: Choose where AutoKMS will be installed. AutoRearm: Choose where AutoRearm will be installed. KMS Server Service: Choose where KMS Server Service will be installed. License Backups: Choose where License Backups will be saved. Microsoft Toolkit FAQ My AV/Firewall Detected a Virus when activating.: Most major AV’s have decided to flag KMSEmulator as a virus/hack tool, because it can be used for piracy and many AV’s flag cracks. The file is completely safe but you must add it to your AV exclusions for proper use of KMS activation. So add AutoKMS's (AutoKMSAutoKMS.exe), KMS Server Services's (KMSServerServiceKMS Server Service.exe), and KMSEmulator's (Microsoft.NETFrameworkv2.0.50727vbc.e xe) path to AV/Firewall exclusions. Can I really trust these files?: They are confirmed safe by MDL community and our reputations would be damaged if we were trying to infect you, but if you still don’t trust the files don’t use KMS activation. You can use AutoRearm to keep Microsoft Office in grace period forever without any AV Configuration/False Positive hassles. I tried to activate via KMS and it failed.: First be 100% sure your AV and any security products (including built in Windows Products) are not interfering. In any other case, please post to the forum with the output when you attempted activation. Microsoft Office licensing is shot/Setup window shows on start of Office/I get red bar and nag.: If your Microsoft Office licensing gets damaged or marked as tampered, Microsoft Office will try to repair itself and when it does you will be in Notifications Mode (with 0 rearms). The only way to resolve this is to activate Microsoft Office successfully (You’ll have to use KMS due to lack of MAK/Retail keys). If you successfully activate you’ll be activated with 5 rearms. I have an issue or question not contained in this readme.: If you are experiencing a problem and you have read through relevant parts of the readme (99% of questions I am asked are contained here in the readme so I don’t answer those due to it being a lack of time and delaying those with questions/problems not in the readme. If you have a question that isn’t related to issues with activation troubleshooting, freely ask. Otherwise follow the troubleshooting steps so you can post all the info I need to help you. Troubleshooting/Support Guide General: Please do not send support requests via PM. My PM fills up quick and other people besides me can help if you post it publicly. Not following the rest of this guide will mean I will ignore the post. "KMS failed please help" does not give me enough info. Be absolutely 100% positive no AV/Firewall/Security are interfering. There are few reasons KMS fails and this is the main one. Do not assume things are OK because no alert occurred, make sure things are excluded. Steps: For whatever the problem is, if applicable, copy a full amount of the output/log. EX; If AutoKMS is failing get the AutoKMS.log contents, if another function is failing get all of the output sent to the Information Console. Get the output of Check Activation Status Post the output gathered in Step 2. If it is large, dump it to pastebin.org or a similar site and post the link to that dump in Microsoft Toolkit thread and explain that you had problems. You may have to obfuscate it (hxxp:// instead of http://) if your post count is too low to post links. Requirements: Microsoft .NET Framework 4.0 or 4.5 (Not 3.5) Microsoft Office 2010 or Later for Office Toolkit Support Windows Vista or Later for Windows Toolkit Support Credits: -Bosh for the original GUI Design and co-development of Office Toolkit -ZWT for the original KMSEmulator -letsgoawayhell, Phazor, nosferati87, and mikmik38 for KMSEmulator fixes and improvements -MasterDisaster, FreeStyler, Daz, nononsense, and janek2012 for work on Key Checker 2.5.2 -Added Label to show Microsoft Office Setup Version and Architecture on Customize Setup tab. -Added more checks to Add Languages and do better filtering of Language Packs. -AutoKMS no longer attempts activation/displays error when there are no KMS keys installed. -AutoKMS skips running if a BSOD occurred within 30 minutes of the last Scheduled Task run. -Fixed Customize Setup failing if file extensions were not lowercase. -Scheduled Tasks now retain their last run date. -Updated TAP Driver. Год выхода: 2014 Версия: 2.5.2 Stable Платформа: Windows® Vista/7/8/8.1/Server 2008/2012 Язык Интерфейса: English Таблетка: оно и есть лекарство Размер: 50 Mb [center]Скачать Microsoft Toolkit 2.5.2 Stable[/center] Цитата | |
| Категория: Программы | Просмотров: 312 | Добавил: gorodoksmol | Теги: | Рейтинг: 0.0/0 | | |
Рекомендуем ещё:
| |
| Всего комментариев: 0 | |
