The Windows command-line tools are used to perform various tasks related to Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows 7, and Windows Vista. You can use the command reference to familiarize yourself with new and enhanced command-line tools, to learn about the command shell, and to automate command-line tasks by using batch files or scripting tools.
Here’s a test. What does the Clip command do?
What’s scary is how many of these commands I actually do know.
I installed a .Net 3.5 application onto a Windows 2008 Web R2 (64 bit) What makes this a little unique is that the ASP.Net code is stored on a UNC file share. Because of this issue, I received the following error:
Security Exception
Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application’s trust level in the configuration file.
While searching I came across the caspol solution from Microsoft:
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\caspol.exe -m -ag 1 -url “file:////\\fs\share\*” FullTrust -exclusive on
After restarting IIS, all sorted.
I’ve recently started on a project that required IIS7.5 to be load balanced using windows network load balancing, part of the proposal was to describe how were the two web servers going to keep in sync, there were several options open to us.
After reviewing them all we proposed to have the two server load balanced using windows network load balancing, connected to the same IIS configuration using the built in “shared Configuration” tool, and then hold all the web data such as the sites and content on a Windows clustered back end file share.
For the benefit of this post I’m not going to blog how to set up a pair of windows network load balanced servers, but i will document the steps you need to take to configure content sharing and how to redirect a site to a UNC path on a backend cluster share.
First off we will configure the steps to share the IIS config between the two web servers for this i assume you already have two servers with IIS role installed, and a shared volume that both servers will be able to see.
Configure IIS Shared Configuration:
2. In the in the centre pane, then open shared configuration.
3. In the right pane, select the export configuration
Fill in the details for the share that you have created that both web servers can see.
Enter an encryption key (this is a password that will be needed to add nodes to the shared configuration).
the next step is to add the nodes to both share the configuration.
4. Enable shared configuration box, and fill the details to the configuration files that you
have just exported.
5. Restart IIS to apply the configuration, Repeat the impost on the other web server and hay presto, the servers are sharing the configuration and to test if you create a new site on one of the web servers you will see that is is mirrored on the other server.
Redirect the site content
The next part to the blog is to redirect the site content to ensure both web servers are using the same web content file, the benefit to this would be there would only be one location to upload new content to, you are sure that the content on both servers are the same.
Only a few steps to ensure that this is correct, and if you have already done steps above to share the configuration you will only have to do this on one of the servers as the configuration is mirrored and will automatically be replicated onto the other web server.
1. Launch the IIS manager on one of the web servers,
2. Right click on sites and select “Add new site”
3. Under the physical path section enter the UNC path to your clustered share.
(this share again needs to be accessible by both web servers.
4. Once the site has been created, right click on it navigate to:
“Manage web site>Advanced settings”
5. Under “physical path credentials” enter a domain account that has permissions to the
clustered share as below.
6. Test the web site, and if you have configured the NLB content sharing as above look on the other web server and you will notice that the settings are visible and matched on both.
Hope this helps someone along the way.
JW
Recently vie had a problem with email contacts sometimes receive email messages with a strange file attached, called winmail.dat. When they attempt to open this file, either it can’t be opened at all, or it contains "garbage" data.
When an Outlook user composes and sends a message using Rich Text Format or HTML Format, Outlook automatically generates a file, winmail.dat, and attaches it to the end of the message. winmail.dat contains formatting information, in a human-unreadable form, that Outlook will use on the receiving end to display this email message correctly. Unfortunately
there are a lots of blogs that told me to change my email to plain text or change my firewall settings none of these solved my problem.
In the end (totally frustrated I decided to look at our Exchange install for the solution, After digging for over an hour I found the MIME setting under Hub Transport role, I changed these to never use RTF and blow me, it started working, those users that could not receive the attachments suddenly were back OK.
Don’t know if this will help you as I’m not sure we had ever change this setting in the past but if it points you in the right direction….
Screen shot of the Hub Transport role.
To fix the issue:
Go back into Windows and start up your HyperV console. The error should now be gone.
Microsoft Security Essentials is a free* download from Microsoft that is simple to install, easy to use, and always kept up to date so you can be assured your PC is protected by the latest technology. It’s easy to tell if your PC is secure — when you’re green, you’re good. It’s that simple.
Microsoft Security Essentials runs quietly and efficiently in the background so that you are free to use your Windows-based PC the way you want—without interruptions or long computer wait times.
Download LINK
(a) High availability and live migration for managing a dynamic IT infrastructure
(b) Support for 64 logical processors future proofing our customers to scale up with the hardware
(c) Support for running up to 384 virtual machines with up to 512 virtual processors
(d) Processor compatibility mode for live migration across different processor SKU’s from the same vendor
(e) Hot add/remove virtual storage
(f) Networking enhancements (VMQ, Chimney, support for Jumbo Frames)
(g) Simplified management using sconfig
(h) Boot from flash
Many thanks to Vijay Tewari.
<HERE>.
Jason Whitaker 
