E' passato un po' in sordina il fatto che è uscito il prodotto Hyper-V Server 2012 gratuitamente, segnalo il seguente articolo che permette di incominciare ad affrontare l'installazione
Live Migration! Configure and use Live Migration between non-clustered Hyper-V Server hosts (aka Live Migration Shared Nothing)
High Availability! Use Server Manager to remotely install the Failover Clustering feature and use the Failover Clustering Admin Tool to remotely configure your cluster.
Ovviamente anche in questo caso, se non abbiamo un dominio, dobbiamo utilizzare hvremote per poter gestire il server da Windows 7/8 client
Non è raro che un server Vmware ESX/ESXi 3.x/4.x/5.x rimanga senza corrente dopo un lungo blackout oppure vada in crash. Per evitare di intervenire dal cliente oppure che l'operazione del riavvio delle macchine virtuali debba essere fatta a mano è sufficiente seguire il seguente articolo ufficiale di Vmware per poter far in modo che il server avvii lui le macchine virtuali. Per Vmware 4.x/5.x:
Configuration tab.
Select Virtual Machine Startup / Shutdown under Software.
Click Properties in the upper right hand side of the window.
In order to be able to configure any options, enable Allow virtual machines to start and stop automatically with the system.
Per Vmware 3.x:
Log into the client and select an ESX host from the inventory.
Click the Configuration tab.
Under Virtual Machine Startup/Shutdown, configure your virtual machine startup options, as required.
This
security update resolves a privately reported vulnerability in
Microsoft System Center Configuration Manager. The vulnerability could
allow elevation of privilege if a user visits an affected website by way
of a specially crafted URL. An attacker would have no way to force
users to visit such a website. Instead, an attacker would have to
persuade users to visit the website, typically by getting them to click a
link in an email message or Instant Messenger message that takes users
to the attacker's website. This security update is rated Important
for all supported editions of Microsoft System Center Configuration
Manager. For more information, see the subsection, Affected and Non-Affected Software, in this section. The
security update addresses the vulnerability by modifying the way that
System Center Configuration Manager handles specially crafted requests.
For more information about the vulnerability, see the Frequently Asked
Questions (FAQ) subsection for the specific vulnerability entry under
the next section, Vulnerability Information. Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.
The Debug Diagnostic Tool (DebugDiag) is designed to assist in troubleshooting issues such as hangs, slow performance, memory leaks or fragmentation, and crashes in any user-mode process. The tool includes additional debugging scripts focused on Internet Information Services (IIS) applications, web data access components, COM+ and related Microsoft technologies. The Debug Diagnostic Tool (DebugDiag) is designed to assist in troubleshooting issues such as hangs, slow performance, memory leaks or memory fragmentation, and crashes in any user-mode process. The tool includes additional debugging scripts focused on Internet Information Services (IIS) applications, web data access components, COM+ and COM+ related Microsoft technologies, Sharepoint, and .NET framework.
DebugDiag 1.0 was released as part of the IIS Diagnostic Toolkit and as a standalone tool (x86 only).
DebugDiag 1.1 was released as a standalone tool only (x86 and limited x64 support).
DebugDiag 1.2 is currently available as a standalone tool only (x86 and full x64 support).
DebugDiag provides an extensible object model in the form of COM objects and provides a script host with a built-in reporting framework. It is composed of the following 3 components: a debugging service, a debugger host, and the user interface. The Debugging Service The debugger service (DbgSvc.exe) performs the following tasks: Attach/Detach the host to processes Collect performance monitor data Implement HTTP ping to detect hangs Inject leak monitor into running processes Collect debugging session state information Shows the state of each rule defined The Debugger Host The Debugger Host (DbgHost.exe) hosts the Windows Symbolic Debugger Engine (dbgeng.dll) to attach to processes and generate memory dumps. It also hosts the main analyzer module to analyze memory dumps. Dbghost.exe has no dependency on the service “DbgSvc.exe” and can be used separately. The User Interface The user interfaces (DebugDiag.exe and DebugDiagAnalysisOnly.exe) present an interface to analyze memory dumps, automate the creation of control scripts and to show the status of running processes, including services. It is composed of 3 views: Rules: Creates control script for the debugger host through a wizard. The script is located under the directory \scripts. Advanced Analysis: Runs a selected “Analysis Script” against one or more memory dumps. Processes: Shows status of running processes/services. Note: DebugDiagAnalysisOnly.exe does not require privilege elevation on operating systems beginning with Windows Vista, so it only contains the Advanced Analysis view. Supported operating systems:
Microsoft Exchange PST Capture is used to discover and import .pst files into Exchange Server or Exchange Online
PST
Capture is used to discover and import Outlook Personal Folder (.pst)
File Format files into Exchange Server and Exchange Online. PST Capture
helps an organization that wishes to gain more control over their email
data repositories by placing them into Exchange. By optionally
installing PST Capture Agents on target machines, administrators can
determine where .pst files are located and who their file owner is via
the PST Capture Console. Administrators can import .pst files via Import
Lists to Exchange Server or Exchange Online. Data can be directly
imported into the primary mailbox or associated archive mailbox.
Supported operating systems: Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Vista
