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 advanceAndroid Dedicated device logs.
May be a stupid question, and something I should have found going through documentation. But we have setup 20 or so dedicated devices (Samsung Tablets) that are enrolling and registering all required applications correctly all profiles/policies seem to be getting applied to them OK. What is the best way of getting the logs off of the dedicated devices so our software support team can go through them and see what is happening on these devices?. The issue is that the dedicated devices are experiencing a number of crashes and other technical issues that were not experienced on non MDM registered devices. All these Devices are running in dedicated mode, no forced desktop. We have opened up developer options etc so that support can get to various different settings for testing. Any advise on this one gratefully accepted. Thanks.
