Can’t ping the domain controller via FQDN while on the internal network? Trouble accessing any of the internal domains that are available via Direct Access while on your internal network?
This is a quick blog post to document an error I encountered that took me a while to figure out, as is typical with errors that are caused by configuration mistakes, yes self-inflicted. In the Microsoft Unified Access Gateway administration documentation for configuring Direct Access (DA), it says 2 things that are extremely important but does not emphasize just how important they are, or the errors that will be encountered if they are not followed.
Your Network Location Server (NLS), which must be able to serve HTTPS requests, is used by your DA clients to determine whether they are on the internal network, this site must not and cannot be accessible through DA or any other means from outside your network, so make sure the HTTPS resource is NOT something you need to access from external networks. If your clients can access the NLS then they will not attempt a DA connection. If they cannot access the server, then they will attempt a DA connection. There are a few key points to this server that also cannot be overlooked.
Continue reading Direct Access Computers Can’t Ping Domain Controller on Internal Network?
So I’ve run into this problem multiple times and ‘hacked’ my way around it various ways, but there is a better way that doesn’t require the use of certutil.exe or any other console utilities. This scenario applies under the following conditions:
- CA (Certificate Authority) Server is running on Windows Server 2008 R2
- Web Server is running on Windows Server 2008 R2
- Both servers are members of the same domain
- You want to use the Certificates snap-in
- You want to stay away from the console if you can
By default, you cannot generate a web server certificate request directly from your servers and you are presented with this screen based on the default Active Directory Enrollment Policy:
As you can see from the screenshot, most of the certificate templates are unavailable with the exception of the computer certificate template.
Continue reading Enable Web Server Certificate Requests On Windows Server 2008R2 CA Server
I decided to sign up for Microsoft Connect and download the Windows Home Server “Vail” public preview and install it in my lab vSphere lab. I recently picked up an Iomega ix4-200 and had some extra space so I wanted to try to streaming media and backup functionality.
After Windows (Server 2008 R2) installed, and the WHS configuration wizard started running, it would error out at 36% or 37% consistently. It would post an error, and instruct me to reboot and contact the vendor if the error continued. Hmm… contacting Microsoft about a beta, yehrite, and I’m impatient so I didn’t feel like posting on the forums and trying to wait for a response what would likely be a dance of posting log files etc. I so I went into reinstall / reboot hell.
After numerous reboots, rebuilds, and a successful VMware Workstation deployment (yes I actually wondered if Microsoft put something in the bits to keep it from being installed on VMware… hahah), I tracked down the issue. In the installation guide it says to use a hard drive that has a minimum of 160GB of space. I made a drive that had exactly 160GB. This was the problem. The successful workstation VM I created had a hard drive of 165GB. I went back and increased the size of the vSphere VM to 165GB and voila! Success. Hopefully this saves someone some time and trouble with virtualizing WHS “Vail”.
EDIT: 2011/04/14 – I’m working on another method of doing this since it appears that this only works sporadically or no longer works as written. I will update this post if I can figure out where the disconnect / issues are.
I’ve been experimenting with creating a good Windows Server 2008 R2 template for VMware vSphere 4 and wondered just how many times Microsoft would allow an activation on the same MSDN license key (Multiple Activation) for the OS. I often deploy multiple servers at a time and am always fearful of activating since I don’t want the key to be shut off. Typically I only run these servers for short periods of time so not activating is no big deal, however in longer running projects I often have no choice but to either activate or destroy and redeploy. With information that I’ve come across on the Internet, I’ve managed to consolidate a method that does not break the Windows Server 2008 activation, while still sysprep’ing and generating a new SID.
This process can be used for other virtualized environments as well I’m sure, but in this case I created it for VMware vSphere.
Continue reading Creating an Activated Windows Server 2008 R2 VMware Template using Microsoft Sysprep
This is a quick post, or maybe not so quick, just to illustrate how to create and add records to a DNS zone on your own Windows Server with the DNS role configured. This server can be a domain controller with DNS installed or just a DNS server, it doesn’t make any difference.
A quick primer on DNS. DNS, or domain name servers (services), provides the ability for servers to access systems by name instead of IP address. Without DNS servers, we would all have to navigate the Internet by typing in IP addresses, like http://126.96.36.199. From reading this link, you’d have no idea where you were navigating to, but it just so happens that this is one of Google’s many public IP addresses. Try it.
Continue reading Creating and Managing a DNS Zone Using Windows Server + Quick DNS Primer
Have you tried rebooting?
I ran across an issue on Windows Server 2008 R2 but also found the issue to happen on Windows 7 installations.
Apparently this will be fixed in the R2 releases of SQL but since those aren’t available yet for the enterprise and similar versions, there’s a pretty simple fix. I found an article that references a few fixes that I’ll link to here in case the fix that I have doesn’t work.
The error states that “Invoke or BeginInvoke cannot be called on a control until the window handle has been created.”
Continue reading SQL Server 2008 Installer Fails on Windows 7 and Windows Server 2008 R2
As I’ve upgraded my lab environment to vSphere over the weekend, I’ve been running across the occasional VM that fails to allow me to upgrade it’s VMware Tools. This seems to be predominantly happening with my Windows Server 2008 VMs.
I’ve received various error messages including ‘can’t find vmware tools.msi’ looking at c:windowsinstallers, and messages stating that Installation cannnot continue because a previous version is installed, even though it had just been removed. FRUSTRATING! Fortunately, this isn’t the first time people are running across it and there’s a VMware KB article on how to address this.
Issues as noted on the VMware KB:
- Unable to upgrade existing VMware Tools
- Unable to upgrade existing installation of VMware Tools because the previous installation fails to be removed
- The uninstall feature of VMware Tools fails to complete, and finally
- Cannot uninstall VMware Tools.
All this boils down to ‘IT’S BROKE! HOW CAN I FIX IT!?’
Continue reading VMware Tools Fail During Upgrade / Uninstall