I build lots of VPC’s for demos, labs, prototypes, etc. With the various flavors of Windows out there, I find it hard to find the Windows Activation icon to verify activation.
I found a new tip today to fire Windows Activation from the command line. This technique works on Windows XP and Windows Server 2003, but does not work on Windows Vista or Windows Server 2008.
No more searching to find the Windows Activation icon!
- Click Start > Run
- Type “oobe/msoobe /a”
- This command triggers the “Out Of Box Experience” activation application, which opens the Windows activation screen.
- If Windows is already activated, it will tell you so, otherwise, you can continue to activate Windows.
Thanks to command-tab.com for this useful tip! For more info, see How To Activate Windows XP in 5 Minutes or Less.
Categories: Windows Server 2003 · Windows XP
After installing Windows Server 2008, I found I can’t ping the server, even within a “Private Network”. I like to ping stuff in my spare time, so this was distressing to me. I suspected to find a firewall issue, but was surprised to find enabling the Network Discovery option in the firewall configuration settings didn’t fix it.
Configure Windows Firewall Settings – File and Printer Sharing
By default, Windows Firewall for WIndows Server 2008 is configured to disallow File and Printer Sharing on the network. By default Windows Server 2008 firewall is configured with Windows Firewall running, and with File and Printer Sharing disabled. This blocks ICMP Echo Request packets used by the PING command. You can allow the server to respond to ping requests by doing the following:
- Turn off Windows Firewall on the Windows 2008 Server (not recommended)- OR -
- Enable the File and Printer Sharing option in Windows Firewall Configuration Settings
- Start > Control Panel > Network and Intranet
- Under the Windows Firewall section heading, Click the Allow a program through Windows Firewall link
- In the programs and ports list, check the File and Printer Sharing option
Categories: Windows Server 2008
November 11, 2008 · 1 Comment
An issue you’re likely to run into in XAML (WPF, XBAP, and SIlverlight applications) is the need to keep whitespace characters intact in your markup. By default, XML collapses all whitespace, ignoring strings of spaces, tabs, and return characters inside an XML node, which it graciously converts to a single space.
If you want to include a series of spaces in your XML node markup, you can add a xml:space=”preserve” attrbute to your XML elements. This attribute is part of the XML standard. If you turn it on, it preserves all whitespace appearing inside the XML node, including any hard return characters included inside the XML node.
<Button Name="btnSample" xml:space=preserve">Respects my spaces
and carraige return</Button>
Categories: .Net · C# · Silverlight · WPF
del.icio.us it!
digg it!
reddit!
technorati!
yahoo!