To totally disable Firewall in Vista, execute the following command from command line:
netsh firewall set opmode mode=DISABLE
netsh firewall set opmode mode=DISABLE profile=ALL
Before you install this Beta release, back up all MP3 files that might be accessed by the Windows 7 – The first hotfix for Windows 7
Here’s the warning by Microsoft for those who intends to download and install Windows 7 beta:
To protect your MP3 files:
- Before you install this Beta release, back up all MP3 files that might be accessed by the computer, including those on removable media or network shares.
- Install the Beta release of Windows 7; download and install the Update to Windows 7 Beta (KB961367) located on this page.
Microsoft releases Update for Windows 7 Beta (KB961367) in MSDN and TechNet Subscriber Downloads page to fix the bug and protect the MP3 files for users who use the Windows 7 beta build 7000. The KB961367 is not be published on Microsoft Download Center yet.
Windows 7 Beta is available for download by MSDN subscribers and TechNet Plus subscribers as of 18:30 PT yesterday. Also, I just wanted to let you know that the Windows 7 Beta TechNet forums are live.
Everybody knows that Windows caches Usernames and Passwords, include domain credentials and credentials that we type in when we try to access shared resources, when we click the Save Password feature. But question is how to Clear this cache in case you have to do so.
So, to clear cached credentials on a Windows-based computer do the following steps:
- Open Command Prompt.
- Type the command: rundll32.exe keymgr.dll, KRShowKeyMgr
The Hyper-V role enables you to create a virtualized server computing environment using a technology that is part of the Windows Server® 2008 operating system. This solution is provided through Hyper-V. You can use a virtualized computing environment to improve the efficiency of your computing resources by utilizing more of your hardware resources.
The Failover Clustering feature enables you to create and manage failover clusters. A failover cluster is a group of independent computers that work together to increase the availability of applications and services. The clustered servers (called nodes) are connected by physical cables and by software. If one of the cluster nodes fails, another node begins to provide service (a process known as failover). Users experience a minimum of disruptions in service.
This guide shows you how to use these two technologies together to make a virtual machine highly available. You will do this by creating a simple two-node cluster and a virtual machine, and then failing over the virtual machine from one node to the other. Continue @ Source…
One of the software requirements for VMM is Windows PowerShell v1. If we try to install SCVMM Administrator Console, we could get this error in the prerequisites dialog:
“System Centercentre Virtual Machine Manager requires Windows PowerShell 1.0.”
We can see this error in two situations:
- We have not installed PowerShell 1.0.
- We have installed another version of PowerShell, let say PowerShell CTP 2.
BTW, we will have the same issue if we try to install Exchange 2007 Admin Tools while having PowerShell CTP 2 installed.
The workaround is very simple.
“Prerequisites Checking” is looking for a registry key named PID. The value for this key should be “89383-100-0001260-04309“.
We can create it manually, create file PSv1.reg. Here is a content of PSv1.reg:
Windows Registry Editor Version 5.00
Import the PSv1.reg, by running it, and ran the SCVMM installation again and the problem will disappear.
Now that the prerequisite phase is complete we can safely remove the created key.
After a few months of supporting customers, Microsoft has enough case data to report on the top issues being reported for Hyper-V. The issues are categorized with the top issue(s) in each category listed with possible resolutions and additional comments as needed. Continue here
To control background colour on the client’s computer (XP) the custom ADM file (BGColor.adm) could be created. The BGColor.adm should be manually added to the network environment before start using it. Here is a content of BGColor.adm:
KEYNAME “Control Panel\Colors”
PART !!labeltext DROPDOWNLIST REQUIRED
NAME “Normal” VALUE “0 128 128”
NAME “Black” VALUE “0 0 0”
NAME “White” VALUE “255 255 255”
NAME “Red” VALUE “255 0 0”
NAME “Brown” VALUE “128 0 0”
NAME “Yellow” VALUE “255 255 0”
NAME “Green” VALUE “0 128 0”
NAME “Sky” VALUE “0 255 255”
NAME “Brown” VALUE “0 0 255”
NAME “Blue” VALUE “0 0 255”
NAME “Dark Blue” VALUE “0 0 128”
NAME “Pink” VALUE “255 0 255”
NAME “Grey” VALUE “160 160 164″
category=”Custom Policy Settings”
categoryname=”Desktop BG Colour Changer”
policyname=”Change the background color of the client computer via GPO”
explaintext=”This policy sets the background color of the client computer”
To minimize all open windows Microsoft provides “Hot Keys”, like Windows Logo Key + M or Windows Logo Key + D. All Hot Keys was disabled by old GPO. To allow using Windows Logo Keys the following steps should be enabled through GPO:
- Go to: Administrative Templates \ Windows Components \Windows Explorer
- Change “Turn off Windows+X hotkeys” settings to Disable
Note: Client’s computer should be restarted to start using Windows Logo Keys.