16 septembre 2009
The fix for installation of Exchange 2007 SP2 with Windows 2008 R2 Domain Controllers is now available.
We have released the updated Setup prerequisite files for the problem we wrote about in Exchange 2007 SP2 Setup fails if all domain controllers are running Windows Server 2008 R2. This fix will unblock Exchange 2007 SP2 setup in those environments.
Installation on non-Internet connected computers
Using an Internet connected computer:
1. Download and extract Exchange 2007 SP2 to a local hard drive.
2. Download the updated ExBPA.PreReqs.xml and ExBPA.Readiness.xml files listed below. Please note: We suggest that you right-click the link and select "Save target as..." as otherwise the XML file might open in your browser window:
- English
- Chinese - Simplified
- Chinese - Traditional
- German
- French
- Italian
- Korean
- Japanese
- Portuguese
- Russian
3. Save the files to your local hard drive.
Note: Do not make any modifications to downloaded xml files. Modifying those files will result in Setup failure.
4. Locate ExBPA.PreReqs.xml and ExBPA.Readiness.Xml files which were extracted from the Exchange 2007 SP2 download. The default location is "Setup\ServerRoles\Common\<language>". Rename original XML files to something else or save them to a different location.
5. Place the ExBPA.PreReqs.xml and ExBPA.Readiness.Xml files which you downloaded into the place of original xml files.
6. Copy the Exchange 2007 SP2 setup files that you have modified to the non-Internet connected Exchange Server which you are trying to upgrade to Exchange 2007 SP2.
7. Run Setup on the non-Internet connected computer by using the files you copied as per above.
If you are installing Exchange 2007 SP2 from the DVD media
1. Copy the Setup files to the local hard drive. This step is necessary, because if Setup is run from a DVD, it will not check for updated XML files. This applies to both Internet and non-Internet connected computers.
2. Follow the applicable directions from above, depending on if the computer is connected to the Internet or not.
Once the new XML files are in the right place, Exchange 2007 SP2 setup should pass the prerequisite check phase if there are only Windows 2008 R2 domain controllers in the environment.
http://msexchangeteam.com/archive/2009/09/15/452494.aspx
Nouvelles e-demos : 1er pas avec Windows Server 2008 R2
Voici enfin les premières e-demos "1er pas avec Windows Server 2008 R2", série de e-démos destinées à montrer comment monter une infrastructure Windows Server 2008 R2 de test.
Premiers pas avec Windows Server 2008 R2 : Promotion du 1er controleur de domaine Active Directory
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=04dabde5-652b-430c-a3cb-65791cd1e11a
Premiers pas avec Windows Server 2008 R2 : Installation d'une CA d'entreprise avec Windows Server 2008 R2
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=a276f92d-51f6-492f-84b3-ed5910746194
Premiers pas avec Windows Server 2008 R2 : Configuration DirectAccess - partie 1 - Les certificats
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=3a3e0a19-0bfa-409e-a57e-06f06f5c4271
Premiers pas avec Windows Server 2008 R2 : Configuration DirectAccess - partie 2 - GPO Parefeu Windows
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=b032fc09-7994-411e-b403-26d4531c971c
Premiers pas avec Windows Server 2008 R2 : Configuration DirectAccess - partie 3 - configuration DNS interne et externe
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=c14c9118-6935-4341-b33e-37082f6ab40b
Premiers pas avec Windows Server 2008 R2 : Configuration DirectAccess - partie 4 - Configuration du NLS
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=a152d6bb-5f44-4e44-a0ed-f6f860575fac
Premiers pas avec Windows Server 2008 R2 : Configuration DirectAccess - partie 5 - Configuration des prérequis du serveur DirectAccess
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=8c37bc43-3b6d-4592-9520-3dbdb1de3a8d
Premiers pas avec Windows Server 2008 R2 : Configuration DirectAccess - partie 6 - Assistant de configuration du serveur DirectAccess
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=47fc2bb9-8627-4da1-80f9-5f4e0ab86d2b
Premiers pas avec Windows Server 2008 R2 : Configuration d'une passerelle VPN sur Windows Server 2008 R2
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=47e23c50-f3fd-4483-953e-3954c10c87ee
Premiers pas avec Windows Server 2008 R2 : Installation des RSAT sur Windows 7
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=8869001d-a4bd-48f5-b62a-f4ce2c318166
Premiers pas avec Windows Server 2008 R2 : Windows 7 BitLocker to Go - partie 1
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=5f54df46-23f4-4279-835b-8f788f836d8f
Premiers pas avec Windows Server 2008 R2 : Windows 7 BitLocker to Go - partie 2
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=23b1100a-791a-429f-b237-a8ba33cdef74
Premiers pas avec Windows Server 2008 R2 : Windows 7 BitLocker to Go - partie 3
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=d0c641f2-e89e-461a-a065-5f40d4042280
Premiers pas avec Windows Server 2008 R2 : NAP DHCP avec Windows Server 2008 R2 - partie 1
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=6b954fc6-11a3-43e2-ba5d-12266fc9fab0
Premiers pas avec Windows Server 2008 R2 : NAP DHCP avec Windows Server 2008 R2 - partie 2
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=55a7a353-8929-496f-81ac-35a04e3de9ac
Premiers pas avec Windows Server 2008 R2 : Restriction de l'usage des applications avec AppLocker
http://www.microsoft.com/france/vision/WebcastTechnet.aspx?eid=c5efb796-0520-41a1-bd8b-a7fe01a63b77
Bon visionnage !!
Plus d’informations sur Windows 7 et Windows Server 2008 R2 sur le blog dédié : http://blogs.technet.com/windows7
Windows Server 2008 R2 et la virtualisation : mode de licence
Un sujet compliqué mais après la lecture de ce document tout sera enfin plus clair :)
10 septembre 2009
Microsoft® Deployment Toolkit (MDT) 2010 est disponible
Réussissez votre déploiement vers Windows 7 et Windows Server 2008 R2 !!
Deploy Windows 7 and Windows Server 2008 R2 with the newly released Microsoft Deployment Toolkit 2010. MDT is the recommended process and toolset for automating desktop and server deployment. MDT provides you with the following benefits:
- Unified tools and processes required for desktop and server deployment in a common deployment console and collection of guidance.
- Reduced deployment time and standardized desktop and server images, along with improved security and ongoing configuration management.
- Fully automated Zero Touch Installation deployments by leveraging System Center Configuration Manager 2007 Service Pack 2 Release Candidate and Windows deployment tools. For those without a System Center Configuration Manager 2007 infrastructure, MDT leverages Windows deployment tools for Lite Touch Installation deployments.
What’s New in MDT 2010
Improvements to the newest version of MDT allow you to:
- Access deployment shares from anywhere on the network and replicate files and settings across organizational boundaries or sites.
- Organize and manage drivers, operating systems, applications, packages, and task sequences with an improved UI.
- Automate UI functionality using the Windows PowerShell command line interface.
Plus d’informations sur MDT : www.microsoft.com/mdt
03 août 2009
Nouveauté importante de Windows Server 2008 R2 Core : SCONFIG
Server Core est une avancée importante apparue avec Windows Server 2008.
![image9_thumb[1]](http://blogs.technet.com/blogfiles/windows7/WindowsLiveWriter/NouveautimportantedeWindowsServer2008R2C_F480/image9_thumb%5B1%5D_2.png "image9_thumb[1]")
Les gains sont maintenant bien connus :
- surface d’attaque réduite,
- réduction des mises à jours et des redémarrages pour les appliquer
Cependant la configuration de Server Core n’était pas toujours simple puisqu’il faut (ré)apprendre toutes les commandes sous forme de lignes de commandes :
- Changement du nom de l’ordinateur : netdom renamecomputer %computername% /newname:<new_computername>
- Rejoindre un domaine: netdom join %computername% /domain:<domain> /userd:<username> /passwordd:*
Des solutions complémentaires existent. Voir notamment :
- Outil de configuration pour Windows Server 2008 Core
ou - Script de configuration Hyper-V Server in depth : hvconfig
Mais avec Windows Server 2008 R2 c’est une solution complètement intégré à Windows qui apparait : SCONFIG
Et cerise sur le gâteau, l’outil est traduit en 20 langues !
Il permet notamment de :
1°) Rejoindre un domaine
2°) Changer le nom de l’ordinateur
3°) Configurer Windows Update
4°) Configurer les accès distants (notamment pour PowerShell V2 !)
5°) Configurer le bureau distant
6°) Configurer le réseau
Ca ressemble à ca :
![clip_image001_thumb[1]](http://blogs.technet.com/blogfiles/windows7/WindowsLiveWriter/NouveautimportantedeWindowsServer2008R2C_F480/clip_image001_thumb%5B1%5D_2.jpg "clip_image001_thumb[1]")
![clip_image002_thumb[1]](http://blogs.technet.com/blogfiles/windows7/WindowsLiveWriter/NouveautimportantedeWindowsServer2008R2C_F480/clip_image002_thumb%5B1%5D_2.jpg "clip_image002_thumb[1]")
Pour de plus amples détails sur cet outil vous pouvez allez sur cet article :http://blogs.technet.com/virtualization/archive/2009/07/07/windows-server-2008-r2-core-introducing-sconfig.aspx 
30 juillet 2009
Microsoft Days Automne 2009 !
Tous les détails sont ici :
http://technet.microsoft.com/fr-fr/microsoft-days.aspx 
http://blogs.technet.com/windows7/archive/2009/07/29/microsoft-days-automne-2009.aspx
27 juillet 2009
GPL Hyper-V Paravirtualized Drivers and Industry Next Steps
Yesterday Microsoft announced what I believe was a brilliant move – Hyper-V paravirtualized drivers (Microsoft calls them Integration Components) released under GPL 2.0. This announcement reflects Microsoft’s long term Linux strategy, in my opinion, and is the first step toward positioning Hyper-V as a platform for hosting Linux workloads. Getting Hyper-V paravirtualized device drivers in the mainline Linux kernel will simplify deployment of Linux-based VMs on the Hyper-V platform in coming years. In the short term, it’s important for Microsoft’s key partners (Novell and Red Hat) to backport the paravirtualilzed drivers so that their currently shipping Linux distros will run more efficiently on Hyper-V. Given Microsoft’s close partnerships with Novell and Red Hat, I see SUSE Linux Enterprise Server 10/11 and Red Hat Enterprise Linux 5 support as foregone conclusions.
With this move, I think that Microsoft has acknowledged that Linux is here to stay, and has provided additional momentum to the growing number of Linux-based VM appliances. A growth in Linux-based VM appliances benefits everyone, including the Linux community and VMware (who hosts the Virtual Appliance Marketplace). Microsoft still has more work to do on this Linux front. Open sourcing Hyper-V paravirtualized drivers was a great first step. Next up, I would like to see Microsoft support Linux VMs with multiple virtual CPUs on Hyper-V. This opens the door for Microsoft to tout Hyper-V as a platform for production-class Linux workloads.
To take this a step further, let’s turn back the clock to October 2008. At Catalyst Europe, I asked Steve Herrod and Ian Pratt about VMware and Citrix collaborating on an exchange of device driver libraries to further reduce VM compatibility issues between hypervisors, and both agreed to continue the conversation (more details here). Citrix XenServer and Microsoft Hyper-V share device driver libraries and include the driver libraries for each platform as part of their paravirtualized driver installation (i.e., XenServer Tools and Hyper-V Integration Components). With Microsoft releasing Hyper-V paravirtualized Linux drivers, I think it’s a good time to revisit the idea of an open source driver framework that supports the core paravirtualized driver libraries of each major hypervisor platform (ESX, Xen, Hyper-V, and KVM). Sure, we’ll need a community/standards body (or whatever you want to call it) to manage driver library updates, but I can’t see why it isn’t possible. Such collaboration would make life easier for everyone. Imagine being able to run a few tests on one of your VMs “in the cloud,” and not having to care what the hypervisor is. Isn’t that what cloud’s supposed to be about anyway? Here’s my service level and security requirements. Can you give me the service I need?
Yes I understand that my cloud analogy is overly simplistic and there will always be some benefits to having a consistent virtual infrastructure both internally and with external providers. Still there are times when such consistency isn’t needed, and that’s why shared driver libraries make a lot of sense (besides removing another barrier to vendor lock-in). VM configuration metadata is addressed with Open Virtualization Format (OVF). From a technology perspective, nothing is preventing collaboration on a common VM device driver framework and shared driver libraries (that is something I’d love to see in the mainline Linux kernel). And finally, hypervisor vendor support for both .vmdk and .vhd virtual hard disk formats is the last major hurdle blocking VM compatibility (without the necessary conversions) between hypervisors. Vendors – let’s not talk about cloud openness, open architectures, etc. Let’s do something about it. Microsoft made a great move yesterday. Next I’d like to see collaboration between all virtualization vendors that further promotes choice among users, IT departments, and service providers. VMware, Microsoft, Citrix, Novell, Red Hat, Oracle – what do you say?
http://www.chriswolf.com/?p=394
Windows Server 2008 R2 & Hyper-V Server 2008 R2 RTM!!!!
Virtualization Nation,
Today is a really big day at Microsoft and more importantly for our customers. Both Windows Server 2008 R2 and Microsoft Hyper-V Server 2008 R2 (our FREE standalone Hyper-V Server) have both been Released To Manufacturing (RTM)!! If you haven't seen the announcement on the main Windows Server blog, be sure to check it out. In this blog, I'm going to focus on the Windows Server 2008 R2 Hyper-V release, I will follow-up with a blog on the standalone Microsoft Hyper-V Server 2008 R2 soon.
These R2 releases continue to highlight one of our core goals for Hyper-V. Simply:
We believe everyone should have access to high performance hypervisor based virtualization. Period.
Virtualization shouldn't only be available to the largest enterprises with the largest budgets and we're delivering on that goal. We're pleased and humbled to announce that in the first 12 months of Hyper-V R1 availability with Windows Server 2008, there have been over 1+ million downloads of Hyper-V R1 Gold (RTM) software, making Hyper-V the fastest growing bare metal hypervisor in x86 history.
To our customers: Our deepest and sincerest thanks. We appreciate your support and are pleased to present Hyper-V R2 based on your input.
--> The rest of the announcement on :
R2 Veeam Too
Hello, I’m Doug Hazelman and I’m the director of the Global Systems Engineers Group at Veeam Software. I’ve been with Veeam for almost two years, and prior to that I was with Aelita Software (which was acquired by Quest Software) where I worked with the same management team now behind Veeam Software. I’d like to thank Microsoft for this opportunity to guest blog on Veeam’s direction around Hyper-V.
Veeam’s tagline is “listening to you, building the tools you need.” We’ve heard your requests and we’d like to announce now that Veeam is committed to fully supporting Microsoft Windows Server 2008 R2 Hyper-V and Microsoft Hyper-V Server 2008 R2. While Veeam has continued to build some of the best software for data protection and management of VMware infrastructures, we realize that customers are now faced with more virtualization choices. By fully supporting Microsoft Hyper-V and VMware vSphere, Veeam can help you manage heterogeneous hypervisor deployments and clouds with the innovative solutions you’ve come to expect from Veeam. The management and R&D teams at Veeam have a long history of working with Microsoft going back to the Aelita days, and we’re all excited to be working with Microsoft again.
The Veeam engineers are currently focusing a lot of time and energy on how we can provide the best support for Hyper-V. Look for more information in the coming weeks as we disclose more about Veeam’s plans for Hyper-V. And congratulations to Microsoft for releasing R2.
Thanks,
-doug
Blog: http://www.VeeamMeUp.com
Twitter: @VMDoug or @Veeam
http://blogs.technet.com/virtualization/archive/2009/07/23/r2-veeam-too.aspx
23 juillet 2009
Windows 7 Has Been Released to Manufacturing
I am pleased to announce that Windows 7 has RTM’d!
As I mentioned previously, RTM officially happens only after sign-off occurs. What happens is a build gets designated as a RTM contender after going through significant testing and meeting our quality bar for RTM. Then, it goes though all the validation checks required for RTM including having all languages of that build completed. If all the validation checks have passed – sign-off for RTM can occur. Today after all the validation checks were met, we signed off and declared build 7600 as RTM.
Not only is RTM an important milestone for us – it’s also an important milestone for our partners. Today’s release is the result of hard work and collaboration with our partners in the industry to make Windows 7 a success. We delivered Windows 7 with a predictable feature set on a predictable timetable that allowed OEMs to focus on value and differentiation for their customers.
Our customers told us what they want (and expect) and we defined those specific experiences and then built features to support them (like HomeGroup and the Windows Taskbar enhancements). Our customers also told us that “fundamentals” on both the hardware and software side was extremely important. Windows 7 today runs great on the broadest array of hardware types ranging from netbooks to high-end gaming machines. We worked closely with OEMs so that their PCs delight customers with the new features in Windows 7.
Of course, today’s release is also the result of the amazing amount of feedback we received from the millions of people who tested Windows 7 – from Beta to RC. We actually had over 10 million people opt-in to the Customer Experience Improvement Program (CEIP). That’s a lot of people opting in to help us make Windows 7 a solid release. Through CEIP, our engineers were guided by customer feedback all the way to RTM. We also have had a great group of beta testers who have dedicated a great deal of their time to testing Windows 7 too. A special thank you goes out to all the people who helped test Windows 7.
I’d also like to give a shout-out to my friends over on the Windows Server Team. Today they are also announcing that Windows Server 2008 R2 has RTM’d. Windows 7 and Windows Server 2008 R2 together can help businesses cut costs and increase productivity. Click here to read their blog post on Windows Server 2008 R2 RTM.
The RTM code will be delivered to our partners within the next few days who will then start preparing to deliver some amazing new products timed to hit at General Availability (GA) of Windows 7 on October 22nd. And going forward, I expect to be showcasing MANY of these new products here on The Windows Blog.
We continue to be overwhelmed at the community’s response to Windows 7 and it has been an extremely rewarding experience to witness. We hope the enthusiasm will continue to grow even more as our partners build amazing experiences with their products and Windows 7.
If you want to know when you’ll be able to get RTM of Windows 7, click here to read my post from yesterday outlining which audiences will get access to the RTM bits
PS : RTM Full Build String is :
"6.1.7600.16385.090713-1255," which indicates that the final build was compiled over a week ago: July 13, 2009, at 12:55pm.