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

[Sergio Masone1709161115]

Upgraded ELM to 2304, published image template, i noticed in our monitoring console and monitor cannot retrieve ica latency metrics, further investigation, the ICA SEssion performance counters are completely missing. dont hav ethis issue with the previous version of ELM. anyone else have this behavior?
Thanks

[Mike Kelly1709153237]

34 minutes ago, Sergio Masone1709161115 said:

sure Mike, we are testing republishing today on two images, with the rebuild done in new OS version layer + machine tools. will let you know If i observe the same behavior with those counters.

Thanks.  I let Citrix support  know about this as well.  Our images also seem unstable.  We had users saying they were getting dropped, connection errors etc.    We have abandoned 2304 at this point and rolled back to 2211 and are in the process of redeploying our images.  I would not suggest anyone use this version at this point until there's a resolution to this.  

[Mike Kelly1709153237]

21 hours ago, Mike Kelly1709153237 said:

Thanks.  I let Citrix support  know about this as well.  Our images also seem unstable.  We had users saying they were getting dropped, connection errors etc.    We have abandoned 2304 at this point and rolled back to 2211 and are in the process of redeploying our images.  I would not suggest anyone use this version at this point until there's a resolution to this.  

We've rolled back to 2211 and redeployed our images and our users are happy again.  I'm interested to see where the support ticket goes from here on a permanent resolution.

[Sergio Masone1709161115]

30 minutes ago, Mike Kelly1709153237 said:

We've rolled back to 2211 and redeployed our images and our users are happy again.  I'm interested to see where the support ticket goes from here on a permanent resolution.

Im a bit shaky to use 2304 now to be honest, i havent see issues with cpu counters, however i did export the counters on my 2112 layered VDA using lodctr /S:c:\temp\outcounters.txt then re ran the same command even after rebuilding  the counters in the OS layer , upgrade tools version, when i rerun tons are missing in 2304.
@Chip Gonsalvesim not sure thats normal between 2304 and 2211, but you should be able to see similar in your lap if you export the counters to a txt file built from the registry on a 2211 image, vs 2304, there over 5k lines missing! is there any workaround that can be done for this or should i revert back to 2211 from restore?

[Chip Gonsalves]

1 hour ago, Sergio Masone1709161115 said:

Im a bit shaky to use 2304 now to be honest, i havent see issues with cpu counters, however i did export the counters on my 2112 layered VDA using lodctr /S:c:\temp\outcounters.txt then re ran the same command even after rebuilding  the counters in the OS layer , upgrade tools version, when i rerun tons are missing in 2304.
@Chip Gonsalvesim not sure thats normal between 2304 and 2211, but you should be able to see similar in your lap if you export the counters to a txt file built from the registry on a 2211 image, vs 2304, there over 5k lines missing! is there any workaround that can be done for this or should i revert back to 2211 from restore?

Sergio, we do not see the same things that you and Mike are reporting.  So while you both are reporting having issues with the release in respect to counters, I actually can not duplicate your results in my lab.  So there is something different in both of your environments and you both should have escalated your problems to support (I'm not in support).  The reason you may have to escalate is that since we are seeing nothing even close to the results you both are reporting, it means that you may have something unique in both of your environments, and there is no way for us to know what that is without you providing some feedback.  I know Mike has stated that he is waiting for some feedback from his report, but I can tell you that nothing has been escalated to us in development.  So we have nothing to go on other than we know that both of you are having problems that are not seen internally or by other customers.   And this is the wrong forum to try to diagnose exactly what is different in your environments.  Both of you are assuming that the problems you are reporting are generic and can be seen by everyone, but that is not the case. 

[Sergio Masone1709161115]

31 minutes ago, Chip Gonsalves said:

Sergio, we do not see the same things that you and Mike are reporting.  So while you both are reporting having issues with the release in respect to counters, I actually can not duplicate your results in my lab.  So there is something different in both of your environments and you both should have escalated your problems to support (I'm not in support).  The reason you may have to escalate is that since we are seeing nothing even close to the results you both are reporting, it means that you may have something unique in both of your environments, and there is no way for us to know what that is without you providing some feedback.  I know Mike has stated that he is waiting for some feedback from his report, but I can tell you that nothing has been escalated to us in development.  So we have nothing to go on other than we know that both of you are having problems that are not seen internally or by other customers.   And this is the wrong forum to try to diagnose exactly what is different in your environments.  Both of you are assuming that the problems you are reporting are generic and can be seen by everyone, but that is not the case. 

Hi, I know this isnt place for debugging, I already have a support case opened, and before it reaches your level, its painfully long with citrix, at least from past calls I have opened. To be honest, I would of not even noticed anything wrong if I didnt go into the performance counters, the VDA looks to run just fine, its if i open perfmon i can clearly see all the .NET counters for example are not present, and that is what id would of liked confirmation on. unless you explictly compare the performance counters present on one vs the other, i dont think its fair to say it isnt a generalized problem, im speaking only in the context of performance counters, im not experiencing the stability isues mentioned prior based on tetsing on our end so far. i did look at the perf batch file, and it reregisters the ica counters just fine.
i can see the ones missing by exporting whats in the registry between 2211 / 2304
This is from 2211

[Perflib]
Base Index=1847
Last Counter=14258
Last Help=14259

[PERF_.NET CLR Data]
First Counter=6840
First Help=6841
Last Counter=6852
Last Help=6853

[PERF_.NET CLR Networking]
First Counter=6828
First Help=6829
Last Counter=6838
Last Help=6839

[PERF_.NET CLR Networking 4.0.0.0]
First Counter=6900
First Help=6901
Last Counter=6926
Last Help=6927

[PERF_.NET Data Provider for Oracle]
First Counter=8916
First Help=8917
Last Counter=8944
Last Help=8945

[PERF_.NET Data Provider for SqlServer]
First Counter=6854
First Help=6855
Last Counter=6882
Last Help=6883

[PERF_.NET Memory Cache 4.0]
First Counter=6884
First Help=6885
Last Counter=6898
Last Help=6899

[PERF_.NETFramework]
First Counter=8740
First Help=8741
Last Counter=8914
Last Help=8915

[PERF_BITS]
First Counter=8966
First Help=8967
Last Counter=8982
Last Help=8983

[PERF_Citrix User Profile Manager]
First Counter=13778
First Help=13779
Last Counter=13826
Last Help=13827

[PERF_CitrixBrokerAgent]
First Counter=11064
First Help=11065
Last Counter=11110
Last Help=11111

[PERF_CitrixICA]
First Counter=13404
First Help=13405
Last Counter=13574
Last Help=13575

[PERF_ESENT]
First Counter=6928
First Help=6929
Last Counter=8708
Last Help=8709

[PERF_LSM]
First Counter=9042
First Help=9043
Last Counter=9048
Last Help=9049

[PERF_Microsoft Dynamics AX Client 6.3]
First Counter=10292
First Help=10293
Last Counter=10314
Last Help=10315

[PERF_MSDTC]
First Counter=6776
First Help=6777
Last Counter=6802
Last Help=6803

[PERF_MSDTC Bridge 3.0.0.0]
First Counter=10024
First Help=10025
Last Counter=10046
Last Help=10047

[PERF_MSDTC Bridge 4.0.0.0]
First Counter=6804
First Help=6805
Last Counter=6826
Last Help=6827

[PERF_rdyboost]
First Counter=8984
First Help=8985
Last Counter=9004
Last Help=9005

[PERF_RemoteAccess]
First Counter=9050
First Help=9051
Last Counter=9088
Last Help=9089

[PERF_ServiceModelEndpoint 3.0.0.0]
First Counter=9916
First Help=9917
Last Counter=9954
Last Help=9955

[PERF_ServiceModelOperation 3.0.0.0]
First Counter=10048
First Help=10049
Last Counter=10078
Last Help=10079

[PERF_ServiceModelService 3.0.0.0]
First Counter=9956
First Help=9957
Last Counter=10022
Last Help=10023

[PERF_SMSvcHost 3.0.0.0]
First Counter=9886
First Help=9887
Last Counter=9914
Last Help=9915

[PERF_SMSvcHost 4.0.0.0]
First Counter=8710
First Help=8711
Last Counter=8738
Last Help=8739

[PERF_TapiSrv]
First Counter=8946
First Help=8947
Last Counter=8964
Last Help=8965

[PERF_TermService]
First Counter=6774
First Help=6775
Last Counter=6774
Last Help=6775

[PERF_UGatherer]
First Counter=9134
First Help=9135
Last Counter=9238
Last Help=9239

[PERF_UGTHRSVC]
First Counter=9240
First Help=9241
Last Counter=9310
Last Help=9311

[PERF_usbhub]
First Counter=9006
First Help=9007
Last Counter=9040
Last Help=9041

[PERF_Windows Workflow Foundation 3.0.0.0]
First Counter=10080
First Help=10081
Last Counter=10122
Last Help=10123

[PERF_Windows Workflow Foundation 4.0.0.0]
First Counter=9090
First Help=9091
Last Counter=9132
Last Help=9133

[PERF_WmiApRpl]
First Counter=14092
First Help=14093
Last Counter=14258
Last Help=14259

[PERF_WSearchIdxPi]
First Counter=9312
First Help=9313
Last Counter=9438
Last Help=9439

this is from 2304
 

[Perflib]
Base Index=1847
Last Counter=7644
Last Help=7645

[PERF_Citrix User Profile Manager]
First Counter=2188
First Help=2189
Last Counter=2236
Last Help=2237

[PERF_CitrixICA]
First Counter=2016
First Help=2017
Last Counter=2186
Last Help=2187

[PERF_WmiApRpl]
First Counter=7478
First Help=7479
Last Counter=7644
Last Help=7645


if you say on your end exporting the counters using loctr /S:txtfile from a 2211 image, then publish a 2304 and reexport, and they are identical on a windows 10 VDA, then I'm in agreement with you its not generalized, but if they differ than im pretty sure it affects evryone, but unless they use these counters, wont even notice they are missing, the only ones that made me look originally was because we use UX monitoring tool that couldnt poll the ica metrics, which that was fixed with what you had suggested concerning upgrading the tools.

Thanks for having responded to our posts it is appreciated. I will continue with lvl 1 support from this point on...

[Sergio Masone1709161115]

to get the counters back again, in running inside my test session lodctr /R:<path to export of 2211> then they are all reloaded again properly.. could be a workaround for anyone having this behavior with missing perf counters as a startup script or something.

I seem to be seeing this counters missing problem only from my Windows 10 layer, my Server 2022 does not have this problem on publish.

[Chip Gonsalves]

1 hour ago, Sergio Masone1709161115 said:

to get the counters back again, in running inside my test session lodctr /R:<path to export of 2211> then they are all reloaded again properly.. could be a workaround for anyone having this behavior with missing perf counters as a startup script or something.

I seem to be seeing this counters missing problem only from my Windows 10 layer, my Server 2022 does not have this problem on publish.

The change is intended to always run the rebuild anytime the machine boots.  Take a look at two files on your machine that is seeing a problem.  First check in c:\programdata\unidesk\log\ulayersvc.log and search for lines with "PerfMonService:"  The last one in the file should show you the result of trying to execut the lodctr /r.  The second file is the c:\windows\setup\scripts\kmsdir\PerfGenRecompile.log.  Look in that file to see the results of all of the perf commands that were issued to rebuild the perf counters.  I believe your support engineer is going to ask you to provide those very same things.  So this post is not only for you, but for anyone else that may be seeing something unexpected.

 

[Sergio Masone1709161115]

7 minutes ago, Chip Gonsalves said:

The change is intended to always run the rebuild anytime the machine boots.  Take a look at two files on your machine that is seeing a problem.  First check in c:\programdata\unidesk\log\ulayersvc.log and search for lines with "PerfMonService:"  The last one in the file should show you the result of trying to execut the lodctr /r.  The second file is the c:\windows\setup\scripts\kmsdir\PerfGenRecompile.log.  Look in that file to see the results of all of the perf commands that were issued to rebuild the perf counters.  I believe your support engineer is going to ask you to provide those very same things.  So this post is not only for you, but for anyone else that may be seeing something unexpected.

 

in the unidesk log there is no reference to the perfmon anywhere, in the kmsdir it shows to have run sucessfully (PerfGenRecompile.log), yet its missing a ton of counters. I have to recompile, the same way your script is, but referencing an export done of the counters from the lodctr /S command previously run from my 2211 image which had all the counters.

one thing i can try is open my os layer, run the lodctr /R specifying the file that has all the counters from my 2211 template, and see if it sticks, but for whatever reason lodctr /R on 2304, is not registering all the counters, while it is running at bootup, and says it ran sucessfully,

I believe its when i create a new OS layer version with 2304, boot up, in my os layer running the /R command without a backup files, the counters are missing when i export the list, so thye seem to be missing at creation of new OS layer revision on 2304 in my case, so when it boots up the VDA after template done, it does run the /R but its already seems to be broken at that point for whatever reason i cant figure out yet.. support told me they are discussion this internally.

[Sergio Masone1709161115]

20 minutes ago, Sergio Masone1709161115 said:

in the unidesk log there is no reference to the perfmon anywhere, in the kmsdir it shows to have run sucessfully (PerfGenRecompile.log), yet its missing a ton of counters. I have to recompile, the same way your script is, but referencing an export done of the counters from the lodctr /S command previously run from my 2211 image which had all the counters.

one thing i can try is open my os layer, run the lodctr /R specifying the file that has all the counters from my 2211 template, and see if it sticks, but for whatever reason lodctr /R on 2304, is not registering all the counters, while it is running at bootup, and says it ran sucessfully,

I believe its when i create a new OS layer version with 2304, boot up, in my os layer running the /R command without a backup files, the counters are missing when i export the list, so thye seem to be missing at creation of new OS layer revision on 2304 in my case, so when it boots up the VDA after template done, it does run the /R but its already seems to be broken at that point for whatever reason i cant figure out yet.. support told me they are discussion this internally.

OK, now I know the why the /R is missing counters, /R restores off of a file called C:\Windows\System32\PerfStringBackup.INI, and this one has the missing counters, but in my 2112 image, the file has all the counters, so something fiddled or exported a new set of counters overwritting this file somewhere along the way.. so in theory if i replace the perfstringbackup.ini from my 2112 vda, and throw it in my os layer, that should make the "/r" work, or create an app layer containing this file, and add it as part of the publish... any idea if changes in 2304 would have done something to touch this file?

[Chip Gonsalves]

19 minutes ago, Sergio Masone1709161115 said:

OK, now I know the why the /R is missing counters, /R restores off of a file called C:\Windows\System32\PerfStringBackup.INI, and this one has the missing counters, but in my 2112 image, the file has all the counters, so something fiddled or exported a new set of counters overwritting this file somewhere along the way.. so in theory if i replace the perfstringbackup.ini from my 2112 vda, and throw it in my os layer, that should make the "/r" work, or create an app layer containing this file, and add it as part of the publish... any idea if changes in 2304 would have done something to touch this file?

Actually, the thing that I am most interested in is the fact that you state there is no perf counters mentioned in the ulayersvc.log.  Please work with your support engineer and provide that file to them.  Because that should have run the command, and you should not have to do all of the extra work you are trying to do.  So please go that route before trying to change things on your own.  This could be as simple as for some reason your ulayer didn't get updated for what ever reason, and that is where the problem resides.  The intent is that you would not have to do anything at all.

[Sergio Masone1709161115]

18 minutes ago, Chip Gonsalves said:

Actually, the thing that I am most interested in is the fact that you state there is no perf counters mentioned in the ulayersvc.log.  Please work with your support engineer and provide that file to them.  Because that should have run the command, and you should not have to do all of the extra work you are trying to do.  So please go that route before trying to change things on your own.  This could be as simple as for some reason your ulayer didn't get updated for what ever reason, and that is where the problem resides.  The intent is that you would not have to do anything at all.

the script does run at bootup, even if the ulayer.svc log doesnt mention it, that's the output of the recompile.
 

2023-05-12-10:13:05.78-PerfGenRecompile.cmd: Begin Register Of Percounters from Ini files 
2023-05-12-10:13:05.78-PerfGenRecompile.cmd: Register C:/Program Files (x86)/Citrix/ICA Client/Configuration/module.ini  
 
2023-05-12-10:13:05.87-PerfGenRecompile.cmd: Register C:/Program Files (x86)/Citrix/ICA Client/Configuration/module_Wince.ini  
 
2023-05-12-10:13:05.94-PerfGenRecompile.cmd: Register C:/Program Files (x86)/Citrix/ICA Client/module.ini  
 
2023-05-12-10:13:06.03-PerfGenRecompile.cmd: Register C:/Program Files/Citrix/HDX/bin/IcaPerf.ini  
 
2023-05-12-10:13:12.06-PerfGenRecompile.cmd: Register C:/Program Files/Citrix/User Profile Manager/upmPerf.ini  
 
2023-05-12-10:13:18.81-PerfGenRecompile.cmd: Register C:/Program Files/Microsoft Office/root/Office16/1033/OUTLPERF.INI  

Unable to open Driver key: SYSTEM\CurrentControlSet\Services\Outlook\Performance
Status value: 2 
2023-05-12-10:13:18.94-PerfGenRecompile.cmd: Rebuild counters 

Info: Successfully rebuilt performance counter setting from system backup store 

my point is even if the script runs the lodctr /R which it does at the end, it is importing from the system backup store, which is c:\windows\system32\PerfStringBackup.INI, and this one has the missing counters in it, so the end result is missing counters + ICA ones since it loads those as well, for whatever reason this file changed from 2211. all I did was upgrade to 2304, and republish an unchanged image and the counters were missing.

yes im still working with support, they haven't asked me for any logs yet.

Thanks

[Sergio Masone1709161115]

On 5/12/2023 at 6:00 PM, Sergio Masone1709161115 said:

the script does run at bootup, even if the ulayer.svc log doesnt mention it, that's the output of the recompile.
 

2023-05-12-10:13:05.78-PerfGenRecompile.cmd: Begin Register Of Percounters from Ini files 
2023-05-12-10:13:05.78-PerfGenRecompile.cmd: Register C:/Program Files (x86)/Citrix/ICA Client/Configuration/module.ini  
 
2023-05-12-10:13:05.87-PerfGenRecompile.cmd: Register C:/Program Files (x86)/Citrix/ICA Client/Configuration/module_Wince.ini  
 
2023-05-12-10:13:05.94-PerfGenRecompile.cmd: Register C:/Program Files (x86)/Citrix/ICA Client/module.ini  
 
2023-05-12-10:13:06.03-PerfGenRecompile.cmd: Register C:/Program Files/Citrix/HDX/bin/IcaPerf.ini  
 
2023-05-12-10:13:12.06-PerfGenRecompile.cmd: Register C:/Program Files/Citrix/User Profile Manager/upmPerf.ini  
 
2023-05-12-10:13:18.81-PerfGenRecompile.cmd: Register C:/Program Files/Microsoft Office/root/Office16/1033/OUTLPERF.INI  

Unable to open Driver key: SYSTEM\CurrentControlSet\Services\Outlook\Performance
Status value: 2 
2023-05-12-10:13:18.94-PerfGenRecompile.cmd: Rebuild counters 

Info: Successfully rebuilt performance counter setting from system backup store 

my point is even if the script runs the lodctr /R which it does at the end, it is importing from the system backup store, which is c:\windows\system32\PerfStringBackup.INI, and this one has the missing counters in it, so the end result is missing counters + ICA ones since it loads those as well, for whatever reason this file changed from 2211. all I did was upgrade to 2304, and republish an unchanged image and the counters were missing.

yes im still working with support, they haven't asked me for any logs yet.

Thanks

just wanted to share some tests I have done with 2304
New OS layer revision boot                       > perfstringbackup.ini > intact with all counters in the layer during edit
Install new machine tool version             > perfstringbackup.ini > intact with all counters in the layer during edit
Reboot OS layer                                             > perfstringbackup.ini > intact with all counters in the layer during edit

add another version of os layer                > perfstringbackup.ini > intact with all counters in the layer during edit


Publish template                                           > perfstringbackup.ini > Missing counters in the final image

 

publish is doing something with this file causing it to miss counters for us in 2403 that was different in 2112 since it doesn't have this behavior.

[Mike Kelly1709153237]

On 5/15/2023 at 11:11 AM, Sergio Masone1709161115 said:

just wanted to share some tests I have done with 2304
New OS layer revision boot                       > perfstringbackup.ini > intact with all counters in the layer during edit
Install new machine tool version             > perfstringbackup.ini > intact with all counters in the layer during edit
Reboot OS layer                                             > perfstringbackup.ini > intact with all counters in the layer during edit

add another version of os layer                > perfstringbackup.ini > intact with all counters in the layer during edit


Publish template                                           > perfstringbackup.ini > Missing counters in the final image

 

publish is doing something with this file causing it to miss counters for us in 2403 that was different in 2112 since it doesn't have this behavior.

Sergio,

 

What OS are you using? We are seeing this in Server 2016.

[Sergio Masone1709161115]

1 minute ago, Mike Kelly1709153237 said:

Sergio,

 

What OS are you using? We are seeing this in Server 2016.

Im seing this behavior on my windows 10 VDAs, but have not seen this on my server 2022 template. the perfstring looks ok, its intact at the expected size and contains all counters.

clearly something is happening during the publishing process with this file, i even tried just OS and Platform layer to see if the file at minimum without other app layers would have this issue, and it does, so its not a layer overwritting this file or anything like that. support so far have asked me all the same questions from this forum and even referenced this forum a few times. id be very surprised this isnt reproduceable, the only thing im doing is publishing without any changes, and the perfstringbackup.ini file is intact during image editing, but is half the size with bunch of counters during publishing the final template... so clearly there is something in that process that changed somewhere in 2304.

 

only workaround to get the coutners again, is take a copy of the perfstringbackup.ini from my working 2212 image, and via startup script have lodctr /R:<perfstringbackup,ini from 2212> then all the counters come back..

[Darryl Sakach]

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.

[Sergio Masone1709161115]

On 5/18/2023 at 4:51 PM, Mike Kelly1709153237 said:

Sergio,

 

What OS are you using? We are seeing this in Server 2016.

Citrix is still investigating this, but as a workaround if your interested,
In my OS layer, set this reg key in a new version

HKLM\System\CurrentControlSet\Services\Uniservice\GeneratePerfGenRecompileScript_disabled

DWORD

Set to 1
afterward PerfStringBackup.ini was fine and all counters were there post publish

[Mike Kelly1709153237]

2 hours ago, Sergio Masone1709161115 said:

Citrix is still investigating this, but as a workaround if your interested,
In my OS layer, set this reg key in a new version

HKLM\System\CurrentControlSet\Services\Uniservice\GeneratePerfGenRecompileScript_disabled

DWORD

Set to 1
afterward PerfStringBackup.ini was fine and all counters were there post publish

Thanks Sergio.  I'm still waiting on my engineer to give me an update from the information I uploaded to my case from last week.  

 

I'm not really interested in a workaround to be honest.  We rolled back to 2211 and are going to continue to use that until a permanent solution is provided.

[Richard Buffone]

App Layering 23.4.5 is now available upon request to fix this issue. The same fix will be in version 23.6 / 2306 once released.

[Mike Kelly1709153237]

@Sergio Masone1709161115- Have you gotten a permanent fix?  We were issued the appliance hotfix but some of our performance counters are different.

 

On App layering v2211 these counters are showing "Multi Instance" but on 2304+ they are showing "Single Instance"

NET Memory Cache 4.0

HTTP Service Request Queues

HTTP Service Url Groups 

 

We are not entirely aware of what kind of impact this will have on our environment as we haven't tested this with users on the system yet but I'm hesitant to do so without knowing what kind of impact this will have.

 

I'm curious if you are seeing the same thing on your images.

[Sergio Masone1709161115]

31 minutes ago, Mike Kelly1709153237 said:

@Sergio Masone1709161115- Have you gotten a permanent fix?  We were issued the appliance hotfix but some of our performance counters are different.

 

On App layering v2211 these counters are showing "Multi Instance" but on 2304+ they are showing "Single Instance"

NET Memory Cache 4.0

HTTP Service Request Queues

HTTP Service Url Groups 

 

We are not entirely aware of what kind of impact this will have on our environment as we haven't tested this with users on the system yet but I'm hesitant to do so without knowing what kind of impact this will have.

 

I'm curious if you are seeing the same thing on your images.

I tested the patch quickly, i still find a 200kb discrepancy between the file size of perfstringbackup.ini in 2211 or 2304 with the registry key workaround i was provided, I haven't checked yet the difference inside file to find whats missing, but I'm guessing it will be the same as you posted, but I will check to confirm this later on today, and report my findings here.

[Richard Buffone]

14 minutes ago, Sergio Masone1709161115 said:

I tested the patch quickly, i still find a 200kb discrepancy between the file size of perfstringbackup.ini in 2211 or 2304 with the registry key workaround i was provided, I haven't checked yet the difference inside file to find whats missing, but I'm guessing it will be the same as you posted, but I will check to confirm this later on today, and report my findings here.

 

You will need to remove the registry workarounds set on 23.4.5 before the fix will run.

[Sergio Masone1709161115]

17 minutes ago, Richard Buffone said:

 

You will need to remove the registry workarounds set on 23.4.5 before the fix will run.

yes i did do that, i was simply mentioning with the reg workaround, the file was at the same size as 2112, but with patch, without reg key, the size of the file was 200kb less.

[Mike Kelly1709153237]

On 6/15/2023 at 12:37 PM, Sergio Masone1709161115 said:

yes i did do that, i was simply mentioning with the reg workaround, the file was at the same size as 2112, but with patch, without reg key, the size of the file was 200kb less.

@Sergio Masone1709161115- Were you able to compare your counters on the hotfixed 2304 appliance vs 2211?  Do they match?

[Sergio Masone1709161115]

On 6/28/2023 at 5:14 PM, Mike Kelly1709153237 said:

@Sergio Masone1709161115- Were you able to compare your counters on the hotfixed 2304 appliance vs 2211?  Do they match?

Sorry i have been on other things and have not had much time to put more on this, there still looks to be a slight descrepency but nothing that causes us any problems. the counters we leverage seem to all be there and working. We have since upgraded our OS layer to 22H2, so there are more factors in play in my environment now, and no longer have 2211 to play around with.. Im facing a seperate issue ill post in a new thread though, when running citrix optimizer in my platform layer, the "Disable scheduled Tasks" for some reason do not save anymore in my template, and all tasks show as "enabled" in the published template, not sure why yet. but since its not related to the original problem i posted, ill open a new post on this one.
I have not tried 2306 either, but release notes seem to indicate something related to the "perfgenrecompile" script, id try that version in a test environment, and see if the counters look ok afterwards.

[Mike Kelly1709153237]

On 7/3/2023 at 8:47 AM, Sergio Masone1709161115 said:

Sorry i have been on other things and have not had much time to put more on this, there still looks to be a slight descrepency but nothing that causes us any problems. the counters we leverage seem to all be there and working. We have since upgraded our OS layer to 22H2, so there are more factors in play in my environment now, and no longer have 2211 to play around with.. Im facing a seperate issue ill post in a new thread though, when running citrix optimizer in my platform layer, the "Disable scheduled Tasks" for some reason do not save anymore in my template, and all tasks show as "enabled" in the published template, not sure why yet. but since its not related to the original problem i posted, ill open a new post on this one.
I have not tried 2306 either, but release notes seem to indicate something related to the "perfgenrecompile" script, id try that version in a test environment, and see if the counters look ok afterwards.

That's likely the fix they put in based on the issue we encountered.

 

You have your 2211 perf counters that were posted earlier in this thread.  Curious how they compare to what you're seeing with 2304 hotfix / 2306.