Microsoft Azure WVD (Windows Virtual Desktop) – Auto-deploy FSLOGIX

Windows Virtual Desktop is a comprehensive desktop and app virtualization service running in the cloud. It’s the only virtual desktop infras07ucture (VDI) that delivers simplified management, multi-session Windows 10, optimizations for Office 365 ProPlus, and support for Remote Desktop Services (RDS) environments. Deploy and scale your Windows desktops and apps on Azure in minutes, and get built-in security and compliance features.


When you want to use the default images without too much alterations (because you only need to publish simple applications or just a desktop/browser/etc), you still might want to use the FSLogix profile manager. This post describes the installation of the agent in an automated way so quick deployment of marketplace images is now possible.
In this blog post I have an Azure FileShare with AD integration available and a group policy that automatically configures the FSLogix agent (if installed) – so after the installation of the FSLogix agent it will automatically be configured for users.
The way I did this in my demo environment is the following:
  • I downloaded the agent (FSLogixAppSetup.exe) and placed it on a blob storage account in Azure with blob anonymous permissions (optionally you could enable a private endpoint for more security)
    • In the existing group policy I created an instant task under the computer\preferences\con07ol panel\scheduled tasks hive


    Next, give the task a name, set the security options to SYSTEM and run whether user is logged on or not.





    Under Actions you create 1 tasks (if you cannot select Run whether user… save the task first, and then re-open it later after configuring everything):
    • Start PowerShell and invoke a download – this will download the exe file from the blob and store it locally on the client and executed for instalation in 1 go:
      • Program: PowerShell
      • Arguments: Invoke-WebRequest C:>powershell -command Invoke-WebRequest https://.blob.core.windows.net/installs/FSLogixAppsSetup.exe -UseBasicParsing -outfile c:\packages\FSLogixAppsSetup.exe ; start-process -FilePath c:\Packages\FSLogixAppsSetup.exe -Argumentlist “/install”,”/quiet” -NoNewWindow
      • Start-in: C:\Packages




    Next, we don’t want to run this task if the agent is already installed (for example when we also have template computers or when the task is completed already. So, under common we use the item-level targeting to filter out the task if needed.

    Once this is implemented, newly deployed computers will initiate the download and install of FSlogix, including newly deployed WVD hosts.

    Note : I did the same for Microsoft Edge Chromium, so any newly deployed WVD image, automatically gets the latest Edge Chromium and FSLogix installed!
    Stay healthy and safe.  In coming blog you will see that how WVD can be deployed in Enterprise and SME sector. 
    Feel free to comments and reach if you any more queries you may have in this regards.  
    Regards
    Shiv

    Comments

    Post a Comment

    Popular posts from this blog

    Getting Started with Logic Apps - XML to EDI X12

    Image
    Continuing from last post where I explained the basics of EDI and EDI X12 standards , let’s  see how we can enable EDI communication with Logic Apps Logic Apps and EDI together Earlier it was BizTalk from Microsoft which has all capabilities around Enterprise Application Integration(EAI) and Electronic Data Interchange (EDI)(which is server product) but with the cloud shift where everything is desired as service, Microsoft provided Logic Apps to cater the integration needs for cloud users and it is continuously getting matured (most of BizTalk capabilities already added). Read more about  Logic App Fundamentals To enable the logic apps to be leveraged in Business to Business EDI communication Microsoft introduced Enterprise Integration Pack,  which adds B2B capabilities like AS2 and X12, EDI standards support , XML capabilities like XML Validation, XSLT Transformation, Flat file to XML encode/decode etc.(Available as actions in Logic app e.g., AS2 Decode, Encode t
    Read more

    Operation on target Copy data failed: Failure happened on 'Source' side

    Image
    A simple Pipeline created to fetch data by querying the Rest Api and dumping the data received in blob storage, failed with following error: Error Operation on target Copy data_From API failed: Failure happened on 'Source' side. ErrorCode=UserErrorHttpStatusCodeIndicatingFailure,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=The HttpStatusCode 400 indicates failure. {"errors":{"detail":"Internal server error"}},Source=Microsoft.DataTransfer.ClientLibrary,' Why it happened As the error says, something went wrong at source side however, I have tested the Rest API using postman and was able to get the response back with data. And I have reflected same in Source setting of Copy Data activity while creating the pipeline i.e. query, headers – content type and authorization etc Still getting the error, I rechecked again the keys,content type etc - no clue. Took hel
    Read more

    The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

    Image
    While doing testing after doing a POC on Securing Logic App with Azure Active Directory authentication , where I have put logic app behind APIM and before passing the request to logic app, apim does validation of the token.  I was encountered with an error "The request has both SAS authentication scheme and 'Bearer' authorization  scheme.  Only one scheme should be used." Why it happened After validating the token which is part of the header i.e. Authorization, APIM forwards the request as it is to backend. As  Logic app is configured as  back end , it's url already consist of SAS signature plus the request also has Authorization section and this is the problem. By default every request endpoint on a logic app has a Shared Access Signature (SAS) in the endpoint's URL, which follows this format: https://<request-endpoint-URI>sp=<permissions>sv=<SAS-version>sig=<signature> As of now logic App only
    Read more