IT Core Blog

Never stop questioning. Curiosity has its own reason for existing…

Posts Tagged ‘Windows

KB2413735: Mouse and screen resolution issues when managing a virtual machine using the Hyper-V

leave a comment »

From KB2413735

Windows Server 2008 or Windows Server 2008 R2, you may experience one of the following symptoms when you connect to a Hyper-V virtual machine using the Hyper-V Manager console or the System Center Virtual Machine Manager Administrator Console:
· The mouse cursor is frozen or has disappeared
· The screen resolution has reverted to the default size
If you connect to the virtual machine using a Remote Desktop Connection (RDP), the symptoms listed above are not exhibited.

This issue can occur after a new Hyper-V VMMS certificate is generated.
Note: The following event will be logged in the Hyper-VMMS event log when a new VMMS certificate is generated:

Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Event ID: 12520
Level: Warning
Description:
Auto-generating a self-signed certificate for server authentication.

To resolve this issue, perform one of the following steps on the Hyper-V server:
·Place the virtual machines in a saved state and then resume the virtual machines.
or
·Restart the virtual machines.

The self-signed certificate that is generated by the Hyper-V Virtual Machine Management service is valid for one year.

To create a self-signed certificate that doesn’t expire for several years, perform the following steps:
1.
Copy the PowerShell script from the following Microsoft Web site:
http://gallery.technet.microsoft.com/ScriptCenter/en-us/be2da634-978b-48d7-b3ab-01c593c9d177 (http://gallery.technet.microsoft.com/ScriptCenter/en-us/be2da634-978b-48d7-b3ab-01c593c9d177)
2. Paste the script into notepad, and then save the file as Cert.ps1. 
3. Copy Makecert.exe to the same directory as the Cert.ps1 file.
For more information on how to obtain Makecert.exe, please visit the following Microsoft web site: http://msdn.microsoft.com/en-us/library/aa386968(VS.85).aspx (http://msdn.microsoft.com/en-us/library/aa386968(VS.85).aspx)
4. Open an elevated Windows PowerShell command prompt. 
5. Run the Cert.ps1 script.

🙂

Written by IT Core

September 23, 2010 at 12:14 PM

Documentation for Dynamic Memory Resources

leave a comment »

From Virtual PC Guy’s Blog, here’s a documentation list for Dynamic Memory included in in the Windows Server 2008 R2 SP1 beta release:

Dynamic Memory Technical Overview whitepaper
This paper talks about what dynamic memory is, what it does and how it does it.  It is a good read for those curious to understand what is happening under the covers.
http://download.microsoft.com/download/E/0/5/E05DF049-8220-4AEE-818B-786ADD9B434E/Implementing_and_Configuring_Dynamic_Memory.docx

Hyper-V Dynamic Memory Evaluation Guide
This article steps you through the process of setting up SP1 and enabling dynamic memory.  It also gives you some good tips on configuration and troubleshooting.
http://technet.microsoft.com/en-us/library/ff817651(WS.10).aspx

Windows Server 2008 R2 Service Pack 1 – TechNet Center
For all things “Windows Server 2008 R2 Service Pack 1” related – the TechNet Center has you covered.
http://technet.microsoft.com/en-us/library/ff817647(WS.10).aspx

Hyper-V: Dynamic Memory Survival Guide
The TechNet Wiki also has a “Dynamic Memory Survival Guide” article with some extra links.
http://social.technet.microsoft.com/wiki/contents/articles/hyper-v-dynamic-memory-survival-guide.aspx

Thanks Ben 🙂

Written by IT Core

July 15, 2010 at 12:53 AM

SCVMM Administrator Console does NOT show up properly “Windows 2000”

leave a comment »

Another great article from Michael. This time he explains how to fix a problem that we also had in our SCVMM…

if you are managing a Windows 2000 Server Virtual Machine with Hyper-V, you might notice that VMM does not recognize this operating system in the Administrator Console. Even if you manually change the OS name in the Virtual Machine properties, VMM will make it empty on the next refresh of the VM.

To get around this issue and get the proper name to display follow these steps

1.First close the VMM Administrator Console
2.Then, stop the VMMService windows service on the VMM server computer
3.Take a FULL database backup of the VMM database [Just in case; this is a safety net in case something goes wrong]
4.Now you are ready to edit the database and insert the columns that will allow VMM to recognize the OS name for Win2k.
5.Install Microsoft SQL Server Management Studio Express on the same computer where the VMM database exists. This is a free download from microsoft and you can search for it on Bing.
6.Open SQL Management Studio, select the VMM database and run the two SQL insertion statements/scripts below. That should change the VMM knowledge of supported guest operating systems and also add Win2k to the list (for both Server and Advanced Server).
7.Once the sql script complete, restart the VMMService and open the Administrator Console. Wait for approximately 30 minutes to 1 hour and your VMs will display the proper Win2k operating system in the Administrator Console. Make sure your Virtual Machines are running during this time, otherwise the guest operating system version will not be discovered
8.Good luck

INSERT INTO tbl_IL_OS
(OSId, Name, Description, Edition, ProductType, Version, Architecture, OSFlags, VMWareGuestId)
VALUES (’08f954f9-6475-4e07-9e32-4d2ddefc4c54′, ‘Windows 2000 Advanced Server’, ‘Windows 2000 Advanced Server’, 1, 3, ‘5.0’, ‘x86’, 0x3f, ‘win2000AdvServGuest’)

INSERT INTO tbl_IL_OS
(OSId, Name, Description, Edition, ProductType, Version, Architecture, OSFlags, VMWareGuestId)
VALUES (‘e85f1375-c69e-4cbd-8249-0e32caa04abb’, ‘Windows 2000 Server’, ‘Windows 2000 Server’, 0, 3, ‘5.0’, ‘x86’ , 0x3f, ‘win2000ServGuest’)

🙂

Written by IT Core

April 17, 2010 at 8:02 PM

How to use Problem Steps Recorder

leave a comment »

From App-V Team Blog.

“On Windows 7 and Windows Server 2008 R2, there is a great troubleshooting tool called the Problem Steps Recorder (PSR). The PSR allows screenshots and details of actions to be automatically recorded and saved in a .MHT file that is automatically zipped. A user can send this file to Microsoft Support to provide an accurate account of steps to reproduce and issue. There is a short video on TechNet that gives a demonstration of the Problem steps recorder.

We can appropriate this tool and turn it into a Sequencing Steps Recorder to document “recipes” for sequencing applications. Other App-V blog articles have demonstrated how to use video to document sequencing. The Problem Steps Recorder just provides another alternative, especially for those users that like to read from a printout.

The PSR can be easily be found on Windows 7 or Server 2008 just by clicking on the Windows Logo and typing “steps” ,“record”, or “PSR.exe” in the search bar”

Read more at: “Document Sequencing on Windows 7 with the Problem Steps Recorder

Windows Script 5.7 Setup Error

leave a comment »

You download the Windows Script 5.7 for Windows Server 2003, then you try to install it on windows 2003 64Bit version OS, when you do that you get the following error message:

Windows Script Setup Error
This Windows Script is for a different hardware platform.

This error is expected in windows 2003 64bit version since that the Windows Script 5.7 for Windows Server 2003 download is for Windows 2003/32Bit versions.

Solution:
Request and download the hotfix from KB955360.
Install the hotfix and reboot the system. after reboot verify that you are on 5.7 version by typing from cmd:
cscript.exe
or
wscript.exe

DONE!!!
🙂

Written by IT Core

January 2, 2010 at 12:00 PM

HP System Management Homepage Timeout Error

leave a comment »

From time to time, I get the following error when trying to load the HP System Management Homepage:

A timeout occurred when while loading data for the HP System Management Homepage which may result in missing or incomplete information. See the HP System Management Homepage log for additional information

How to solve this?
This is normally caused by bad SNMP settings, Community Strings and/or Version Control Agent on the problem host, make sure it is pointing to a valid version control repository manager.

Here are some samples….

 

🙂

Written by IT Core

January 2, 2010 at 10:22 AM