User Profile
CGunter
Copper Contributor
Joined 5 years ago
User Widgets
Recent Discussions
OneDrive File Sharing With Team Member That Does Not Have a Mailbox / Ex Employees Showing Up
Hi All, We have a situation where one team member has attempted to share a document via OneDrive with another team member, but received a bounced email notification. When I looked into this, it was because the team member they attempted to share the document with does not have an Exchange license (the team member currently only has a Power BI Pro license). From my understanding, sharing files both internally and externally does not require a license. So the fact that the user shows up in attempting to share with them makes sense. My question however, is there a way to prevent the sharing of documents with internal users that do not have an Exchange license? That way I can help our end users avoid receiving a bounce back message. We have also noticed that former employees can be autocompleted when attempting to share files via OneDrive. When looking into SharePoint, we can see that former employees continue to have a SharePoint user profile. Would this in any way to be related to converting the former employees mailbox into a shared mailbox? Any help would be greatly appreciated! CoreySolvedMerge Two Microsoft 365 Groups Together
Hi All, I have the following scenario: We have two separate active Microsoft 365 Groups that serve essentially the same purpose (we'll just call them 'Group A' and 'Group B') in terms of the materials that are stored on their respective SharePoint sites. Group A does not have Microsoft Teams connected and Group B does have Microsoft Teams connected. What we would like to do is take all the information from Group B and transfer it over to Group A. This includes all the SharePoint material as well as transfer the associated MS Teams team from Group B to Group A (As a reminder, Group A does not have Microsoft Teams connected at the moment). I'm wondering if transferring all this information is possible. If it is, what are the necessary steps, and what are some of the things I should take into account before actually merging these two Microsoft 365 Groups together? Any help is greatly appreciated. Thank you! Corey4.3KViews0likes1CommentAutopilot Reseller Partnership Security
Hi all, I have a question about setting up a Reseller partnership so that our reseller can upload device info to Autopilot only. I want to set this up, but I want to confirm if anyone knew what all info besides Autopilot that they might have access to. It looks like you can remove delegated admin privileges (even if they request it) and they should still be able to upload the info to Autopilot, but I know our security team is most likely going to want to know what all they have access to. I've seen a few screenshots of what it looks like in the partner portal, but I cannot find anything that lists out what all the reseller has access to inside the portal. Any help would be greatly appreciated! Corey1.2KViews0likes1CommentRe: User name and password not recognized error after Intune/Autopilot Device Provisioning Process
Hey Niels, that could definitely be a factor and that's been the route that I've been going down to figure out what's going on. What I found during my testing yesterday was that if I set my UPN and Primary Email for the user in AD to match exactly, I'm able to log into my desktop without issue after the provisioning process. Because of this, it makes me wonder if the issue is with the credential validator in Ping Federate and what it's trying to match on.9.9KViews0likes0CommentsRe: User name and password not recognized error after Intune/Autopilot Device Provisioning Process
Hey Jannik, in regards to your question about the UPN, the UPN of my test user in AD is something like email address removed for privacy reasons and the primary email address of my user is email address removed for privacy reasons. What I found during testing was that if I have those two values match in AD, I'm able to log in after the provisioning process without issue. This is interesting information. I'll have to look into this to see how to properly configure this policy and if that would resolve my issue.9.8KViews1like0CommentsRe: User name and password not recognized error after Intune/Autopilot Device Provisioning Process
Thanks for the response! The username that I enter at the welcome screen is the same UPN value of the user in AD. As an example, the UPN is email address removed for privacy reasons and that's the same value I enter at the welcome screen before it takes me to the MFA page. What I found during my testing is that if I have the UPN and the primary email address of the user in AD match exactly, then I'm able to log in after the provisioning process without issue.9.8KViews0likes0CommentsUser name and password not recognized error after Intune/Autopilot Device Provisioning Process
Hi All, I am currently in the middle of rolling out an Intune deployment strategy using Azure AD Joined rather than Hybrid Azure AD Joined. Everything is working as intended with the exception of an issue I am having after the device is provisioned during the Autopilot/OOBE process. Before I reach the ESP page, I authenticate using MFA with Ping Identity. After I am authenticated, I am taken to the ESP page where the Device Preparation, Device Setup, and Account Setup are completed successfully. After the Account Setup stage is finished, I am taken directly to the workstation desktop where I am able to use the computer. The issue occurs if the computer is locked or restarted. I try to use the username and password that is associated to the user that was created in AD, but I receive the "User name or password is incorrect" message. The only way that I've been able to resolve this issue is change the domain part of the UPN of my user in AD. I'm not sure if the issue is that the user info is not getting cached after the OOBE, or if the issue is with WS-Trust or something completely different. What am I missing? Any help would be greatly appreciated.10KViews0likes8CommentsIntune - Surface Management Portal
Hi All, I'm hoping to get some clarity around the Surface Management Portal in Intune because unfortunately there isn't much information out there for troubleshooting. I have a few Surface Laptops that are currently being "Co-managed" between Intune and SCCM (Surface Laptop 3 and Surface Laptop 4). When I go to the Surface Management Portal, there are a couple of weird things happening: Under Device Information, the count shows 1 Total device (Surface Laptop 3). If I click on the View Report button, both Surface Laptops are displayed in the report. When I click on the View Report button under Warranty and Coverage, the Surface Laptop 3 shows the "Coverage Status" as expired and the Surface Laptop 4 "Coverage Status" as Unknown (the Surface Laptop 4 is actually covered by a warranty). I know this is a newer feature released by Microsoft (end of October of 2021 I believe), so would the issue be that the Surface Management Portal doesn't work with the Laptop 4 yet? Is there a way to trigger some sort of sync on the Surface Management Portal to get the information on the Surface Laptop 4 (I've done a sync on the device itself)? Any help would be appreciated!Solved981Views0likes1Comment
Recent Blog Articles
No content to show