Network World senior editor John Fontana has sent Microsoft Subnet this guest blog. He is reporting from the IDG editors meeting with Microsoft in Redmond this week. He writes: Larry Orecklin, who runs the System Center business and virtualization, laid out the Microsoft vision on virtualization from the server to the desktop. He clearly put the emphasis on management, focusing on core pieces of System Center with Operations Manager, Configuration Manager, Data Protection Manager and Virtual Machine Manager (VMM).
If the hub of Orecklin's vision is management, the pieces that revolve around the hub are server virtualization, applications virtualization, desktop virtualization and presentation virtualization (i.e. terminal services). He said the VMM version that will support Hyper-V will ship with the hypervisor add-on for Windows Server 2008. He said the timeframe for that release will be June or July. He hinted that the beta of VMM that supports Hyper-V would be released next week at Microsoft's Management Summit in Las Vegas. In addition, he disclosed that Microsoft has 4.5 million seats of Microsoft Application Virtualization (SoftGrid) out in the field. He said Kidaro, which Microsoft acquired in March, would become an important tool for managing virtual PCs.
source: http://www.networkworld.com/community/node/27152
I am working on generating a list of DCR (Desired Configuration Requests). The following are some high level complaints
-
WQL. Simply why are we using this instead of SQL for console connections? I understand the need for WQL on a client because of the intense use of WMI. However, a client is pulling all the info directly from SQL. So why the WQL?
-
Lack of Multithreading. Almost every server now has multicore and multisocket CPUs. Why are so many threads in SMS linear? My biggest complaint is the collection evaluation SMS_Collection thread. If there are multiple collectionstatus at 5 why isn't the multicore cpus turning through those like butter?
-
DFS, Dynamic File systems. Why are DPs not put into a DFS. That way a traveling client will always attempt to connect to same share and have DFS determine cloesest. Talk about solving the source path healing issue if a DP/Share goes down with no product code available.
-
Powershell integration?
Just thinking out loud