Activating Windows 7 with MAK passed in Unattend.xml via WDS Announcing the arrival of Valued...
Is the Mordenkainen's Sword spell underpowered?
Why not use the yoke to control yaw, as well as pitch and roll?
Recursive calls to a function - why is the address of the parameter passed to it lowering with each call?
Married in secret, can marital status in passport be changed at a later date?
How was Lagrange appointed professor of mathematics so early?
What were wait-states, and why was it only an issue for PCs?
Raising a bilingual kid. When should we introduce the majority language?
Can gravitational waves pass through a black hole?
Putting Ant-Man on house arrest
A journey... into the MIND
Who can become a wight?
What is the ongoing value of the Kanban board to the developers as opposed to management
Etymology of 見舞い
2 sample t test for sample sizes - 30,000 and 150,000
When does Bran Stark remember Jamie pushing him?
Kepler's 3rd law: ratios don't fit data
Pointing to problems without suggesting solutions
Is Mathematical Biology analogous to Mathematical Physics?
Suing a Police Officer Instead of the Police Department
Like totally amazing interchangeable sister outfit accessory swapping or whatever
Why these surprising proportionalities of integrals involving odd zeta values?
Can the van der Waals coefficients be negative in the van der Waals equation for real gases?
Protagonist's race is hidden - should I reveal it?
Why do people think Winterfell crypts is the safest place for women, children & old people?
Activating Windows 7 with MAK passed in Unattend.xml via WDS
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Windows 7 Enterprise MAK needs Reactivation?Windows 7 deployment thru WDSUnattended XML file - Product Key doesn't activate the first timeActivate Windows 8 with Server 2008 R2 KMS HostWindows 7 Activation during image deploymentUsing WDS to Deploy Custom OEM ImageCan't activate volume license Office 2013 installed on retail Windows 7 via KMSHow to determine what kind of key Win7 was activated with (retail or volume license)?Can Windows 7 Professional OEM be imaged using WDS?Run PowerShell-Script from Server in unattend.xml
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have configured WDS to deploy a Windows 7 Pro image (Volume Licensed) and I'm using an unattend.xml file for the configuration. The only problem I'm running into is activation. I'm passing a MAK Volume License key in the unattend.xml file but after the image gets pulled down from the server and it installs and the machine reboots, not only does it NOT activate but the license key specified in the unattend.xml file doesn't appear; a totally different license key is there (in My Computer in the license/activation section on the bottom).
I'm entering the product key in the correct spot in the unattend.xml file (or so I'm led to believe from Microsoft's documentation) so I'm not sure what's wrong?
active-directory windows-server-2008-r2 windows-7 wds
asked Jan 15 '14 at 7:46
MisterMikeMisterMike
10814
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have configured WDS to deploy a Windows 7 Pro image (Volume Licensed) and I'm using an unattend.xml file for the configuration. The only problem I'm running into is activation. I'm passing a MAK Volume License key in the unattend.xml file but after the image gets pulled down from the server and it installs and the machine reboots, not only does it NOT activate but the license key specified in the unattend.xml file doesn't appear; a totally different license key is there (in My Computer in the license/activation section on the bottom).
I'm entering the product key in the correct spot in the unattend.xml file (or so I'm led to believe from Microsoft's documentation) so I'm not sure what's wrong?
active-directory windows-server-2008-r2 windows-7 wds
asked Jan 15 '14 at 7:46
MisterMikeMisterMike
10814
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
How are you attaching the unattend file? Are you embedding it in the image, or attaching it in WDS? It’s possible that the system is using a different unattend file based on implicit search order. Is there anything in the log files that might help? Also, you are installing Windows 7 pro x86, right?
– dwolters
Jan 22 '14 at 19:14
It's Windows 7 Pro x64 that I'm installing. The file is being attached via WDS. I know the file is being read and working properly as everything else in the file BUT the MAK activation is working. Nothing in log files.
– MisterMike
Jan 23 '14 at 2:20
add a comment |
I have configured WDS to deploy a Windows 7 Pro image (Volume Licensed) and I'm using an unattend.xml file for the configuration. The only problem I'm running into is activation. I'm passing a MAK Volume License key in the unattend.xml file but after the image gets pulled down from the server and it installs and the machine reboots, not only does it NOT activate but the license key specified in the unattend.xml file doesn't appear; a totally different license key is there (in My Computer in the license/activation section on the bottom).
I'm entering the product key in the correct spot in the unattend.xml file (or so I'm led to believe from Microsoft's documentation) so I'm not sure what's wrong?
active-directory windows-server-2008-r2 windows-7 wds
asked Jan 15 '14 at 7:46
MisterMikeMisterMike
10814
I have configured WDS to deploy a Windows 7 Pro image (Volume Licensed) and I'm using an unattend.xml file for the configuration. The only problem I'm running into is activation. I'm passing a MAK Volume License key in the unattend.xml file but after the image gets pulled down from the server and it installs and the machine reboots, not only does it NOT activate but the license key specified in the unattend.xml file doesn't appear; a totally different license key is there (in My Computer in the license/activation section on the bottom).
I'm entering the product key in the correct spot in the unattend.xml file (or so I'm led to believe from Microsoft's documentation) so I'm not sure what's wrong?
active-directory windows-server-2008-r2 windows-7 wds
active-directory windows-server-2008-r2 windows-7 wds
asked Jan 15 '14 at 7:46
MisterMikeMisterMike
10814
asked Jan 15 '14 at 7:46
MisterMikeMisterMike
10814
asked Jan 15 '14 at 7:46
MisterMikeMisterMike
10814
asked Jan 15 '14 at 7:46
MisterMikeMisterMike
10814
asked Jan 15 '14 at 7:46
MisterMikeMisterMike
10814
10814
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
How are you attaching the unattend file? Are you embedding it in the image, or attaching it in WDS? It’s possible that the system is using a different unattend file based on implicit search order. Is there anything in the log files that might help? Also, you are installing Windows 7 pro x86, right?
– dwolters
Jan 22 '14 at 19:14
It's Windows 7 Pro x64 that I'm installing. The file is being attached via WDS. I know the file is being read and working properly as everything else in the file BUT the MAK activation is working. Nothing in log files.
– MisterMike
Jan 23 '14 at 2:20
add a comment |
How are you attaching the unattend file? Are you embedding it in the image, or attaching it in WDS? It’s possible that the system is using a different unattend file based on implicit search order. Is there anything in the log files that might help? Also, you are installing Windows 7 pro x86, right?
– dwolters
Jan 22 '14 at 19:14
It's Windows 7 Pro x64 that I'm installing. The file is being attached via WDS. I know the file is being read and working properly as everything else in the file BUT the MAK activation is working. Nothing in log files.
– MisterMike
Jan 23 '14 at 2:20
How are you attaching the unattend file? Are you embedding it in the image, or attaching it in WDS? It’s possible that the system is using a different unattend file based on implicit search order. Is there anything in the log files that might help? Also, you are installing Windows 7 pro x86, right?
– dwolters
Jan 22 '14 at 19:14
How are you attaching the unattend file? Are you embedding it in the image, or attaching it in WDS? It’s possible that the system is using a different unattend file based on implicit search order. Is there anything in the log files that might help? Also, you are installing Windows 7 pro x86, right?
– dwolters
Jan 22 '14 at 19:14
It's Windows 7 Pro x64 that I'm installing. The file is being attached via WDS. I know the file is being read and working properly as everything else in the file BUT the MAK activation is working. Nothing in log files.
– MisterMike
Jan 23 '14 at 2:20
It's Windows 7 Pro x64 that I'm installing. The file is being attached via WDS. I know the file is being read and working properly as everything else in the file BUT the MAK activation is working. Nothing in log files.
– MisterMike
Jan 23 '14 at 2:20
add a comment |
1 Answer
1
active
oldest
votes
From the Picture that you posted, you are adding the x86_Microsoft-Windows-Shell-Setup node, and not the x64_Microsoft-Windows-Shell-Setup to your unattend file. Changing this to the appropriate architecture should solve this problem.
Hope this helps,
answered Jan 23 '14 at 18:14
dwoltersdwolters
1,240711
Sorry, that picture was just for reference to what the option is and what pass it's being added to (not for the architecture). I'm using the proper architecture.
– MisterMike
Jan 24 '14 at 1:07
@mistermike You can enter the proper key using an elevated command prompt and the command “slmgr.vbs /ipk <your kms key>”? You can then force activation with “slmgr.vbs –ato”. If running the command manually works, you can script it and add it to the unattend file. Do you have enough clients activating to exceed the KMS minimums (25 for Windows 7)?
– dwolters
Jan 24 '14 at 13:47
So there's no way to pass in the key and make it activate without running something extra? I feel like solutions such as those are "workarounds" and while they work aren't what was intended for the product.
– MisterMike
Jan 29 '14 at 3:43
@MisterMike I supplied the work around in case this was a time-sensitive issue. Is this an Image Unattend file? Are you re-attaching the file to the image each time you make changes? I ask because when you attach the unattend to an image, it makes a copy of the unattend in a subfolder under the specific image folder and renames it to ImageUnattend.xml, so changes you make to the original file do not get used unless you re-attach the file after each change.
– dwolters
Jan 29 '14 at 20:42
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f567361%2factivating-windows-7-with-mak-passed-in-unattend-xml-via-wds%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
From the Picture that you posted, you are adding the x86_Microsoft-Windows-Shell-Setup node, and not the x64_Microsoft-Windows-Shell-Setup to your unattend file. Changing this to the appropriate architecture should solve this problem.
Hope this helps,
answered Jan 23 '14 at 18:14
dwoltersdwolters
1,240711
Sorry, that picture was just for reference to what the option is and what pass it's being added to (not for the architecture). I'm using the proper architecture.
– MisterMike
Jan 24 '14 at 1:07
@mistermike You can enter the proper key using an elevated command prompt and the command “slmgr.vbs /ipk <your kms key>”? You can then force activation with “slmgr.vbs –ato”. If running the command manually works, you can script it and add it to the unattend file. Do you have enough clients activating to exceed the KMS minimums (25 for Windows 7)?
– dwolters
Jan 24 '14 at 13:47
So there's no way to pass in the key and make it activate without running something extra? I feel like solutions such as those are "workarounds" and while they work aren't what was intended for the product.
– MisterMike
Jan 29 '14 at 3:43
@MisterMike I supplied the work around in case this was a time-sensitive issue. Is this an Image Unattend file? Are you re-attaching the file to the image each time you make changes? I ask because when you attach the unattend to an image, it makes a copy of the unattend in a subfolder under the specific image folder and renames it to ImageUnattend.xml, so changes you make to the original file do not get used unless you re-attach the file after each change.
– dwolters
Jan 29 '14 at 20:42
add a comment |
From the Picture that you posted, you are adding the x86_Microsoft-Windows-Shell-Setup node, and not the x64_Microsoft-Windows-Shell-Setup to your unattend file. Changing this to the appropriate architecture should solve this problem.
Hope this helps,
answered Jan 23 '14 at 18:14
dwoltersdwolters
1,240711
Sorry, that picture was just for reference to what the option is and what pass it's being added to (not for the architecture). I'm using the proper architecture.
– MisterMike
Jan 24 '14 at 1:07
@mistermike You can enter the proper key using an elevated command prompt and the command “slmgr.vbs /ipk <your kms key>”? You can then force activation with “slmgr.vbs –ato”. If running the command manually works, you can script it and add it to the unattend file. Do you have enough clients activating to exceed the KMS minimums (25 for Windows 7)?
– dwolters
Jan 24 '14 at 13:47
So there's no way to pass in the key and make it activate without running something extra? I feel like solutions such as those are "workarounds" and while they work aren't what was intended for the product.
– MisterMike
Jan 29 '14 at 3:43
@MisterMike I supplied the work around in case this was a time-sensitive issue. Is this an Image Unattend file? Are you re-attaching the file to the image each time you make changes? I ask because when you attach the unattend to an image, it makes a copy of the unattend in a subfolder under the specific image folder and renames it to ImageUnattend.xml, so changes you make to the original file do not get used unless you re-attach the file after each change.
– dwolters
Jan 29 '14 at 20:42
add a comment |
From the Picture that you posted, you are adding the x86_Microsoft-Windows-Shell-Setup node, and not the x64_Microsoft-Windows-Shell-Setup to your unattend file. Changing this to the appropriate architecture should solve this problem.
Hope this helps,
answered Jan 23 '14 at 18:14
dwoltersdwolters
1,240711
From the Picture that you posted, you are adding the x86_Microsoft-Windows-Shell-Setup node, and not the x64_Microsoft-Windows-Shell-Setup to your unattend file. Changing this to the appropriate architecture should solve this problem.
Hope this helps,
answered Jan 23 '14 at 18:14
dwoltersdwolters
1,240711
answered Jan 23 '14 at 18:14
dwoltersdwolters
1,240711
answered Jan 23 '14 at 18:14
dwoltersdwolters
1,240711
answered Jan 23 '14 at 18:14
dwoltersdwolters
1,240711
1,240711
Sorry, that picture was just for reference to what the option is and what pass it's being added to (not for the architecture). I'm using the proper architecture.
– MisterMike
Jan 24 '14 at 1:07
@mistermike You can enter the proper key using an elevated command prompt and the command “slmgr.vbs /ipk <your kms key>”? You can then force activation with “slmgr.vbs –ato”. If running the command manually works, you can script it and add it to the unattend file. Do you have enough clients activating to exceed the KMS minimums (25 for Windows 7)?
– dwolters
Jan 24 '14 at 13:47
So there's no way to pass in the key and make it activate without running something extra? I feel like solutions such as those are "workarounds" and while they work aren't what was intended for the product.
– MisterMike
Jan 29 '14 at 3:43
@MisterMike I supplied the work around in case this was a time-sensitive issue. Is this an Image Unattend file? Are you re-attaching the file to the image each time you make changes? I ask because when you attach the unattend to an image, it makes a copy of the unattend in a subfolder under the specific image folder and renames it to ImageUnattend.xml, so changes you make to the original file do not get used unless you re-attach the file after each change.
– dwolters
Jan 29 '14 at 20:42
add a comment |
Sorry, that picture was just for reference to what the option is and what pass it's being added to (not for the architecture). I'm using the proper architecture.
– MisterMike
Jan 24 '14 at 1:07
@mistermike You can enter the proper key using an elevated command prompt and the command “slmgr.vbs /ipk <your kms key>”? You can then force activation with “slmgr.vbs –ato”. If running the command manually works, you can script it and add it to the unattend file. Do you have enough clients activating to exceed the KMS minimums (25 for Windows 7)?
– dwolters
Jan 24 '14 at 13:47
So there's no way to pass in the key and make it activate without running something extra? I feel like solutions such as those are "workarounds" and while they work aren't what was intended for the product.
– MisterMike
Jan 29 '14 at 3:43
@MisterMike I supplied the work around in case this was a time-sensitive issue. Is this an Image Unattend file? Are you re-attaching the file to the image each time you make changes? I ask because when you attach the unattend to an image, it makes a copy of the unattend in a subfolder under the specific image folder and renames it to ImageUnattend.xml, so changes you make to the original file do not get used unless you re-attach the file after each change.
– dwolters
Jan 29 '14 at 20:42
Sorry, that picture was just for reference to what the option is and what pass it's being added to (not for the architecture). I'm using the proper architecture.
– MisterMike
Jan 24 '14 at 1:07
Sorry, that picture was just for reference to what the option is and what pass it's being added to (not for the architecture). I'm using the proper architecture.
– MisterMike
Jan 24 '14 at 1:07
@mistermike You can enter the proper key using an elevated command prompt and the command “slmgr.vbs /ipk <your kms key>”? You can then force activation with “slmgr.vbs –ato”. If running the command manually works, you can script it and add it to the unattend file. Do you have enough clients activating to exceed the KMS minimums (25 for Windows 7)?
– dwolters
Jan 24 '14 at 13:47
@mistermike You can enter the proper key using an elevated command prompt and the command “slmgr.vbs /ipk <your kms key>”? You can then force activation with “slmgr.vbs –ato”. If running the command manually works, you can script it and add it to the unattend file. Do you have enough clients activating to exceed the KMS minimums (25 for Windows 7)?
– dwolters
Jan 24 '14 at 13:47
So there's no way to pass in the key and make it activate without running something extra? I feel like solutions such as those are "workarounds" and while they work aren't what was intended for the product.
– MisterMike
Jan 29 '14 at 3:43
So there's no way to pass in the key and make it activate without running something extra? I feel like solutions such as those are "workarounds" and while they work aren't what was intended for the product.
– MisterMike
Jan 29 '14 at 3:43
@MisterMike I supplied the work around in case this was a time-sensitive issue. Is this an Image Unattend file? Are you re-attaching the file to the image each time you make changes? I ask because when you attach the unattend to an image, it makes a copy of the unattend in a subfolder under the specific image folder and renames it to ImageUnattend.xml, so changes you make to the original file do not get used unless you re-attach the file after each change.
– dwolters
Jan 29 '14 at 20:42
@MisterMike I supplied the work around in case this was a time-sensitive issue. Is this an Image Unattend file? Are you re-attaching the file to the image each time you make changes? I ask because when you attach the unattend to an image, it makes a copy of the unattend in a subfolder under the specific image folder and renames it to ImageUnattend.xml, so changes you make to the original file do not get used unless you re-attach the file after each change.
– dwolters
Jan 29 '14 at 20:42
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f567361%2factivating-windows-7-with-mak-passed-in-unattend-xml-via-wds%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
How are you attaching the unattend file? Are you embedding it in the image, or attaching it in WDS? It’s possible that the system is using a different unattend file based on implicit search order. Is there anything in the log files that might help? Also, you are installing Windows 7 pro x86, right?
– dwolters
Jan 22 '14 at 19:14
It's Windows 7 Pro x64 that I'm installing. The file is being attached via WDS. I know the file is being read and working properly as everything else in the file BUT the MAK activation is working. Nothing in log files.
– MisterMike
Jan 23 '14 at 2:20