lquinnuk

Did you install all the software and drivers yourself or are you using the machine as it came? The first two things I'd be looking at are reinstalling your motherboard chipset driver and your graphics card driver.

I thought I'd replied much earlier, evidently not.... That was exactly my thinking as I was leaving, so today I decided to remove the image from the domain and then upl;oad it to the server, initially I got a load of errors and had to defreg the client, after defragging I got a TFTPD error and had to restart the service, but finally the image was uploaded. I am literally right now deploying the image to a machine chosen at random, fingers crossed it will go smoothly. Cheers for all the help.

The AD password is encrypted... "have the necessary files been copied over to the fog client"...unsure what that means "Is fog set to put the computers into an OU or has that box been left blank?" the OU box is blank. Essentially I used my old fog server (which everything worked fine on) imaged a client, I then used that same client to upload the same working image to my new fog server, now the new image is on my new fog server I have tried deploying it to a few clients, which is workign fine apart from this strange domain problem. It's odd because once I remove the machine from the domain and put it in a work group and reboot, FOG has no problems adding the machine by itself once I've logged back in as local admin, the FOG box appears in the right hand corner and 30 seconds later everything is groovy and all works well, its just ideally i'd like to avoid having to add machines to a work group first before FOG adds them to the domain, expecially when my old man FOG server images and joins in one automatic swoop. cheer5s

OK, another snag if anyone would be so kind. After the image has deployed and completed (XP Pro) the machine cannot log in using a domain user account although the log in screen show the correct domains are there to be logged on to, it says my domain controller is unavailable. If I log in as local admin, remove the machine from the domain put it in a workgroup (reboot) When I log back in now FOG tells me the machine needs to join the domain and reboots itself, once it does this everything works fine. TLDR - domain accounts can only be used if I remove and re-add my PC to the domian manually.

Damn, that was embarassingly easy.....I dismissed 'other information' as a useless option. Cheers, Magic.

Hello, The fog server set up by the guy I've taken over is running fine but the server is getting noisy and I'm fearing hardware failure. Due to this I've built and imaged a new FOG server and it's running fine. The issue comes when I add a 'new host' on the old fog server I could click the check box "Join Domain after image task:" and the details would auto populate. On the fog server I have created I have to enter this manually every time I add a new host. Does anyone know why, or how to make this information auto-populate? Cheers in advance.

Hi, Yeah, I've tried \\name\share and \\192.168.1.251\share neither give me much joy. The strange thing is when ever I do try to browse to the drive or map it as a network drive from an admin machine I do get a credentials box to connect to 192.168.1.251 as opposed to the "cannot connect" I was expecting, how ever no matter what or who's credentials I use it never authenticates. I've double checked the share permissions on the folder in question and it is definitely shared to users on both domains, I've added extra groups, ive added different users outside of their groups, no matter who's credentials I use I get nothing?

OK so an update. I've looked into setting up a trust, and it seems that there is already a trust in place between the two domains. Also, the share is hosted on the 'classroom' domain controller, the 'admin' domian controller can see and access the required share (using it as a mapped drive) how do I enable my 'admin' users to access the same share from their machines? Cheers.

Cheers fellow, looks like some good reading, much appreciated, back from half term today so going to give it a try this week, cheers to all of you.

Thanks for the response, I can't say I'm over familiar with trusts but will look into that asap, a small handover note said and I quote.. "There is a trust at 192.168.1.1" Literally all it said, does that make any sort of sense? Cheers

Hi all, first time post! Apologies if this is a common question, I just can't find an answer I can comprehend fully. Basically I have just taken an ICT role in a school and have a snag, I had no real hand over going into the role so am a little unfamiliar with the networks I'm workign with. I have a "classroom" network/domain which is 192.168.1.X, it has two domain controllers/servers running 2008 R2 I have an "admin" network/domain which is 10.49.202.X it has one domain controler/server running 2003 Both networks access the internet through a Forefront server using 192.168.1.252 and 10.49.202.231 respectively. The servers on their relevant networks have some shared folders as you'd imagine, basically, how can I allow machines on my "admin" network to access a staff share on my "classroom" network? I've seen a great deal about VPN's, FTP Servers and Routing tables, but nothing definitive to sink my teeth into. Any help at all massively appreciated.