Here are some tips that makes troubleshooting easy:
1) Check the event log
2) Google it
4) Run IISreset
5) Empty the Recycle Bin
6) Hit [CTRL]+[BREAK]
7) Kill the ASPNET worker process
8) Clear Temporary Internet Files
9) Touch the config file
10) Degauss the monitor (Not that applicable any more, I suppose)
11) Simmer ground rhino horn on a bed of whale pancreas
12) "get latest" and rebuild
13) Login as admin
14) Run ipconfig /renew (Windows)
15) Check if CAPSLOCK is on.
VMs – Gotta love them.
I like playing with Virtual Machines. I like playing with Virtual Hosts. In fact, 90% of my servers are all VM based at the office. It makes business sense to go virtual when the positives far outweighs the negatives.
The ability to swap between them when failure occurs in the blink of an eye is such a great advantage, any business who has not looked at going this direction is shooting themselves in the foot.
Unless specific requirements are needed, I prefer creating VMs that have “host only” communication. This way I can lock away what needs to be locked and NAT what needs to be seen. One of the issues that I have run into when going the “host only” route is that some installations throughput is seriously lacking with the speed cracking. A little bit of scratching showed me that it was Microsoft Windows(2008 and up) trying to be [their version of] clever by doing some TCP off loading(among others).
This becomes a problem when speed is exactly what the doctor ordered. How did I get around it?
Easy, follow these steps:
The default behavior for Windows Explorer in Windows 7 and Vista is to display a context menu when you right-click a folder.