{"id":63,"date":"2010-06-10T13:48:51","date_gmt":"2010-06-10T19:48:51","guid":{"rendered":"http:\/\/localhost\/todd_wp\/automating_windows_7_boot_entry_creating_with_powershell\/"},"modified":"2013-07-09T11:39:14","modified_gmt":"2013-07-09T17:39:14","slug":"automating_windows_7_boot_entry_creating_with_powershell","status":"publish","type":"post","link":"https:\/\/toddbaginski.com\/blog\/automating_windows_7_boot_entry_creating_with_powershell\/","title":{"rendered":"Automating Windows 7 Boot Entry Creation With PowerShell"},"content":{"rendered":"

 <\/p>\n

Recently I needed to create an automated process to make boot entries for developer lab machines to allow them to boot to a virtual hard disk (VHD). The main requirements were to make the process simple and easily configurable. In this blog post I\u2019ll show you the PowerShell script and accompanying XML settings file I used to get the job done.<\/p>\n

Configuration file<\/strong><\/p>\n

The following XML configuration file (settings.xml) stores the settings for the boot entry. It allows you easily configure where the VHD is located and the description you would like to give to the boot entry. The Drive, Path, and Description values are extracted by the PowerShell script and used to configure the new boot entry.<\/p>\n

\n
\n
<?<\/span>xml<\/span> version<\/span>=\"1.0\"<\/span> encoding<\/span>=\"utf-8\"<\/span>?><\/span><\/pre>\n
<\/p>\n
<<\/span>Settings<\/span>><\/span><\/pre>\n
<\/p>\n
    <<\/span>BootEntry<\/span> Drive<\/span>=\"C\"<\/span> Path<\/span>=\"VHDsSP2010.VHD\"<\/span> Description<\/span>=\"Boot To SP 2010 VHD\"<\/span> \/><\/span><\/pre>\n
<\/p>\n
<\/<\/span>Settings<\/span>><\/span><\/pre>\n
<\/p>\n<\/div>\n<\/div>\n
PowerShell Script<\/strong><\/p>\n
\n
The full PowerShell Script can be downloaded here<\/a>. The following portions of the script do the heavy lifting.<\/div>\n
<\/div>\n
\n
First, the PowerShell script returns the values from the settings.xml file.<\/div>\n
<\/div>\n
\n
[System.Xml.XmlElement]$settings = Get-Settings\r\n$BootEntry = $settings.BootEntry\r\n$Drive = $BootEntry.Drive\r\n$Path = $BootEntry.Path\r\n$Description = $BootEntry.Description<\/pre>\n
 <\/p>\n<\/div>\n
Then it copies the current boot entry and assigns it the description from the settings.xml file.<\/p>\n
\n
$BootEntryCopy = bcdedit \/copy '{current}'<\/span> \/d $BootEntry.Description<\/pre>\n
 <\/p>\n<\/div>\n
Then the script extracts the GUID for the new boot entry.<\/p>\n
\n
$CLSID = $BootEntryCopy | ForEach-Object {$_.Remove(0,37).Replace(\".\"<\/span>,\"\"<\/span>)}<\/pre>\n
 <\/p>\n<\/div>\n
Then it uses the values from the settings.xml file to create the path to the VHD which bcdedit<\/strong> uses to modify the boot entry.<\/p>\n
\n
$VHD = 'vhd=['<\/span> + $Drive + ':]' + $Path<\/pre>\n
 <\/p>\n<\/div>\n
Finally, the script calls bcdedit<\/strong> to configure the boot entry.<\/p>\n
\n
bcdedit \/set $CLSID device $VHD\r\nbcdedit \/set $CLSID osdevice $VHD\r\nbcdedit \/set $CLSID detecthal on<\/pre>\n
 <\/p>\n<\/div>\n
The script output looks like this when it is run. (Your GUID will differ from the screenshot.)<\/p>\n
\"PowerShell<\/a><\/p>\n
Enjoy the script, I hope it helps you out!<\/p>\n
Thanks to my buddy Gary Lapointe<\/a> for showing me how to make XML settings files with PowerShell!<\/p>\n
Thanks to Chris Mayo<\/a> for showing me how to use BCDEDIT<\/strong> to make custom boot entires. His blog series that describes how to make bootable VHDs is excellent.<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
  Recently I needed to create an automated process to make boot entries for developer lab machines to allow them to boot to a virtual hard [\u2026]<\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[89],"tags":[5,8],"class_list":["post-63","post","type-post","status-publish","format-standard","hentry","category-operations","tag-helpful-code","tag-virtual-environments"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/posts\/63","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/comments?post=63"}],"version-history":[{"count":5,"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/posts\/63\/revisions"}],"predecessor-version":[{"id":927,"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/posts\/63\/revisions\/927"}],"wp:attachment":[{"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/media?parent=63"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/categories?post=63"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/toddbaginski.com\/blog\/wp-json\/wp\/v2\/tags?post=63"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}