I am running X11 on Ubuntu 22.10. First of all, I am not sure if I should really care that I am not using Wayland. I don't know how much of a big deal it is or if I should just be happy things seem to be working well.

I AM Running Nvida for video - I have seen in the past where this MAY be a cause but I don't know if that is still true.

On the login screen, I do NOT have a gear icon so I can choose the session I want to use for some reason.

The only edit that I have made is that in grub I changed this line:

GRUB_CMDLINE_LINUX_DEFAULT="text nomodeset"

1. I like having the text on bootup instead of the regular screen because, I think it looks cool. Yeah, I know... Silly but I like it.
2. The nomodeset is required because without it it gets stuck on boot... An issue with NVIDIA.

So I am not sure if it's a big deal or not it's just weird to me that in previous versions of Ubuntu I did see I could change.

Found the problem and fixed it.

For anyone else having this problem:

sudo nano /etc/default/grub

Change this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
To: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"

sudo update-grub

Potentially issue with NVIDIA Drivers:
https://www.reddit.com/r/Ubuntu/comments/y0c1k9/cant_boot_on_515050generic_and_nvidia_driver/

I am running the latest BIOS for the computer (released in August)

When I boot my PC into Ubuntu, with Linux 5.15.0-50-generic it doesn't boot. I just get what's on this screen and it hangs.

If I select Ubuntu with Linux 5.15.0-48-generic I get the very same screen but then it asks me for the disk encryption password (encrypted as a part of loading Linux [no 3rd party tools]) then boots to the login screen where I enter my password and everything works fine.

Of course when I update to 50 and reboot it no longer boots.

I know I am probably using the wrong terms but trying my best to describe the issue.

@flaxking said in Windows Defender Application Control:

@obsolesce said in Windows Defender Application Control:

@ccwtech said in Windows Defender Application Control:

@obsolesce said in Windows Defender Application Control:

@ccwtech said in Windows Defender Application Control:

Has anyone played with Windows Defender Application Control, specifically Group Policy to turn it on for each workstation?

I have a request from a client to do this, but I am very leery of using group policy for something like this.

Are they all running Win 10 Enterprise?

For sure no... Win 10 Pro.

Then it won't work as it's a requirement.

I think specifically it's using Group Policy for WDAC that's enterprise edition only, right?

Yes, you can use it in Pro, just not enforced by a GPO

@obsolesce said in Windows Defender Application Control:

Then it won't work as it's a requirement.

Well that's easy. Thanks!

@obsolesce said in Windows Defender Application Control:

@ccwtech said in Windows Defender Application Control:

Has anyone played with Windows Defender Application Control, specifically Group Policy to turn it on for each workstation?

I have a request from a client to do this, but I am very leery of using group policy for something like this.

Are they all running Win 10 Enterprise?

For sure no... Win 10 Pro.

Has anyone played with Windows Defender Application Control, specifically Group Policy to turn it on for each workstation?

I have a request from a client to do this, but I am very leery of using group policy for something like this.

@krzykat This wouldn't have been that. Was just worth getting an RMA and starting fresh.

The new router arrived and adopted without any issues. It would have been nice to try the old router since the MTU changed so we know which of the two was the fix, but I am happy to report all is working well with the new router in place.

Sending in the old one for RMA credit.

@dashrender I think I tried as low as 1400 but not that low.

@dashrender Even tried that and it adopts. I tried to then migrate from that local controller to the online one and no luck. I had the ISP make a change (increase MTU) and going to try when the new one arrives tomorrow. Hopefully that will fix the issue.

@syko24 Tried both.

@gjacobse How would that help adopt a USG Pro?

@syko24 Tried that. And thanks. This one isn't easy.

@syko24 It has been factory reset multiple times and not in our controller anywhere.

@syko24 Yes.

@syko24 said in Unable to adopt USG Pro into Unifi Controller - Server Reject:

@CCWTech - Are you seeing the USG Pro in the controller with the option to Adopt? Or are you setting the inform and it just doesn't show up in the controller?

Never shows up in the controller.

@dashrender said in Unable to adopt USG Pro into Unifi Controller - Server Reject:

@ccwtech Is the device actually on the internet?

Yes it is. It can ping the controller without issue. Right now I have ordered a different router to see if it's an issue with this particular one. I am also asking the ISP to investigate a possible issue on their side as well.

It's odd, but I remember that when I put in a new server about a year ago. I had to manually set the MTU in Windows Server 2016 to 1450 or it wouldn't stay connected. Hopefully one of the two will solve the issue... Unifi support is beyond worthless.