Win 7 upgrade paths
Archive for July, 2009
Win 7 upgrade paths
AD LDS proxy authentication
The most import parts of the wall of text in the post is the following…
For Partners & OEMs:
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.
There is already a lot of momentum from ISVs and IHVs in the ecosystem
today for Windows 7 as Mike Nash blogged last week.
If you are a partner who has been working on Windows 7 for a while, now
is the time to complete your testing with final version of Windows 7.
For partners that haven’t gotten started yet with Windows 7, now is the
time to get involved. You can also visit www.readyset7.com to learn more about getting ready for Windows 7.
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.
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. This will allow them to begin preparing
images for new PCs to ship with Windows 7 on them. We know our OEMs are
excited for Windows 7 and we can’t wait to hand them the final RTM bits!
For Business Customers:
If you are a 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
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. Mark these dates on
your calendar and start making your deployment plans!
For IT Professionals:
are a few ways you can get Windows 7 RTM. IT Professionals with TechNet
Subscriptions will be able to download Windows 7 RTM in English on
August 6th and remaining languages by October 1st.
IT Professionals at companies with Volume Licensing see above on how you can get Windows 7 RTM.
have quite a bit of resources for IT Professionals to use to become
experts on Windows 7 and to aid in their deployments. Those resources
can be found at the Springboard Series.
with MSDN Subscriptions will be able to download Windows 7 RTM in
English on August 6th and remaining languages by October 1st.
help developers who are developing applications for Windows 7 or
updating existing applications to take advantage of new Windows 7
features, check out the Windows 7 for Developers Blog. Also, be sure to check out the Windows 7 Developers Guide on MSDN. Oh and there are also some fantastic videos on Channe
I know there have been some rumors going around about a
“family pack” for Windows 7. We have heard a lot of feedback from beta
testers and enthusiasts over the last 3 years that we need a better
solution for homes with multiple PCs. I’m happy to confirm that we will
indeed be offering a family pack of Windows 7 Home Premium (in select
markets) which will allow installation on up to 3 PCs. As I’ve said
before, stay tuned to our blog for more information on this and any
other potential offers.
Beta testers will not automatically
receive a free copy of Windows 7. Many beta testers are already
subscribers to TechNet; those of you who fit that description will be
able to download Windows 7 RTM shortly after RTM happens for free as
part of your subscription.
taken from here…
Link-local addresses and zone indices
All interfaces have an associated link-local address, that is only guaranteed to be unique on the attached link. Link local addresses are defined by the address prefix fe80::/10, with the only allocated subnet (54 bits) being zero, such that a standards-based link-local address has an effective format fe80::/64. The least significant 64 bits are usually chosen as the interface hardware address constructed in modified EUI-64 format.
Because all link-local addresses in a host have a common prefix,
normal routing procedures cannot be used to choose the outgoing
interface when sending packets to a link-local destination. A special
identifier, known as a zone index, is needed to provide the
additional routing information; in the case of link-local addresses,
zone indices correspond to interface identifiers.
When an address is written textually, the zone index is appended to the address, separated by a percent sign "%". The actual syntax of zone indices depends on the operating system:
- the Microsoft Windows IPv6 stack uses numeric zone indexes, e.g., fe80::3%1. The index is determined by the interface number.
- Some Unix-like systems (e.g., BSD and Linux) use the interface name as a zone index: fe80::3%eth0.
- Mac OS X (10.5.7) also uses the interface name (e.g. en0) as a zone index: fe80::3%en0.
Relatively few IPv6-capable applications
understand address scope syntax at the user level, thus rendering
link-local addressing inappropriate for many user applications.
However, link-local addresses are not intended for most of such
application usage and their primary benefit is in low-level network
management functions, for example for logging into a router that for some reason has become unreachable.
One my studnets John tipped me off to something that could really help. He reported a significant improvement after adjusting these settings. NOTE – this is a reg hack. I always recommend exporting your current keys for restore purposes, just in case. EVEN if the steps are provided from Microsoft…
WDS getting started guide – provided by TechNet
As taken from here.. MSExchangeTeam.com
We have released Update Rollup 9 for Exchange Server 2007 Service
Pack 1 (KB 970162) to the download center. The release of the rollup
via Microsoft Update will happen on July 28.
The majority of changes in this rollup are bug fixes. Here are a few that I would like to call out:
- KB 969911 – This is bug likely to affect customers who have deployed the Messaging Records Management
feature and have specified a storage limit for a managed folder. After
a move mailbox, the property which marks the folders as managed is not
- KB 968621 – Store stops responding under certain conditions when scheduled backup is canceled and online maintenance is in progress.
- KB 945877 – Performance improvements to eseutil when it verifies the checksum of transaction logs.
- Support for Windows Server 2008 R2 Domain Controllers in the
environment (Note: Exchange Server 2007 itself is not supported to be
installed on a Windows Server 2008 R2 system.
- KB 968715 – This bug is likely to affect customers who have deployed CAS-CAS proxying. When a user selects This is a public or shared computer or This is a private computer
on the Outlook Web Access logon page, this value is not maintained
between the CAS servers when the request is proxied. This bug will most
likely affect customers with Internet facing CAS sites which proxy the
requests to internal sites. Now the bug was that we defaulted to
private access irrespective of the option selected by the user. Outlook
Web Access has the following features which allow the administrator to
control access of users depending on the logon type.:
Public and Private Computer File Access
WebReady Document Viewing