Event Id 304 and 307 Accompanied With Black Screen

  1. Home
  2. Windows
  3. Windows Server

New Server 2019 VM (latest ISO download)

I can't seem to get the User Device Registration EventIDs 304, 307, 360 from showing up at restart even tho I've already disabled both computer/user instances of "Use Windows Hello for Business" via GPO

Is there something else I'm missing to get these to stop?  Or a scheduled task that needs to be deleted/disabled?  This isn't a major issue as nothing is broken and things seem to be fine, I'm just trying to clean up the Events to minimal error/warnings as possible prior to deploying.



Troy_PBGNW
Troy_PBGNW This person is a Verified Professional
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
Jun 13, 2019 at 18:49 UTC

I just noticed something this week when I built another 2019 VM, this time I changed my build procedure by disabling the Scheduled Task PRIOR to moving the server to the Member Servers OU and this time after multiple reboots, the task is still disabled...so it probably has something to do with one of the multitude of GPOs that are assigned that's causing it to either get re-enabled or prohibits me from disabling a system created scheduled task.

I built it on Tuesday (11th):


10 Replies

EminentX
EminentX This person is a Verified Professional
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
May 9, 2019 at 18:05 UTC

No offense, Why do you spend your energy and time to solve these unimportant stuff?

Have a look at this:  http://www.tecfused.com/2017/07/user-device-registration-event-id-304-307/

Troy_PBGNW
Troy_PBGNW This person is a Verified Professional
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
May 9, 2019 at 18:17 UTC

I had tried that back with my 2016 servers and they would always come back enabled...there was no real way to disable that.  I'll give it a try on 2019 but won't hold my breath.

To your question as to why...because.  I like to get it as clear as possible prior to deployment...as stated in my OP

Troy_PBGNW
Troy_PBGNW This person is a Verified Professional
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
May 9, 2019 at 18:42 UTC

So I manually disabled that scheduled task...rebooted...seems to still be disabled...nice!  304/307 are now gone but 360 still remains...weird that Windows Hello for Business warning still shows up...even when it's disabled via GPO.

Thanks for the link as I didn't think it would work on 2019 as it never would disable on 2016 so I blew that off...I'll add that scheduled task disable back into my script

360 looks like it's going to stick around as I'm not the only one who has disabled the "Use Windows Hello for Business" in both Computer/User GPO and it still shows up

https://answers.microsoft.com/en-us/windows/forum/windows_10-hello/how-to-disable-windows-hello-for-...

EminentX
EminentX This person is a Verified Professional
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
May 9, 2019 at 19:20 UTC

Troy_PBGNW wrote:

So I manually disabled that scheduled task...rebooted...seems to still be disabled...nice!  304/307 are now gone but 360 still remains...weird that Windows Hello for Business warning still shows up...even when it's disabled via GPO.

Thanks for the link as I didn't think it would work on 2019 as it never would disable on 2016 so I blew that off...I'll add that scheduled task disable back into my script

360 looks like it's going to stick around as I'm not the only one who has disabled the "Use Windows Hello for Business" in both Computer/User GPO and it still shows up

https://answers.microsoft.com/en-us/windows/forum/windows_10-hello/how-to-disable-windows-hello-for-...

I'm glad your issue was solved. Please mark my post as an answer. Thanks

EminentX
EminentX This person is a Verified Professional
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
May 9, 2019 at 19:34 UTC

Troy_PBGNW wrote:

The only thing I'm seeing for 360 is to disable event logging if the GPO doesn't work

https://social.technet.microsoft.com/Forums/windows/en-US/df6fabb9-6965-42af-8f5c-e313351eefc3/cant-...

I would appreciate if you post your new question in a separate post. Thanks

Troy_PBGNW
Troy_PBGNW This person is a Verified Professional
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
May 10, 2019 at 19:39 UTC

So, same thing as Server 2016...after subsequent reboots, the scheduled task is re-enabled, and no matter how many times you set it to disabled, Automatic-Device-Join always gets re-enabled...So no fix.  That's why I didn't mess with that in the first place.


Troy_PBGNW
Troy_PBGNW This person is a Verified Professional
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
May 13, 2019 at 18:07 UTC

Anyone else with constructive ideas?  Is it solely based off the scheduled task and if so, any way for permanently force it to be disabled?

cdoublejj

Troy_PBGNW wrote:

Anyone else with constructive ideas?  Is it solely based off the scheduled task and if so, any way for permanently force it to be disabled?

i've seen apps that run other apps as services and email if you they lock up or stall, yada yada, blah blah and all that stuff. i wonder if some sort of script or app can be had to constantly disable a selected app?

Troy_PBGNW
Troy_PBGNW This person is a Verified Professional
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
Jun 13, 2019 at 18:49 UTC

I just noticed something this week when I built another 2019 VM, this time I changed my build procedure by disabling the Scheduled Task PRIOR to moving the server to the Member Servers OU and this time after multiple reboots, the task is still disabled...so it probably has something to do with one of the multitude of GPOs that are assigned that's causing it to either get re-enabled or prohibits me from disabling a system created scheduled task.

I built it on Tuesday (11th):


This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Event Id 304 and 307 Accompanied With Black Screen

Source: https://community.spiceworks.com/topic/2209592-server-2019-user-device-registration-304-307-360

0 Response to "Event Id 304 and 307 Accompanied With Black Screen"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel