RE: Problems with GPO's after changing domain name in windows 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Steven Liu (stevenl_at_online.microsoft.com)
Date: 02/13/04 

Date: Fri, 13 Feb 2004 05:21:11 GMT

Hi Dominic,

I think you probably forgot to follow the section of "Step-by-Step Guide to
Implementing Domain Rename", avalaible at
http://www.microsoft.com/windowsserver2003/downloads/domainrename.mspx,
which says:

STEP 12: Fix Group Policy Objects and Links

In this step, you will use the gpfixup.exe command-line tool to repair
Group Policy objects (GPOs) as well as GPO references in each renamed
domain. It is necessary to repair the GPOs and the Group Policy links after
a domain rename operation to update the old domain name embedded in these
GPOs and their links. This procedure is necessary so that Group Policy
continues to function normally in the new forest after the domain rename
operation has completed. The tool also repairs any Group Policy-based
Software Installation and Maintenance data (such as Software Distribution
Point network paths), if present in Active Directory, so that managed
software deployment continues to work in your environment. The GPO and link
fix-up tool needs to be run once in each renamed domain. There is no GPO
and link fix-up required corresponding to renamed application directory
partitions because you cannot apply Group Policy to an application
directory partition.

RESOLUTION:
===========

1- Download the DomainRename Tool from:
http://www.microsoft.com/windowsserver2003/downloads/domainrename.mspx

2- At the command prompt, browse to the location that you extracted the
domainrename tools and type the following command (the entire command must
be typed on a single line) and press ENTER:

gpfixup /olddns:OldDomainDnsName /newdns:NewDomainDNSName
/oldnb:OldDomainNetBIOSName /newnb:NewDomainNetBIOSName /dc:DcDnsName 2>&1
>gpfixup.log

-Where-

OldDomainDnsName is the old DNS name of the renamed domain.
NewDomainDnsName is the new DNS name of the renamed domain.
OldDomainNetBIOSName is the old NetBIOS name of the renamed domain.
NewDomainNetBIOSName is the new NetBIOS name of the renamed domain.
DcDnsName is the DNS host name of a domain controller in the renamed
domain, preferably the PDC emulator.

Thanks for using Microsoft Newsgroup!

Sincerely,

Steven Liu [MSFT]

Microsoft Online Partner Support

MCSE 2000

Get Secure! - www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.

Relevant Pages

  • RE: Problems with GPOs after changing domain name in windows 2003
    ... Fix Group Policy Objects and Links ... It is necessary to repair the GPOs and the Group ... >a domain rename operation to update the old domain name ... >2- At the command prompt, browse to the location that you ...
    (microsoft.public.windows.server.migration)
  • Re: group policies
    ... That can not be done via Group Policy. ... That is a ntfs permission issue. ... the users have modify rights to the file then they can rename it. ...
    (microsoft.public.win2000.security)
  • adding group policy to new OU
    ... If I add and rename a group policy object to a newly created OU from an old ... does any of the changes effect the old OU or is the changes only applied ...
    (microsoft.public.win2000.group_policy)
  • Re: Great SWT Program
    ... a good tutorial on Unix CLI tools? ... command there, ... then rename everything in the search scope with the CLI, ... I'd have to boot up a Windows system and try stuff, ...
    (comp.lang.java.programmer)
  • Re: How To Make index.shtml As A Home Page?
    ... is the correct command, but will only be effective if AllowOverride All ... overridden (provided AllowOverride is set) using .htaccess as you have done. ... > DirectoryIndex index.shtml index.html index.htm index.php ... you should be able to open your online web in FrontPage and rename ...
    (microsoft.public.frontpage.client)