Migrating GPO's between different domains

If we need to carry policies from one Active Directory to another and we don't have a trust relationship, or there is no possible communication between them, we could make a backup of the GPO's that we are interested in in the source domain and import them through the migration tables in the destination domain. This document is valid for migrating GPO's between any version of Windows Server, since 2000, 2003, 2003 R2, 2008 or 2008 R2; In this document we will see how to perform these steps.

FAQ: OWA directory redirection in TMG

We will perform the following steps if we want our users not to have to write the /owa directory in Exchange, if we are using Microsoft Forefront Threat Management Gateway (TMG) 2010. 1º Create the rule to allow OWA to https://correo.midominio.com/owa (HTTP://www.bujarra.com/?p=4862). 2º Copy & Paste that rule into the TMG. Rename it and give it a correct name. 3º Edit it, from your properties: – On the “Action” put 'Deny'’ and redirect http to 'https://correo.midominio.com/owa'. – On the “Paths” delete all paths and create one with the following settings: External path: <same as internal> Internal path: /

Data Migration between 2 Untrusted domains (Subinacl)

In some not very frequent cases we find domain migrations in which we do not have permissions to manage the current domain completely and only access to OUs where we manage only the users within them. In the event that we need “Becoming independent” and migrate the data to a new domain, we will not be able to use Microsoft's common tools such as FSMT since they require a trust relationship to be able to pass the permissions. The first thing we must have is to create the same users and groups on the new server. To do this, we have two options: Create them by hand or use a tool such as ldifde that will allow us to export them from the OUs we have permissions to a text file and import them into the new domain. As there is no trust relationship, we will not have the same SIDs in the users of the domain 1 and mastery 2 so when performing […]

Installing SQL Server 2008 in Windows cluster 2008 R2

In this document, we'll look at installing a SQL Server cluster 2008 under two Windows Server nodes 2008 R2, we will install both nodes to obtain a SQL Server service in high availability. First of all, you have your Windows cluster 2008 R2 mounted and well configured, to which we will have several disks available for the databases, Logs, backup and MSTDC (We can rely on to create the cluster: HTTP://www.bujarra.com/?p=2290).

Exporting and Importing Mailboxes or PST Files into Microsoft Exchange 2010 SP1

Prior to Exchange 2010 SP1 we used the Export-Mailbox command (Exchange 2007 and Exchange 2010) o Dive (Exchange 2003) to export our mailboxes to PST's files. Thanks to Exchange SP1 2010 we'll use 'New-MailboxExportRequest’ and it will therefore not be necessary to have any Outlook on premises. We will perform this procedure on an Exchange server 2010 SP1, We will have to indicate which user or group will be in charge of carrying out these imports or exports, so we will have to add the role of 'Mailbox Import Export'. Otherwise, by default members of the 'Organization Management'’ will have such roles.

Migrating ISA Server 2006 to Microsoft TMG 2010

Those of us who need to upgrade or migrate our previous ISA environments to the new Microsoft product, called Forefront TMG we will need to perform a migration by import/export configuration, since Forefront TMG only works under 64bit systems or Windows 2008 SP2 or R2 and we will not be able to upgrade it from an earlier version of ISA Server, be ISA 2004 or ISA 2006 (since they run on x86). We will also have to manually export the certificates along with their private key to the TMG, since this process simply migrates the configuration.

Configuring Debian+Apache as an OWA Reverse Proxy in DMZ

If we have an Exchange installation and we want to publish OWA abroad, we should never open the ports directly to our Exchange, for this there are proxies located in the DMZ that will present us with our OWA. In this case we are going to set up a Reverse Proxy with DEBIAN and APACHE. To do this, we start from the fact that we have a debian installed in our DMZ with the port 443 of the WAN pointing at it and allowing the port to pass through 443 from our server to the LAN's Exchange CAS.

Setting up Outlook Anywhere in Microsoft Exchange 2010

In this post we will see how to enable in Microsoft Exchange Server 2010, Outlook Anywhere (formerly called RPC over HTTPS), in order to connect from the outside with our Outlook via HTTPS, an ideal setup for those with mobile devices who use Outlook, we will make a secure connection via SSL to our server or Client Access array, with this we will avoid making VPN connections to open the Outlook. If we do not want to publish our CAS servers directly to the Internet, we will set up a TMG server to make the transfer to us.