SBS 2008 and TS Gateway

I got a call this morning from a client who was unable to remote in to their computer from RWW using their SBS 2008 server. I had another client that had this issue a few months back and to fix it all I had to do is recreate the TS Gateway policies.

Typically this one wasn’t that easy to resolve so I ended up searching the Technet website. To fix the issue I ended up changing the SSL Cert that TS Gateway uses and checking every setting in the SBS Web Applications using this Technet article since everything in this post, except for the /RPC settings, was set up or configured the same.

The more detailed explanation:
After I checked all the SSL and Authentication settings in the Remote, RPC, RpcWithCert virtual sites and SBS Web Applications I changed the SSL settings under the virtual site remote to require client certificates from this forum post and I was unable to login to the remote site. Once I changed it back to ignore and restarted the site I was able login though the server without any errors.

image

I also changed the SSL certificate to the one we got from GoDaddy (third party cert) so that it would match the same certificate that was used when connecting to RWW. I assume that is what Microsoft meant when they say “Sites” in the directions under To configure the certificate for Terminal Services Gateway.

image

Who knows what caused this issue and its really hard to track down since nothing was logged in the event viewer. I think a custom app was installed and changed a few settings in IIS which the client didn’t know about.

My next Bike

I’ve been looking at motorcycles for the past month and I’ve narrowed it down to two. The Honda Shadow Phantom and the Harley Davidson Iron 883. The Honda Phantom has a 750cc, liquid cooled, 52° V-Twin and is shaft drive where as the Iron 883 has 883cc engine, air-cooled 63° V-Twin and is belt driven. They are both great bikes and I think I’ll have Craigslist open for the next six months till I find a deal.

2010 Honda Phantom:

image

image

Video From YouTube:

2010 Harley Davidson Iron 883:

image

image

image

YouTube Video:

Photos From TopSpeed.com

Boot from iSCSI – Part 1

I found out that one of my network cards can boot from an iSCSI target. When you boot from an iSCSI target you are actually booting off of a disk, real or virtual, that is located on another server over the network. What’s cool about this technology is that you can turn a server on without hard drives. That means you have one less thing to worry about and when you have ten or fifteen servers that makes a huge difference.

So far I was able to flash the boot ROM to the Intel PT card but I’m running in to issues having it connect to the volume. I have Windows Server 2008 R2 installed on the server and have the authentication set to the MAC Intel’s address and it can connect to the volume so I’m unsure why I cant boot form it. I posted on the Microsoft forums and hope I can get this working. I posted some screen shots below, once I get it working I’ll make a diagram to explain what I’m up to :).

I know that I’m using home PC to workstation class hardware which might be part of my issue but so far testing in my “lab” has gone ok with minor hitches. I would love to have some Xeon servers with 100Gb RAM and 300GB SSD’s.

Intel Boot Configuration Settings:
iSCSI_Intel_NIC_Settings

Error on boot:
iSCSI_doesnt_Connect

Windows Server 2008 can see the iSCSI volume:
iSCSI_Works_Wiindows