While Deploying Virtual Desktop Infrastructure (VDI), I'm not able to add any VM's in the Collection
I am trying to create a Virtual Desktop collection, when ever i reach the page where it asks to select a Virtual Desktop Template it does not detect any Virtual Desktop even when I have a VM on the server and it has been sysprep'd. Is there any specific location where I should store the Virtual Desktop?
can any one suggest what should I do, I have attached a picture of where I get stuck.
virtual-machine virtualization virtual-desktop vdi rds
add a comment |
I am trying to create a Virtual Desktop collection, when ever i reach the page where it asks to select a Virtual Desktop Template it does not detect any Virtual Desktop even when I have a VM on the server and it has been sysprep'd. Is there any specific location where I should store the Virtual Desktop?
can any one suggest what should I do, I have attached a picture of where I get stuck.
virtual-machine virtualization virtual-desktop vdi rds
add a comment |
I am trying to create a Virtual Desktop collection, when ever i reach the page where it asks to select a Virtual Desktop Template it does not detect any Virtual Desktop even when I have a VM on the server and it has been sysprep'd. Is there any specific location where I should store the Virtual Desktop?
can any one suggest what should I do, I have attached a picture of where I get stuck.
virtual-machine virtualization virtual-desktop vdi rds
I am trying to create a Virtual Desktop collection, when ever i reach the page where it asks to select a Virtual Desktop Template it does not detect any Virtual Desktop even when I have a VM on the server and it has been sysprep'd. Is there any specific location where I should store the Virtual Desktop?
can any one suggest what should I do, I have attached a picture of where I get stuck.
virtual-machine virtualization virtual-desktop vdi rds
virtual-machine virtualization virtual-desktop vdi rds
edited Nov 29 '13 at 16:47
Scott Chamberlain
28k583101
28k583101
asked Nov 29 '13 at 16:34
user273284user273284
614
614
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I ran in to this issue myself. VDI does not work with Generation 2 VM's. Remake the sysprepped VM as a Generation 1 VM and it should show up.
Thanks for the reply Scott but its already a generation 1 VM. can you please tell me the other steps that you had performed in this process?
– user273284
Nov 29 '13 at 17:10
Do you have the VM still attached to hyper V and is the VM in a "shutdown" state? When you do the sysprep you should doing the commandsysprep /generalize /oobe /shutdown /mode:vm
? I just followed this test lab guide and i got it to work.
– Scott Chamberlain
Nov 29 '13 at 17:17
Oh, one more thing. If the VHD file was a differential image based off of a base image I could not get it to work. Having the VM not based on any external VHD files was the only way I could get it to work.
– Scott Chamberlain
Nov 29 '13 at 17:23
yes i had followed the same sysprep command. This is a lab/test environment. all the things are running on the same physical server. I am trying to create a new VM, i hope it work this time. if it doesn't can I ask to to help me via remote desktop? or team viewer?
– user273284
Nov 29 '13 at 17:38
No, I can't do that. I would double check that you really made a Generation 1 VM, that the VM is still attached but in the off state on the Hyper-V server, and the VHD file the VM is based off of is not based on a 2nd VHD file.
– Scott Chamberlain
Nov 29 '13 at 17:39
|
show 7 more comments
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f682172%2fwhile-deploying-virtual-desktop-infrastructure-vdi-im-not-able-to-add-any-vm%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
I ran in to this issue myself. VDI does not work with Generation 2 VM's. Remake the sysprepped VM as a Generation 1 VM and it should show up.
Thanks for the reply Scott but its already a generation 1 VM. can you please tell me the other steps that you had performed in this process?
– user273284
Nov 29 '13 at 17:10
Do you have the VM still attached to hyper V and is the VM in a "shutdown" state? When you do the sysprep you should doing the commandsysprep /generalize /oobe /shutdown /mode:vm
? I just followed this test lab guide and i got it to work.
– Scott Chamberlain
Nov 29 '13 at 17:17
Oh, one more thing. If the VHD file was a differential image based off of a base image I could not get it to work. Having the VM not based on any external VHD files was the only way I could get it to work.
– Scott Chamberlain
Nov 29 '13 at 17:23
yes i had followed the same sysprep command. This is a lab/test environment. all the things are running on the same physical server. I am trying to create a new VM, i hope it work this time. if it doesn't can I ask to to help me via remote desktop? or team viewer?
– user273284
Nov 29 '13 at 17:38
No, I can't do that. I would double check that you really made a Generation 1 VM, that the VM is still attached but in the off state on the Hyper-V server, and the VHD file the VM is based off of is not based on a 2nd VHD file.
– Scott Chamberlain
Nov 29 '13 at 17:39
|
show 7 more comments
I ran in to this issue myself. VDI does not work with Generation 2 VM's. Remake the sysprepped VM as a Generation 1 VM and it should show up.
Thanks for the reply Scott but its already a generation 1 VM. can you please tell me the other steps that you had performed in this process?
– user273284
Nov 29 '13 at 17:10
Do you have the VM still attached to hyper V and is the VM in a "shutdown" state? When you do the sysprep you should doing the commandsysprep /generalize /oobe /shutdown /mode:vm
? I just followed this test lab guide and i got it to work.
– Scott Chamberlain
Nov 29 '13 at 17:17
Oh, one more thing. If the VHD file was a differential image based off of a base image I could not get it to work. Having the VM not based on any external VHD files was the only way I could get it to work.
– Scott Chamberlain
Nov 29 '13 at 17:23
yes i had followed the same sysprep command. This is a lab/test environment. all the things are running on the same physical server. I am trying to create a new VM, i hope it work this time. if it doesn't can I ask to to help me via remote desktop? or team viewer?
– user273284
Nov 29 '13 at 17:38
No, I can't do that. I would double check that you really made a Generation 1 VM, that the VM is still attached but in the off state on the Hyper-V server, and the VHD file the VM is based off of is not based on a 2nd VHD file.
– Scott Chamberlain
Nov 29 '13 at 17:39
|
show 7 more comments
I ran in to this issue myself. VDI does not work with Generation 2 VM's. Remake the sysprepped VM as a Generation 1 VM and it should show up.
I ran in to this issue myself. VDI does not work with Generation 2 VM's. Remake the sysprepped VM as a Generation 1 VM and it should show up.
answered Nov 29 '13 at 16:45
Scott ChamberlainScott Chamberlain
28k583101
28k583101
Thanks for the reply Scott but its already a generation 1 VM. can you please tell me the other steps that you had performed in this process?
– user273284
Nov 29 '13 at 17:10
Do you have the VM still attached to hyper V and is the VM in a "shutdown" state? When you do the sysprep you should doing the commandsysprep /generalize /oobe /shutdown /mode:vm
? I just followed this test lab guide and i got it to work.
– Scott Chamberlain
Nov 29 '13 at 17:17
Oh, one more thing. If the VHD file was a differential image based off of a base image I could not get it to work. Having the VM not based on any external VHD files was the only way I could get it to work.
– Scott Chamberlain
Nov 29 '13 at 17:23
yes i had followed the same sysprep command. This is a lab/test environment. all the things are running on the same physical server. I am trying to create a new VM, i hope it work this time. if it doesn't can I ask to to help me via remote desktop? or team viewer?
– user273284
Nov 29 '13 at 17:38
No, I can't do that. I would double check that you really made a Generation 1 VM, that the VM is still attached but in the off state on the Hyper-V server, and the VHD file the VM is based off of is not based on a 2nd VHD file.
– Scott Chamberlain
Nov 29 '13 at 17:39
|
show 7 more comments
Thanks for the reply Scott but its already a generation 1 VM. can you please tell me the other steps that you had performed in this process?
– user273284
Nov 29 '13 at 17:10
Do you have the VM still attached to hyper V and is the VM in a "shutdown" state? When you do the sysprep you should doing the commandsysprep /generalize /oobe /shutdown /mode:vm
? I just followed this test lab guide and i got it to work.
– Scott Chamberlain
Nov 29 '13 at 17:17
Oh, one more thing. If the VHD file was a differential image based off of a base image I could not get it to work. Having the VM not based on any external VHD files was the only way I could get it to work.
– Scott Chamberlain
Nov 29 '13 at 17:23
yes i had followed the same sysprep command. This is a lab/test environment. all the things are running on the same physical server. I am trying to create a new VM, i hope it work this time. if it doesn't can I ask to to help me via remote desktop? or team viewer?
– user273284
Nov 29 '13 at 17:38
No, I can't do that. I would double check that you really made a Generation 1 VM, that the VM is still attached but in the off state on the Hyper-V server, and the VHD file the VM is based off of is not based on a 2nd VHD file.
– Scott Chamberlain
Nov 29 '13 at 17:39
Thanks for the reply Scott but its already a generation 1 VM. can you please tell me the other steps that you had performed in this process?
– user273284
Nov 29 '13 at 17:10
Thanks for the reply Scott but its already a generation 1 VM. can you please tell me the other steps that you had performed in this process?
– user273284
Nov 29 '13 at 17:10
Do you have the VM still attached to hyper V and is the VM in a "shutdown" state? When you do the sysprep you should doing the command
sysprep /generalize /oobe /shutdown /mode:vm
? I just followed this test lab guide and i got it to work.– Scott Chamberlain
Nov 29 '13 at 17:17
Do you have the VM still attached to hyper V and is the VM in a "shutdown" state? When you do the sysprep you should doing the command
sysprep /generalize /oobe /shutdown /mode:vm
? I just followed this test lab guide and i got it to work.– Scott Chamberlain
Nov 29 '13 at 17:17
Oh, one more thing. If the VHD file was a differential image based off of a base image I could not get it to work. Having the VM not based on any external VHD files was the only way I could get it to work.
– Scott Chamberlain
Nov 29 '13 at 17:23
Oh, one more thing. If the VHD file was a differential image based off of a base image I could not get it to work. Having the VM not based on any external VHD files was the only way I could get it to work.
– Scott Chamberlain
Nov 29 '13 at 17:23
yes i had followed the same sysprep command. This is a lab/test environment. all the things are running on the same physical server. I am trying to create a new VM, i hope it work this time. if it doesn't can I ask to to help me via remote desktop? or team viewer?
– user273284
Nov 29 '13 at 17:38
yes i had followed the same sysprep command. This is a lab/test environment. all the things are running on the same physical server. I am trying to create a new VM, i hope it work this time. if it doesn't can I ask to to help me via remote desktop? or team viewer?
– user273284
Nov 29 '13 at 17:38
No, I can't do that. I would double check that you really made a Generation 1 VM, that the VM is still attached but in the off state on the Hyper-V server, and the VHD file the VM is based off of is not based on a 2nd VHD file.
– Scott Chamberlain
Nov 29 '13 at 17:39
No, I can't do that. I would double check that you really made a Generation 1 VM, that the VM is still attached but in the off state on the Hyper-V server, and the VHD file the VM is based off of is not based on a 2nd VHD file.
– Scott Chamberlain
Nov 29 '13 at 17:39
|
show 7 more comments
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f682172%2fwhile-deploying-virtual-desktop-infrastructure-vdi-im-not-able-to-add-any-vm%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