Discussion Locked

Cloning Group Policies etc

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have PROD, TEST & DEV Windows 2000 environments. We need to keep these in sync. Has anyone done much work on tools or processes for cloning, including cloning to an isolated (non-connected) domain. We need to duplicate everything GP, OU, sec templates, sysvol, groups, members etc.

Any ideas?

9 replies

by abubin

why don't u check out Ghost? I heard the new version will create a different SID for your machine.

Also, since it is so isolated, have you tried duplicating the whole HDD? If the domain does not conflict one another then having the same SID mightnot cause a thing.

by expertpc

Real time cloning.....Very unique request

2 ideas

clone the machines one time as a base line.

1. Use your nightly backups on the main servers and restore them to the cloned systems (REAL SLOW AND A GREAT PAIN)

2. RAID 1-MIRRORING all your drives with HARDWARE RAID. Every morning yank one of the drives and plop them into your cloned systems. Rebuild from the new drive. (VERY EXPENSIVE AND A GREAT PAIN) There are lots of things to consider if you go this route, your system has to support hot swapable drives, the RAID configurations have to be identical and not store the RAID info on the drives (Compaq's do this), potential system instability form repeated loss of drives, ect.

As a Network Admin, I personally would never ever do either of these do to the very possible destruction of the production environment.

Why do you need this? This will help in determining a different course of action.

by tom.dutkowski

W2K with AD is much different to NT4. The potential for stuff-up is much higher. This means that a rigorous change and config management regime must be put in place. Any changes must be tested in DEV (isolated) than promoted to TEST and finally PROD. It is essential that all these environments are as identical as possible, so that the testing is valid.
Ripping the drives out would work from PROD to DEV, but not PROD to TEST as both are on the same wire. (apart from the no-no of touching production systems)
Tape copies face the same problems and are too slow as well
From experience, creation of Group policies (as an example) is manual, and prone to error. It is just about impossible to create the same Group Policy on two seperate environments.
Scripting is a possibility, but will take some time (est 200 hours), but a tool would be better.
Cheers

by expertpc

Here is a new idea (for me at least)

add both the Test (GROUP)and Dev (GROUP)machines to your existing Prod domain (After you have striped them of any AD stuff). DCPROMO one server from each GROUP and make them DC's in the PROD domain. After all replication has taken place, physically/network isolate your groups from the domain.

Have each group on their own switch/hub. When you want to isolate, remove the uplinks to the Prod and other domain/groups. I would also suggest diferent subnets but then you are bringing in a router. This would help in the DNS and DHCP departments.

Now you have 3 seperate yet identical domains. You will have to play with DNS and DHCP here. Also make ABSOLUTELY SURE that your domains (all called PROD) are physically unable to communicate with the Main PROD domain. Make sure you transfer all the FSMO roles to the servers in question so that they all function properly.

Even though you will not be able to change the Domain name you will have identical environments, RID's, GPO's, etc.

If you ever have to reconnect the domains, make sure you do a DCPROMO to take down the DC's and whatever changes you have done to date.

This method will leave some dead entries in the AD in reference to the orphaned DC's. You will have to go through and clear out the entries using various MMC's

Good Hunting.

If you have any questions or want better clarification, email me at my username.

by shanghai sam

Pat, thanks for your responses. Your proposal has some merit, but misses some major points.
DEV is isolated, but we want TEST to be on the same wire as PROD, so we can test with real users in a real connected environment (Unix DNS, Exchange, Internet, aminframes etc). So there cannot be 2 PRODS.
Also your method only gives us a snapshot, whereas we want to have daily syncs. From experience working with the AD (for example creating/modifying GPO's)is a manual, time-consuming and error prone process. You can never get the same results twice.

Cheers

by mktz

Ithink i have some things that might help one product is called fazam which can back up and restore your total group policy and security settings i was told that it came free with the resource kit but have yet to find it. I dont have the address forthe site but you can also download a limited version from microsoft. As far as cloning rapid deploy from alriris works good but a machine has to come down good luck

by tom.dutkowski

We have tried FAZAM V1.2 (Full Version) and found a number of shortcomings. Some of these are to be addressed in the next FAZAM version, but some of these are because of Microsoft AD design.

This discussion is closed to new replies.