User Profile
svhelden
Brass Contributor
Joined 7 years ago
User Widgets
Recent Discussions
Users in other tenant cannot open one user's calendar
Hi, we are using cross-tenant sync for two M365 tenants. We have calendar sharing enabled, and it's working fine for everyone - except for one mailbox. All users in all tenants can see Free/Busy times of all other users in all tenants when scheduling a meeting Users in Tenant A can open all other users' calendars (from all tenants) and, unless they have wider permissions, see their Free/Busy times - except for the calendar of ONE user in Tenant B Users in Tenant B can open all other users' calendars (from all tenants) and, unless they have wider permissions, see their Free/Busy times - including the calendar of that one user So, when they schedule a meeting with that user, they can see her Free/Busy times, but when they try to add her calendar to Outlook, nothing happens (in classic Outlook) or they get an error message (in Outlook on the Web): Folder permissions look identical to other mailboxes: All users have the same sharing policy applied. Does anyone have an idea what I could check?524Views0likes0CommentsRe: Intermittent issues with SMB over QUIC (Server 2022 Datacenter Azure Edition)
Does anyone have an idea? Already verified few more things: Certificate (used for both, QUIC and KDC proxy) is from corporate CA and trusted by the clients Ports are open (clients can reach tcp/443 and udp/443) SMB signing is not required on client side Group Policy for KDC proxy includes all UPN suffixes Still, connections stop with "The specified network name is no longer available" after a while or after reboot. Then unmapping/mapping, or restarting workstation service bring it back. Reboot usually does NOT with the drive persistently mapped. Rebooting without the drive mapped, and then mapping it after reboot does usually work.1.4KViews0likes0CommentsIntermittent issues with SMB over QUIC (Server 2022 Datacenter Azure Edition)
Hi, we're trying to implement SMB over QUIC using a Windows 2022 server syncing with an Azure File Share. This seems to work fine in the first place - when we bring up the server and map the drive on a client, we can connect and everything is good. However: After a while, clients lose connection ("the network share is no longer available") When mapping the drive as persistent, in many cases it does not work after reboot (but after disconnecting it and mapping it again) Sometimes it works again after restarting the client's "workstation" service Sometimes it works again after restarting the server's "lanmanserver" service Sometimes it requires server reboot to work again Sometimes it requires client reboot to work again It behaves similarly from both the internal network (using the server's internal IP) as well as the Internet (using the server's public IP). Per WAC everything seems configured correctly: KDC proxy is enabled and configured and known to clients: Regularly (apparently on every connection attempt, but also if nothing is connected), server logs a QUIC error with its own IP: "This event commonly occurs because the server certificate mapping is not created", but the certificate mapping seems fine: Screenshot from the client (services.msc was used to restart the workstation service): Does anybody have an idea what could be wrong, or which logs to check, or which events to collect?Chatting with cross-tenant synchronization
We have implemented the new cross-tenant synchronization feature (https://learn.microsoft.com/en-us/entra/identity/multi-tenant-organizations/cross-tenant-synchronization-overview). Now, every user has his "own" account in his home tenant, plus the synchronized account in other tenant. So, imagine I am UserA in TenantA, and I want to chat with UserB in TenantB. In my Teams (New Teams), when I search for UserB, I find two entries: "UserB" which is the synchronized account in my tenant (TenantA) "UserB (External)" which is his account in his own tenant (TenantB) I can select both and chat with both, due to New Teams' multi-tenant feature. However, UserB sees my chat only if I use his home tenant account. If I chat with "UserB" (his synchronized account in my tenant), he never sees that in his Teams, unless he manually switches to TenantA. Same for me, if UserB chats with "UserA (External)", I see this in my Teams. But if he chats with "UserA" (my synchronized account in his tenant), I never see that. Is there anything we can do?7.3KViews0likes3CommentsHow to get the REAL hostname with Powershell (or Graph API)
Not sure if this question belongs here. I want to retrieve a list of Azure VMs and their real host name (not the VM name). Azure portal shows this name just fine: Per documentation, I should get the same name from OsProfile property through Get-AzVM or Graph API. But this returns the instance name, or part of that, not the host name: How can I get the real host name? Obviously Azure knows it because it is displayed fine in the portal.Solved2.7KViews0likes5CommentsHow to get rid of RestrictedGroups/ConfigureGroupMembership settings?
Colleagues had created a configuration profile with a RestrictedGroups/ConfigureGroupMembership policy to overwrite the local Administrators group on workstations. We have removed the policy assignment weeks ago, but on some devices it is still applying: We have some exception devices where we want to have the Administrators group managed locally, but on every Intune policy sync the group gets overwritten, and any changes done locally or by GPO are reverted. On an affected computer, I can see the old policy in WMI class MDM_Policy_Result01_RestrictedGroups02, but I cannot delete it from there. I do not see the old policy in WMI class MDM_Policy_Config01_RestrictedGroups02. How can I get rid of this policy?400Views0likes0CommentsRe: "New Outlook" stopped auto-updating inbox
The icons don't matter. You cannot have separate links, one for the old and one for the new Outlook. You have ONE link to Outlook per user (!), and that starts either the old or the new Outlook. You need to switch the "New Outlook" option off, that should close the new Outlook and open the old one. If you're running it "as Administrator", I guess you're supplying a separate account for that? In that case it uses the other user profile which has its own settings.49KViews0likes1CommentRe: "New Outlook" stopped auto-updating inbox
I didn't try now because I want to use the "new outlook." But when it appeared originally, I switched to new outlook and back, that had worked. (Could be that some background processes keep Outlook open and that you need to reboot after turning "new outlook" off.)49KViews0likes3CommentsRe: Can't manually change response
All I can say is that if what you want works, I would consider it a bug. The "Response" column should show what the invitee responded. If the invitee did not respond then it should show "None". Maybe someone else can comment on this topic, I'm out. I initially commented because I wasn't sure if I understand what you want. Now I do.1.6KViews0likes2CommentsRe: Can't manually change response
Ok, so you book a meeting with me, I decline, and you change my answer to "Accepted"? Interesting concept. Personally I'd consider it a bug that it has worked before 😉 My guess would be that either your assumption that everyone would run the same Outlook version is wrong, and the behavior has been changed (I'd call it "fixed") in a recent update, or it has something to do with permissions (like you had full access to the invitee's mailboxes before.)1.6KViews0likes4Comments"New Outlook" stopped auto-updating inbox
Hi, I switched to the "New Outlook" a while ago (using for an M365 enterprise account). It worked fine for a while, then it started updating the inbox view when new mail arrived. That is, if Outlook is open with the Inbox folder displayed and a new mail arrives, the unread count next to Inbox in the folder pane increases by one, but the new mail is not displayed. Only when I switch to another folder and then back to Inbox do I see the new mail. It works fine in the browser (although it looks 100% identical otherwise). You have Microsoft Outlook Version 1.2023.405.100 (Production). Client Version is 20230331005.09Solved51KViews0likes14Comments