Also, it's a Multiple Activation key and i don't use KMS in the infrastructure, is that bad to use this method I hope not because i already started to deploy Win 7 and activate it this way?
No, this method is fine - in fact, you almost need to use slmgr to activate if you're going for automation. You should be able to do the above assuming your MAK key is in the xml file correctly and get fairly unattended setup and activation. If you still get stuck with an "OK" click, consider wrapping your slmgr steps in an autoit script or similar. Actually, i did exactly what you suggested me. I put this command in a task sequence instead of letting it in the application list and everything went fine.
No more "Ok" to click. You need to be a member in order to leave a comment. Sign up for a new account in our community. It's easy! Already have an account? The way I do it is with the netdom command. Chris, MySysprep2 works well at adding the system to the domain during sysprep, but it is not unattended.
It will prompt for Username, Password In the clear , and computername. There is one for x64 also. I am trying to join the domain as well but I need to run a scriptit script to name the PC according to company naming conventions. I use wmic and it forces me to reboot before it pulls the new name.
Will your sysprep2 use the currently changes name or would it require a reboot as well? Thanks for the guide, I have done exactly as you did but I have some issues, only the last prompts are manage by the unattend.
Language, EULAPage appears and disc options is prompting, also the licens key is not entered and activated by it self. Any ideas? Bohack thank this helped me create my first ever sysprep xml file. Also to allow a popup box to enter the admin password to be entered since admin password per computer is unique. Glad it helped… There is a lot missing from sysprep that I hope the next release fixes… Mainly joining domains, after a rename and allowing for prompts.
Yes it is missing those things. Sysprep I discovered if auto join domain it joins before naming the pc. Also like you said no prompts such as for admin password. I solved these issues by using mysysprep in order to name pc before auto joining domain, allowing for admin password to be entered, and even if wanted allow for selection of multiple domains from a dropdown menu.
According to this page on Technet, you do not need to input the KMS key separately if you run sysprep on an install from Volume License media. Running Sysprep. If no rearms are left, the Sysprep operation completes but the activation timers are not changed and an error is returned that explains the situation. My experience in the past has been if you do not put a KMS key, then when you try to use the KMS server it fails because it defaults to look for a retail key.
However this was on and not R2 so something might have changed with this release. The slmgr. If you put the KMS dummy key in the unattend. I keep encountering the same exact problem. Here are the steps I am following. I then clone the hard drive using a hardware disk duplicator we have on site. This should create multiple drives ready to be deployed into machines. However, when I boot up, I am asked all the questions I expected to be answered in the file. How do I get Windows to activate automatically when I apply the wim file?
Monday, April 4, PM. Best regards. Thursday, April 7, AM. OK, that question isn't getting any attention. How about I rephrase it? How do I get Windows to activate automatically when I apply a wim file? Wednesday, April 6, PM. During the next reboot PNP is initiated and the Out Of Box Experience is run; this is similar to a preloaded laptop or computer from the factory starting up for the first time.
The unattend. The following process will automate the sysprep so next reboot it will only ask for computer name. Step 1. Step 2. You will need to allow Windows SIM to access the install.
Step 3. In this tutorial I used x64 amd64 media, this also works for x86 media; using the same steps. Step 4. Step 5. It will be added to the answer file in the center. Step 6. Step 7. Click on the Shell-Setup in the answer file section and fill in the TimeZone under properties. Step 8. These all related to the Windows Update protection. Step 9. Step
0コメント