https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-vad
s
This message was deleted.
k
Yes, before cloning you will have to run dsregcmd /leave on XD-01 and then join it again with dsregcmd /join
dsregcmd /join should also be executed on XD-02 etc.
r
ah, makes sense, and easy enough. thanks!
👍 1
@Kasper Johansen When setting up Azure AD Connect, do you select the OU your CVAD boxes are in the sync up to Azure AD?
looks like yes....
k
Yes, I do
That and the OU with the golden image, if such exist
r
and this basically just runs the dsregcmd /join automatically for each system there? or is there some GPO or something else need to turn on ? I'm reading through Deyda's article, i just have questions
k
I usually configure a scheduled task with the dsregcmd /join command to run at startup
r
nods
k
Startup script would of course also work
r
cool, ty
👍 1
Interesting though Manual's article says "Because the above-mentioned operating systems automatically connect hybrid, you should also see them in the Azure Portal after a maximum of 30 minutes."
technically should not have to do the taskschd or startup script? Will test
Interesting none of it worked until I ran dsregcmd /join as NT\SYSTEM
so, good reason for Scheduled task...
r
r
@Kasper Johansen Can I see your scheduled task? I can't seem to get it to work... this shouldn't be difficult. 🙂
k
Yeah, just a moment let me see if I can find it
$A = @()
$A += New-ScheduledTaskAction –Execute "%SystemRoot%\System32\dsregcmd" -Argument "/join"
$T = New-ScheduledTaskTrigger -AtStartup
$P = New-ScheduledTaskPrincipal -UserId SYSTEM -LogonType ServiceAccount -RunLevel Highest
$S = New-ScheduledTaskSettingsSet
$D = New-ScheduledTask -Action $A -Principal $P -Trigger $T -Settings $S
Register-ScheduledTask "Azure AD Hybrid Join" -TaskPath "\Microsoft" -InputObject $D
r
thanks.. testing...
i keep getting 0x1
k
I apply this in a posh script via MDT
r
nods
i'm using 2016, not that i think that should matter?
same result.. wondering if this is a 2016 nuance...
the only way i can get it to run manually is with psexec -i -s cmd.exe, then run dsregcmd /join from there
otherwise it bitches at me about having to run as NT Authority\SYSTEM
k
Hmm...I it should work in bot 2016/2019/2022 and W10/W11. I have it running in both my lab and at various customer setups
r
yeah, you're right... looking at the errors, my system dissapeared out of AzureAD... after I did a dsregcmd /leave...
that's why it's bombing.... Thanks for all the help here, man, I appreciate it!
👍 2
k
Sharing is caring 🙂
💯 2
r
Trying to understand here.. Is it actually Azure AD Connect that populates the devices in AzureAD Devices? They dsregcmd /join finishes the registration?
and wth does my Server 2016 say Windows 10? lol
k
AD Connect enables the hybrid join feature. The dsregcmd /join essentially just speeds up the hybrid join. If you leave the machine running, it will eventually hybrid join itself at some point
If AD Connect has been setup properly with an SCP configuration and the correct OUs
r
ok, i did all that and got it working.... i then did a /leave command, so i could test the task schedule, and now it's not showing up in Devices in AzureAD again.
does /leave remove it from Devices ?
k
No, it shouldn't remove the device, but it removes the registration status
r
odd, the device is gone from AzureAD now....
k
3 of my golden image machines in my lab
r
very odd then
it showed back up after the 30 minute sync time, and your scheduled task worked.. @Kasper Johansen Thanks again!!!!!!
👍 2
k
Great :D
r
@Kasper Johansen Did you end up figuring this out? Simply hybrid-joining these systems does not resolve the published Office Apps being able to sign-in. https://discussions.citrix.com/topic/412560-microsoft-365-apps-activation-issues-in-publish-apps-mode/ I'm about to look at some other things like FSLogix includeofficeactivation and such, but just wanted to see if you knew.
k
Yes and no, I have a posh script I use as a workaround
Let me see if I can find it
if (-not (Get-AppxPackage Microsoft.AAD.BrokerPlugin)) { Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown } Get-AppxPackage Microsoft.AAD.BrokerPlugin
Run as logon script/scheduled task
r
thanks man. Still nuts that Citrix/MS hasn't figured this one out yet?
k
Agree
r
i'll play with it a bit and see if i can figure something out before doing this. Maybe a fresh set of eyes can find something
👍 1
k
Let me know if you find anything
r
of course. 🙂
@Kasper Johansen No luck... i did the script and it seems to work. You tried this shit on 2022 server yet?
k
Hmm...it should work, I have a colleague who has implemented it at a few customers. I'll check with him.
I haven't tested with WS2022 since it was in preview, but at that time it wasn't resolved, if I remember correctly
Also the official statement from MS is that Office 365 is not supported in WS2022
r
oh yeah..... i forgot about that
and i meant without the logon script....
just curious
k
So, it's working with the script on WS2019?
r
that's correct
k
Great 😄
r
yeah, i guess at the end of the day, "it's working".... heh
i tried for many hours, many settings, etc etc... nothing
k
I am away from home until Friday, so I will not be able to do some testing. I'll see if I can find some time to test Office apps as published apps on WS2022 during the weekend
r
no worries man. Just curious. On holiday?
k
No, unfortunately not holiday 🙂 I am on an instructor led course, Microsoft MS-101
r
ah, have fun! 🙂
👍 1
k
Thanks. A lot of new stuff and only 2 days in
7 Views
Open in Slack
PreviousNext
Powered by