BDD and WINS

BDD and WINS (Full Version)

All Forums >> [Management Products] >> Operating System Deployment

Message

EdwardKK -> BDD and WINS (4/28/2008 2:02:08 PM)
Hi all! We are a pure Win 2k3 and XP shop here, as a result we do NOT have WINS running. I'm asking my machines that are imaged to join my domain. The images load fine, and run through the initial setup loading the network settings, etc. But they fail a moment or two later when they try to join the domain. If I try to manually join the domain at this point, it still fails. If I tell it to go on and join the domain later, it will finish loading and eventually I can go into windows and join the domain (without a reboot mind you) with the same accounts. At first I thought it was a driver issue, and later that I had screwed up entering the password for my account that has rights to join the domain. But when I setup a temporary WINS server and had DHCP hand out the WINS server to clients, the problem went away. I found this article http://technet.microsoft.com/en-us/library/bb978352.aspx and was shocked to learn that Microsoft would build BDD to expect WINS to exist in an AD environment as it just seems SOOO 1990's. I've seen the articles about adding a LMHOSTS file to my WinPE disks, but frankly, I don't have a problem in WinPE, it's in XP when I get this error. And the system can resolve the domain just FINE 5 minutes later after it finishes the app installs etc. BDD is able to resolve all my servers and install software etc, it just can't join the domain. Does anyone have any advice on what I might need to do to get my imaged machines to join the domain without WINS?

rbennett806 -> RE: BDD and WINS (4/28/2008 4:20:18 PM)
Are you sure you entered Fully Qualified Domain Names (FQDNs) where prompted for server names and such throughout your configuration of your BDD environment? Make sure the machine is trying to use YYYY.XXX.XXX and not simply YYYY for name resolution. Also, have you tried migrating to the newer MDT 2008? I don't know for sure that this got touched from BDD 2007, but it might be something to look into...

EdwardKK -> RE: BDD and WINS (4/28/2008 6:30:38 PM)
Yes to both. I downloaded the BDD tools just a few weeks ago, so they should be the latest. Also, I've tried to do EVERYTHING via FQDN and with basic netb names as well just trying to get it to work. WINS solved it. But frankly, I can't figure out why I would need it. I'm going back into try to resolve it all again, but it's really annoying.

rbennett806 -> RE: BDD and WINS (4/30/2008 9:55:26 PM)
Well first off, BDD and MDT are two separeat toolkits. MDT is the one I'd say to test. Secondly, I'm assuming that everything else is resolving IP to FQDNs just fine, so have you gone back through your setup and made sure that you don't have a typo in something like the OU path or maybe the domain name or something?

EdwardKK -> RE: BDD and WINS (5/6/2008 1:17:46 PM)
Sorry, I said that wrong. I'm using MDT build 4.1.423.0. I checked the FQDNs, and can't find any typos. And yeah, things seem to resolve other FQDNs just peachy. My MDT/SMS box is in another AD site, but I have a local DC with DNS providing the DHCP scopes. it's really weird. The exact same machine I built the image on (a dell d630) could not join the domain, so I KNOW the image has the drivers. Even if Driver injection is failing it shouldn't matter because all the NIC Drivers for that OS and machine were built into the image when that image was captured. When I added WINS, it worked just fine. Could it be a format for the domain that I'm screwing up? I'm using "dom.domain.com" as the format. We have a big forest so it's not just a simple domain.com format, but has a couple levels to it. But frankly, thats the domain format I use to join the machine manually, and it works great. But having said that my FQDNs are all perfect, I seem to have problems with Driver injection on other platforms as well, so there's got to be something else going on. I've got an Optiplex 755 that just will NOT inject drivers and as a result, after imaging I just get bluescreens. WinPE seems to be pulling all the settings needed from the FQDN of my MDT/SMS box, but when it flashes the "driver injection" notice in ZTI it's going way too fast to pull them down. But the FQDN for my resource root is indentical to the FQDN used in my bootstrap.ini and other settings used to query the MDT databases, the only difference being the drive share. So SOMETHING weird is going on here that i can't seem to find.

EdwardKK -> RE: BDD and WINS (5/6/2008 1:50:28 PM)
heres an interesting thought. When booting my WinPE CD for OSD, I've set it up so I can select the program i want run from the SMS OSD package. This is so i can keep an eye on it, and troubleshoot as I go along. Sometimes when I select the package and click next I get an error that the deployment point can't be found for that package. if I just click OK, and wait a moment, and click next again, things fly. it doesn't happen all the time, and I blew it off (somedays I'm blonder than others). I wonder if I'm running into a networking problem where some of my systems are unable to resolve in time since my SMS/MDT server are not local to my environment. is there a way I can increast a timeout someplace? Thanks

rbennett806 -> RE: BDD and WINS (5/6/2008 5:14:59 PM)
Firts off, domain information... You're using the right stuff ChildDomain.Domain.com. I seem to fuzzily remember running across a post on this site (probably in the SMS 2003 forums) about someone needing to add a sleep command into the ZTI scripts so that it acquired a valid IP address (not sure how old that post was though). So maybe what's happening is that your machine isn't fully on the network before it tries to contact things? Of course, that may not be what's happening. You mention driver issues several times, so when you create your reference machine, prior to capturing it, do you delete the C:\Windows\INF\OEM.inf and OEM.pnf files? This will ensure that all your hardware devices will be discovered again - I've seen some oddities when these files arne't removed before capturing the .WIM image. Oh, and on your 755, make sure you inject the SATA driver - otherwise nothing else will work because it can't contact the hard disc drive. have you double-checked the account information on your Operating System image package? Make sure you've got the right username and password set there and that that account still has rights to join the domain (remember if you change it to update everything and build a new OS Installation CD). Have you been able to image any machines at all? Or is this a recent problem?

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.2030029