Scenario: I have the domain contoso.com with only one DC (with DNS) and I wish to add another one in case something goes wrong. – The first thing that you must have is, of course, the new server where you are going to install your second DC. It’s highly recommended that both servers are working with the latest updates, Windows Server 2003 R2 SP2. And the domain is raised into “Windows 2003” functional level (on this level there are some improvements in many things, including the replications between 2003 servers). – Run the Administration Tool “Manage Your Server” in the new Windows 2003 and add the role “Active Directory” for this server. Domain controller promotion wizard – Configure the server as a DC for an existing domain and follow the instructions in the wizard. You’ll be asked for the credentials of privileged account to add a new server. The account must be a member of the “Domain Admins” group. – After the promotion of the new DC is completed, visit again “Manage your Server” and add the role “DNS Server”, but don’t set any new zone on this server. When you configure it as a DNS server the primary server will replicate the zones with this new server. – Each DC must be pointing to themselves as the first preferred DNS server and the secondary DNS must be the remaining DC. First DC TCP/IP configuration Second DC TCP/IP configuration – […]
For those, like me, who uses several times a day and for different connections the Terminal Services and Remote Desktop knows that is a must having a nice and simple way to manage all the connections. That’s why you probably use the “Remote Desktops” snap-in. This is how I use it in Windows Vista: What if I tell you that you can manage all the connections that you want in your Internet Explorer? And if you’re using Mozilla Firefox or IE7 all the connections can be in you different tabs? Probably have the same functionality as this one, but it’s always good to know the option is there right?. This is really simple and easy. Works with Windows Server 2003 and XP: Using “Add or Remove Programs”, select “Add/Remove Components” and in “Application Server” select “Details”. You will find another list and in “Internet Information Services” select “Details” again and check “Remote Desktop Web Connection”. When the installation starts you’ll be prompted to insert the Windows Server 2003 CD. After the installation is complete you are ready to use your Remote Desktop Connection in the default direction established in IIS: http://localhost/tsweb/ As a best practice, is always recommended that you set your permissions in IIS to not allow anonymous authentication, any other will be fine; and use HTTPS for the communication. Cheers!!
“My DC is online, the TCP/IP it´s OK, the DNS service running but I still cannot make a valid connection with AD! “ This is a problem that can be present in many ways. The most common example is: you have your DC completely configure for Active Directory, the DNS server too, and you try to join a workstation to your domain and the following error appears: An Active Directory Domain Controller for the domain [yourdomain.com] could not be contacted.Ensure that the domain name is typed correctly(…) First of all, the obvious: Check that the connectivity is working fine… the DNS server and the DC both of them responds to PING requests. It’s most likely that if you cannot connect to the domain, the PING requests for the FQDN (such as: ping dcname.yourdomain.com or ping yourdomain.com) will not respond as well… but with the IP parameter should be working… if it’s not, then there’s definitely a connectivity problem, a bad TCP/IP configuration or a firewall within the way . Well, let’s see, this is a problem that can really make you nuts trying to solve it. Let’s assume that you have the correct configuration in your DC and workstations. If you have a DHCP server in you network, check that he is doing his job… giving the correct IP address for the workstations, the subnet mask, the DNS server and the other parameters that you are using. DCDIAG really? Can […]
If you are thinking that you have all the installation requirements for Team Foundation Server, to avoid surprises, check them again: In a clean installation of Windows Server 2003, install all the components in the order that they are listed here: – First of all, the complete enviorenment of TFS in a single-server mode must be in 32bits.– Windows Server 2003 with SP1 or SP2 (R2 optional): Standard, Enterprise and Datacenter editions supported.– Internet Information Services 6.0 with ASP.NET enabled (and no support to Front Page Extensions, they are incompatible with Sharepoint). In addition, IIS must have a default web site.– SQL Server 2005 SP1 or SP2 Standard or Enterprise Edition as the default instance of SQL Server *. If you are not planning to install SP1 on your SQL 2005, the hotfix KB912838 is required for TFS installation.– .Net Framework 2.0 with the hotfix KB913393 installed.– Windows Sharepoint Services 2.0 with SP2. Server-farm type of installation **.– If you are using a firewall check that the appropriate ports are open *. IMPORTANT: The hotfixes for SQL 2005 and .Net Framework you may find it in TFS installation media. You probably may have problems finding the .Net Framework hotfix over the Internet. * For a complete reference and all the components needed to SQL 2005 installation and the ports needed to TFS take a look to the TFS Installation guide at: http://www.microsoft.com/downloads/details.aspx?familyid=E54BF6FF-026B-43A4-ADE4-A690388F310E&displaylang=en** Download Sharepoint Services 2.0 SP2 at http://go.microsoft.com/fwlink/?linkid=55087. Do […]
Hello everyone! This is going to be my new blog where I’ll keep publishing about all the data and technologies that I put my hand in to. http://blog.augustoalvarez.com.ar/ I’ll be migrating old posts to this one in the next few days, and I’ll add a few more articles. We’ll keep in touch! Cheers! Augusto