[Activating App Protection on Windows Server 2022]

If I understand correctly, you are trying to install CWA on a Server OS with App Protection enabled. If this is correct, then unfortunately "This feature is supported only on desktop operating systems such as Windows 11, Windows 10, Windows 8.1." See https://docs.citrix.com/en-us/citrix-workspace-app/app-protection/configure.html#limitations

[Microsoft Teams 2.x]

Citrix published a new section under the App Layering 2312 Known Issues: https://docs.citrix.com/en-us/citrix-app-layering/4/known-issues.html#microsoft-teams-2x 

 

I first noted that it does not include the MS requirement to enable Sideloading: https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy#requirements

 

Second, the Citrix instructions include step 7 "To complete the installation, launch Microsoft Teams." Launching Teams in the OS Layer packaging machine results in the popup below.  WebView2 of course is not included in the OS Layer.

 

What are the corrections required to the newly published Citrix Teams 2.x instructions?

 

[Power bi retrive the 100 raw with odata]

Is there any help for you here: https://docs.citrix.com/en-us/tech-zone/learn/poc-guides/citrix-daas-monitor-powerbi

[New Teams for VDI with Office 365]

I published the New MS Teams OS Layer with O365, but without the AV layer. Everything works. We are working on applying the recommended AV exclusions.

[New Teams for VDI with Office 365]

I am having an issue getting the New Teams for VDI working. It works fine without the Office 365 App Layer, but once I add the O365 App Layer to the image it fails to open.

 

I have:

1. Set the WEbSocketService ProcessWhitelist to include msedgewebview2.exe

2. Updated to the FSLogix 2.9.8716.30241 (2210 Hotfix 3) (no exclusions in Redirections.xml related to Teams or Packages locations).

3. Installed New Teams MSIX x64 in the Server 2019 OS Layer via dism command

4. Set Teams registry to not autoupdate.

 

The errors I get once the O365 layer is added are:

 

Faulting application name: ms-teams.exe, version: 23320.3021.2567.4799, time stamp: 0x65719f33
Faulting module name: ucrtbase.dll, version: 10.0.17763.1490, time stamp: 0x48ac8393
Exception code: 0xc0000409
Fault offset: 0x000000000006e77e
Faulting process id: 0x2c44
Faulting application start time: 0x01da562b8f46c9ce
Faulting application path: C:\Program Files\WindowsApps\MSTeams_23320.3021.2567.4799_x64__8wekyb3d8bbwe\ms-teams.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: d9040988-817d-485b-a15e-4a3cfb0d365a
Faulting package full name: MSTeams_23320.3021.2567.4799_x64__8wekyb3d8bbwe
Faulting package-relative application ID: MSTeams

And:

Failure to instantiate storage folder C:\Users\xxxxx\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache for package MSTeams_8wekyb3d8bbwe with Error Code: -2147024809

 

[Citrix Workspace App Full Installer]

Does anyone know of any documentation for the CitrixWorkspaceFullInstaller.exe? I expect it is intended for air-gapped systems. Does it full featured?

[MachineGUID Population]

We are facing an issue with vendor software that revealed that all of our App Layered PVS 2019 Servers have the same MachineGUID at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\MachineGuid. This caused all machines to have the same vendor generated ID. Clearing the MachineGUID in the registry successfully generates unique vendor IDs, however the MachineGUID registry entry never gets reset, it remains blank.

 

How does app layering deal with the MachineGuid? In persistent servers it is set to a unique value at OS installation. What should be setting it in App layering? 

[The behaviour of certain Windows values in non-persistent VDI]

On 5/10/2019 at 5:28 AM, James Kindon said:

If you seal your machine appropriately all machines should always be completely unique, those values should always be unique 

 

This is not true for (Get-ItemProperty -Path HKLM:\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography).MachineGuid. At least not for Citrix App Layering and PVS. We are facing a current issue with vendor software that brought this to light. All of our App Layered PVS 2019 Servers have the same MachineGUID. This caused all machines to have the same vendor generated ID. Clearing the MachineGUID in the registry does successfully generate unique vendor IDs, however the MachineGUID registry entry never gets reset, it remains blank.

[Enquiry of Storefront Upgrade due to Current Security Vulnerability]

Agreed, unless the Release Notes specify otherwise. 

[App Layering RunOptimizer.cmd]

Can the app layering runoptimizer.cmd be run silently, feeding in the form selection(s) via argument, having no gui or popup to deal with?

[What Citrix Studio - Administrator Role setting display session control]

Should be

[Windows 2022 server won't boot after using Provisioning Imaging Wizard]

What is your BDM? ISO, hdisk, network? What is the VM boot device order? If BDM is hdisk is it in slot 0,1?

[Vcenter server maintenance impact on Citrix VDIs]

None of those will be impacted by a vCenter outage. As you say power management will not be available and of course adding new machines will not be possible.

[Setting defragsvc Startup Type will not Persist]

We added a Layer Script to the FSLogix App Layer that sets the service to Manual on startup.

[PVS Export Devices Wizard Returns 'No Devices Found to Export...']

Support was able to point me in the right direction. Although I had just created the AD record for the recovered target device PVS did not accept that. I had to remove the AD Computer Account for the target device and then created it from the PVS Console > Active Directory > Create Machine Account...  I assume PVS adds information to its database through this process that must be populated for the Export Devices Wizard to work. This is covered at 

 

https://support.citrix.com/article/CTX310415/adding-physical-devices-to-citrix-cloud-using-the-provisioning-devices-export-wizard-no-devices-found-to-export

[Citrix HDX Devices x64 Network Provider Order Error 1603]

Updating VDA from 1912 to 2203. Getting error while installing Citrix HDX Devices x64 component. MSI Log Analyzer output is below. Permissions on NetworkProvider key seem OK. Order key does not exist after failure. Any ideas?

 

Product Name: Citrix HDX Devices x64
Product Msi: IcaDevices_x64.msi
Product Version: 7.33.2000.14
Manufacturer Name: Citrix Systems, Inc.
Install Type:  Install
MSI Return Code: 1603
Helpful Details to troubleshoot/resolve the issue
PortICACustomActions:  entered
PortICACustomActions:  Command line is 'CommaSeparatedRegistry' 'prepend' 'SYSTEM\CurrentControlSet\Control\NetworkProvider\Order' 'ProviderOrder' 'PICAClientNetwork'
PortICACustomActions:  returning.  Result is 2
CustomAction CA_InstallNetProv returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Failure Error Code: 1603
Failing Action: CA_InstallNetProv
Action Time:  5/23/2023 9:50:36 AM
Operation: MSIEntry
Data: 'CommaSeparatedRegistry' 'prepend' 'SYSTEM\CurrentControlSet\Control\NetworkProvider\Order' 'ProviderOrder' 'PICAClientNetwork
ObjectCategory: Service
ObjectInfo: CommaSeparatedRegistry

[Testing App Layering 2304, after upgrading and publishing image template, my VDAs are missing ICA Session performance counters....]

What in OSTools builds the PerfGenRecomplile.cmd?

 

How does it determine the Perf Counters that need to be recompiled?

 

It does not appear to be identifying the complete set of Perf Counters for recompilation.

[Setting defragsvc Startup Type will not Persist]

No elastic layers, just published images.

 

We will try it out.

[Setting defragsvc Startup Type will not Persist]

Citrix Profile Management

 

https://docs.citrix.com/en-us/profile-management/current-release/configure/vhd-disk-compaction.html 

[Setting defragsvc Startup Type will not Persist]

We do not use UPM, we use FSLogix, but I just noted that it recently rolled out for UPM as well.

 

Seems reasonable that it would then be supported on PVS. I cannot find any confirmation of that.

[Setting defragsvc Startup Type will not Persist]

3 minutes ago, Rob Zylowski1709158051 said:

When App layering is used the degrag service is always disabled because it would cause lots of issues.  So I dont think you are going to be able to use that feature.  I am making the engineering team aware of the issue.

Thank you Rob.

 

Is it only an issue for packaging or publishing? Could it be set in the running vDisk (gpo, startup script)?

[Setting defragsvc Startup Type will not Persist]

FSLogix requires defragsvc (Optimize drives) be running in order for profile VHD compaction to function at user log off.

 

I have changed the defrag svc to Manual as recommended by MS. I have tried to do this in the FSLogix app layer, OS Layer and Platform Layer. In all cases after finalizing the layer the Startup Type reverts to disabled. This is the case in another layer version and a published image. Changes to other services startup type persist without issue.

 

How do I set the required startup type for defragsvc in an app layer?

 

What is changing the setting back to disabled? There is no entry in the Event Log showing this change.  

[PVS Export Devices Wizard Returns 'No Devices Found to Export...']

Thank you for the guidance.

 

I located the AOT logs and was able to find the detailed error being returned:

 

1 devices removed as they did not belong to domain domain: computername    [XdExportCollectionController.cs(243): FilterDevicesBasedOnActiveDirectoryDomainSelection]'

 

However, the AD computer record was newly created in the domain.

[Connection Quality Indicator Windows 11 Support]

We have opened two cases with this question. In both cases the answer has been it is not yet supported and they do not have any information on a date. Windows 11 is here folks.

[PVS Export Devices Wizard Returns 'No Devices Found to Export...']

Thank you for the feedback Simon. The original and recovered target devices are using different AD records with different SIDs.

 

Where would I locate the logs you mentioned?