User Profile
sebamedo
Copper Contributor
Joined Jun 25, 2019
User Widgets
Recent Discussions
Same Active Directory but different AAD
Hey Guys, so currently im working in an environment where we have one big domain and many departments in different areas. Every department is part of this (on premise) domain but for some reason some departments want to use their own azure ad tenant even though we have one tenant for everyone - No way to change that for now. In fact this results in some serious issues, for example in the Office Suite where they have to change the logged on user everytime theyre opening Word or Excel. We also have Roaming Profiles active, so things they change for there profile will be deleted later on, so they have to do this configuration everytime they log in. We arent Intune enrolled or hybrid managed, pretty oldschool everything. Im searching for a possibility where we could set up an association for those Users or departments to their own tenants, so that if a user logs in, they automatically get logged in into their own individual Azure AD Tenant - or at least get asked for their credentials for their own tenant. I read something about Alternate Login ID but im not sure if this is the right thing we need. I really appreciate your suggestions 🙂 Best regards sebamedoWindows 10 Enterprise activation error with Intune
Hey Folks, im working for a project where all devices (currently running with Windows 10 LTSC 1809, LTSB or Windows 7) are migrated to Windows 10 Enterprise. The goal is to manage all devices with intune. As the update path from all those versions to Windows 10 Enterprise is kinda difficult we are reinstalling them with a fresh Windows 10 Image. So far so good. The autounattend.xml is filled with a generic Windows 10 Enterprise Key, I want Windows to license the device with the Microsoft E3-License which is assigned to my user. The problem is, the device is not going to activate, saying KMS-Server isnt reachable. What am I doing wrong at that point? I bet its some kind of Logic error or I dont get the way microsoft is activating their devices with intune. Another problem i was thinking about is that the generic key makes the device to use the digital key which is of course a LTSC Key, not a Enterprise Key. Do you have any ideas, what I am doing wrong?9.9KViews0likes1CommentRe: Defaultuser0 wrong password
For 2 months im facing that problem, I had absolutly no idea where to search for, so that I started to create a thread on here. And just today I found the solution: The login of Defaultuser0 hasnt worked, because in the registry there was set an Autologon for Defaultuser0 and with the DefaultDomain of my company. As there isnt a defaultuser0 in my local AD, that sign in fails. But why was a Domainname in the Autologon? The reason for it was a GPO that sets the Domain Name for every Device, so that a user has not to manually write it down. After disabling that GPO the Problem has been solved.10KViews1like2CommentsDefaultuser0 wrong password
Hey folks! I really need your help as I cant figure out how to find a solution for my problem. Im doing Autopilot with White Glove (Hybrid AD Join) and Im getting stuck at the point, where the user should log in. The first process of White Glove seems to be working well and it finishes with the green page and the message, that i can turn off my device. Then I turn the device on again, and i get the message "Password wrong". After pressing "Enter" I see, that defaultuser0 has tried to log in. After that I have to log in many times with my own user account to go ahead the autopilot process. The curious thing about it: If I change the following setting in the Autopilot Deployment Profile: User Type: User => Administrator Then this message does not appear. Im pretty sure, that all the intune regarding settings in the Portal are set up correctly, I already had many sessions with an intune supporter. We already had this problem, while we have enabled SSO/ Deep Packet Inspection on the Firewall. After disabling all those settings we could reach all the needed Microsoft-Domains and IPs and the problem has gone. But now as we changed the user type to "User" we are facing those problems again, and I dont no what to change or where to look. Any ideas on this? I already checked if I can reach the needed domains, while Autopilot i opened Internet Explorer and checked that. Thanks !Solved9.7KViews0likes3CommentsRe: Intune Update Scenario
jenstf Okay thats also an interesting point; My Wrapper writes a Branding with the Softwareversion into the registry. Actually I only check, if the Branding exists, but due to your information I will compare the Version-Key. What still dont me make happy is that intune doesnt removes the old version. If you have a MSI this will probably be no problem as it checks the Upgradecode. But if you have an EXE-File, then you could get trouble when the software doesnt detects, that theres already a preversion installed - which could end in having two different Versions on that client. Still trying to find a solution for that... If I choose the way, to create an app for each version, then I could assign the uninstallation of the preversion to the current version. But is there a chance to create a installation order? So that first of all the uninstallation assignment will be executed and then after it the installation?7.1KViews0likes1CommentRe: Intune Update Scenario
jenstf Hey thanks for your fast reply. So in my case it isnt a MSI we use a Powershell-Wrapper, that is packed into a intunewin-file. With that way, downgrading should be still possible I guess? So if I replace the MSI (or in my case the intunewin-file) intune will start a (re)installation on every client, even though it is already installed on that client with a different version? Or does intune still compares the detection rule if the app is already installed?7.3KViews0likes3CommentsIntune Update Scenario
Hi Guys, I havent found something that helps me with my question so I created a new thread for this. When deploying a software package in intune you do this by using Active Directory groups. When deploying an update of a pre-existing app what is the best case szenario for it? I have already read, that it is recommended to edit the already pre-existing package and change the installation file. But what about having two ad groups? The first parent group is for managing all the end users (Example Group Name: Google Chrome). And then there is another child ad group which is the installation group of the current version (Google Chrome Version 1.2.3)? So if adding a new version, i just change the child group, so that i can keep all older versions in case of emergency Downgrades? Would that be a practicable way? Thanks for your help!7.5KViews0likes5Comments
Recent Blog Articles
No content to show