I’m running Windows Server 2008 R2 on my laptop and after I Hyper-V role the following error message showed, when trying to start a Hyper-V machine. Seems the Hyper-Visor entry was never made to the BCD store.
To add the hypervisor auto launch into the BCD store you’ll need to run the following command in administrator mode
bcdedit /set hypervisorlaunchtype auto
make sure virtualization feature is enabled in BIOS!
Recently I set up a Windows 2008 server with ConfigMgr 2007 SP1 (aka SCCM 2007) & wanted to do OS deployment. I ran into some issues because this server was also a DHCP server, this post will address the high level steps I took to get this working.
its rather simple, create an entry in the “HKEY_LOCAL_MACHINESOFTWAREMicrosoftActive SetupInstalled Components” key. the entrees in this key is the stuff you se in the upper left hand corner during first log on. (the Personalized Settings box). Most if not all entries in this key will be in the GUID format, but it does not have to be..
Open REGEDIT and follow the instructions below.
 |
Right click Installed Components and click New KEY, and name the key {Z-UserSetup}. NOTE: The different keys are executed in number and alphabetical order, so to make sure our key is executed last we name it Z-“something” and put it in { }. Everything not in curly braces wile be executed first. |
 |
In the new key create two new String Values (REG_SZ) and name them StubPath and Version. StubPath has info on what we want to run, and could be any executable, script, run.dll e.t.c. Version will show in the Installed Components section in CURRENT_USER (Default) will be the info showed in the Personalized settings box during logon. (can also be sat as @=”info”) |
Now just reboot and log on with a different user, and notepad will be executed during logon.
If you want to set this with a script ,then here small one for disabling the Windows Media Player wizard.
Set oShell = CreateObject("WScript.Shell")
RegPath="HKEY_LOCAL_MACHINESOFTWAREMicrosoftActive SetupInstalled Components{Z-UserSetup}"
oshell.RegWrite Regpath & "Stubpath", "reg.exe add HKCUSOFTWAREMicrosoftMediaPlayerPreferences _
/v AcceptedPrivacyStatement /t REG_DWORD /d 1 /f", "REG_SZ"
oshell.RegWrite Regpath & "Version", "1.00", "REG_SZ"
oshell.RegWrite Regpath & "@", "Accept MP Privacy Statement", "REG_SZ"
you can add as many as you want, just remeber the execution order.
Full details at: Windows7news.com
The previously rumored leak has been confirmed.
Wzor has placed the download links to the Windows 7 RTM on their home page, and it definitely the real deal. The build string is:
6.1.7600.16384.win7_rtm.090710-1945
Windows 7 7600 RTM (x64):
7600.16384.090710-1945_x64fre_client_en-us_Retail_Ultimate-GRMCULXFRER_EN_DVD.iso
Size: 3,224,717,312 bytes
CRC32: 1EE7DC6F
MD5: E6CE9644D0C7A8E1C950D257A7B2C8A4
SHA-1: 31849B315290EFABFD81F967ED3C553D82925E4C
Windows 7 Server 2008 RTM (x64):
7600.16384.amd64fre.win7_rtm.090710-1945.serverenterprise_en-us_vl. serverenterprise.vhd or file-tracker.ru
SIZE: 6,857,337,856 bytes
CRC: 2AA7974F
SHA1: EA13B569AD4EA4F34955D1FB8A7ADFF8A30297E6
MD5: EC65EE9F3B18F7A232F8B0073A02216A
Office 2010 Beta (x86):
14.0.4302.1000_Mondo_volume_ship_x86_en-us_wzt
Size: 798,101,835 bytes
CRC32: 8BE7AB28
MD5: 874AE2B75AD8FAF169784AFEC099B526
SHA-1: E8E13E9DF771314C2B8A615B4952A49DDE3C9117
Office 2010 Beta (x64):
14.0.4302.1000_Mondo_volume_ship_x64_en-us_wzt
Size: 893,402,501 bytes
CRC32: 7CBEF7DF
MD5: 24A46B000B79520969508CF940D6D581
SHA-1: E22690C6E63ACF0D0BDF9588E8308C5C855A38BC
I downloaded this ISO and can confirm its hashes match those of the official believed-to-be-RTM:
File Name: 7600.16384.090710-1945_x64fre_client_en-us_Retail_Ultimate-GRMCULXFRER_EN_DVD.iso CRC32: 1ee7dc6f MD5: e6ce9644d0c7a8e1c950d257a7b2c8a4 SHA1: 31849b315290efabfd81f967ed3c553d82925e4c
See:
http://windows7center.com/news/windows-7-rtm-finalized-at-build-7600-download-leaked/
Also, here are the properties of the setup.exe:
http://cid-0edc1d24b4a14025.skydrive.live.com/self.aspx/Public/Signed.png
I was trying to sysprep a Windows 7 image (build: 7201)
Everytime i started the sysprep process, it was fail with the error: “A fatal error occurred while trying to sysprep the machine.” seems to be a problem with the windows media player. (wmpnscfg.exe) after killing the process, the deployment process ran smoothly.. had to kill it twice once, seems to be starting again after some time… in my case i had to kill the process twice..
During the text-mode setup phase of operating system installation, the Setup program installs drivers for devices that are required to boot the machine. Most of these drivers are included with the operating system. A vendor can enable users to install an additional driver during text-mode setup by supplying a txtsetup.oem file on a floppy disk.
A txtsetup.oem file is a text file that contains the following information:
This section describes the format of a txtsetup.oem file. For additional information, see Installing a Boot Driver.
A txtsetup.oem file consists of several sections that use the following general format:
[SectionName] entry = value1,value2,...
The name of the section is enclosed in square brackets ([ ]). A pound sign (#) or semicolon character (;) at the beginning of a line indicates a comment. Strings with embedded spaces, commas, or hashes must be enclosed in double quotes (” “).
A txtsetup.oem file must include the following sections:
A txtsetup.oem file for a PnP mass storage device must also include the following section:
060 PXEClient
066 IP Address of WDS Server
067 bootx86wdsnbp.com
These are required steps if your DHCP Server is on a different subnet than your SCCM/WDS/PXE Server.
Here is a good KB Article on this subject – http://support.microsoft.com/default.aspx/kb/926172 and http://technet.microsoft.com/en-us/library/cc732351.aspx
