I don't know. Remember that I am learning. I can tell you that in general, the process should be the same, but you must have the right names. As for OS versions, I remember reading a post about their image names some where at MDL. Just don't remember where and I looked for a saved link and seems I did not saved it. As for the names of the packages inside the image, I don't know and I don't remember seen such a post here at MDL. I think you will be better served if MasterDisaster can make some time to answer your questions. We all could learn from the process. Best regards
jsmithy I suspect I'm on the right track with my post but I'm reluctant to mess with something that is currently working so well so I didn't bother pursuing the matter further. More than likely, MD has the prescription to remove the evaluation origins but may not want to share it at this time. The idea may be to see if MS can successfully attack installations from the evaluation images before releasing the scripts that erase those origins.
@gmaslin I don't know the name of the package for Server 2008 R2, but you can find out using dism. dism /Mount-Wim /WimFile:C:\dvd\sources\install.wim /index:1 /MountDir:C:\mnt dism /Image:C:\mnt /Get-Packages | Find "WLMS" The output of the last command will be the names of the required package dism /Image:C:\mnt /Remove-Package /PackageName:<name of the package found> dism /Image:C:\mnt /Set-ProductKey:<GVLK key for index value> dism /Unmount-Wim /MountDir:C:\mnt /commit You would have to repeat the above steps for all the index values.
Okay. OP wanted to hear feedback about the v6 beta, so here's this machine's story. Before... Originally, twas a BIE month-something-year-2010 install. Which /seemed/ to work but every few months (or was it: 'month' (singular)? I don't recall that much, sorry) it was nagging about activation again, so run the BIE stuff as admin and Hosanna. Tried a few other things as well, because I got worried a bit, but when MS stopped nagging after a while, I stopped looking. Until now, when it turned out the 'number of rearm' rounds was depleted: 0 rearms left. Oops. Then I went nuts and tried the lot: The Daz loader (1.9.2) doesn't even give access to its 'install' button (run as admin) for whatever reason (I tried to seek through that 1K+ pages thread but this site's search + my search foo didn't deliver, so I don't know PRECISELY why that happened to me except that I encountered a lot of notes saying something along the lines of 'you use BIE so you must be retarded beyond belief' and no further help there. Dang.) The RemoveWAT wasn't an option when I panicked for real because the RemoveWAT tool panicked even better... by crashing. Period. Next I tried KMS v5.0 ... no dice. Some RPCyayada failure (error code 0 (!)) because KMS seemed to fail dramatically in step #3 there. Running KMS.exe in other ways (it was sitting in AppData/Local/ anyway, so I copied it someplace I could try it together with all the slmgr script-stuff I found on this site). Busted. Badly. How many crashes and 'no more rearm' reports later I don't know, but then I found IR4 (also on this site; it turned out to be a life saver!). Oh, wait. KMS beta v6? Looks nice, failed to run through; reported a failure in the script execution and no worky. 0x8007000D, 0xC0048004 and all the rest. Sorry, haven't written down what it reported exactly; it failed to complete, anyway. Bottom line: it did not deliver, while KMS v5 did -- if you help it. (On Second Thought, now that I'm writing this: v6beta /might/ have worked, when KMS v5 started to work, but then v5 gave me a lot more control over the process and I wasn't exactly into full-auto tools anymore at the time v5 started to do what I hoped it would.) What works when you start out with 0x8007000D plus other trouble (number of rearms equals zero ~ 0) The magic happens when you FIRST run IR4 to completion, which itself succeeds (= works as it says it will), so that's - install - rearm and another reboot later you run KMS fix v5.0 and suddenly that bugger works as advertized! steps 1,2,3,4 an no failure in steps 3+4 any longer! A check in the Control Panel:SysteM reveals the success is for real: status: activated. Summarizing: Thank You for IR4, KMS, and the v5.0 script. v6beta might have worked out at the moment v5 did, but now I have an activated box again so it's hard to tell what v6 delivers over v5: the latter gives me more control as I can step through, and /that/ I like. Applies to a Win7 64 Ent which has been updating MS KB#'s regularly up to about a week ago.
Heh. (Okay, tested v6beta on another box just now and there it also fails. Error message: 'this key has been blocked' (or similar words, didn't write them down). (The 'key is blacklisted' thing is maybe because it was another BIE install before? :-S ...) Anyway, that one only required KMS Activator v5.0 as the number of rearm cycles hadn't yet run out (fresh install on a VM, just to see whether v6 would do some good after running a series of MS updates on it. Alas, it doesn't. Pity. v5.0 delivers, though, absolutely. ) Someone else mentioned today that step #2 wouldn't correctly set the IP to localhost and that he had to do it manually using slmgr.vbs -skms 127.0.0.1:1688 but I didn't have that issue on this second machine; only step #4 failed the first time, but return to main menu, restart KMS and then waiting a bit before running another #4 activation request solved it.
Question about Server Datacenter 2008 x86 and the R2 release Hey i'll got a question about Server Data 2008 normal x86 version and the R2 when i'll won't to aktivate these 2 versions it's say's you got a wrong DNS name how can i'll fix this I'll most say i'll will tryed with the KMS Aktivator 5.0 is this problem on these version resolved.? on the kmsa 6.0.? Sorry for my bad Enlische as wel greetings
I honestly have no idea, since i never ran into any such problem myself. Perhaps it has to do with the fact that youre executing it under XP? Can you try it on a Win7 installation instead?
Remember that this app is merely an Alpha, a concept-test if you will, it does not install any keys or anything, all it currently does is providing the emulated KMS host and the activation commands, which means GVLK installation and HostMachineName setting is up to the tester.
You should be able to activate with 5.0 if you execute Option 5, or 1-4 manually. (You only need the correct GVLK and the correct HostMachineName.)
Very soon. I have completed almost everything two days ago, all thats left to do now is looking it over one more time and then giving it a thorough test-run to see if everything works when compiled into exe form. (PS: I will send you a copy in private before posting the Beta/RC in public since i think youre an excellent tester, not to mention way more skilled in CMD than i am.)
Thanks for the fast reply. I appear to only have one rearm left so I'll spare it for the moment since I don't really have the time to reinstall the whole thing should anything bad happen. I'll try this as soon as I have trouble with my current temporary activation. Edit: did what you and timesurfer said, it worked fine, now my Win 7 Enterprise is properly activated