30 septembre 2009
Téléchargez et testez la première Beta de Data Protection Manager 2010 (DPM)
Quand on vous disait hier, que System Center 2010 arrive à grand pas, on ne vous mentait pas. Après System Center Essentials 2010 (solution tout en un destiné aux PME), voici son collègue côté sauvegarde à savoir Data Protection Manager 2010 ! Cette troisième génération (après 2006 & 2007), apporte énormément de nouveautés et offre une véritable solution complète de sauvegarde et restauration pour tous vos environnements : Hyper-V / SharePoint / Exchange / SQL et également Active Directory ainsi que vos postes de travail (XP, Vista, Seven).
Pour rappel, voici la liste des nouveautés qui avait été annoncé avant l’été. Il semblerait que tout ne soit pas intégré dans cette première Beta et il se peut que des changements soient encore opérés dans les builds à venir.
La Beta 1 est accompagné d’une dizaine de documents Word assez complet pour vous aider à prendre en main l’outil dans les différents scénarios d’utilisation. Alors profitez en et n’hésitez pas à laisser vos impressions et/ou remarques sur le produit.
Microsoft Security Essentials est disponible en téléchargement sur microsoft.com !!
ça y est Microsoft Security Essentials, l’antivirus gratuit pour la maison est disponible en téléchargement à l’adresse suivante :
http://www.microsoft.com/security_essentials/
Il est compatible Windows XP, Windows Vista et Windows 7
J'adore Exchange 2010 !!!
Ce soir, ma boite aux lettres de production vient d'être migrée vers Exchange 2010 !
A moi tous les bénéfices de l'interface Outlook Web App et l'intégration des SMS dans ma boites et le Personnal Auto Attendant …
Tout cela, c'est génial, mais le mieux, c'est :
Venez aux Microsoft Days, on vous expliquera comment c'est possible sans que ça vous coute un œil !
http://blogs.technet.com/dcaro/archive/2009/09/17/j-aodre-exchange-2010.aspx
How to fix: Hypervisor not running
This is a Hypervisor 101 case that keeps showing itself every so often the forums, mailing lists, etc: A message to the effect of “The Hypervisor is not running” when a user tries to launch a VM. Felipe Ayora, one of our awesome UA people, has created this video that steps through how to investigate such a failure and fix it
http://www.microsoft.com/video/en/us/details/25d07f2e-b2e0-4c0c-b456-79b08bfe58be
http://blogs.technet.com/virtualization/archive/2009/09/29/how-to-fix-hypervisor-not-running.aspx
Single Item Recovery in Exchange Server 2010
Users often delete data from their mailboxes that they later want recovered. Recovery of these deleted items is the most common reason for IT admins to recover data from traditional point-in-time backups today.
With previous versions of Exchange Server, administrators implemented two solutions to enable single item recovery, dumpster and restores. Both had their issues, unfortunately.
Exchange 2010 aims to reduce the complexity and administrative costs associated with single item recovery.
Terminology
The following definitions may be useful for understanding the content within this article:
- Store Soft Delete - this is when an item has been deleted from the Deleted Items folder and placed within dumpster.
- Store Hard Delete - This is when an item has been marked for purging out of the store.
- Hard Delete via Outlook (Shift-Delete) - This is when the end user performs a shift-delete on an item. This results in the item bypassing the deleted items folder and being directly placed in dumpster.
Single Item Recovery in Previous Versions of Exchange
The end user single item recovery functionality was enabled through the store via the store dumpster. Administrators configured the dumpster setting on a per database or per mailbox basis. The default deleted item retention window in Exchange 2003 is 7 days, while with Exchange 2007 the default is 14 days.
The rest of it is there :
http://msexchangeteam.com/archive/2009/09/25/452632.aspx
17 septembre 2009
vSphere VI client sur Windows Seven / 7 !!!!
Je suis sous Windows Seven x64, et à mon grand regret je ne peux pas lancer le client vSphere VIClient, il me met à chaque fois une erreur... j'ai donc cherché et j'ai trouvé cet article :
http://communities.vmware.com/thread/211440
1. Obtain a copy of %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dll from a non Windows 7 machine that has .NET 3.5 SP1 installed.
2. Create a folder in the Windows 7 machine where the vSphere client is installed and copy the file from step 1 into this folder. For example, create the folder under the vSphere client launcher installation directory (+%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib+).
3. In the vSphere client launcher directory, open the VpxClient.exe.config file in a text editor and add a <runtime> element and a <developmentMode> element as shown below. Save the file.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
...
<runtime>
<developmentMode developerInstallation="true"/>
</runtime>
</configuration>
3. Create a batch file (e.g. *VpxClient.cmd*) in a suitable location. In this file add a command to set the DEVPATH environment variable to the folder where you copied the System.dll assembly in step 2 and a second command to launch the vSphere client. Save the file. For example,
SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
"%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"
4. (Optional) Replace the shortcut on the start menu to point to the batch file created in the previous step. Change the shortcut properties to run minimized so that the command window is not shown.
You can now use the VpxClient.cmd (or the shortcut) to launch the vSphere client in Windows 7.
Note that this workaround bypasses the normal .NET Framework loading mechanism so that assembly versions in the DEVPATH folder are no longer checked. Handle with care.
Fernando
J'ai testé, je confirme!
Si vous êtes en x64, remplacez %ProgramFiles% par %ProgramFiles(x86)% et hop!!!!
Netscaler (AGE inclus) VPX Express virtuel gratuit depuis hier – part I
Bonsoir Citrixiens et Citrixiens en herbe,
Citrix depuis hier a mis en téléchargement sur www.citrix.com, une version gratuite d’un Netscaler (incluant Access Gateway) virtuel limité à 1Mo de bande passante. Il vous faut juste avoir un compte mycitrix (enregistrement gratuit aussi).
Ce qui me permet de remplacer mon Citrix Secure Gateway sous Windows (gratuit) dans ma DMZ de démo par une version sous Linux 
(aussi gratuit).
Merci Citrix devrais dire
A bientôt,
Patrice Jacques-gustave
Many customers are not aware that now it’s better to deploy ESXi than ESX
ESXi 4 IS the Standard now:
I have to explain that on almost weekly basics to my customers and prospects, that, the ESXi 4 version of VMware is the version that they should adopt now as the ESX 4 version with the COS will disappear. The ESXi 4 version of VMware Hypervizor has all the features of ESX 4 and has thinner footprint. Then it only depends the licensing you purchase with the package. It starts for the SMB with VMware Essentials or VMware Essentials Plus.
Look at all the features availables in ESXi 4 version, FT, vMotion, DRS ... all is there..
Today I saw a new blogpost on VMware Blogs about the comparision and the features and the size of the ESXi 4 hypervizor. See here.
Then on the same blog earlier this year You can see the detailed info about the ESXi 4:
- The functionality and performance of VMware ESX and ESXi are the same; the difference between the two hypervisors resides in their packaging architecture and operational management. VMware ESXi is the latest hypervisor architecture from VMware. It has an ultra thin footprint with no reliance on a general-purpose OS, setting a new bar for security and reliability (learn more).
- In the future, ESXi’s superior architecture will be the exclusive focus of VMware’s development efforts.
New and existing customers are highly encouraged to deploy ESXi. Many Fortune 100 companies have already standardized on the ESXi platform.
So for me, I guess the best now is to deploy the COS-less versions of ESX …
The ESXi 4.
The rest on the blog :
http://www.vladan.fr/esxi-4-is-a-standard/
File Server Capacity Tool (FSCT) 1.0 available for download
Version 1.0 of the File Server Capacity Tool (FSCT) was announced yesterday during a presentation by Jian Yan and Bartosz Nyczkowski at SNIA’s Storage Developer Conference in Santa Clara, CA. The presentation covered a number of details about FSCT and included a demo running FSCT with the HomeFolders workload.
If you are not familiar with FSCT, the download page offers this overview: “File server capacity planning and performance troubleshooting are critical aspects of high-level network administration. Central file servers and distributed client workstations are now the norm in most corporate networks. This structure reduces storage capacity requirements, centralizes backup, increases the availability of files, and simplifies the document revision and review process. However, because data storage and access are centralized, performance limitations impact the entire network population. Accurately projecting the number of users that hardware can support under a specific workload, and understanding when and where bottlenecks occur, are critical to making efficient improvements to the server configuration. File server capacity planning tools can be valuable in choosing new hardware for purchase, identifying the capacity of existing hardware, locating existing bottlenecks, and planning for resource expansion in advance of resource exhaustion. The throughput capacity of a file server can be expressed either as the maximum number of operations per second or a maximum number of users supported by the configuration. These values are influenced by several factors, some of which include processor speed, available memory, disk speed, network throughput and latency, and the speed with which SMB requests are processed.”
The final version is available for download in both 32-bit (x86) and 64-bit (x64) versions. It is supported on Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista and Windows 7 (with the latest service pack applied).
Downloads are available now:
x64: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b20db7f1-15fd-40ae-9f3a-514968c65643
x86: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0b212272-1884-4af1-972d-42ef1db9f977
A white paper is also included in the download packages, with detailed description of the tool, step-by-step instructions on how to use it and reference of the command line interface.
For questions about FSCT and how to use it, please use the forum at
http://social.technet.microsoft.com/Forums/en-US/fsct/threads
Also check some details on FSCT on these previous posts (from the release of the beta last year and the release candidate back in July):
http://blogs.technet.com/josebda/archive/2009/07/08/file-server-capacity-tool-fsct-release-candidate-available-for-download.aspx
http://blogs.technet.com/josebda/archive/2008/10/06/fsct-a-cifs-smb-smb2-file-server-tool-for-capacity-planning-and-performance-troubleshooting.aspx
This is a major milestone in the two-year journey to offer this tool publicly, which included efforts from a number of people from different teams at Microsoft, including the File Server Team and the Windows Performance Team.
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.