User Profile
Yazo97
Copper Contributor
Joined 5 years ago
User Widgets
Recent Discussions
Re: Recovery of Unsaved Recording of Teams meeting
AsifaliHi, I trust you are well. Recordings are set by default to be accessed via Microsoft Stream, or OneDrive all depending on your orgs settings. What you can do is see if the recording is displayed in the teams chat or channel you started to record, by default the person who started the meeting will automatically get an email. The meeting recording ends when the last person leaves. https://docs.microsoft.com/en-us/microsoftteams/cloud-recording#:~:text=Meeting%20recordings%20are%20stored%20in%20Microsoft%20Stream%20cloud%20storage.59KViews1like1CommentRe: Microsoft365 device management not showing all company devices
Moe_KinaniThanks it has worked but now one last issue, do I require the MDM GPO for auto enrollment? I think its conflicting with Autopilot, when I did a RSOP.MSC it shows an error and when I log on to the Client is says The security database on the server does not have a computer account for this workstation trust relationship18KViews0likes0CommentsRe: Microsoft365 device management not showing all company devices
Thijs Lecomte @moe_kinani I managed to get it working. My VM gets a red error page at the Windows Autopilot OOBE page, so I heard VMs dont support White Glove deployement? Should I disable this setting for my Enrolment policy? Neither can I sign into the end users Microsoft work/school account but there is connectivity and I can ping my domain. Setup: Intune Connector Device writeback Azure Hybrid join Group for Devices, I am trying to do a Hybrid Join for the VM, added organization and Container Attributes as well as Delegation on the Intune DC connector19KViews0likes2CommentsRe: Microsoft365 device management not showing all company devices
Thijs LecomteHi I have this issue, devices were currently Azure AD registered, but no compliance status, it says N/A but in Endpoint Manager it shows my Android device is Compliant. Now I have a duplicate of my Windows 10 VM which is now Hybrid Joined which I am trying to achieve. How do I enforce policies with these kind of joins?19KViews0likes4CommentsRe: Error joining Azure VM AD to on_prem AD through VPN
Kurt Johnson Good day. I have an ON-Prem environment running on a Hyper-V Hyper Visor (Windows Server 2019) with two network adapters. One for Internet and one from my firewall (Fortigate) I created a Domain on Prem and synchronized it with AD Connect to Office 365 for my users etc. I also synced my custom domain to Office 365 and on prem. I then created a site to site VPN to Azure from on Prem and it is connected, my goal is to join the Windows 10 Client I created in Azure to my on prem domain but I cannot due to DNS settings. I am able to ping the domain controller, its ip address and do a nslookup and vice versa. My site to site vpn in the firewall has nat enabled. My Azure environment has two virtual networks that are peered to each other. One VNET has the VPN created in it, the other one is in another region because I could not deploy reseources or vms in my VPN region (South Africa North) so I had to peer it for my vm to get connected. Please assist. On prem configs: IP Address: 10.70.20.20 DNS Server: 172.10.0.10 No DHCP, cause its connected to my on prem networjk Azure environment: VNET DNS SERVERS: 172.10.0.10 client vm ip : 10.1.0.4 DNS SERVER : 172.10.0.10 I have SVR records and DNS installed on prem but stilll cant get client to connect to my domain. Please assist The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "YASEEN-DC.YASEEN.LOCAL": The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc._msdcs.YASEEN-DC.YASEEN.LOCAL Common causes of this error include the following: - The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses: 8.8.8.8 172.10.0.10 - One or more of the following zones do not include delegation to its child zone: YASEEN-DC.YASEEN.LOCAL YASEEN.LOCAL LOCAL . (the root zone) PS C:\Users\yaseen.abrahams> ipconfig /flushdns Windows IP Configuration Successfully flushed the DNS Resolver Cache. PS C:\Users\yaseen.abrahams> Get-DnsClientServerAddress InterfaceAlias Interface Address ServerAddresses Index Family -------------- --------- ------- --------------- Ethernet 5 IPv4 {172.10.0.10, 8.8.8.8} Ethernet 5 IPv6 {} Loopback Pseudo-Interface 1 1 IPv4 {} Loopback Pseudo-Interface 1 1 IPv6 {fec0:0:0:ffff::1, fec0:0:0:ffff::2, fec0:0:0:ffff::3} PS C:\Users\yaseen.abrahams> Resolve-DNSName yaseen.local Name Type TTL Section IPAddress ---- ---- --- ------- --------- yaseen.local A 600 Answer 208.91.112.55 yaseen.local A 600 Answer 208.91.112.55 PS C:\Users\yaseen.abrahams> Resolve-DNSName _ldap._tcp.dc._msdcs.yaseen.local Name Type TTL Section PrimaryServer NameAdministrator SerialNumber ---- ---- --- ------- ------------- ----------------- ------------ yaseen.local SOA 3600 Authority yaseen-dc.yaseen.local hostmaster.yaseen.local 455KViews0likes0Comments