I have a TS to install Windows Server 2003 R2 to a Dell PowerEdge 2650 with Broadcom NICs. The TS seems to have trouble joining the computer to the domain, but everything else seems to work fine. In the TS report, I see the following information: ==============================[OSDNetSettings.exe]=========================== Commandline:"osdnetsettings.exe"configure Initializinganswerfile"C:\sysprep\sysprep.inf" Configuringglobalnetworksettings Jointype:0 Joiningdomain:corp.domain.com JoinOU:LDAP://CN=Computers,DC=corp,DC=domain,DC=com DNSdomain: DNSdomainsearchorder: IPfiltersecenabled:false Noadaptersfoundinenvironment.Performingglobalconfigurationonly. Configuring"OSDNetSettings.exefinalize"torunonfirstboot OSDNetSettingsfinished:0x00000000 I do have network connectivity (I can ping the box the entire time the process is running) so it is on the network during this step. This is showing up in the log before the "Mini Setup" runs, which I thought was odd. The next step shows this: L"",L"",1,1,slstSMBPaths,slstHttpPaths),HRESULT=80040102(e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2598) TS::Utility::ResolveSource(pContent->getContentId(),wcstoul(pContent->getContentVersion(),0,10),pContent->getContentHash(),wcstoul(pContent->getContentHashVersion(),0,10),sSource),HRESULT=80040102(e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\onlinedrivercatalog.cpp,728) pDriverCatalog->resolveSource(pDriver->getContent(),sSource),HRESULT=80040102(e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,615) Failedtofindasuitabledevicedriverfordevice'DELLManagementSCSIProcessorDevice'. Failedtofindasuitabledevicedriverfordevice'Genericvolume'. Failedtofindasuitabledevicedriverfordevice'Genericvolume'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB\4&1A0F8909&0'. Exitingwithreturncode0x00000000 Failedtoresolvecontentfordriver"DellPERCManagementDevice".Code0x80040102 When the computer is deployed, there are no uninstalled drivers/hardware left in Device Manager, and these drivers are added to SCCM. But after the above log goes, it copiesthe SCCM client install files on the machine (I see the executables copy over in the progress bar) and the machine reboots. It then goes into the Windows Mini Setup (part of the "OSDNetSettings.exe Finalize" step I assume), and still does not join the domain. After the Mini Setup runs, the machine reboots and finishes the SCCM client installation. The report shows this during that time frame: ==============================[OSDSetupWindows.exe]=========================== Commandline:"OSDSetupWindows.exe" Foundcommandlinestorunonfirstboot. Executingcommandline:"OSDNetSettings.exefinalize". Commandlineforextension.exeis"%1"%* Setcommandline:"OSDNetSettings.exe"finalize Executingcommandline:"OSDNetSettings.exe"finalize ==============================[OSDNetSettings.exe]=========================== Commandline:"OSDNetSettings.exe"finalize Noadaptersfoundinenvironment.Performingglobalfinalizationonly. Finalizingglobalnetworksettings DNSforWINSenabled: LMHostsfileenabled: WINSscopeID: OSDNetSettingsfinished:0x00000000 Processcompletedwithexitcode0 Successfullyexecutedcommandlines,clearing_SMSTSRunOnFirstBoot. Exitingwithcode0x00000000 The machine then boots into Windows and everything is happy, other than any of the pieces that hinge on Domain membership. I appreciate any help with this at all. Thanks!

See if %SystemRoot%\debug\netsetup.log does contain some errors that might help troubleshooting.

Hi Try joining to a non built in container. David

Both are good points - and lead to some more information. The nesetup.log does not contain any entries until the Mini Setup runs (the second time SCCM tries). I checked the netsetup.log and found some failures about ID mapping, like it was expecting the object to be pre-populated in Active Directory prior to the Task Sequence running. So we pre-populated an object in the "Computers" container and tried again. We get the exact same messages in the SCCM TS report that I posted previously, but the 2nd time it tries (from the Mini Setup) it does join the domain. This also works if the object is pre-populated in another OU (as expected, since the Mini Setup is browsing for the object in ADUC before it joins the domain). But it still shows the "No adapters found in environment" and the driver errors both times (even when the Mini Setup is successful in joining the domain). I then modified the TS to join the domain and add it to an OU (not a built-in container). I did not pre-populate the account in ADUC. Again, the SCCM TS reports show the failures, but it does join the domain (and in the correct OU). But in either scenario, there are some errors in the netsetup.log for each, but they show up in all of our netsetup.log logs (even ones where we manually built the server - no managed deployment). These errors shouldn't have anything to do with the TS failing to join the domain, but here they are: 06/10 15:17:51 NetpLsaOpenSecret: status: 0xc000003406/10 15:17:51 SamLookupNamesInDomain on TESTOSD2650X3$ failed with 0xc000007306/10 15:17:51 NetpJoinDomain: status of setting machine password: 0x53406/10 15:17:51 NetpJoinDomain: initiaing a rollback due to earlier errors This happens three times, and then instead of the "SamLookupNames..." failing you see a"Cracking DNS name..." message and it moves on and works. It almost feels like a driver issue with SCCM, but the drivers are loaded and are working. I know this because neither the NIC nor the RAID controller were drivers that SCCM saw natively. Once I added them into SCCM, I could see both in the SCCM GUI. So since I get a DHCP address when the TS starts and it sees my hard drive on the RAID controller, I would have to think that the drivers are working, but I don't know what else to look at. Your help is greatly appreciated. Thanks! Brandon

Brandon,Did you ever find a solution to this issue? We are experiencing the EXACT same issue with ThinkPad T42, where we experience the "Noadaptersfoundinenvironment.Performingglobalconfigurationonly" Error message.Thanks in advance.

JoinOU:LDAP://CN=Computers,DC=corp,DC=domain,DC=com That's not an OU, it's a container. You can only join OUs during OSD (or leave the OU empty so that the computer account will be created in the computers container).

Good point Thorsten this is a tricky one... Works for me.

Join OU: LDAP://CN=Computers,DC=corp,DC=domain,DC=com That's not an OU, it's a container. You can only join OUs during OSD (or leave the OU empty so that the computer account will be created in the computers container). Torsten, I have been fighting this for the last couple of days. Thank you for clarifying this for me and everyone else that attempted to configure the joining of the domain in this manner. I know that the computers container is not an OU, but didn't even think that SCCM OSD would care that I chose this location instead of an actual OU. Thank you again!!!

Any other ideas if above is not a case and computer does not join the domain while TS OSD 1. i do not set Computers OU, i left it blank 2. the account used to connect to domain is also ok 3. drivers seemt to be ok, i can add to the domain manually but now as a step in TASK SEQUENCE Please help, I am fighting with that the third days and cannot fine the solution. Any help very appreciated.Mariusz Zarzycki