https://worldofeuc.com logo
Join Slack
Powered by
Has anyone tried new teams on sever 2019 wiht App ...
# citrix-app-layering
r
Has anyone tried new teams on sever 2019 wiht App Layering? Did it work?
l
Yes we run it without issues, but it took us a while to get there
r
did you have to script anything or was just getting the 24.3.7 enough
l
We had to create multiple scripts in order to get everything running as we wanted it
r
was this a requirement Add-AppxPackage -Path 'C:\Program Files\windowsapps\MSTeams_24180.205.2980.1757_x64__8wekyb3d8bbwe\appxmanifest.xml' -Register -DisableDevelopmentMode
as a logon script?
l
We run this as a scheduled task as the local administrator account 2min after startup: Add-AppxPackage -Path "C:\Program Files\WindowsApps\MSTeams*\AppxManifest.xml" -Register -DisableDevelopmentMode
It seems to register Teams correctly for all users that log on to the server
r
Thanks You thats very helpful
l
no problem
r
I thought it had to be by user
l
You can't use the SYSTEM account, it needs to be a real user account, but it only needs to be done once per server. Since we use PVS we run it at startup every time the server get rebooted.
r
👍
@Lennart Hermansson Did you come across this error and figure out a way around it?
l
I do not remember that error, is Teams working ok despite this error or is it failing?
r
No it wont open. When i log on it takes about a minute for the teams start menu icon to show up, Then when i clikc on it it spins for a secodn then stops. And i get that erorr in the evenlogs
There are lots fo hits omn that error in google but none have a solution
l
And you have entered the command "Add-AppxPackage" with the arguments we talked about above and it completes without errors?
r
right now my shcedule tasks for that has an error but i logged on as administrator first and ran it as administrator
l
Try and delete these registry keys if they exist: HKCU:\Software\Classes\ms-teams HKCU:\Software\Classes\TeamsURL
r
as the user if i do a get-appxpacke -online i see the package
ok ill try
Only had the first one and it didnt change anything
l
Unlucky
r
yea
l
We have opted to start Teams automatically by script so we run this command to start it: Start-Process -FilePath C:\Windows\explorer.exe -ArgumentList "shell:AppsFolder\MSTeams_8wekyb3d8bbwe!MSTeams" Shouldn't really help you but doesn't hurt to try Other then that have you tried to delete your Windows profile, or using another account?
r
right now im just trying to get it to work during the first logon using a local profile wiht no containers
but ill try the script to see if its dfferen
thsi feels like somehting permission related to the sideloading
l
We used this script to install Teams, although we modified it slightly to fit our environment but it should contain everything needed in order to get Teams installed correctly https://github.com/Koetzing/Powershell-Scripts/blob/main/install-new-teams-srv2019.ps1
r
tahsnk ill take a look
b
@Rob Zylowski have you gotten Teams 2.1 to work in an app layer for Windows 10? Did you have to do the same scheduled task?
r
For windows 10 that is not required and yes it should just work
are you haing issues?
b
the layer is there, sometimes we see it in the start menu but it won't launch. Launches fine on the packaging machine
r
What are you using to persist it after the first logon
FSLogix?
What version of app layering
b
24.3.2.1021 for app layering, let me find out on FSLogix
What's curious is that this is a conversion from Horizon to DaaS, App Layering used for both. Works on the Horizon image but not the Citrix image. Only difference is the platform layer
r
We started fully supporting teams in 2402 VDA which can matter but so can if you are using UPM, Citirx COnatiner or FSLogix.
Im checking to see if you shuld have a newer version of app layering
ill let you know
b
thanks
p
getting teams 2.1 to consistently autolaunch (or even show up in the start menu) is a complete lottery Edit - i guess it's been a while since i looked at the Citrix docs. Went back and re-read this, applied the new recommendations on profile containers and it worked first try...
Open in Slack
PreviousNext
Powered by