-
Posts
194 -
Joined
-
Last visited
-
Days Won
7
Content Type
Forums
Articles
Labs
Videos
TechZone
Citrix Community Articles
Events
Profiles
Posts posted by Nick Panaccio
-
-
Just make sure you don't mass deploy the current CWA 1912 LTSR, as it is only a Tech Preview and must be manually uninstalled when the GA version is released.
-
In case anyone stumbles across this thread, there is both an ELM appliance upgrade hotfix as well as a machine tools hotfix. Once the new machine tools were extracted, the issue was resolved.
-
17 hours ago, Raymond Colon said:
There is a hotfix available, since my initial post, or you can manually edit the file, kmssetup.cmd.
I just installed the hotfix (upgraded the ELM and published a new image), but it did not resolve the issue for me. Back to the drawing board, I guess.
-
I asked earlier today and was told there was no hotfix and to simply REM out the lines. Is the hotfix anything more than kmssetup.cmd? While testing the kmssetup from 1901 seems to work fine, I'm not a fan of the workaround. I just asked the tech who has my ticket if he can provide the hotfix.
-
Anyone else seeing WEM instance notifications on reconnects to a disconnected session in WEM 1912 (on-prem)? I don't see this behavior in 1906 with the same exact settings, and the only way to resolve it is to uncheck Launch agent on Reconnect in the WEM console. The event log shows the following errors:
SensMonitoring.StartReconnectTask() : Starting Reconnect Processing for User :
ReconnectController.InternalRun() : Error while trying to close Ui Agent for user domain\me in session 1
To add to this, I have a custom Start tile that runs tsdiscon.exe that I'm using to test. When I run that, the error will occur at reconnect. However, if I use the Disconnect button in the Desktop Viewer toolbar up top, I don't receive any errors on reconnect.
-
14 hours ago, Raymond Colon said:
Please open a case, since we recently discovered and fixed this issue
I currently have a case open, and was told that the fix would be released in the next App Layering release. The workaround is to simply comment out the CCMEXEC stuff in kmssetup.cmd. Is there another fix that I'd be able to get without having to wait for the next build?
-
I'm testing my new 1912 LTSR VDA (W10 1809) on App Layering 2001, and kmssetup.cmd is constantly running in the background (after calling StartCCMEXEC.cmd), so it never actually finishes processing. I do not have SCCM installed on this VDA, and the registry keys it's looking for don't actually exist, so I have no idea why the log file says otherwise. I've validated this behavior in three different images that have App Layering 2001 installed. Has anyone else seen something similar? I've opened a case with Citrix, but figured this was worth posting here, as well. Attached are the relevant logs.
-
On 1/24/2020 at 9:34 PM, Andrew Gresbach1709152664 said:
awesome thanks for the heads up! i just updated last night. i still see the blue screens after log out if i dont have citrix optimizer set (which ironically in another thread about slow logins w/ 2 monitors someone may have found that the optimizer may be causing it). I need to get our 7.15.2000 environment up to the latest 1912 so maybe thats my issue
Which other thread are you referring to? I'd like to follow it. I'm curious to know which optimization is causing the issue, if somebody is taking the time to go through them one by one. My own Citrix Optimizer template is in the Marketplace.
-
FYI, App Layering 2001 was just released, with official support for 1912 LTSR and W10 1909.
-
I'm still on 1809, but haven't seen any blue screens. The only oddity I saw was that my small target devices (2 vCPU/5GB) worked fine, but my large target devices (4 vCPU/8GB) all failed to register when they came online. Of course, my entire environment is still 7.15 LTSR CU2, so my results are effectively worthless.
-
@Rob Zylowski1709158051: Any word on 1912 support in AL? I've seen a few people elsewhere comment on 1911 having issues with 1912 LTSR, so I assume it's not entirely supported yet.
-
Has anyone done any preliminary testing with 1912 LTSR in a W10 VDA using the ResetCache registry entry?
-
12 hours ago, Clement Thuraisamy1709154286 said:
Understood, I don’t plan to use dynamic layers. Not in my scope now. I have tested UL and as much I like them, I noticed logon are extremely slow.
thanks again Rob for your assistance.
Rob beat me to the replies, but we're still in the same boat. Logon performance goes down drastically for us with EL enabled, so we've left it out of our images entirely. We've been on App Layering with FSLogix in Production for a month or so now and so far everything has gone well. I do keep FSLogix in my Platform layer, though testing it in an App layer also worked.
-
I'm finding conflicting information on the procedure for updating Office 365. In CTX224566, it states that you need to change <Updates Enabled="FALSE" /> to <Updates Enabled="TRUE" /> in the configuration XML file before updating 365 using the /configure switch. However, before reading the article, I left that setting at 'FALSE' and O365 appeared to update just fine. Is the information in that article still accurate?
Furthermore, if we're upgrading Office 365 in a Layer version, do I need to do anything else, like re-run Office2013Windows81_PREP.cmd before Finalizing the layer?
-
I've asked this everywhere and have yet to find a solution. Only two users have come forward with this issue, but I have to believe that others just aren't reporting it. Occasionally, when somebody is writing an e-mail (no attachments) and they click on Send, Outlook 2016 completely crashes:
The crash log is less than useless, because it doesn't point to anything in particular. I've had both users run Outlook with no add-ins enabled and it still crashes. This only happens in our App Layering image for Windows 10, in both build 1709 and 1809.
Anyone have any ideas here? I'm trying to avoid building the Office 2016 layer from scratch again, but at the same time, feel that's my only play here.
-
Honestly, I haven't even tried. And once I posted that, I realized that it made more sense for me to simply duplicate the few settings in yours, in my own custom template. For the most part, your template loaded fine in 2.6 when I went to modify it, except for the Hybernation configuration. The PS code was blank in the editor, so that may need to be resolved.
-
2
-
-
@Rob Zylowski1709158051 Any chance you're going to be posting a v2.6 AppLayering Supplement template in the Marketplace? I don't see one available right now.
-
2
-
-
I've had no issues keeping Windows Update disabled in our images in our current 1709 image and our new 1809 image. I disable the WU service both in the OS Layer (manually disabling it; not via local GPO), as well as in a domain GPO. I don't think they exist anymore, but there were some random scheduled tasks in 1709 that used to change that behavior, which I disable in VMware OSOT in my Platform layer. These tasks were all in the Microsoft\Windows\rempl folder in Scheduled Tasks, and all were deleted. While I'm deleting a number of other tasks, I don't think any of them are known to turn on WU.
We do set the following registry key in our Platform layer:
Key: HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
Value: NoAutoUpdate
Data: 1
-
2 minutes ago, David Hendy said:
Hi. where did you get get the sign out and disconnect icons? I cannot find them anyway!
I'm pretty sure that I found these icon files online somewhere, but may have modified them myself. Either way, let me see if attaching them to this post works. If not, I'll upload it to my Google drive.
-
This doesn't appeal or apply to everyone, but Citrix App Layering makes these Windows 10 build upgrades a little smoother, since you only have to actually run the upgrade in your OS layer, and may only just have to add revisions to some of your other Application layers (like Office).
-
Are you actually using XenServer as your hypervisor? If so, see if this is your issue: https://discussions.citrix.com/topic/399684-xenserver-tools-timesync-disable. We had this very same issue with our Server OS VDAs, which are hosted on XenServer 7.1 CU1 and are running the 7.1.1118 XS agent. We implemented the registry change in the initial post in our gold image and it resolved the issue completely.
-
I love that the Optimizer tool is being expanded, and look forward to v2.6 (still in beta, I hear). I may actually sit down and convert my hefty VMware OS Optimization Tool script to Citrix Optimizer so that I can use one tool from here on out.
Better yet, Citrix could develop a tool to do that conversion for us, hint hint... ;)
-
2
-
-
@Rob Zylowski1709158051: Any chance you have information on the User Virtualization Layer that is supposedly coming to App Layering in the near future? They mentioned it in the What’s new and next with Citrix Virtual Apps and Desktops webinar today, but glossed over it so quickly that I didn't get any useful information on it.
-
1 minute ago, Mike Kelly1709153237 said:
Did you have to use the Layer Priority tool and move it to the top of the priority list? We also use Ivanti Application Control (filter driver) and the vshield filter driver for trend micro so I'm assuming that's why we needed it in the platform layer.
I used the utility to move that layer to the top of the list just in case, yes. I didn't test it at a lower level. I'm also running Trend Micro Apex One (in an App layer).
Outlook 2016 crashes when sending e-mail
in App Layering
Posted
I haven't had a report of this in a while, but that doesn't mean much since our users simply may just not be reporting it. My next step was going to be disabling the hook for Outlook.exe, as well. If you go that route and have users who can actually report a success, definitely let me know. We're upgrading to 1912 LTSR next month, and and are actually running FSLogix already, though we're online mode for on-prem users. The few users who have been migrated to O365 are in cache mode with FSLogix's ODFC container.