garethEds Posted July 6, 2009 Posted July 6, 2009 Morning everyone, Having a little problem with a new RIS server I am building. The previous techician build one the other year and since the server started playing up I decided to rebuild it. Everything seems to be working. I have my flat CD image on the server. I have made sure the AD/DHCP is aware of everything. The machine starts up - F12 blah blah - type in the the username for building (on the Custom option), give the machine name and away it goes. The machine connects to the server and starts installing Windows XP. All the drivers go on (set this up fine). The whole thing then stops and tells me that it cannot connect to the Domain and I am not sure why. It has already connected to the domain and has been put in the correct part of the school OU. I'm thinking I must have missed something somewhere but cannot see what. Any ideas? Many thanks Gareth
cookie_monster Posted July 6, 2009 Posted July 6, 2009 (edited) Is the network driver definatly installing correctly? How close to finishing the install is it when you get this message? Edited July 6, 2009 by cookie_monster 1
garethEds Posted July 6, 2009 Author Posted July 6, 2009 Is the network driver definatly installing correctly? How close to finishing the install is it when you get this message? I'll check the percentage in a moment. But I'll check the driver. I've followed the instuctions for the Intel drivers. Back in a bit... GJE
Guest Guest Posted July 6, 2009 Posted July 6, 2009 Theres only really a couple of places to go wrong here; the answer file (.sif) - is the domain entered corectly here? JoinDomain = %MACHINEDOMAIN% Or the drivers. It can be abit tricky adding drivers manually. Have a look at Autoimage and driver packs RogueSpear's Forums • Index page News | DriverPacks.net
Butuz Posted July 6, 2009 Posted July 6, 2009 Have you changed the password on your build user? (akin to the setup user on CC3?) Just on the offchance Butuz 1
garethEds Posted July 6, 2009 Author Posted July 6, 2009 Right - checked everything. The ris setup user is fine. The drivers are all in the correct place using RogueSpears stuff. I have also applied an update using RyanVM Inegrator and AutoRIS. It adds the machine to the domain during the text setup. 30 minutes left: Machine cannot join the domain. DO I want to continue with the installation. So I am going to let this go through just to see if the driver is missing. I've added everything else. Also got it to work on my virtual test build so cannot see any differences. Will come back later - thanks everyone so far. GJE
garethEds Posted July 6, 2009 Author Posted July 6, 2009 Well what a stupid mistake to make. I was referencing the directories in the $OEM$ folder wrongly. I'd left out a whole directory in one of the paths so.. Drivers\NIC\Pro1000\ should have been Drivers\NIC\Intel\Pro1000 What a stupid mistake to make. Thanks everyone for helping. Gareth
contink Posted July 6, 2009 Posted July 6, 2009 Congrats on finding your mistake.. It's rare that you can see something that on reflection is so obvious but requires a large step back to see. 1
garethEds Posted July 6, 2009 Author Posted July 6, 2009 It doesn't happen often - but even teachers make mistakes ;-))))))) Gareth
Butuz Posted July 6, 2009 Posted July 6, 2009 It doesn't happen often - but even teachers make mistakes ;-))))))) Gareth *bites lip* Butuz
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now