Universally_challenged

sorry, i thought i put a reply up. The machine now has 2 new drives in it. and the only error in the event log is a Kerbos one. -------------------------------------- Event Type: Error Event Source: Kerberos Event Category: None Event ID: 3 Date: 07/05/2011 Time: 14:05:20 User: N/A Computer: S****1 Description: A Kerberos Error Message was received: on logon session Client Time: Server Time: 13:5:20.0000 5/7/2011 Z Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN Extended Error: Client Realm: Client Name: Server Realm: ********.****.SCH.UK Server Name: s****1.********.****.sch.uk Target Name: s****1.********.sch.uk@********.****.SCH.UK Error Text: File: 9 Line: b22 Error Data is in record data. For more information, see Help and Support Center at Events and Errors Message Center: Basic Search. ------------------------------------------------ Im led to believe that this could be due to DNS Problems. (which have been about for a while.) I have demoted the second DC and removed DNS off of that a couple of days ago, so were are just down to this one. The second DNS is still showing in the DNS records as a name server. should i remove this or will ir go by itsself. I know NOTHING anoud DNS, its just self learning black magic to me. So where do you start about trouble shooting it? is there a way to just factory fresh it?

as of yet i still havent nailed this one. sorted the DCOM errors. have kerberos and other errors now. this has to be something simple.....

@bodminman Was just reading up on these two. seems to be conflicting infomation ref the DHCP. Do you thing i should create a Domain Admin account just for this and enter the credentials?

I have re-installed the software that the DCOM errors were refering to and they have stopped. I wiped the system event log and restarted the DC a short time ago. now i have these errors. ----------------------------------------------- Event Type: Warning Event Source: WinRM Event Category: None Event ID: 10154 Date: 03/05/2011 Time: 22:03:37 User: N/A Computer: STGRG1 Description: The WinRM service failed to create the following SPNs: WSMAN/stgrg1.stgrgb16.bham.sch.uk; WSMAN/stgrg1. Additional Data The error received was 8344: Insufficient access rights to perform the operation. . User Action The SPNs can be created by an administrator using setspn.exe utility. For more information, see Help and Support Center at Events and Errors Message Center: Basic Search. ---------------------------------------------------- and this one ---------------------------------------------------------- Event Type: Warning Event Source: DhcpServer Event Category: None Event ID: 1056 Date: 03/05/2011 Time: 22:03:45 User: N/A Computer: STGRG1 Description: The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service. This is not a recommended security configuration. Credentials for Dynamic DNS registrations may be configured using the command line "netsh dhcp server set dnscredentials" or via the DHCP Administrative tool. For more information, see Help and Support Center at Events and Errors Message Center: Basic Search. Data: 0000: 00 00 00 00 ....

@bodminman - yes, if i look in the dhcp records for the machines IP your straight in. Go via machine name and something your connected to a totally different machine. @Dos_Box - i was way to busy that day and was maybe hoping that would have been why the system was so unresponsive... I recall it having a bad restart that morning due to just every app /servicve/ you name it just not responding.. it was probably just resyncing the drives after a abrupt restart. Drives since then have checked All Ok

Hi Guys. I think this is my first post here, but i have watched for a while. Anyway, I'll cut to the chase. Last week was the first day back for our kids at our primary school. During the holidays i had re-imaged Every machine in school, upgraded the Nics and memory etc... Everything seemed fine untill the first day back. Despite having every machine up and installing software etc the day before (which was hunkey-dorey) everything just ground to a holt as soon at the teachers and kids hit. FYI The users have redirected folders, no roaming profiles. The XP clients were sat on "Preparing Network Connections" or "applying Computer Settings" for nearly 30 minutes before the logon dialogue appeared. Then logon would take a good 20 minutes too. When you were in there was problems with shares, they would just come and go. The DC its self was a 40 minute wait to logon aswell. and once you were in is was dog slow. Yet memory usage was normal, network traffic and processors were next to nothing. The Raid of this server was for some reason rebuilding its self. I sort of put it down to that, and next day everything seemed normal again. But today the same thing............. When i got the call it was a 20 minute logon to the DC, i rebooted it and could logon as normal, 5 seconds or so but after an hour it all went to pot again. A friend thinks its a DNS problem as of late we have had a few cases of Machine names not resolving to the correct IP's The Clients are XP SP3 and W7 SP1 2 DC's running DNS and one of those does the DHCP. After looking around on here i have tried adding the domain name to section 15 In the DHCP settings Deleted all the client entries from both DNS servers. Added the second DNS to the DHCP Settings Changed DHCP to force DNS updates if the client doesnt request them. Scavinaged Both DNS's for stale records. I will add to the note that the DC has alot of DCOM errors in the Event viewer which i cant get to the bottom of. Error 10016. Could this be to blame? Unfortunatly, i cant seem to wake any of the clients remotly for some reason so i dont know if any of this has helped. Your thoughts?

hey reggiep. all sorted now.

Hi guys. i put my first Fog server in a production enviroment the day before this was released. anyway, does anybody use the "rename host" function. Im finding its borked my AD. The images are syspreped and set to automaticly join the domain. Then FOG's client gets involved and changes the host name, which changes it locally, but not in the AD causing me to have to leave, and then rejoin the domain after deleting the computer out of the AD. As it never promps for and AD authentication im guessing its just some forced reg injection. I know the FOG client can add a machine to a domain, but i'd rather sysprep did it. But would this solve the problem? Thoughts.....