Jump to content

Collin Joyce

Members
  • Posts

    21
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Collin Joyce's Achievements

  1. That sounds like an interesting thought, I don't know why anyone wouldn't want to utilize Azure SSO (aka Entra ID SSO for anyone confused with Microsoft's million different renames) since it makes the experience way better from the end user standpoint. Personally, I think it should be a requirement anyways because of the functionality benefits alone.
  2. Makes me want to look further into how they're deploying the Windows 11 Explorer, wonder if it actually a "Windows App" instead of how it was previously deployed.
  3. Windows 11 Powershell runs through the "Terminal" app so it would require loading the admin profiles apps vs the taskmgr is still just running as a normal exe program.
  4. Seems to me there is something fishy with the provisioned apps not hitting until the admin profile is being loaded. I know the newest hotfix for FSLogix is supposed to create a folder for the MSIX packages in the ODFC container FSLogix Release Notes - FSLogix | Microsoft Learn I'm wondering if there's something funky going on there.
  5. Yep! The admin profile has the apps loaded so when you open the admin profile it is loading the dependencies that aren't loading in the user profile. I'm guessing the admin profile is local to the image and the user profile is FSLogix containerized right? Since the container isn't carrying the Appx updates it is dumping them each time it reloads it isn't there, but the admin profile being loaded then updates the Apps on the profile that is currently loaded, I believe Microsoft calls this the staged vs installed app package. Does this environment have the Microsoft Store available to the users? If so try without opening the admin powershell to open the Microsoft Store and update the apps. Also might be worth running Get-ProvisionedAppxPackage
  6. When you log off does the profile show the apps are still a part of the profile? I'm guessing they're not being stored with the FSLogix profile and are being deleted after the disconnect because they're not roaming with the profile.
  7. Sounds to me that we definitely need to keep an eye on that and maybe Omnissa might want to look at making the OSOT be a bit more dynamic on the default apps since Microsoft is being a bit more aggressive with their built-in apps. I didn't mention in my OOBE step I generally also update the Microsoft store; it seems that is holds a bunch of dependencies for things as well and the standard ISOs don't seem to be on the current version of the store. I mostly do it because of the "App Installer" app since Winget is a nice tool to be able to leverage, but it also just seems that a lot of the updates they've implemented require the apps to be updated to function without constant crashing or weird behavior.
  8. Yea I think if Microsoft continues to roll out things as an "App" then the OSOT should probably be adjusted to populate the default app removal to be dynamic and grab some whatever is installed. I haven't deployed out the Windows 11 image to my user base yet, but after hearing a bunch of the nightmare people are running into with 24H2, I'll probably hold off deployment until a few more people find the issue out. My guess would 100% be they're implementing changes that "ties" the OS together a bit more and makes it feel more "fluid" for end users, but also makes disabling un-needed functionality a bit harder of a balancing act which will make administrating the image especially in a virtual environment where we are trying to limit the amount of impact each machine has on the hosts increasingly difficult. Phew, excuse the run-on sentence.🥴
  9. I've found this to be the case with removing any of the apps lately. What I've been doing is utilizing a "decrapifier" script that I roll out in the OOB default profile before I do anything else. Then when it comes to getting rid of the apps, I've already deprovisioned everything I don't want in the image, and I leave the rest of them when using the OSOT. Might be worth checking the image to figure out what is installed in the apps, you can do this using powershell running Get-AppxPackage -AllUsers This should drop all of the packages that are in the image currently. I'd probably try running this before and after running the OSOT and see what it removes entirely, because the options not being dynamic means we only have a select few of apps that we can "keep" but I think Microsoft is baking more in that are required for functionality.
  10. Out of curiosity, are you keeping the default apps in the image or removing them? I've noticed Microsoft has been sneaking in more Microsoft Apps in their default image the same way they converted Teams to an app that the old OSOT deleted. I'm wondering if their newest update is using one of those apps as a backbone for functionality.
  11. I can attest that ADBA works for Instant Clones, as far as being "supported" I would doubt they're going to go out of their way to test it and figure out what issues they could have with it. Honestly, I would recommend people utilize ADBA to avoid the need for a separate server specifically for KMS activation, but that would probably be a case-by-case basis where some folks might prefer to have it broken out in case there is an issue with the AD deployment.
  12. I've found that the update to 2406 did help with the Outbound JMS Responder being hung up. The licensing switch did impact me a bit as I upgraded my load balanced connection servers not realizing my non-load balanced connection servers would lose their licensing. I'd recommend if anyone is in a similar situation where you are deploying a load balancer but are still in the testing phase to upgrade all of your non-load balanced servers first when no one is utilizing them. I'm using the edge appliance to get my server licensing, so perpetual might differ from my experience.
  13. I've also been running into random issues with 2312.1 suddenly declining new sessions. I'm planning to upgrade to 2406 tonight and I'll report back if the same issues are being seen. Essentially for us we've had where randomly we're not able to accept new users to our connection servers without anything declining the sessions they just eventually time out. No errors show on the connection server admin console or on the debug log with getting the session to start. It just won't complete the handshake and seems to force us to restart the connection server service. After restarting the service everything is back to normal until it randomly decides to end it again. The issues I generally see are Item enqueued on "Outbound JMS Responder" but there are no workers available to process it. Busy workers = 1, queue length = 10 and the only way to fix this I've found is to restart the service.
  14. We had been running it since it was released and I recently downgraded since it was listed as not supported on Omnissa's chart since they're the ones that should be doing the support now. That's good to know though, seems like it would be an oversight on Omnissa's side then to be listed as not supported...but at the same time they're the ones that are now supporting it or would be the ones supporting it if an issue were to come up I'd like to get their official word that it is supported before I re-upgrade.
×
×
  • Create New...