Most of the things done by the toolkit is similar to the script, the registry would have been overwritten in that case. If everything is working then no need to worry.
Yes, I know. But when you have been in this field for so long, you know that somewhere in the evaluation OS code, remains parts of that code indicating that the install was done with an evaluation ISO. Even when you activated it successfully and looks to be a regular OEM source. This is specially true with M$ stuff. I would not trust M$ eval code to do an important (to me) install, like in the machine I would use every day. What I need is a non eval ISO file. That is why I had to use BIE's release. That is why I asked for a link to a clean x64 OEM ISO. Best regards
You are in principle, but theres a little more to it than just running the CMDs. Do you have any experience with DISM?
It's because the keygen included in the program. It's a false positive. Don't worry about. It's clean and safe to use.
Activating Visio Premium with Universal KMS Firstly let me say that my low level skills may mean that this query has been asked and answered previously even though I have searched this thread over the last couple of days. if that is so I apologise. I have a Win 7 Pro x86 OS I activated with the Universal KMS Activator. It is running Office Professional Plus 14.0.4760.1000 MAK edition which self activated (using the MAK serial I suppose) straight after installation. Now I need to get Visio Premium working on this machine (not willingly - Visio is far from an ally of mine but I need to use it for a couple of network projects) My chief problem appears to be the issue of Visio specific OSPP.VBS commands. If I had installed Visio first this may not have been a problem. Visio Premium and Office Professional Plus share the same directory, and that holds the OSPP.vbs script so if I : cscript "%PROGRAMFILES%\Microsoft Office\OFFICE14\OSPP.VBS" /inpkey: <visio premium kms key> then cscript "%PROGRAMFILES%\Microsoft Office\OFFICE14\OSPP.VBS" /sethst:localhost and then activate command, the Office key and activation is modified but the Visio key and activation are not. Is there a Visio specific switch for that command that anyone is aware of?
Phazor, As soon as I have finished installing the converted Eval in the disk I have reserved for this test, I will test the KMSA 6.0. I am very interested in seen that KMSA 6.0 keeps advancing. I will take a couple of days as I will have to unplug the current disk been used and perform the W7 install. I want to make the test on the same mainboard and a similar model disk that failed BIE's KMS and KMSA 6.0 activation before. Best regards
Phazor, In the scripts, the instruction before the last (the last is Pause) is writen like this: Imagex /export "C:\ent\install.wim" 1 "C:\new\install.wim" "Windows 7 ENTERPRISE" The proper syntax is: Imagex /export C:\ent\install.wim 1 C:\new\install.wim "Windows 7 ENTERPRISE" The quotation marks on C:\ent\install.wim are not to be used. This I write because I want our peers to be able to make the change. The converted OEM ISO is ready and I have burned it. I did a preliminary test and I could verify the computer detects is bootable. Something that is very desirable vs inserting a boot image. I have learned a lot during this process. Thanks. Best regards
Results of Activation of Converted Enterprise Evaluation x64 version to non Eval OEM Phazor, Just like with the BIE Enterprise x64 Version, UniKMS Alpha2.7 could not activate the Enterprise Evaluation x64 converted to Enterprise OEM x64 (Non-Evaluation) that was produced with your script. It was successfully converted to a non evaluation, bootable, installation ISO. But could not be activated. The error was: Incorrect Data. Same error as with BIE's activation hack. I have now confirmed that this is one of the mainboards with controller (SATA3) that will not allow ZWT kg to read the disk. I will make another test tomorrow, swapping the disk to the secondary (SATA2) controller, after installation of the drivers for that controller. Best regards