{"id":339,"date":"2018-10-12T11:16:26","date_gmt":"2018-10-12T09:16:26","guid":{"rendered":"https:\/\/backes.nu\/?p=339"},"modified":"2018-10-12T11:16:26","modified_gmt":"2018-10-12T09:16:26","slug":"diskpart-to-the-rescue","status":"publish","type":"post","link":"https:\/\/backes.nu\/index.php\/2018\/10\/12\/diskpart-to-the-rescue\/","title":{"rendered":"Diskpart to the rescue"},"content":{"rendered":"\n\nIn my work, I recently heard that more often new devices (desktop’s\/laptop’s) fails in the beginning of the OSD (OS deploy) because of something is wrong with the partitions on the hard drive. The Boot-image can’t download policys or files to the disk, so it fails.\n\n\n\n\n\nOften the IT-person needs to boot the device and re-partition the disk, and after that start the OSD again, and it will work.\n\n\n\n\n\nI have not done some examination on why it fails. The OEM’s OS works on the device\/disk.\n\n\n\n\n\nBut I have a workaround, or it’s not mine workaround. I did find it on the Internet for a few years ago, so I don’t remember whos to credit (I’m sorry).\n\n\n\n\n\n

But this is the workaround I have.<\/h4>\n\n\n\n\n\nBegin by creating a txt-file with the content of commands for diskpart we will be using later (this is for UEFI-disks).\n\n\n\n\n\n
sel disk 0\nclean\nconvert gpt\ncre par efi size=200\nassign letter=s\nformat quick fs=FAT32\ncre par msr size=128\ncre par pri\nassign letter=c\nformat quick fs=NTFS\nexit<\/blockquote>\n\n\n\n\n\nSave the file (I have named my file uefi_disk.txt<\/strong> ), and put it on your SCCM Package-share.\nThen you will need to create a Package in your SCCM-console, where you will point out the source files (where you saved your new .txt-file).\n\n\"\"\n\nYou don’t need to create a program, just select “Do not create a program” and click next, and just go on and finish the wizard.\n\n\n\n\n\n\"\"\n\n\n\n\n\nHere is two ways to use this.\n\n\n\n\n\nThe first one, if you boot your PC’s from a boot-media (CD\/USB), you can create a new boot-media and put in a prestart command to run diskpart. So go one and create a new Task Sequence Media if you choose this way.\n\n\"\"\n\nMark Boot media, and Next\n\"\"\n\nContinue the wizard, entering your “SCCM-info” till you come to Customize the task sequence media.\n\nHere you will need to tick the Enable prestart command checkbox, and also enter Command line:\ncmd.exe \/c diskpart \/s uefi_disk.txt <\/em><\/strong><– or the name you gave your .txt-file\nYou must also select the Diskpart package you created\u00a0earlier, and point out your Distribution point.\n\"\"\n\nAfter that, finish the wizard, and you are now ready to boot using your new boot-media.\n\n
\n\n\n\n\n\nThe other one is to put this in your boot-image (if you PXE-boot your devices, choose this). Using this way the prestart command will always run (when using TS using this boot-image), and you don’t need to create a new boot-image with this prestart command.\n\nGo to your Boot-image in the SCCM-console, and right-click it and choose Properties.\nGo to the\u00a0Customization tab, and\u00a0tick the Enable prestart command checkbox, and also enter Command line:\ncmd.exe \/c diskpart \/s uefi_disk.txt<\/strong><\/em> <– or the name you gave your .txt-file\nKlick Ok, to save and re-distribute your boot-image, and after that your done.\n\n\"\"\n\n
\n\nWhen you are here, click Next\n\"\"\n\nAnd diskpart will run\n\"\"\n\nAfter diskpart is finished, you can choose your TS, and\u00a0continue your installation\n\"\"\n\n\n\n\n\n","protected":false},"excerpt":{"rendered":"

In my work, I recently heard that more often new devices (desktop’s\/laptop’s) fails in the beginning of the OSD (OS deploy) because of something is wrong with the partitions on the hard drive. The Boot-image can’t download policys or files…..<\/p>\n","protected":false},"author":1,"featured_media":355,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[12,5],"tags":[28,79,78,22,80],"class_list":["post-339","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-note-to-myself","category-shared-with-the-world","tag-configmgr","tag-diskpart","tag-osd","tag-sccm","tag-uefi"],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/backes.nu\/wp-content\/uploads\/2018\/10\/sshot-18.png?fit=1017%2C541&ssl=1","jetpack-related-posts":[],"jetpack_likes_enabled":true,"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p5Cu3K-5t","_links":{"self":[{"href":"https:\/\/backes.nu\/index.php\/wp-json\/wp\/v2\/posts\/339","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/backes.nu\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/backes.nu\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/backes.nu\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/backes.nu\/index.php\/wp-json\/wp\/v2\/comments?post=339"}],"version-history":[{"count":5,"href":"https:\/\/backes.nu\/index.php\/wp-json\/wp\/v2\/posts\/339\/revisions"}],"predecessor-version":[{"id":375,"href":"https:\/\/backes.nu\/index.php\/wp-json\/wp\/v2\/posts\/339\/revisions\/375"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/backes.nu\/index.php\/wp-json\/wp\/v2\/media\/355"}],"wp:attachment":[{"href":"https:\/\/backes.nu\/index.php\/wp-json\/wp\/v2\/media?parent=339"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/backes.nu\/index.php\/wp-json\/wp\/v2\/categories?post=339"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/backes.nu\/index.php\/wp-json\/wp\/v2\/tags?post=339"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}