Because Windows 7 and Windows 2008 R2 are not certified clients for System Center Virtual Machine Manager 2008 Self-Service Portal, when you try to remotely connect to a VM using SSP you are rejected with an message like “Virtual Machine Manager failed to connect to the virtual machine because the guest operating system’s computer name —- could not be resolved by the Domain Name System.”
Starting from VMM 2008 R2, Windows 7 and Windows 2008 are certified clients for Self-Service Portal and this issue is solved.
The workaround to solve the issue in VMM 2008 is to copy SytemCenter.VirtualMachineManager.VMMCtlAx.VMConnect Active X control (vmmctlax_amd64.cab and vmmctlax_i386.cab) located in folder “%programfiles%\Microsoft System Center Virtual Machine Manager 2008\wwwroot\activex” from VMM 2008 server to VMM 2008 R2 server.
Also, in the SSP client, Windows 7 or Windows 2008, you have to uninstall Virtual Machine Manager Self-Service Client from Programs and Features to force its reinstallation with the new version once you access SSP again for the first time.
Posted in Hyper-V, Self-Service Portal, Virtual Machine Manager 2008.
Tagged with Hyper-V, Virtual Machine Manager.
By admin
– September 22, 2009
There is a rule included in VMM 2008 Managment Pack disabled by default. This rule, “Microsoft.SystemCenter.VirtualMachine.Manager.2008.Engine.TaskFailure.rule”, is in charge to generate a Warning Alert in System Center Operations Manager 2007 whenever a VMM Job fails.
The procedure to enable such rule, “Engine Task Failure”, is the following:
1.- From the Authoring view in SCOM Console expand Rules view. You can filter the rule view looking for Virtual Machine in filter box.
![post1 How to receive VMM 2008 Job Fails into SCOM 2007: [Engine Task Failure]](http://www.hkeyusers.com/wp-content/uploads/2009/02/post1.jpg "How to receive VMM 2008 Job Fails into SCOM 2007: [Engine Task Failure]")
2.- Once you have located “Microsoft.SystemCenter.VirtualMachine.Manager.2008.Engine.TaskFailure.rule” to enable the rule right-click -> Overrides -> Override the Rule -> For all objects of type: Virtual Machine Manager 2008 Engine Server:
![Post2 How to receive VMM 2008 Job Fails into SCOM 2007: [Engine Task Failure]](http://www.hkeyusers.com/wp-content/uploads/2009/02/Post2.jpg "How to receive VMM 2008 Job Fails into SCOM 2007: [Engine Task Failure]")
3.- From Override Properties parameters Check In Override box and set Override Setting to True.
![Post3 How to receive VMM 2008 Job Fails into SCOM 2007: [Engine Task Failure]](http://www.hkeyusers.com/wp-content/uploads/2009/02/Post3.jpg "How to receive VMM 2008 Job Fails into SCOM 2007: [Engine Task Failure]")
4.- From Override Properties parameters select any unsealed management pack, i.e. “Default Management Pack”, or create a new one, and click on OK.
![Post4 How to receive VMM 2008 Job Fails into SCOM 2007: [Engine Task Failure]](http://www.hkeyusers.com/wp-content/uploads/2009/02/Post4.jpg "How to receive VMM 2008 Job Fails into SCOM 2007: [Engine Task Failure]")
5.- And it´s ready. Good luck.
Posted in Hyper-V, SCOM.
Tagged with Hyper, SCOM.
By admin
– February 5, 2009
It´s a good practice to increase NTFS performace to remove the feature configured by default in Windows 2000, Windows 2003 and Windows XP operating systems, that maintains for every file on the system the date and time of the last operation performed over the file.
Because the quality of the storage impacts directly in the performace of Hyper-V environment it is also a best practice for Hyper-V to remove that audit functionality in Hyper-V parent and guest partitions. But be careful, some applications could depends of that functionality, so you have to assess the applications running into the server to be sure that there are no dependencies.
The way to remove the audit feature is just to modify the registry as following:
You have to create a new REG_DWORD key named NTFSDisableLastAccessUpdate inside the registry path HKLM\System\CurrentControlSet\Control\FileSystem\
In Windows Vista and Windows Server 2008 this feature is unset by default.
Posted in Best Practices, Hyper-V, Registry Tips, Windows 2008.
Tagged with Hyper-V, Registry Tips.
By admin
– December 4, 2008
There is a new feature available in Windows Vista and Windows Server 2008 that allows to increase the value of the TCP Receive Window size over its default maximum value, 65,536 bytes.
This feaute that is configured by default, in some circumstances, for example Firewall products that doesn´t implement correctly TCP Window Scaling, could impact the performace of some network operations launched from a Vista/Win2008 machine, some programs may respond slowly or may stop responding.
The command to check the configuration of this feature is:
netsh interface tcp show global
The command to change the configuration of this feature is:
netsh interface tcp set global autotuninglevel=disabled|highlyrestricted|restricted|normal|experimental
Where:
disabled: Fix the receive window at its default
value.
highlyrestricted: Allow the receive window to
grow beyond its default value, but do so
very conservatively.
restricted: Allow the receive window to grow
beyond its default value, but limit such
growth in some scenarios.
normal: Allow the receive window to grow to
accomodate almost all scenarios.
experimental: Allow the receive window to grow
to accomodate extreme scenarios.
WARNING: This can dramatically degrade
performance in common scenarios and should
only be used for research purposes.
Posted in Netsh, Tools, Windows 2008.
Tagged with Netsh.
By admin
– December 4, 2008
Windows Remote Management and Windows Remote Shell allow us to remotely administration of Windows Vista and Windows 2008 machines. For Windows XP SP2 and Windows Server 2003 there is also an update that align them with WinRM features used in Windows Vista and Windows 2008.
WinRM is installed and configured to start automatically in Windows Vista and Windows 2008, but it is not at all configured.
So, before to start to use it it is mandatory to proceed with its configuration. The command to do it is:
“winrm quickconfig” or “winrm qc” in abbreviated mode.
The command will launch the question “Make these changes [y/n]?“, just type y
Once the service is configured you can query its state using the command:
“winrm enumerate winrm/config/listener”
Now it´s time to execute WinRS in the client that will manage the romote machine. These are some examples about some ways to execute commands into the remote machine:
winrs -r:https://myserver.com ipconfig
winrs -r:myserver “dir c:\”
winrs -r:http://169.51.2.101:80 cmd
And finally, if you don´t need anymore WinRM you can remove it running this command:
winrm delete winrm/config/Listener?Address=*+Transport=HTTP
Posted in Management, Windows 2008.
Tagged with Remote Management.
By admin
– September 16, 2008
