Radio Silence For Windows
Tijuana Strauhal
Due to my own error in setting up Conditional Access. I proceeded to Lock out all my global admins as well as users.
Step 1. Acceptance, I made the mistake, I thought I had excluded one Global admin from the Require phishing-resistant multifactor authentication for administrators policy. Like the Big Red Box on the KB had said apparently I did not. I accept my ignorance on that.
Step 2. Call support, here is where things get worse. Opened a ticket with the Data Validation team calling the number given by the first tech I spoke to. The DV team said I needed to validate a few things to ensure I was a global admin. Acceptable account management validation procedures. Then radio silence for 24 hours so I call back again. I was informed that they needed to reset MFA on the account. I advised that was fine but it was not an MFA issue it was a Conditional Access issue but I sent the required emails and did everything they told me to. Also at this point I have had three Quick Assist sessions with all techs that I had delt with to this point and they screenshot the error every time. They seem shocked that the MFA reset did not work. Techs keep saying they need to collaborate with higher tier support but as of now it has not escalated. Error 53003 is well documented as a Condition Access issue. At this point I have not been able to get into the admin centers for 7 days and I find that there is no recourse to escalate on my own. How is this an acceptable SLA? Why continue to pay for this level of "customer service"?
Prior to about a week ago, silence at the beginning or in the middle of a recording worked perfectly for me. I could start recording, record silence as long as I wanted, and then start recording sound from for instance a web site. And I could pause the source, and the silence would record for as long as I remained paused.
It used to be so simple and so perfect. What went wrong? Same hardware, Same operating system, same Audacity version (I even tried 2.3.3 today), same device drivers, same source, same everything; but things are not behaving the same!
What I tried to say is that WASAPI (Audacity) does record audio stream when there is none coming from the audio source (when the Web radio stream is paused). In such a case, WASAPI (Audacity) does count sheep when there are no sheep in the Web page pen: it records silence.
It also records silence before the Web radio stream is unpaused if there has been a previous recording, and it has been undone (Edit > Undo).
It happened to me as well , recently i had to do a scan for hardware changes and since then i could not record silence , but i accidentally found a workaroud , if you get into a discord call by yourself audacity will record the silence that is picking up from the discord call .
I am currently experimenting with a Desktop Bridge application where the main project is a Windows Packaging Project which packages a Windows Service project along with a UWP Runtime component for executing a VPN Client style background task. I want this windows service to invoke the background task via the Windows Networking VPN API. I've gotten this setup working with a .Net 6.0 Console application instead of a windows service, but whenever I adapt this to a windows service, it doesn't work. The service is created successfully when I deploy the app, but while it runs, it appears to be unable invoke the background task (I do not get an error that I can see, but radio silence log-wise). The issues with this has prompted the following questions:
I have a top-level packaging project where I have extensions set up -- one for the background task (Extension category is windows.BackgroundTask, and it uses Task type of vpnClient) and one for the windows service (Extension category is windows.service, and it uses desktop6:Service). I have two versions of my project, one where the entry point is that of windows service, and the other that omits all windows service code and opts for a console application for the entry point. In the console app/service, it will eventually call ConnectProfileAsync(IVpnProfile) which will activate the background task.
I've talked with the team about this. Based on the response I got, that you want to implement- triggering the background from a windows service is not possible. Now, in the OS, Services have always run in session 0. When the first user to log on is connected to session 1, the second user to log on is connected to session 2, and so on. Session 0 does not support processes that interact with the user.
This means that a service cannot post or send a message to an application and an application cannot send or post a message to a service.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
I think this confirms what I was worried might be the case-- windows service just cannot run the app I'm trying to do because of that difference in context. Thank you for the information, I will just need to figure out a solution without the windows service.
After discussion in comments, it seems like calling background tasks through a windows service is something that is unable to be done. Opting for an alternative solution without using a windows service, perhaps a long running user process instead
Running into a weird issue where after waking a machine up, I can't type the user name and password is it keeps delete anything I type immediately as I type. Seems to be in Sierra only. Trying to nail down if it's specific to 10.12.3 or not. Cause I'm also testing another machine that has 10.12.3, but it's not enrolled into the JSS at the moment and it's not happening there. Has anyone come across this and know of any reasons why this may be happening?
Been asking around on the Apple forums as well, but it's radio silence over there. Figured I would ask here, cause I'm also trying to nail down if there is something happening between Sierra and our JSS that might be causing an issue. We upgraded our JSS recently to JSS 9.97.1482356336.
Also seems to be directly related to how we use the fast switching to enter the admin credentials. Like the user who is logged in can enter their password, but when we try to switch to enter the admin name and password, that's when it's doing that weird deleting of anything I type.
Is the machine AD bound?
AD bound machines always delete whatever has been entered in the password field when they manage to get a live network connection (terrible piece of UI design by Apple), perhaps when you are switching user, for whatever reason the machine keeps losing and reaquiring it's connection to the AD servers, thereby repeatedly deleting the password field.
We have lots of 10.12.3 JSS and AD bound machines and other than the behaviour described above we have't had the issue, we also have fast user switching enabled which I use reasonably often.
Some (including myself) have had luck solving weird login window issues by making sure all of your "Login Window" and "Security & Privacy" settings are located in a single configuration profile. I seem to remember also reading about gremlins related to having the password requirement being set to "immediately" and that you may have better luck setting it to "5 seconds."
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
Just as the title says, I'm not getting any audio through my headset while using a link cable for the oculus home-- no desktop audio in oculus home, no game audio when in a game, despite video working flawlessly. Issue persists with games both from oculus library and steamvr library. Audio works perfectly with steam link.
Here is everything I've tried so far to fix it:
enabled Oculus Virtual Audio Device in device manager and audio settings,
tried every audio device in windows settings,
tried every combo of audio settings on the oculus pc app,
reinstalled/repaired oculus pc app,
enabled beta testing and turned it back off,
plugged headphones into the headset,
tried every audio device in in-game menus,
disabled and re-enabled every audio device in device manager,
and restarted both my PC and quest 2 multiple times between attempts.
so far nothing has affected any change at all. When I have music playing on my desktop while establishing the link, there will be a brief blip of desktop audio through the headset, but it immediately goes away. I'm out of ideas as to how to fix this and help is appreciated.
Once you are connected to the PC, open the control panel and click on sound and make your oculus the default. You can also try the c.same thing with the little speaker on your taskbar to the right of that bring up your sound devices and make the quest default. Sometimes it will switch back or it gets funny. If you open a game and no sound, hit the left button twice twice and it comes back. This happens to me alot especially in Virtual Desktop which looks so much better then airlink.
Hey there, @lovelyperilune, and thank you so much for bringing this to the community! Audio issues can be very frustrating, especially with so many adjustment options that can come up with PCVR setups and games, so we totally understand any frustration you're having trying to get this narrowed down to root cause. Please be assured we'll be happy to dig into this with you, and help you find a resolution! From the symptoms you describe, especially that short-burst of desktop audio that goes away, this definitely seems more like a software/setting issue, and not a "data being blocked or misinterpreted" hardware issue of some sort. You've already done many of the things we would normally recommend you try, and the suggestions that @ItsNoodIes made shouldn't be missed either, but lets have you walk through these steps in this order as well to see if we can affect any change in your symptoms:
c80f0f1006