July 2009 - Posts
ISV (Independent software vendor) and IHV (Independent hardware vendor) Partners will be able to download Windows 7 RTM from Microsoft Connect or MSDN on August 6th.
Microsoft Partner Program Gold/Certified Members will be able to download Windows 7 RTM in English through the Microsoft Partner Network (MPN) Portal on August 16th. By October 1st, the remaining languages will become available to download.
Microsoft Action Pack Subscribers will be about to download Windows 7 RTM in English starting August 23rd. By October 1st, the remaining languages will become available to download.
OEMs will receive Windows 7 RTM software images beginning approximately 2 days after we officially RTM, as a little time is required to release and distribute these images.
Volume License (VL) customer with an existing Software Assurance (SA) license you will be able to download Windows 7 RTM in English starting August 7th via the Volume License Service Center (VLSC). The rest of the languages for Windows 7 RTM should be available within a couple of weeks after that.
Volume License customers without a SA license will be able to purchase Windows 7 through Volume Licensing on September 1st as we announced last week at WPC09.
IT Professionals with TechNet Subscriptions will be able to download Windows 7 RTM in English on August 6th and remaining languages by October 1st.
Developers with MSDN Subscriptions will be able to download Windows 7 RTM in English on August 6th and remaining languages by October 1st.
and last: Windows 7 will be in retail stores and shipping on new PCs starting October 22nd.
wooh! Is that RTM? How come the others on the internet can get more latest build than MVP?
New Windows Server 2008 R2 Build appear on the net..
I hope MS can make RTM avaliable to MVPs and Partner earlier so that we can test and give report on it.
As too many students asking me for the licensing information on WIndows Server 2008, I suggest all of you to take a look at the following link first:
Sites regarding Windows Server 2008 licensing.
For licensing questions, I suggest contacting Microsoft Licensing Center for detailed explanation.
For licensing questions, please call 1-800-426-9400 (select option 4), Monday through Friday, 6:00 A.M. to 5:30 P.M. (PST) to speak directly to a Microsoft licensing specialist.
Worldwide customers can use the Guide to Worldwide Microsoft Licensing Sites http://www.microsoft.com/licensing/index/worldwide.asp to find contact information in their locations.
If you select “Respond to all (known and unknown) client computers”, and check the box “For unknown clients, notify administrator and respond after approval”, the result is:
When PXE booting a client, it will wait for you to approve it. Click Pending Devices in the WDS console, right-click the pending devices in the right pane and click Approve. The client computer continues with the network boot operation and a computer account object is created in AD DS to represent the physical device. Press F12 on the client and boot into a boot image. Before loading install images, you will be prompted to enter a domain user account name and password. This domain user account does not need to belong to a domain administrator groups.
Configuring When DHCP is on the Same Server
The method of communication between the booting client and the server uses data fields (known as options) in DHCP packets. The Windows Deployment Services solution for booting over the network works well in many configurations. It works well when Windows Deployment Services is located on the same physical computer or on a different physical computer than the DHCP server. However, the default installation is that Windows Deployment Services and a DCHP server (Microsoft or non-Microsoft) are located on different physical computers. In this scenario, no additional configuration steps are required for interoperability between Windows Deployment Services and the DHCP server.
However, if you are running Windows Deployment Services and DHCP on the same computer, in addition to configuring the server to not listen on port 67, you will need to use your DHCP tools to add Option 60 to their DHCP scopes. This allows booting clients to learn about the Windows Deployment Services PXE server from the DHCP response that is generated by the DHCP server. Setting DHCP option tag 60 has one side effect: clients booting from the network are always notified that the Windows Deployment Services PXE server is available, even if the server is not operational or has stopped. For instructions on configuring these options, see the DHCP section of How to Manage Your Server.
There are some scenarios (particularly those that require running a DHCP server) that do not support adding custom DHCP option 60 on the same physical computer as the Windows Deployment Services server. In these circumstances, it is possible to configure the server to bind to UDP Port 67 in non-exclusive mode by passing the SO_REUSEADDR option. For more information, see Using SO_REUSEADDR and SO_EXCLUSIVEADDRUSE (http://go.microsoft.com/fwlink/?LinkId=82387).
If DHCP is installed on a server that is located in a different subnet, then you will need to do one of the following configure your IP Helper tables (recommended) or add DHCP options 66 and 67. For more information, see Managing Network Boot Programs.
And here are some procedures:
To configure Windows Deployment Services to run on the same computer as Microsoft DHCP
- Right-click the server and click Properties.
- On the DHCP tab, select Do not listen on port 67 and Configure DHCP Option #60 Tag to PXEClient.
This procedure does the following:
- Sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Parameters\UseDhcpPorts to 0.
- Adds the option 60 PXEClient tag to all of your DHCP scopes.
To configure Windows Deployment Services to run on the same computer as non-Microsoft DHCP
- Right-click the server and click Properties.
- On the DHCP tab, select the Do not listen on port 67.
- Use your DHCP server tools to set Option #60 Tag to PXEClient.
This procedure sets HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Parameters\UseDhcpPorts to 0.
WDS in Windows Server 2003:
WDS in Windows Server 2008
You can download this content at http://go.microsoft.com/fwlink/?LinkId=89381, or you can browse it using the following links:
An image group is a collection of .wim files that share common file resources and security. Servicing an image within an image group (such as applying a hotfix or a service pack or updating files) requires exclusive access to the entire image group. File resources are shared across the image group (single-instanced) even though the metadata of each image resides in a separate physical .wim file. Image groups contain two file types:
l Res.rwm. Contains the file streams for images as defined in Install.wim, Install2.wim, and WinXP.wim. Note that each image group has its own Res.rwm file.
l Install.wim. Contains image metadata that describes the content of an operating system image. The actual file resources for the image reside in Res.rwm.
Each image group will have a Res.rwm file created when the first image is added to the image group. All resources for all files reside in Res.rwm. The Res.rwm file is a .wim file that is renamed to differentiate the resource-only .wim file from the metadata .wim files and to speed up image enumeration. Because image enumeration only works on .wim files, the Res.rwm file will be skipped.
The .wim file format uses single-instancing technology, so the disk storage requirements for images within an image group are significantly reduced.
Just saw a soluton on installation problem when installing WIndows Server 2008 on Dell Poweeedge machine:
When you find the installation process stop and display the following error:
"windows could not update the computer's boot configuration"
First, if your Installation and Maintenance DVD isn't version 5.4, get that ISO and make your new DVD.
Second, when you use that disk to prepare your array for Windows 2008, do not install a utility partition!
Third, the installation that the disk does left you with a splash screen and it never moved beyond that, so I hit F11 on bootup and chose to boot from the Windows 2008 DVD.
Fourth, please also check the BIOS settings and see if the boot hard disk has been set to the proper hard disk. Besides, you can try turning off all the boot devices from the BIOS except for the CD/DVD and the hard drive and see how it goes. It is reported that similar issues may occur when some boot devices interfere the installation.