Very easy to use and good reports on the Archivist Site :
Microsoft Opalis becomes System Center Orchestrator.
This System Center tool makes your datacenter dynamic by automation the workflow process.
In this topic you can see the most important changes about Service pack 1 for Hyper-V R2 components :
Dynamic memory feature working more efficient with the memory of your virtual machine environment on Hyper-V !
Get a great user experience with Remote FX on your Virtual Desktop with excellent performance for example with video’s
Download here the complete Hyper-V R2 Service Pack 1 Architecture Poster at Microsoft :
This topic is about Microsoft System Center project codename “Concero” what means “connected” was presented at Microsoft Technet Live day 2011 in The Hague Netherlands at the keynote.
“The initial release of “Concero” will enable customers to deploy, manage and control applications and services deployed on private clouds built using System Center Virtual Machine Manager 2012 and in the public cloud offering of Windows Azure. This provides a consistent and simple user experience for service management across these clouds.”
- Copy Windows Azure configuration, package files and VHD’s from on-premises and between Windows Azure subscriptions
- Ability to access resources across multiple VMM Servers
- Deploy and manage Services and virtual machines on private clouds created within VMM 2012 and on Windows Azure
Great new features to manage integration of on-premises Microsoft products and to combine with Cloud services as Windows Azure.
On Technet Live 2011 on the 27th of April Microsoft shows also the diagram view of a Service with operational control.
A very good prospect for centrally managing the Microsoft System Center products and good for virtualization.
I will try you guys to keep you up to date of project “Concero”
See also on Hyper-V.nu :
About This Video
Corey Hynes and Symon Perriman provide an advanced introduction to VMM 2012 in this module. Viewers will understand the key features and design goals of VMM 2012 as well as experiencing the Library and the concept of the “Fabric.”
Additionally, see how to perform basic configuration and management tasks with services and service templates.
Checklist: Library Preparation for Deploying Services
|1||Update the InstallSAV.cmd script in the Application Frameworks resources that are added to the VMM default library share during setup.
|2||Add your application files to the library.|
|3||Download a Microsoft Windows Server 2008 R2 Evaluation VHD to a library share, and install the needed updates.|
The following procedure explains how to update the InstallSAV.cmd script, which is distributed with VMM 2012, to fix the installation order for Microsoft Web Deploy and the Server App-V agent.
|This procedure is only needed if the Web Deployment Tool is installed with Server App-V -(that is, when the \w parameter is used with the InstalSAV.cmd).|
To update the InstallSAV.cmd script
- Locate the InstallSAV.cmd script in Windows Explorer.
The file is stored in the ApplicationFrameworks folder, which is added to the default library share when a stand-alone VMM 2012 management server is installed. The default share name is MSSCVMMLibrary. The default physical location for the share is the following local path:
C:\ProgramData\Virtual Machine Manager Library Files\ApplicationFrameworks
Note The ProgramData folder is hidden by default. To display the ProgramData folder, in Windows Explorer, on the Tools menu, click Folder options. Then, on the View tab, click Show hidden files, folders, and drives.
In the Application Frameworks resources, x64 and x86 versions of the Server App-V resources are stored in separate folders. For US English installations of VMM 2012, the folders have the following names, where “en-US” identifies the language of the VMM 2012 installation:
Update both copies of the script.
- Open InstallSAV.cmd in Notepad or another editor.
- In the script, move installation of Web Deploy ahead of installation of the SAV agent by modifying the following .cmd section:
Description Code Current code
echo Installing SAV agent... start /wait agentsetup.exe /q "LOG_LEVEL=voicewarmupx!" if errorlevel 1 ( echo "SAV agent installation failed. See log(s) at %%temp%% for more details." goto EOF ) echo SAV agent installed. if defined _InstallWebDeploy ( echo Installing WebDeploy... start /wait %windir%\system32\msiexec.exe /qn /i webdeploy.msi /l %temp%\WebDeploy.log if errorlevel 1 ( echo "WebDeploy installation failed. See log at %%temp%%\WebDeploy.log for more details." goto EOF ) echo WebDeploy installed. )
if defined _InstallWebDeploy ( echo Installing WebDeploy... start /wait %windir%\system32\msiexec.exe /qn /i webdeploy.msi /l %temp%\WebDeploy.log if errorlevel 1 ( echo "WebDeploy installation failed. See log at %%temp%%\WebDeploy.log for more details." goto EOF ) echo WebDeploy installed. ) echo Installing SAV agent... start /wait agentsetup.exe /q "LOG_LEVEL=voicewarmupx!" if errorlevel 1 ( echo "SAV agent installation failed. See log(s) at %%temp%% for more details." goto EOF ) echo SAV agent installed.
- Repeat the previous step to update the other version (x86 or x84) of SAVInstall.cmd.
Next, add the application packages that you will use during service deployment to the library. Maintain a folder that holds all releases of the application, and add a subfolder for each application release.
In the example scenario, the application folder is created in the default library share, which makes the application files available to administrators. You can add the application files to any library share. If the application will be deployed to a private cloud, see How to Configure the Library to Support Application Deployment in a Private Cloud in VMM 2012 for guidance on how to make the application files available to self-service users.
While you are configuring library paths, you will create a folder to store the XML files for exported virtual machine templates and service templates.
Enter here the right credentials