Many moons ago we had a web app with a 3rd party control that appeared to leak memory over time. The web server was IIS 5 (Windows 2000) and at the time it seemed like the easiest way to work around the leak was to simply restart IIS every night with a scheduled call to
|
|||
|
I have spent the past few days working on migrating a bunch of classic ASP web applications from a Windows 2000 server to a Windows 2003 server. A long overdue task, but one who’s time has finally come. The hardware under the Windows 2000 box has been acting up a bit lately and I’m rapidly I needed to put a new domain controller up at one of our production sites this week. We had an older web server in the dev environment that doesn’t get much use these days so I converted it to a virtual machine (I love VMware Converter!) and then reloaded it with Windows 2003 R2. The install Sometimes you just have to give credit… Earlier today I installed VMware Server on a machine at work and then built a client Windows 2003 server on it. The install went smoothly, but once it was up and running I found I couldn’t get it on the network. In fact, I couldn’t even ping the gateway  December 22nd, 2008 |  Tags: network, troubleshooting, vmware, VMware-Server, windows-2003 |  One comment I’m having a heck of a time with VMware Converter on my Windows 2003 x64 VMware Server machine. Before I built this particular x64 box, I used to run Converter all the time on a 32bit server with no issues. But for some reason, it gets wonky on the new one. Heck, I even upgraded to |
|
||
|
Copyright © 2010 Solo Technology - All Rights Reserved
|
|||
