About the VM with Visual Studio Code installed

Noriko 251 Reputation points
2023-05-09T04:29:29.04+00:00
When I sysprepped the VM with Visual Studio code installed and deployed it to the session host for AVD, Visual Studio code was not included. Do you know the reason?
Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,835 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Sreeju Nair 12,666 Reputation points
    2023-05-09T05:25:57.3066667+00:00

    Did you follow the below documentation to create the "Golden Image"

    https://learn.microsoft.com/en-us/azure/virtual-desktop/set-up-golden-image

    Also, while installing Visual Studio code and other apps, you must ensure you follow the recommendations below.

    https://learn.microsoft.com/en-us/azure/virtual-desktop/set-up-golden-image#customize-your-vm

    If the above doesn't help, read the general recommendations below.

    https://learn.microsoft.com/en-us/azure/virtual-desktop/set-up-golden-image#other-recommendations

    Hope this helps

    0 comments No comments

  2. vipullag-MSFT 26,487 Reputation points Moderator
    2023-05-15T01:18:29.3033333+00:00

    Hello Noriko

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    Adding more details to previous response from sreejukg.
    Based on the issue description, looks like VScode was installed into the user profile which is deleted during sysprep process. It can be installed as a user or in system (with admin permissions) Ref: https://code.visualstudio.com/docs/setup/windows

    If you want it to be available after sysprep, then it should be installed in the system. This way it will be available with the image.

    Hope this helps.

    If the suggested response helped you resolve your issue, please 'Accept as answer', so that it can help others in the community looking for help on similar topics.

    0 comments No comments

  3. Noriko 251 Reputation points
    2023-05-15T01:30:34.8266667+00:00
    thank you. I solved it here.
    Since the installed type was for the "User" plan, the installation destination was installed under C:\Users, so it could not be seen when connecting to AVD.
    When I set the plan to "System" type, it was installed in C:\Program Files, so I was able to use it in multiple sessions.
    
    
    

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.