Techie Than

Continuing on from my last post about setting up RemoteApp on Windows XP. I needed to make the old application available to multiple users, so I have decided to modify the Terminal Service in my WinXP box to allow multiple remote session. I found the instructions here . It's pretty simple. You just need to replace termsrv.dll file and apply some registry changes. But you do have to consider that Windows XP employs a Windows File Protection system that detects when system files are changed and replaces it back with the original microsoft version of it. Here's what I did: Grab the file termsrv_sp3_patch.rar from the link above. Back the file C:\windows\system32\termsrv.dll into another location.  Open service.msc and change the Start-up property of the Terminal Service to Disabled Restart the computer. After restart, delete the file termsrv.dll from the following locations C:\windows\sytem32\ C:\windows\system32\dllcache C:\windows\ServicePacks\x86 Copy the termsrv.dll file from...

We are using a very old DOS-based system here in the office that is critical to our operations. Unfortunately, it requires IPX protocol and since it's only available on Windows XP (or Windows 2000/2003 servers), I can't upgrade our users' computers to Win 7 or 8. With Window XP now at it's end of support, I need to start migrating to the newer OSes. Short of setting up XP-mode on each one of the new computers, I found a way to make the DOS-based program still available by setting up a Windows XP box as a Terminal Server and using remoteApp to make it appear as if they are only opening the application and not a Remote Desktop session. So what needs to be installed are: Install Microsoft's official Update for Windows XP SP3 to enable RemoteApp To simplify the setup, instead of manually changing registries and modifying RDP files, I opted to use this very handy tool call RemoteAppTool from Kim Knight. You can download here . Once those are installed, logon to the termi...

I encountered this problem today when I tried to convert 2 Dell PCs into VMware virtual machines. The conversion run fine without any errors at all, but the new VMs won't boot up properly. I'd get the Windows 7 blue-screen-of-death saying something about disks being changed (too fast to read through), followed by a reboot and back to the blue screen again. The source machines were both Dell Optiplex 990 PCs and upon checking the settings, I quickly noticed that the hard disks on the VMs are IDEs. I'm certain that my Dells have SATA, so I knew exactly where the problem was. I remember seeing this same problem with physical machines when SATA was new. Windows would crash if you changed to SATA drives and don't update the BIOS setting to "compatibility mode." The thing that would've prevented this from happening was if I set the correct controller type on the VMWare Converter wizard. Instead, I went with all the default options and VMWare uses IDE if there...

Open DOS prompt with elevated permission, then run this command: DISM /online /Cleanup-Image /SpSuperseded NOTE: The contents of this article are for my personal documentation only. I am not liable for any issues casued by other person running the above procedures on their own system.

Open up command prompt and run the following for each website/host header Appcmd set site /site.name:" sitename " /+bindings.[protocol='https',bindingInformation='*:443: certname ] Where: - sitename = the site's name in IIS - certname = the certificate name in IIS

I have spent an entire night trying to figure this out. I was deploying a newer ASA 5510 v7.2(2) - on my network to replace my old ASA 5510 v7.0(6). So I thought it was gonna be straight forward. Copied all the settings and plugged the thing it. Everything looks set at first, although I noticed that the new ASDM shows the Access Rules a little differently now. When adding/changing rules, you don't get to choose the Interface anymore on both the source and destination. Checked the access-lists on CLI and they are the same commands, so I thought it didn't matter. I got thing live, did a few tests, then packed my bag and went home. When I tried connecting back to the office to check on some server, that's when I realized VPN is not working. Using Cisco VPN client 5.0.07.0290, I can connect to the network but I cannot access any of the hosts behind the firewall. I went through the config of both firewalls line by line and they seems to match. But why is my VPN dropping my packe...

I had this problem where I have to setup IIS on a machine that already runs a webserver (CommunigatePro Webmail). The issue was I needed both to be accessible via port 80 so my clients will not have to connection to non-standard ports. After much research and testing, I managed to get this running. The solution is simply to have 2 IP address on the server (one for IIS, one for the other webserver), configure them both to listen only to their specific IPs. Now this seems easy, you just have to assign the IPs to the respective servers to listen to and that's it! But the problem is, IIS locks in to the port number, regardless of the IP address. Even if you specify a website as listening to only a particular IP, IIS will block the entire port number (80). Here's the work around on that: stop the WWW service ( net stop http /y ) grab the httpcfg.exe from your Windows 2003 install CD. It's packaged in the Support/Tools/Support.cab file. run this on the server: httpcfg set ipliste...