https://worldofeuc.com logo
Join Slack
Powered by
Has anyone deployed New Teams on Nonpersistent Win...
# microsoft-365
l
Has anyone deployed New Teams on Nonpersistent Win10 VDI with FSLogix profiles en masse yet? My org has been held up with different issues and currently unable to deploy due to the appx package not registering for users when they login. With new Teams (VDI 1.0) in GA for so long, and Classic unsupported in a couple months, I cannot understand how this can be a show stopping issue.
r
Are you using a login script to register it? A lot of us are doing this even in persistent environments.
s
I've done it at a number of clients. Fully remove Classic Teams, use bootstrapper to install, make sure it's not wiped out by OSOT, etc. New profiles should be provisioned just fine, you might have issues with existing profiles, but you can probably script some actions to remove remaining bits from them so they get provisioned properly on logon via bootstrapper.
l
@Stephen Daniel Wagner, are you also using a login script to register the appx so the user can run it?
s
All my examples are on Horizon or AVD. Just using the bootstrapper, nothing special after that.
r
Copy code
if (-not (Get-AppxPackage -Name "*Teams*")) {
    Start-Job -Name RegisterTeams -ScriptBlock { Add-AppxPackage -RegisterByFamilyName -MainPackage MSTeams_8wekyb3d8bbwe -ErrorAction SilentlyContinue }
    Wait-Job -Name RegisterTeams
    Start-Process -FilePath \\lab.local\netlogon\SetUserFTA.exe "msteams AppXsz2w8kr3vqa5h0xgxy7bdt9816yyqntm" -ErrorAction SilentlyContinue
 }
👍 1
Some of us are doing this at login.
v
Can this script be RUN as DEM Logon Task? is it require Privilege's account or will work as a regular user login?
r
it's required to run as a regular user. The appx needs to register AS the user.
6 Views
Open in Slack
PreviousNext
Powered by