Closed utterances-bot closed 2 years ago
This is great. Nice work! The usb drive, is it identical for all clients? Would i be able to use it in the event of a all-out ransomware attack where devices are not booting into Windows anymore? Or for example a Windows update that stops Windows from booting? I’m looking for a solution that gets off-premise users running asap without our intervention (understaffed). If i could hand them a ‘use this stick wisely’-option that would be fine.
@Knuppel1983 if the device is already enrolled to your Intune tenant, you could use this to wipe the device back to a stock build of Windows 10 and if you have Autopilot configured correctly, the device would go through OOBE and you'd end up with a working device again, yes.
The important thing to remember is the tool itself does nothing special. It just loads Windows 10 onto the device in a fairly aggressive way. The important thing is that it does it reliably and quickly.
Thanks..This is a life saver. I say the Youtube presentation as well and you've made improvement. I dabbed around this weekend and I'm not being prompted to select my autopilot config. Any thoughts? The switch is included in the command. Everything builds successfully.
Hi!
This is awesome and works like a charm, however, I seem to have one issue and that is that my Windows seems to be inactivated after I´ve done the reset with the USB-media tool. We´re licenses with a Microsoft 365 license so it says that we have the business version but anyway it´s not activated.
Any thoughts regarding how to come around that issue before we starts to use it in a broader scale?
Your licence should be attached to your user account which will activate when you log on.
If you are going directly to enterprise and the device has never had a licensed copy of pro installed you will also run into trouble. This generally happens when people buy hardware that comes with home edition.
On Wed, 1 Sept 2021, 7:06 am DrFront, @.***> wrote:
Hi!
This is awesome and works like a charm, however, I seem to have one issue and that is that my Windows seems to be inactivated after I´ve done the reset with the USB-media tool. We´re licenses with a Microsoft 365 license so it says that we have the business version but anyway it´s not activated.
Any thoughts regarding how to come around that issue before we starts to use it in a broader scale?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/tabs-not-spaces/powers-hell-blog/issues/8#issuecomment-909638178, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LNIZHPZD4M5FF4F2UDT7U757ANCNFSM5CP4QVEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Hi Ben,
I've used this solution many times with success and I thank you for that! Now I'm running Powershell 7.1.4 and when it wants to connect to Azure for the Autopilot config I get following error: Grabbing Autopilot config file from Azure.. WARNING: Could not load type 'System.Security.Cryptography.SHA256Cng' from assembly 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
Do I need to go back to an older version of Powershell or am I forgetting something else? Again thank you very much for this.
Regards, Pieterjan
Just make sure you have the msal.ps module installed for both pwsh5.1 AND whatever core version you are using
On Thu, 2 Sept 2021, 7:45 pm corneillie, @.***> wrote:
Hi Ben,
I've used this solution many times with success and I thank you for that! Now I'm running Powershell 7.1.4 and when it wants to connect to Azure for the Autopilot config I get following error: Grabbing Autopilot config file from Azure.. WARNING: Could not load type 'System.Security.Cryptography.SHA256Cng' from assembly 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
Do I need to go back to an older version of Powershell or am I forgetting something else? Again thank you very much for this.
Regards, Pieterjan
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/tabs-not-spaces/powers-hell-blog/issues/8#issuecomment-911466266, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LPB5SU3Z2EU2FGXDB3T75BSNANCNFSM5CP4QVEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Yes, that hit the spot!
Your licence should be attached to your user account which will activate when you log on. If you are going directly to enterprise and the device has never had a licensed copy of pro installed you will also run into trouble. This generally happens when people buy hardware that comes with home edition. … On Wed, 1 Sept 2021, 7:06 am DrFront, @.***> wrote: Hi! This is awesome and works like a charm, however, I seem to have one issue and that is that my Windows seems to be inactivated after I´ve done the reset with the USB-media tool. We´re licenses with a Microsoft 365 license so it says that we have the business version but anyway it´s not activated. Any thoughts regarding how to come around that issue before we starts to use it in a broader scale? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LNIZHPZD4M5FF4F2UDT7U757ANCNFSM5CP4QVEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
I imaged a few more systems and they are fine. The embedded license for pro is working as expected. I guess the first one was oddball. I appreciate the reply.
During the build process the script checks to see if the autopilot profile is loaded. If one is detected it automatically moves forward. If I want to select another for another project is it easiest to just delete the downloaded one from cache?
Your licence should be attached to your user account which will activate when you log on. If you are going directly to enterprise and the device has never had a licensed copy of pro installed you will also run into trouble. This generally happens when people buy hardware that comes with home edition. … On Wed, 1 Sept 2021, 7:06 am DrFront, @.***> wrote: Hi! This is awesome and works like a charm, however, I seem to have one issue and that is that my Windows seems to be inactivated after I´ve done the reset with the USB-media tool. We´re licenses with a Microsoft 365 license so it says that we have the business version but anyway it´s not activated. Any thoughts regarding how to come around that issue before we starts to use it in a broader scale? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LNIZHPZD4M5FF4F2UDT7U757ANCNFSM5CP4QVEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Okej, but if it´s a computer that never been in use before, then you don´t have any account to connect the licenses to? Now, I have just tested the solution in our M365 environment without local AD, we´re licensed with M365 license.
Look at the pictures regarding the licens issues, and this computer has been in use before with a license and if I use a stick from Windows 10 deployment it is licensed as it should.
I'm having the same issue mentioned a couple days ago;
WARNING: Could not load type 'System.Security.Cryptography.SHA256Cng' from assembly 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
I guess I am not quite getting the fix proposed, which was "msal.ps module installed for both pwsh5.1 AND whatever core version you are using"
I think it's that I don't understand the "and whatever core version you are using" part. I installed msal.ps for 5.1, and also 7. In 5.1, the most recent version didn't work, there is an error about pwershellgetformatversion 2.0 not being supported. Trying older versions, it seems that 4.5.1.1 is the latest that works.
Having an interesting one - got the USB Stick all created, popped it into a new device for testing, and popping showing "Error while getting deviceID of a usb stick. No additional USB Storage devices must be attached" Which would be fine, but its just the installer disk. Wondering if the NVME Disks count as an a USB stick according to the script?
Machines a Dell 3520 Lattatude.
Cheers.
Solid state disk's like nvme drives shouldn't be showing up as a USB device... I'd start with checking the bios to see how it's being handled first.
On Tue, 21 Sept 2021, 7:56 pm Lennethx, @.***> wrote:
Having an interesting one - got the USB Stick all created, popped it into a new device for testing, and popping showing "Error while getting deviceID of a usb stick. No additional USB Storage devices must be attached" Which would be fine, but its just the installer disk. Wondering if the NVME Disks count as an a USB stick according to the script?
Machines a Dell 3520 Lattatude.
Cheers.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/tabs-not-spaces/powers-hell-blog/issues/8#issuecomment-923821991, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LJTBQFI7VPVQMU7NALUDBJF5ANCNFSM5CP4QVEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Aye, what i presumed.
Checked over the bios, not really seeing anything that outstands compared. Guess its going to be a trail and error jobbo
Hi Ben! Thanks for creating this project! I run into the following error message when running the Publish-ImageToUSB command and after i sign in to my tenant. It seems it comes from the -getAutopilotCfg parameter, but i cannot get my finger on it where to solve this. Could you steer me in the right direction?
Nevermind! As always, there were a few corrupted Powershell modules sneaking in the back.. Fixed it, works perfectly now, thanks again Ben!
Great to hear you figured it out.
On Fri, 24 Sept 2021, 5:23 pm StrubeNL, @.***> wrote:
Nevermind! As always, there were a few corrupted Powershell modules sneaking in the back.. Fixed it, works perfectly now, thanks again Ben!
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/tabs-not-spaces/powers-hell-blog/issues/8#issuecomment-926406195, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LMOAM4ELOE46E2ET6DUDQRQ5ANCNFSM5CP4QVEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Thanks again for your hard work. Is there a way for this to work on systems that use BIOS mode. UEFI is good to go on my modern computers but some of my legacy systems don't support the mode.
It should already handle bios // uefi.
On Sat, 25 Sept 2021, 2:50 am captainplanet, @.***> wrote:
Thanks again for your hard work. Is there a way for this to work on systems that use BIOS mode. UEFI is good to go on my modern computers but some of my legacy systems don't support the mode.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/tabs-not-spaces/powers-hell-blog/issues/8#issuecomment-926777159, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LKJZO7HAATFTFMSNVDUDST4BANCNFSM5CP4QVEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
I'll give it another go this weekend. I do have a suggestion for a feature option. +The ability to download all Autopilot profiles and select when one to use during imaging. I my use case, We have dynamic groups membership assigned from matching the prefix in the naming scheme used in autopilot profiles. So at the moment I have different flash drives for each profile. Having all profiles on one drive would be awesome. Thank you for all the hard work. Let me know the best way to support your efforts because you've saved me a lot of time. Cheers!
Hi, I have been having issues with New Dell Laptops, as they come with Raid Mode preconfigured instead of ACHI. Is there a way we can implement Raid Drivers into this process automatically.
If we boot into the USB it gets wiped without installing windows on to the SSD, as its missing Raid Drivers.
If someone has overcome this challenge, please share the secret.
Thanks,
I'll give it another go this weekend. I do have a suggestion for a feature option. +The ability to download all Autopilot profiles and select when one to use during imaging. I my use case, We have dynamic groups membership assigned from matching the prefix in the naming scheme used in autopilot profiles. So at the moment I have different flash drives for each profile. Having all profiles on one drive would be awesome. Thank you for all the hard work. Let me know the best way to support your efforts because you've saved me a lot of time. Cheers!
We have the exact same idea, we have a different prefix for laptops and desktops with 2 profiles. Selectable profiles while booting would be awesome indeed! The next step for me is to see if i can get this deployment bootable from the network through pxe. I work in a school environment with computer classrooms with 25+ desktops each. Making this network bootable would save me lots of time making the switch from on-prem to azuread/intune with desktopmanagement. If anyone has this working already then tips would be more than welcome!
https://github.com/tabs-not-spaces/Intune.USB.Creator#-before-raising-any-issues-
If it's not working in 7, use 5.1.
On Sat, 20 Nov 2021, 7:27 am adzale, @.***> wrote:
Hey there. I love this tool, but I am unable to run it successfully.
I installed all of the modules and msal.ps for both Windows and Powershell 7. How do I actually get the USB installer script to actually connect to AzureAD. I receive this error when it tries to grab the autopilot config file from Azure.
WARNING: Could not load type 'System.Security.Cryptography.SHA256Cng' from assembly 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
Any assistance or guidance would be greatly appreciated.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/tabs-not-spaces/powers-hell-blog/issues/8#issuecomment-974424923, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LLFCFG6YLTUUV5KF7DUM2XMRANCNFSM5CP4QVEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Apologies if this is a dumb question, but does this method create an autopilot device in Intune, so if windows is reset at some point in the future it'll automatically try to re-enrol again?
@saint-david not a dumb question at all. No, this solution does not enroll the device hash for you, it performs what is called an "offline join", which generates the json file that is required for enrolling to the tenant and then based on your autopilot policy, the device can THEN be converted to an autopilot device.
TL;DR - No, but if your autopilot policy is set up to auto convert devices, then it will work that way.
I've had to fight to get this one running - but that is due to PS being turned off by default for security reasons. But - after a tweak I was up and building the USB Drive.
Once done, I also ran into the error listed above:
"Error while getting deviceID of a usb stick. No additional USB Storage devices must be attached"
I've tried on several Lenovo devices with the same result. Nothing stands out in BIOS as a possible direction.
Ignore my comment above.
I can't retrieve my AutoPilot Profiles. Any clue?
Same issue as @strubeNL is showing above..
Is it possible to reboot automatically when finished? Option 3 is already chosen automatically by changing Invoke-Provision.ps1. All our devices need the boot menu to start from usb, so the installation should continue on the harddrive.
Sorry my bad. Was a different error message.
The strange thing is that I'm a global admin in this tenant. I've also tested this with a tenant from our customer and there it works.
This error message shows up when I'm trying to retrieve the autopilot profile from my own developer tenant. You know the one that is available by Microsoft with E5 developer licenses. Could it has something to do with this kind of tenant that there are few restrictions to make sure that I'm not going to use it as a "production" tenant?
A successful-failure.
I went back over the USB Build process and discovered the ESD vs WIM issue and resolved it and now have a working USB drive that will indeed boot and AutoPilot the device.
Initial sign on seems to work; the device imports itself into the Device Enrollment of Azure. Only the device fails to sign in with a Domain Admin level account with error:
Something Went Wrong. Confirm you are using the correct sign-in (~). Error Code: 80070002
As I understand it, this is due to the fact that Microsoft has depreciated ADFS - and it is of course disabled in this environment.
Other than that - it's a great process and worked perfectly - I'm hoping I can find a solution to work with this hurdle.
First I would like to say this was a great help Thank you I am currently try to create a new usbkey but I getting this error warning: webException what am I missing followed your instruction to the letter but no joy
When I'm trying to image a new device I'm getting the error message "WARNING: Error while getting DeviceID of potienttial Windows target drives".
Any clue what to do?
Any reason this wouldn't work for Windows 11 as well? Or is this exclusion to Windows 10?
I'm trying all of the above from a Windows 11 machine, using a Windows 11 ISO. I'm getting similar error messages to others in which the fix is to have MSAL.PS installed on Powershell 5.1 and 7. Installing in both shells didn't fix the issue for me.
It does. Confirm the installation of all of the pre-reqs.
On Tue, 22 Feb 2022, 1:57 am glennbullion, @.***> wrote:
Any reason this wouldn't work for Windows 11 as well? Or is this exclusion to Windows 10?
I'm trying all of the above from a Windows 11 machine, using a Windows 11 ISO. I'm getting similar error messages to others in which the fix is to have MSAL.PS installed on Powershell 5.1 and 7. Installing in both shells didn't fix the issue for me.
— Reply to this email directly, view it on GitHub https://github.com/tabs-not-spaces/powers-hell-blog/issues/8#issuecomment-1046964024, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LMQEL2HRZTCZ7L6LTDU4JHFJANCNFSM5CP4QVEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message ID: @.***>
I'll keep playing, but I'm indeed doing a "import-module msal.ps" on both Powershell 5.1 and Powershell 7.2.1. Gets as far as the Autopilot config before having an issue with connect-msgraph not wanting to do its thing.
I too am having issues on win10 and do have all the pre-reqs installed went through the guide multiple times to verify
On Mon, Feb 21, 2022 at 3:18 PM Ben R. @.***> wrote:
It does. Confirm the installation of all of the pre-reqs.
On Tue, 22 Feb 2022, 1:57 am glennbullion, @.***> wrote:
Any reason this wouldn't work for Windows 11 as well? Or is this exclusion to Windows 10?
I'm trying all of the above from a Windows 11 machine, using a Windows 11 ISO. I'm getting similar error messages to others in which the fix is to have MSAL.PS installed on Powershell 5.1 and 7. Installing in both shells didn't fix the issue for me.
— Reply to this email directly, view it on GitHub < https://github.com/tabs-not-spaces/powers-hell-blog/issues/8#issuecomment-1046964024 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AIDA4LMQEL2HRZTCZ7L6LTDU4JHFJANCNFSM5CP4QVEQ
. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
You are receiving this because you modified the open/close state.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/tabs-not-spaces/powers-hell-blog/issues/8#issuecomment-1047235654, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWNLI3TTTSN6GJE47RWLPMTU4KTZXANCNFSM5CP4QVEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>
Just tried from a fresh machine. Installed PowerShell 7.2.1 and MSAL.PS into both Powershells (5.1 and 7.2.1). Still the same exact error message regarding the AutoPilot cfg (System.Security.Cryptography.SHA256Cng)
Okay, quick update. Write now it is burning to USB. We'll see if it finishes and works. :) Did a ton of digging (remember I'm not a Powershell expert). For my use case, which I'm sure is different from others. I had to run a:
"import-module Microsoft.Graph.Intune -useWindowsPowershell" to move forward.
All of this is handled in the module. I'm sorry you had so much difficulty with it.
On Wed, 23 Feb 2022, 5:01 am glennbullion, @.***> wrote:
Okay, quick update. Write now it is burning to USB. We'll see if it finishes and works. :) Did a ton of digging (remember I'm not a Powershell expert). For my use case, which I'm sure is different from others. I had to run a:
"import-module Microsoft.Graph.Intune -useWindowsPowershell" to move forward.
— Reply to this email directly, view it on GitHub https://github.com/tabs-not-spaces/powers-hell-blog/issues/8#issuecomment-1048066748, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LJPQ2P7MIPEMYPZP63U4PFPLANCNFSM5CP4QVEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message ID: @.***>
Oh not a problem. Gave me a chance to learn some Powershell. Very useful tool, as I can now wipe and set up PCs without doing all of the joining from Powershell during set up.
It does seem to be working for me.
What I had to do slightly different (documented it all for my own notes).
From Powershell 5.1:
Install-Module Microsoft.Graph.Intune -Scope CurrentUser –Force // Needs to be in both shells Set-ExecutionPolicy Unrestricted //Corrects an error when running the next command:
From Powershell 7: Import-Module Microsoft.Graph.Intune -UseWindowsPowershell
After doing the above, I tried to create a few sticks from different machines. So far, so good.
I keep getting this error and I don't have much to show for my research.
Getting install.wim from windows media...WARNING: An error occurred while downloading the resource
wrong installation media is my first guess
On Wed, Mar 2, 2022 at 11:51 AM markorr321 @.***> wrote:
I keep getting this error and I don't have much to show for my research.
Getting install.wim from windows media...WARNING: An error occurred while downloading the resource
— Reply to this email directly, view it on GitHub https://github.com/tabs-not-spaces/powers-hell-blog/issues/8#issuecomment-1056019702, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDA4LK3A36Q7INAL7S2T3LU523PVANCNFSM5CP4QVEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message ID: @.***>
I had this issue myself during some testing. I did two things (not sure which solved it). I re-downloaded the ISO file, and also cleared out the Temp folder, where much of this happens.
First I would like to say this was a great help Thank you, when i load the usb-stick i get the next error bij applying the windows image from the usb: Error:87 the /Index: option is missing a required argument. for more information, refer to the help for the /index: option.
anyone know what i'm doing wrong?
Is this usable on a VM to try it out ? At what step does the device get added in Autopilot on the tenant ? Do we have to wait for a statis to be "assigned" or no ? thanks
I've had to fight to get this one running - but that is due to PS being turned off by default for security reasons. But - after a tweak I was up and building the USB Drive.
Once done, I also ran into the error listed above:
"Error while getting deviceID of a usb stick. No additional USB Storage devices must be attached"
I've tried on several Lenovo devices with the same result. Nothing stands out in BIOS as a possible direction.
@gjacob3412 Could you maybe expand on how you resolved the ""Error while getting deviceID of a usb stick. No additional USB Storage devices must be attached"?
I tried to understand you comment stating
I went back over the USB Build process and discovered the ESD vs WIM issue and resolved it and now have a working USB drive that will indeed boot and AutoPilot the device.
Not exactly sure what you mean by that comment and am currently trying to find a solution.
Hello !
I have a error when I do the Publish-ImageToUSB: Getting install.wim from windows media..Checking if file already downloaded..AVERTISSEMENT : Indexation impossible dans un tableau Null.
Any idea? I'm newbee :)
Resolution to the "Error while getting deviceID of a usb stick. No additional USB Storage devices must be attached"
Main issue was that the E drive was never having the ISO data transferred, as the ISO generated from the Windows Creation Tool Will not work.
Use the Multi Version Windows ISO instead
Luckily I was able to download this version by randomly googling Windows 10 ISO on my mac while on my break. Microsoft webpage will change based on your browser's user-agent, meaning that if you access the webpage https://www.microsoft.com/en-us/software-download/windows10 on a Windows Device, you will only have the option to download the Windows Media Creation tool
Either access the webpage and download Mutli Version ISO to a flashdrive on a Mac, or change the user agent on your Windows Computer!
@GuillaumeG93 My best guess would be due to that error, is that you are not providing the path of the Windows ISO, and simply copying and pasting the default command:
after -windowsIsoPath, specify location of the Windows ISO you will need to use.
You need to edit this portion "C:\path\to\win10.iso" to a specific location on your computer, simply locate the file, hold SHIFT -> Right Click -> Copy as Path, and replace "C:\path\to\win10.iso" with your location of the file.
Hi i am getting an error saying, checking the connection to Microsoft. This might take a while any idea why
Create a bootable Windows 10 Autopilot device with PowerShell! | Powers Hell
The most common complaint that I’ve received from people over the last few years around Intune / Autopilot / Modern Management is that people find it frustrating how much effort is involved in getting a device prepared to handover to a client for Autopilot enrollment.
https://powers-hell.com/2020/05/04/create-a-bootable-windows-10-autopilot-device-with-powershell/