Windows 8 is comming with lot of good surpises. I just heard about the new ribbon:
The new ribbon
The Home tab is focused on the core file management tasks, and we’ve put all the major file management commands there in prominent locations: Copy, Paste, Delete, Rename, Cut, and Properties. We’ve also given new prominence to two popular heritage features, Move to and Copy to, along with exposing a hidden gem, Copy path, which is really useful when you need to paste a file path into a file dialog, or when you want to email someone a link to a file on a server.
The Home tab is the heart of our new, much more streamlined Explorer experience. The commands that make up 84% of what customers do in Explorer are now all available on this one tab:
The Share tab is for sharing files by typical methods like zipping them up and emailing them to a friend, or burning them to optical media. Or you can quickly share files with other people in your home group or your network domain. It also provides one-click access to the ACLs for the currently highlighted file.
When you install the SCVMM 2012 you can assign some of the ports that it will use for communications and file transfers between the VMM components.
Note: Not all of the ports can be changed through VMM.
The default settings for the ports are listed in the following table:
|Connection type||Protocol||Default port||Where to change port setting|
|SFTP file transfer from VMware ESX Server 3.0 and VMware ESX Server 3.5 hosts||SFTP||22|
|VMM management server to P2V source agent (control channel)||DCOM||135|
|VMM management server to Load Balancer||HTTP/HTTPS||80/443||Load balancer configuration provider|
|VMM management server to WSUS server (data channel)||HTTP/HTTPS||80/8530
(non-SSL), 443/8531 (with SSL)
|These ports are the IIS port binding with WSUS. They cannot be changed from VMM.|
|VMM management server to WSUS server (control channel)||HTTP/HTTPS||80/8530 (non-SSL), 443/8531 (with SSL)||These ports are the IIS port binding with WSUS. They cannot be changed from VMM.|
|BITS port for VMM transfers (data channel)||BITS||443||During VMM setup|
|VMM library server to hosts file transfer||BITS||443 (Maximum value: 32768)||During VMM setup|
|VMM host-to-host file transfer||BITS||443
(Maximum value: 32768)
|VMM Self-Service Portal to VMM Self-Service Portal web server||HTTPS||443||During VMM setup|
|VMware Web Services communication||HTTPS||443||VMM console|
|SFTP file transfer from VMM management server to VMware ESX Server 3i hosts||HTTPS||443|
|OOB Connection – SMASH over WS-Man||HTTPS||443||On BMC|
|VMM management server to in-guest agent (VMM to virtual machine data channel)||HTTPS
|VMM management server to VMM agent on Windows Server–based host (data channel for file transfers)||HTTPS
(Maximum value: 32768)
|OOB Connection IPMI||IPMI||623||On BMC|
|VMM management server to remote Microsoft SQL Server database||TDS||1433|
|Console connections (RDP) to virtual machines through Hyper-V hosts (VMConnect)||RDP||2179||VMM
|VMM management server to Citrix XenServer host (customization data channel)||iSCSI||3260||On XenServer in transfer VM|
|Remote Desktop to virtual machines||RDP||3389||On the virtual machine|
|VMM management server to VMM agent on Windows Server–based host (control channel)||WS-Management||5985||During VMM setup|
|VMM management server to in-guest agent (VMM to virtual machine control channel)||WS-Management||5985|
|VMM management server to VMM agent on Windows Server–based host (control channel – SSL)||WS-Management||5986|
|VMM management server to XenServer host (control channel)||HTTPS||5989||On XenServer host in: /opt/cimserver/cimserver_planned.conf|
|VMM console to VMM management server||WCF||8100||During VMM setup|
|VMM Self-Service Portal web server to VMM management server||WCF||8100||During VMM setup|
|VMM console to VMM management server (HTTPS)||WCF||8101||During VMM setup|
|Windows PE agent to VMM management server (control channel)||WCF||8101||During VMM setup|
|VMM console to VMM management server (NET.TCP)||WCF||8102||During VMM setup|
|WDS provider to VMM management server||WCF||8102||During VMM setup|
|VMM console to VMM management server (HTTP)||WCF||8103||During VMM setup|
|Windows PE agent to VMM management server (time sync)||WCF||8103||During VMM setup|
|VMM management server to Storage Management Service||WMI||Local
|VMM management server to Cluster PowerShell interface||PowerShell||n/a|
|Storage Management Service to SMI-S Provider||CIM-XML||Provider-specific
|VMM management server to P2V source agent (data channel)||BITS||User-Defined||P2V cmdlet option|
The Windows Azure Monitoring Management Pack enables you to monitor the availability and performance of applications that are running on Windows Azure.
After configuration, the Windows Azure Monitoring Management Pack offers the following functionality:
- Discovers Windows Azure applications.
- Provides status of each role instance.
- Collects and monitors performance information.
- Collects and monitors Windows events.
- Collects and monitors the .NET Framework trace messages from each role
- Grooms performance, event, and the .NET Framework trace data from Windows
Azure storage account.
- Changes the number of role instances via a task
System Center Monitor version : System Center Operations Manager 2007 R2 CU3 or newer
The goals are:
- We learn a bit more about what everyone is up to
- We can share the findings with everyone so you can learn what everyone else is up to
This survey will run from this morning until 5th of September. We want to publish the results later that week, which just so happens to be the week before the Build Windows conference. We’ll be publishing the percentages breakdowns, and also trying to figure out trends.
In the survey, we ask about:
- Your Hyper-V project/environment
- Your Hyper-V installation
- Systems management
- What you considering to do in 2012
There is no personal information, no company specific information. Microsoft has zero involvement. They’ll see/read the results the same way you do, on the blogs of myself, Damian, and Hans (Hyper-V.nu).
The whole thing will take just 5 minutes; the more people that contribute, the more we will all learn about what people are up to, and the more we’ll be able to tweak blog posts, speaking, training, writing, etc, to what is really being done. If this goes well, we’ll do another one in 2012, 2013, and so on.
So come on …. give the greater community 5 minutes of your time.
One of the most important system resources for SQL Server is memory.
Lack of memory resources for the database engine results in increased I/O that is orders of magnitude slower than accessing memory.
One of the key benefits of leveraging dynamic memory is the flexibility to respond to the needs of a particular workload that would benefit from additional memory resources and make the most use out of all physical memory resources on a system.
VERY IMPORTANT : The benefit of additional memory depends on your workload.
The main highlights of using DM are:
– Without Hyper-V Dynamic Memory the virtual machines would have to be sized with a specific amount of static memory to ensure that all virtual machines could run on a single node in the case of a failover.
– The additional memory provides significant reduction in the number of I/O operations needed to support the same workload throughput.
– It should be noted that the benefit depends on your workload.
To read the complete review: :Running SQL Server with Hyper-V Dynamic Memory – Best Practices and Considerations
The SQL Server team published a whitepaper about considerations for Dynamic Memory in SQL Server VMs.
Dynamic memory enables virtual machines to make more efficient use of physical memory resources. Hyper-V Dynamic Memory treats memory as a shared resource that can be reallocated automatically among running virtual machines. There are unique considerations that apply to virtual machines that run SQL Server workloads in such environments .
To review the document, please download the Running SQL Server with Hyper-V Dynamic Memory – Best Practices and Considerations Word document.