CC3 Issues

[richbrowncardiff]

Hi Everyone,

 

I'm having a bit of trouble with our cc3 domain. (Pc builds) + intermittent poor pc performance.

 

could anyone please tell me if this config would cause any problems as i am gathering evidence to prove what i have done is not the cause of the issues..

 

here is the config:

 

cc3 domain = FRDC + 2 DC Global cat, DNS Origional DHCP. New 2008 child domain dc global cat (no option as a dc must be a GC server) dhcp has been d-eauthorised form the CC3 FRDC and authorised on the new 2008 child DC. (As I setup wds on the new dc) all entries manually moved and tested. DNS working exactly as it should and no issues.

 

I know everything is working as it should, no errors relating to the child domain in any event logs. Yet because some packages fail to install during the build process and we get intermitent pc performance issues (existing servers are getting battered on disk i/o) I keep getting the blame pointed in my direction.

 

Im not a cc3 expert but surely moving dhcp to a new server (and it working correctly) would not cause these issues ?

 

if i remove the child domain (which looks like it will have to happen) will it remove / alter the dhcp config ? or will i need to reauthorise dhcp on the original server first ?

 

i need to clarify only 1 dhcp is active (also been accused of being stupid and trying to run 2 (which is not the case).

 

any feedback would be much appreciated. Even if i am wrong i just want to know for sure.

 

thanks in advance.

[synaesthesia]

I'd be reasonably certain that DHCP has nothing to do with it. The only way it could, is if the current DHCP server wasn't dishing out addresses quick enough, so connections were not established by the time it came to install packages.

Another common issue on modern networks with CC3 (heh) is computers being *too quick* - they get to the logon screen before network has finished initialising therefore bypassing the rm install agent.

 

We have a fairly identical issue currently however we're pretty much ignoring it for the fact it's going this Summer and I wouldn't expect many CC3 networks to be far behind; it's not suitable for current purpose. Sometimes machines fail to build randomly, sometimes packages refuse to install on the same machine as it installed on fine before, it's daft. Only a flat domain though (3 DC/GC). I dont believe removing the child domain will have an affect on the DHCP config if you wanted to give it a try though - won't hurt to make a note of the settings beforehand, unless they're rather complex

[richbrowncardiff]

Hi thanks for your reply. Nice to know im not stupid. I fully agree with what you say i have been told that we have had build issues for years before i came along.

 

the server hands out ip adreses in double quick time. never misses a beat. All clients get their IP allocated its an RM issue regardinf the build process as dhcp / pxe hand the address out, windows installs etc, packages start to install and then fail, fail, fail in the event logs. / ini files.

 

I know what you mean about pc's being too quick. see it quite often!

 

Cheers

[AngryTechnician]

You're right that it shouldn't cause this problem, but if it's RM support you are dealing with, their standard procedure is to blame your changes for everything. Like it or not, they are not going to help you until you put it back the way they want it.

 

On the plus side, you don't need to have DHCP running on the WDS server for WDS to work. Mine is on a different server and works fine. You will need to configure options 66 and 67 on the existing DHCP server, and untick both options on the DHCP tab of the WDS server properties, but once this is done it should work.

 

Option 066 should be set to the hostname or IP of the WDS server.

Option 067 should (in the default config) be set to boot\x86\wdsnbp.com

 

[richbrowncardiff]

Thanks and yes your right. Not going to do as they say though as in july im removing the CC3 junk and putting a vanilla W7 domain in. The Child is working really well but i am tempted to remove it and start again with a new forest.

 

cant wait ! my network design so my problem (which is fine as i would like to think i know what i'm doing).

 

thanks for your help.