locked
The template does not have a virtual hard disk attached that has been generalized. RRS feed

  • Question

  • Hello everybody, I have a small problem. We are currently using Windows Azure Pack on top of System Center Virtual Machine manager and it seems that sometimes when I create a Role in WAP I get an error in system center "Error (10659) Cannot run Sysprep on virtual machine because the template does not have a virtual hard disk attached that has been generalized." Now the role does not use template in virtual machine manager but rather uses its own templating system. I am using WAP Update Release 6. Any ideas why this is happening ?

    Here is a scenario

    1. I use Domain Controller Role and deploy the role using virtual disk named "windows2012r2-ver01.vhdx", the deployment works on this particular deployment. I deploy another role called sharepoint using the same virtual hard disk but I get the error as mentioned above. I try to use another virtual hard disk called "windows2012r2-ver02.vhdx" which is basically the same or is a clone of the other disk and the deployment of the sharepoint role works on that particular virtual hard disk.

    One confused guy.



    Gisli Gudmundsson

    Pro: Windows Server 2008, Server Administrator

    TS: Windows Server 2008 Technology Specialist

    My Blog : http://appvid.blogspot.com

    Twitter : #gamertopro

    LinkedIn : Gisli

    Thursday, May 21, 2015 2:51 PM

Answers

  • I would double check that WAP is actually identifying the virtual disk that you think it is when the role deploys.

    Since WAP templates are not SCVMM templates - they are point in time definitions that match objects together and create a template dynamically and then deploy it.

    So there are ways that WAP can end up with the incorrect VHD when it attempts a deployment.

    If you have multiple virtual disks in your library, drop a little marker file on each one, so you know which on WAP is actually using for each attempt.

    http://itproctology.blogspot.com/2014/05/scvmm-is-deploying-using-wrong-vhd-or.html

    When you manually select the VHD you create a hard link.  But in the case of a role template you might not do that.  Or, SCVMM is actually not getting the correct one.

    As the expectation is that the VHD is generalized and ready for mini-setup.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    Thursday, May 21, 2015 2:57 PM
  • FYI we figured out what was wrong with the template-disks. So the issue was when we deploy disks, templates or roles it failed sometimes. We noticed that the disk/role did not copy the disk we choose in the first place. With that all disks had the same tag name i.e. WindowsServer2012R2;R1. That was for for instance windows server 2012 r2 image with updated in mars, then in april and then in may. So we tried to add tag for each month i.e. WindowsServer2012R2;R1;April for april image WindowsServer2012R2;R1;May for may image, with this change it worked, we had no errors or problems after that. So it seems like the tag names may not be the same on virtual hard disks else this does not work. Don´t know if this is some kind of bug. So by changing the tag it does not choose randomly disk that has the same tag. Some images are not working so we disabled them, but even if we disabled the images it choose the bad image.

    Conclusion

    Don´t tag virtual hard disks with the same tag names but rather add additional ;tag to the tagname.



    Gisli Gudmundsson

    Pro: Windows Server 2008, Server Administrator

    TS: Windows Server 2008 Technology Specialist

    My Blog : http://appvid.blogspot.com

    Twitter : #gamertopro

    LinkedIn : Gisli

    • Marked as answer by Geekman Friday, June 5, 2015 9:11 AM
    Friday, June 5, 2015 9:11 AM

All replies

  • I would double check that WAP is actually identifying the virtual disk that you think it is when the role deploys.

    Since WAP templates are not SCVMM templates - they are point in time definitions that match objects together and create a template dynamically and then deploy it.

    So there are ways that WAP can end up with the incorrect VHD when it attempts a deployment.

    If you have multiple virtual disks in your library, drop a little marker file on each one, so you know which on WAP is actually using for each attempt.

    http://itproctology.blogspot.com/2014/05/scvmm-is-deploying-using-wrong-vhd-or.html

    When you manually select the VHD you create a hard link.  But in the case of a role template you might not do that.  Or, SCVMM is actually not getting the correct one.

    As the expectation is that the VHD is generalized and ready for mini-setup.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    Thursday, May 21, 2015 2:57 PM
  • Hi, the disks that are selected for each role is based on tag which is hard coded in the role pack. I can change the tag name in the role pack with some tools and it works but still even if the role has assigned some tag to use on the vhd or vhdx it does not work. It might be because the tag name is too long i.e. I have a tag named "Windows2012R2Sharepoint2013" which might be the result of this. I am going to change the tag and see if that would work.

    Else you mentioned that WAP is attempting to use other vhd, this might also be valid I have noticed the following

    1. I deploy role and the disk selected is not the disk i selected previously

    2. The role does not copy the disk but rather tries to create a new virtual machine using the disk located in the library. Tried to deploy role 3 times and the vm fails, because of sysprep 3 times. 

    I am going to dig a little deeper into this.



    Gisli Gudmundsson

    Pro: Windows Server 2008, Server Administrator

    TS: Windows Server 2008 Technology Specialist

    My Blog : http://appvid.blogspot.com

    Twitter : #gamertopro

    LinkedIn : Gisli

    • Marked as answer by BrianEhMVP Friday, June 5, 2015 12:54 PM
    • Unmarked as answer by BrianEhMVP Friday, June 5, 2015 12:54 PM
    Tuesday, May 26, 2015 9:15 AM
  • Hi Sir,

    How are things going ?

    Best Regards,

    Elton Ji


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com .

    Friday, May 29, 2015 12:39 PM
  • Still an issue


    Gisli Gudmundsson

    Pro: Windows Server 2008, Server Administrator

    TS: Windows Server 2008 Technology Specialist

    My Blog : http://appvid.blogspot.com

    Twitter : #gamertopro

    LinkedIn : Gisli

    Monday, June 1, 2015 9:09 AM
  • FYI we figured out what was wrong with the template-disks. So the issue was when we deploy disks, templates or roles it failed sometimes. We noticed that the disk/role did not copy the disk we choose in the first place. With that all disks had the same tag name i.e. WindowsServer2012R2;R1. That was for for instance windows server 2012 r2 image with updated in mars, then in april and then in may. So we tried to add tag for each month i.e. WindowsServer2012R2;R1;April for april image WindowsServer2012R2;R1;May for may image, with this change it worked, we had no errors or problems after that. So it seems like the tag names may not be the same on virtual hard disks else this does not work. Don´t know if this is some kind of bug. So by changing the tag it does not choose randomly disk that has the same tag. Some images are not working so we disabled them, but even if we disabled the images it choose the bad image.

    Conclusion

    Don´t tag virtual hard disks with the same tag names but rather add additional ;tag to the tagname.



    Gisli Gudmundsson

    Pro: Windows Server 2008, Server Administrator

    TS: Windows Server 2008 Technology Specialist

    My Blog : http://appvid.blogspot.com

    Twitter : #gamertopro

    LinkedIn : Gisli

    • Marked as answer by Geekman Friday, June 5, 2015 9:11 AM
    Friday, June 5, 2015 9:11 AM