BGInfo.exe – Windows 7 On Start Up

1 – Download/extract BGInfo.exe (http://technet.microsoft.com/en-us/sysinternals/bb897557.aspx) to:

C:\Program Files\bginfo\ -OR- C:\Program Files (x86)\bginfo\

2a – Create a shortcut in the following directory (will require Adminstrator rights) with your switches:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup

-OR-

2b – Use an auto-run regkey (save the below as BGInfoConfig.reg on your desktop):

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"BGInfo"="\"C:\\Program Files\\bginfo\\Bginfo.exe\" \"C:\\Program Files\\bginfo\\BGConfig.bgi\" /SILENT /TIMER:00 /ACCEPTEULA"

Add extra WMI queries to your BGConfig.bgi file as documented here (thanks for the tutorial):

http://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2008/07/22/bginfo-custom-information.aspx

I like this layout:

Host Name: <Host Name>
User Name: <User Name>
Machine Domain: <Machine Domain>
Manufacturer: <Manufacturer> ***CUSTOM*** See screenshot below.
Serial Number: <SerialNumber> ***CUSTOM*** See screenshot below.
IP Address: <IP Address>
Subnet Mask: <Subnet Mask>
Boot Time: <Boot Time>
Default Gateway: <Default Gateway>
DNS Server: <DNS Server>

		
Advertisements

MDT – Deploying a Test Machine to Virtual PC

If you want to run Windows from a Virtual PC image (running on Windows 7) instead of testing on Hyper-V, VMWare or physical hardware, you will need to update the “Validation” settings of your Task Sequence.

Change the processor to “13MHz” in the screenshot below (which is what the processor is emulated at):Virtual PC Validate Settings

Boot Camp – OSX Lion, Windows 7 x86 and Windows 7 x64 – Triple Boot

This was a process I tinkered with in order to triple boot OSX Lion, Windows 7 x86 and Windows 7 x64 (as a VHD file) all on the same device.

Note: Booting Windows as a VHD requires Ultimate or Enterprise editions.(http://technet.microsoft.com/en-us/library/dd440865(WS.10).aspx)

Boot Camp Assistant will set-up your partitions on disk for you automatically. However, it formats the disk so that you cannot create any additional primary partitions. To remedy that, I create a Virtual Hard Disk (VHD) from within Windows and edit it’s bootloader to be able to switch between multiple installations of Windows instead of burning some Linux disk partitioner software and manually creating everything. This way, OS X is installed clean from the Lion image, and doesn’t interfere with my multiple Windows 7 test OSes.

1 – Install/boot up OSX. Make sure you have Recovery Assistant handy if you blow something up. (http://support.apple.com/kb/DL1433)

2 – Open Boot Camp Assistant, split disk according to what you want Windows to use ( I do 50/50)

3 – Download Windows support media and burn using the SuperDrive when prompted

4 – Insert the Windows 7 install media and let OSX finish the installation

5 – Install the support tools from OSX

Ta-da! A standard boot camp installation. Now, lets install our second copy of Windows.

1 – Create a new VHD (Virtual Hard Drive) to install your second copy of Windows 7 on.

Example below created a 100GB fixed size disk. Adjust to what space you want with maximum setting.

From an Elevated Command Prompt:

diskpart
create vdisk file=c:\Windows7.vhd maximum=102400 type=fixed 
select vdisk file=c:\Windows7.vhd
attach vdisk
create partition primary
assign letter=v
format quick label=VHD
exit

2 –  Apply a Windows WIM image to the VHD using ImageX.exe

ImageX.exe is available in the WAIK (http://www.microsoft.com/download/en/details.aspx?id=5753) toolkit and can be copied to the local Windows 7 machine from:

C:\Program Files\Windows AIK\Tools\<x86 or amd64>\imagex.exe .

An install WIM (x64) can be copied from your install media (Extracted .ISO or physical disk): \sources\install.wim

Copy the .WIM file from your location to your fresh Windows 7 image.

imagex.exe /apply <pathtowim> 1 v:

Example:

imagex.exe /apply c:\extractediso\sources\install.wim 4 v:

(I applied a MSDN copy of Windows 7 Ultimate. Windows 7 is index #4 of the install.wim image included in the download from MSDN.

Side note: To determine what is in a WIM image, run command:

dism.exe /get-wiminfo /WimFile:C:\extractediso\sources\install.wim /Index:# )

Unmount the VDISK from an Elevated Command Prompt:

diskpart
select vdisk file=c:\Windows7.vhd
detach vdisk
exit

3 – Edit the Windows bootloader from within the existing Windows installation to recongize the VHD as an OS:

Open an Elevated Command Prompt

bcdedit /copy {current} /d "Name You Want To Appear Windows Boot Manager"

A long number is generated and displayed. Copy the long number {CLSID} and use it in the following commands:

bcdedit /set {CLSID} device vhd=[C:]\Windows7.vhd
bcdedit /set {CLSID} osdevice vhd=[C:]\Windows7.vhd
bcdedit /set {CLSID} detecthal on

Edit the Boot Loader Timeout (if you want to):

bcdedit /timeout 45

Reboot. Select the new virtual disk from the boot menu. It will finish a new installation of Windows. Run the support media again.

References:

http://technet.microsoft.com/en-us/library/dd744338(WS.10).aspx

http://social.technet.microsoft.com/wiki/contents/articles/how-to-boot-from-a-vhd.aspx

Edit an Existing WIM

Open the Deployment Tools Command Prompt, Elevated

Browse to the appropriate version of ImageX you need.

Either: cd C:\Program Files\Windows AIK\Tools\

x86, amd64, ia64

Run the following command:

(Read Only)

imagex.exe /mount c:\winnamehere.wim 1 c:\mountlocationhere

(Writeable)

imagex.exe /mountrw c:\wimnamehere.wim 1 c:\mountlocationhere

(Note: The “1” is the image’s index number, in case you have appended multiple WIMs to a single file.)

When done, unmount the WIM:

imagex.exe /unmount /commit /c:\mountlocationhere

Microsoft’s Technet Library:

http://technet.microsoft.com/en-us/library/cc766067(WS.10).aspx

Windows 7 x64 – Service Pack 1 – Fatal Error C0000034

2011-03-10 – Windows 7 x64 fails to reboot after installing Service Pack 1 from Windows Updates.

You will get something similar to this:

Fatal Error C0000034 applying update operation (Update 282 of 103814)

Which details from the Windows Log are:

MessageId: STATUS_OBJECT_NAME_NOT_FOUND

MessageText:

Object Name not found.

#define STATUS_OBJECT_NAME_NOT_FOUND     ((NTSTATUS)0xC0000034 L)

 

Option 1 – Manually Edit the Pending.xml To Continue SP1 Installation/Revert

1 – Reboot your PC while it is trying to start up.

 2 – Select “Launch Start-Up Repair (Recommended)”

3 – Click Cancel

4 – At the prompt screen displaying “Startup Repair cannot repair this computer automatically”, click “Don’t Send” button

5 – Click “View advanced options for recovery and support”

6 – A new window opens. Select “Command Prompt” at the bottom of the list

7 – A Command Prompt window opens. Enter %windir%\system32\notepad.exe (notepad.exe should also work)

8 – Notepad opens. Select: File > Open

Note: Change your view from “Text Documents (*.txt)” to “All Files (*.*)”

9 – Navigate to: C:\Windows\winsxs\

Note: If you have Windows installed on a different drive letter, browse to that letter instead of (C:).

10 – Find the file called “Pending.xml”. Duplicate the file (Copy/Paste)

11 – Open the original Pending.xml with Notepad.

Note: This will take a while. The document is very large.

12 – We will now search for a specific string. Press CTRL +F, and search for:

0000000000000000.cdf-ms

13 – Delete the following:

<Checkpoint/>
<DeleteFile path=”\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms”/>
<MoveFile source=”\SystemRoot\WinSxS\Temp\PendingRenames\e56db1db48d4cb0199440000b01de419._0000000000000000.cdf-ms” destination=”\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms”/>

Note: You may or may not have all of these sections. Delete what does appear from the text above.

15 – Save the changes to Pending.xml. Exit Notepad

16 – Exit the Startup Repair and reboot the PC. Depending on how far the installation was along during the Service Pack, it will either complete the installation or revert back to pre-SP1.

Option 2 – Revert The System back to RTM instead of Installing SP1:

1 – Reboot your PC while it is trying to start up.

 2 – Select “Launch Start-Up Repair (Recommended)”

3 – Click Cancel

4 – At the prompt screen displaying “Startup Repair cannot repair this computer automatically”, click “Don’t Send” button

5 – Click “View advanced options for recovery and support”

6 – A new window opens. Select “Command Prompt” at the bottom of the list

7 – A Command Prompt window opens. Enter:
DISM /image:C:\ /cleanup-image /revertpendingactions

This wipes out any pending changes that the Service Pack was applying to the Windows 7 image on the disk.

 

Props to the Internet:

(A) http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/608ecca8-b815-4ff6-8f3c-a828518434a7

(B) http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/1c9a7151-b48c-4a98-aae7-a4b82682ea8e#bcabda57-7338-499f-aee2-d708e76df315

(C) http://blogs.webguild.com/gary/archive/2011/02/23/fatal-error-c0000034-installing-windows-7-sp1.aspx