Parameter is incorrect error at ESP phase of Autopilot device preparation policy (Autopilot V2)
Hi Team, I am testing the Windows autopilot device preparation profile (Autopilot V2). Here, I need to rename the device while it is enrolling to the Intune (during ESP). So, I created a script that has below command to rename the device and rebooting it. Rename-Computer -NewName $newname -ErrorAction 'Stop' -ErrorVariable err -Restart -Force The issue I am facing now is that, when the device is at ESP, it runs the script to rename the device and also it restart the device. But after restart it does not complete the device preparation set up and s an shows an error screen called with message "Parameter is incorrect" and after clicking on OK, I get to see the login screen. After logging in, I am able to use my machine fine and the device is also renamed as per my organization standards. Does anyone also have faced this kind of issue while testing the Autopilot V2 with reboot script at ESP. Regards, Ashish Arya
Creating ADMX backed Configuration policies
I am trying to figure out how to create an ADMX backed Config Profile in Intune to disable the weather and stock information that is now sent to the Windows 11 lock screen but I cannot get it to work. According to this post, I should use theWindowsLogon/DisableLockScreenAppNotificationsCSP.This articledescribes the CSP configuration and as it is an ADMX backed policy, it requires SyncML format to configure. Between this article and this article,I created a custom Config Profile like below, Name:Disable App Notifications Description: Blank OMA-URI:./Device/Vendor/MSFT/Policy/Config/WindowsLogon/DisableLockScreenAppNotifications Data Type: String Value: <SyncML xmlns="SYNCML:SYNCML1.2"> <SyncBody> <Replace> <CmdID>2</CmdID> <Item> <Meta> <Format>chr</Format> <Type>text/plain</Type> </Meta> <Target> <LocURI>./Device/Vendor/MSFT/Policy/Config/WindowsLogon/DisableLockScreenAppNotifications</LocURI> </Target> <Data><Enabled/></Data> </Item> </Replace> <Final/> </SyncBody> </SyncML> I've deployed it to my user account first and after it failed, I deployed it to my device where it also failed. The event log shows this error in both cases Can anyone please help tell me where I am going wrong? Thanks in advance
Might have to switch from Mosyle
Hi all, currently using Mosyle to manage 65ish Macs, due to merging with other orgs, it's looking like Intune might be the preferred MDM. Anyone know if using Intune for ADE is limited to having the user create their own user account with admin privileges? Mosyle lets me create an admin account and a Standard user account. SOC2 compliance is now required and having a user account with admin rights won't fly.
Co-managed devices are being tagged as not compliant in Entra ID
Good day! Anyone experienced or familiar with this issue? 🙂 We have the following settings: 1. Conditional Access Policy that blocks Non-Compliant Devices in accessing Corporate Applications. 2. All Corporate Devices are Hybrid Azure AD Joined Devices and Co-Managed with SCCM and Intune 3. Compliance Workload of all devices are being managed by SCCM Our issue is that devices are failing Conditional Access Policy because they are tagged Not Compliant in Entra ID. When I looked in to Intune the device has the correct compliance which is "See ConfigMgr" and the Software Center of the app also shows the device is Compliant.Disable Co-Management and use Intune
Hi We have a Co-managed environment having Hybrid Model (Devices ). Currently, all workloads are on Intune Pilot phase. We now plan to disable co-management and manage devices via Intune standalone. Please share any recommended steps we need to follow or consider as we have 1000+ devices and want to get rid of Co-Managed state.
Device can not join Domain
Hello, i have configure a profile with this article:https://learn.microsoft.com/en-us/mem/intune/configuration/domain-join-configurebut our devices are still in the workgroup and not in our domain environment. We can not install/edit something with our Domain Admin User on any Device. I dont get any errors. Maybe someone have the same issue and can help us? King Regards & ThanksHow to properly switch from Co-Management to Full Intune?
Hi Guys, Intune newbie (and Microsoft platform altogether) here. We have a SCCM + Intune co-management configured setup (Cloud Attach) in a Hybrid AD environment that has Windows 10 and 11 devices in the mix (Intune capabilities are not yet being used). We're gradually trying to move out from SCCM by transitioning the workloads to Intune. My questions are: 1. if we implement the following workload through Intune, when exactly are we supposed to change these switches to 'Intune' side from co-Management ? 2. What exactly Pilot-Intune' mean here? Wondering if these switches are actually affecting the devices or not. 3. If we don't change the switch to Full Intune, what would be the behaviour ? Which one takes the precedence (Intune or SCCM ?) ? 3. If everything is proven to work through Intune, what steps are required to safely decommission SCCM from current devices ? Really appreciate your insights ! Thank you KevUpgrade Existing SCCM Infrastructure and Windows Server OS version
Hi All, I have to upgrade our existing SCCM infrastructure to the latest version along with Windows OS and SQL version. Additionally, I want to remove our existing CAS to simplify the environment. I was wondering what is the best approach to do that. Below is the existing setup and appreciate it if anyone can lead me to the best approach based on the existing setup. Existing setup Three Windows Server 2012 R2 Servers as below. CAS Server Child Primary Site Remote SQL 2012 SP4 Standard Options as for my understanding Option1: In-Place upgrade In-console upgrade to the current branch version 2103 and remove the CAS. In-Place upgrade from Windows Server OS 2012 R2 to Windows Server 2019 In-Place upgrades of the SQL version. In-Place upgrades of the SCCM version. Option2: Backup and Restore In-console upgrade to the current branch version 2103 and remove the CAS. Backup and restore the infrastructure with the newer Windows Operating System (Both Remote SQL and Primary Site). Upgrade to the latest supported SQL version (SQL 2019 Standard) Upgrade to the latest SCCM versions. Option3: Side-by-Site Migration In-console upgrade to the current branch version 2103 and remove the CAS. Implement new SCCM infrastructure with a new Remote SQL server Migrate contents to the new infrastructure Option4: Implement a fresh environment Thanks in Advance Dilan
