Endpoint Fraud / Stalking
Hi everyone Im not a developer however I have a complicated crazy situation where all my devices were auto enrolled in an MDM without my consent which I believe someone I used to know did to stalk me , for the past 6 months Ive tried to figure it out as It makes me have very little privlidges and it auto deploys on brand new devices , It also refuses to ping back to anything but still under full control , I believe its controlled via azure and a server domain I tried to see if I had an azure account even though I never made one and I somehow have one but everything says unknown and a bunch of errors on everything I try to access does anyone have any advice for how to go about this ? Also note I never was a part of an enterprise of any kind
Azure AD Join - Supported Configurations
I'm currently looking into setting up an environment that would consist of AVD Session Hosts that are running Windows 11 Enterprise Multi-Session in their own Host Pools and are Azure AD Domain Joined. Ideal scenario is that we do not require Active Directory Domain Services for this solution, management will be handled solely using Azure AD, Intune and Microsoft Endpoint Manager. User Profiles will be delivered using FSLogix from an Azure Storage Account (preferred) or Locally-Stored. My question however, is the "Supported Configurations" that are mentioned in the documentation. The use-case we have above would be Pooled Desktops that are Azure AD Joined but the article states that only configurations as a Jumpbox or where-by no Data is stored on the machine are supported. Why isn't it supported to have Data/Apps on an AVD Session Host that's AADJ? General File Data (Word, Excel, PDFs etc) can be located on SharePoint but Applications need to be installed on the AVD Session Host and some need to store data on the Virtual Machine for them to work. What's not supported about this?
RDP over VPN to Azure VM - what have I missed
Hi, I've set up a Virtual Machine in Azure; it has an app which links to an Azure SQL Database. When I log into aka.ms/wvdarmweb with the user acct which has access to the app, all works fine. Now I'm trying to setup RDP over VPN, and have followed the Microsoft tutorial documents. Virtual Network Gateway is setup, Admin authority went thru ok, download of Azure VPN was fine, and connection has been established from a client machine to Azure over the VPN. Tick tick tick tick, great stuff. I download and start the RDP for the VM, the computer name defaults to "10.0.0.7". I click Connect and get "Remote Desktop can't connect to the remote computer for one of these reasons:" and three possible reasons display. Well, for reason 2 and 3, the remote computer is on and available on the network (otherwise I wouldn't be able to login in via the portal, I guess). So it must be the first reason "Remote access to the server is not enabled." Any suggestions as to what I might have missed? VM Inbound rules on the NIC include AllowRD (3389), AllowPSRemoting (5986), AllowVnetInBound (any). Several users have access to the VM, as demonstrated by access to it via the portal. Thanks