Yesterday saw the release to TechNet and MSDN – Office 2010 Professional Plus.
After downloading the 650MB file, I attempted to install Office 2010 in a way I have done many times before.
I right clicked the file (en_office_professional_plus_2010_x86_515486.exe) and extracted the contents to a folder and ran Setup.exe and it failed with this error message. “The language of this installation package is not supported by your system.”
After several WTF’s and then some more, I tried a different approach – I installed directly from the downloaded file – by double clicking en_office_professional_plus_2010_x86_515486.exe and this time it installed correctly.
So is this expected behaviour or is there something odd about my setup?
All settings are English and UK.
Clean Windows 7 Ultimate 64bit.
Both Office 2010 64bit beta’s at some point had been on the PC but were cleanly removed.
The reason I was getting this error was due to the method I had used in extracting the data from the file en_office_professional_plus_2010_x86_515486.exe
I had used Winzip, by right clicking the file and selecting Extract to D:\Office
The correct way for extacting the data was to extract using the command line. The syntax being
The switch /extract:D:\Office extracts the files contents to D:\Office on my PC, but could be any location.
The other interesting this was that when extracted with WinZip the contects looked like this when extracted
and like this with the native toolset.
On ActiveDir.org a couple of weeks ago, there was a discussion around the fact that Microsoft now have hardcoded LDAP limits for Active Directory. This may not directly affect you in a Windows 2003 forest – but if you have changed your LDAP Policies to make a poorly written application work in Windows Server 2003 then in Windows Server 2008 and 2008 R2 rather than modify Active Directory – you may have to modify the application – which might not be that simple.
Hardcoded LDAP limitations have been introduced in Windows Server 2008 R2 and Windows Server 2008 to prevent overloading the domain controller. These limits overwrite the LDAP policy setting when the policy value should be higher.
|LDAP setting hardcoded)
||Maximum value (hardcoded)
Full KB Article:
Windows Server 2008 R2 or Windows Server 2008 domain controller returns only 5000 attributes in a LDAP response
Earlier today details emerged around the features of Exchange 2010 Service Pack 1.
“Service Pack 1 will include fixes and tweaks in areas you’ve helped us identify, including a roll-up of the roll-ups we’ve released to date. I also wanted to flag some of the feature enhancements we’re excited to bring to you with Service Pack 1 including: archiving and discovery enhancements, Outlook Web App (OWA) improvements, mobile user and management improvements, and some highly sought after additional UI for management tasks.”
Full Details: http://msexchangeteam.com/archive/2010/04/07/454533.aspx
Active Directory environments configured to use Network Address Translation (NAT) appear to be a support scenario with multiple configurations some supported and some unsupported. Detailed below is the information I have collated so far.
Active Directory over NAT – KB 978772
The Microsoft statement regarding Active Directory over NAT is:
Active Directory over NAT has not been tested by Microsoft.
We do not recommend Active Directory over NAT.
Support for issues related to Active Directory over NAT will be very limited and will reach the bounds of commercially reasonable efforts very quickly.
If you are tasked with configuring a network with NAT and you plan to run any Microsoft Server solution (including Active Directory) across the NAT, please contact Microsoft customer technical support using your preferred approach.
Description of support boundaries for Active Directory over NAT
Tim Springston – DCs and Network Address Translation
Microsoft Online Dedicated Service Descriptions and Service Level Agreements
Microsoft Online Services does not support the implementation of network address translation (NAT) technology between the customer and Microsoft domain controllers. Implementing NAT systems requires a highly specific configuration that is dependent on the networking products used. Even if successfully deployed, NAT systems and devices pose operational risks. They require that customers change their NAT configuration when Microsoft modifies its domain controller deployments. Without NAT reconfiguration, Microsoft authentication to the Customer Forest can fail.
Download the agreements
I picked up on this little bit of information over the weekend, I have never come across the Itanium architecture in a production environment; but somebody somewhere uses it and will be impacted.
Windows Server 2008 R2 will be the last version of Windows Server to support the Intel Itanium architecture. SQL Server 2008 R2 and Visual Studio 2010 are also the last versions to support Itanium.
Full story is at the Windows Server Division WebLog
If you are looking connect with fellow Active Directory administrators, architects or perhaps the people that design the product, then I would strongly urge you to check out Tony Murray’s ActiveDir.org mailing list.
The list which started back in January 2001 provides a forum for discussing various aspects of Microsoft’s Active Directory technology.
Tony Murray has provided a little more insight into the excellent ActiveDir.org
“I had the idea to launch ActiveDir.org based on the mailing-list discussion forums I was participating in; for example, there were some great Exchange mailing lists where the contributions from Microsoft employees, MVPs and other gurus were invaluable. At the time (January 2001), Windows 2000 was getting into its stride but there didn’t appear to be a good mailing list forum for Active Directory. Seeing a gap in the market, as it were, I launched the site purely as a vehicle for the mailing list. Exchange MVP Martin Tuip provided a lot of early help and publicity. Some time later a friend and work colleague (Matty Holland) helped me rebuild the site using DotNetNuke.
Matty and I now run the site together. The idea behind the move to DotNetNuke was to allow subscribers to write AD-related articles for the community and to post them on the site. The article idea has been slow in attracting support – largely due I think to the recent explosion in personal blogging. The mailing list remains the focus of ActiveDir.org and the membership is now nearing the 2000 mark.
The list has been successful largely due to the low signal-to-noise ratio (a problem for many list-based forums). I’d like to say that this is because of the unique and skilful way in which I manage the list (ha ha) – but really it’s down the solid core of regulars who set the tone.”
The ActiveDir list features some of the foremost experts in the Active Directory arena; including Joe Richards, Laura Hunter, Brian Desmond and of course Tony himself. There are lots of silent members on the list too and don’t be surprised to get a reply from the product group or even Don Hacherl (Don was Lead Development Manager at Microsoft for Active Directory).
The list is free and if you can’t find the answer to your Active Directory issues via the list, then you probably have issues that can only be resolved with devine intervention.
A point to note is, the list does not like hotmail or live addresses at the moment, due to some issues on Microsoft’s part.
This year there are a few versions of Windows which will go out of support. If you continue to use these version of Windows beware; it is effectively be the same as driving a Ford Capri around town; it works, everyone of a certain age knows what it is, but good luck if it goes wrong.
Windows 2000 Professional and Windows 2000 Server were both launched over 10 years ago and both products regardless of service pack will go out of support on July 13th, 2010.
Windows XP with Service Pack 2 will go out of support on July 13th, 2010; but support for Windows XP with Service Pack 3 will continue. This means that from July 13th onwards, Microsoft will no longer support or provide free security updates for Windows XP with Service Pack 2.
To ensure you still receive security updates, Windows XP should be upgraded to Windows XP Service Pack 3; this is available for free via the Windows Update website or from http://www.microsoft.com/downloads/details.aspx?FamilyID=68C48DAD-BC34-40BE-8D85-6BB4F56F5110&displaylang=en
Windows Vista with no Service Packs installed will go out of support on April 13th 2010.
To ensure you still receive security updates,Windows Vista should be upgraded to Windows Vista Service Pack 2; this is available for free via the Windows Update website or from: http://www.microsoft.com/windows/windows-vista/default.aspx
For more information and for further clarity, I recommend checking out: