Computer Does Not Join a Domain During Mini-Setup (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message

old_chicago -> Computer Does Not Join a Domain During Mini-Setup (10/6/2008 10:15:24 AM)

I have one remote site that is having difficulties joining a PC to the domain.  They're using the same exact image as 16 other sites (so this shouldn't be an issue on the image).  During Mini-Setup when the client goes to join the PC to the domain (after a 3 to 4 minute wait).  The error indicates that it was unable to join the PC to the domain, do you want to proceed for now and try joining to the domain later. 

09/19 09:38:36 -----------------------------------------------------------------
09/19 09:38:36 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
09/19 09:38:36 NetpCheckNetBiosNameNotInUse: for 'WORKGROUP' returned: 0x858
09/19 09:38:36 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE]  returned 0x858
09/19 09:38:36 NetpValidateName: name 'WORKGROUP' is valid for type 2
09/19 09:38:36 -----------------------------------------------------------------
09/19 09:38:36 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
09/19 09:38:36 NetpCheckNetBiosNameNotInUse: for 'WORKGROUP' returned: 0x858
09/19 09:38:36 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE]  returned 0x858
09/19 09:38:36 NetpValidateName: name 'WORKGROUP' is valid for type 2
09/19 09:38:36 -----------------------------------------------------------------
09/19 09:38:36 NetpDoDomainJoin
09/19 09:38:36 NetpMachineValidToJoin: 'HPDC770REF-PC'
09/19 09:38:36 NetpGetLsaPrimaryDomain: status: 0x0
09/19 09:38:36 NetpMachineValidToJoin: status: 0x0
09/19 09:38:36 NetpJoinWorkgroup: joining computer 'HPDC770REF-PC' to workgroup 'WORKGROUP'
09/19 09:38:36 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
09/19 09:38:36 NetpCheckNetBiosNameNotInUse: for 'WORKGROUP' returned: 0x858
09/19 09:38:36 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE]  returned 0x858
09/19 09:38:36 NetpValidateName: name 'WORKGROUP' is valid for type 2
09/19 09:38:37 NetpSetLsaPrimaryDomain: for 'WORKGROUP' status: 0x0
09/19 09:38:37 NetpControlServices: open service 'NETLOGON' failed: 0x424
09/19 09:38:37 NetpJoinWorkgroup: status:  0x0
09/19 09:38:37 NetpDoDomainJoin: status: 0x0
09/19 09:39:10 -----------------------------------------------------------------
09/19 09:39:10 NetpValidateName: checking to see if 'HPDC770REF-PC' is valid as type 1 name
09/19 09:39:10 NetpCheckNetBiosNameNotInUse for 'HPDC770REF-PC' [MACHINE] returned 0x0
09/19 09:39:10 NetpValidateName: name 'HPDC770REF-PC' is valid for type 1
09/19 10:58:33 -----------------------------------------------------------------
09/19 10:58:33 NetpValidateName: checking to see if 'test.dom' is valid as type 3 name
09/19 10:58:33 NetpCheckDomainNameIsValid for test.dom returned 0x54b
09/19 10:58:33 NetpCheckDomainNameIsValid [ Exists ] for 'test.dom' returned 0x54b
09/20 13:10:49 -----------------------------------------------------------------
09/20 13:10:49 NetpValidateName: checking to see if 'ad.test.com' is valid as type 3 name
09/20 13:10:50 NetpCheckDomainNameIsValid [ Exists ] for 'ad.test.com' returned 0x0
09/20 13:10:50 NetpValidateName: name 'ad.test.com' is valid for type 3
09/20 13:10:57 -----------------------------------------------------------------
09/20 13:10:57 NetpDoDomainJoin
09/20 13:10:57 NetpMachineValidToJoin: 'HPDC770REF-PC'
09/20 13:10:57 NetpGetLsaPrimaryDomain: status: 0x0
09/20 13:10:57 NetpMachineValidToJoin: status: 0x0
09/20 13:10:57 NetpJoinDomain
09/20 13:10:57  Machine: HPDC770REF-PC
09/20 13:10:57  Domain: ad.test.com
09/20 13:10:57  MachineAccountOU: (NULL)
09/20 13:10:57  Account: ad.test.com\rich
09/20 13:10:57  Options: 0x25
09/20 13:10:57  OS Version: 5.1
09/20 13:10:57  Build number: 2600
09/20 13:10:57  ServicePack: Service Pack 2
09/20 13:10:57 NetpValidateName: checking to see if 'ad.test.com' is valid as type 3 name
09/20 13:10:57 NetpCheckDomainNameIsValid [ Exists ] for 'ad.test.com' returned 0x0
09/20 13:10:57 NetpValidateName: name 'ad.pella.com' is valid for type 3
09/20 13:10:57 NetpDsGetDcName: trying to find DC in domain 'ad.test.com', flags: 0x1020
09/20 13:11:13 NetpDsGetDcName: failed to find a DC having account 'HPDC770REF-PC$': 0x525
09/20 13:11:13 NetpDsGetDcName: found DC '\\blah.ad.test.com' in the specified domain
09/20 13:11:13 NetpJoinDomain: status of connecting to dc '\\blah.ad.test.com': 0x0
09/20 13:11:13 NetpGetLsaPrimaryDomain: status: 0x0
09/20 13:11:13 NetpGetDnsHostName: Read NV Hostname: hpdc770ref-pc
09/20 13:11:13 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS domain name: ad.test.com
09/20 13:11:13 NetpLsaOpenSecret: status: 0xc0000034
09/20 13:11:13 NetpGetLsaPrimaryDomain: status: 0x0
09/20 13:11:13 NetpLsaOpenSecret: status: 0xc0000034
09/20 13:11:13 SamLookupNamesInDomain on HPDC770REF-PC$ failed with 0xc0000073
09/20 13:11:13 NetpJoinDomain: status of setting machine password: 0x534
09/20 13:11:13 NetpJoinDomain: initiaing a rollback due to earlier errors
09/20 13:11:13 NetpLsaOpenSecret: status: 0x0
09/20 13:11:13 NetpJoinDomain: rollback: status of deleting secret: 0x0
09/20 13:11:13 NetpJoinDomain: status of disconnecting from '\\blah.ad.test.com': 0x0
09/20 13:11:13 NetpDoDomainJoin: status: 0x534

Any ideas on the cause?

Thanks!

Rich



jsandys -> RE: Computer Does Not Join a Domain During Mini-Setup (10/6/2008 10:34:12 AM)

Don't know what the exact error is, but the key line is:

09/20 13:11:13 SamLookupNamesInDomain on HPDC770REF-PC$ failed with 0xc0000073

Did you specify a container/OU to create the computer objects in?  Did you double-check the credentials of the account specified in the TS to join the domain?  Have you tried alternates for either?



old_chicago -> RE: Computer Does Not Join a Domain During Mini-Setup (10/6/2008 10:39:16 AM)

Hi Jason,

Yes, I'm using the MachineObjectOU property in my CS.ini and have verified the information is correct.  The account specified in the TS is configured in the DBWB of MDT 08 and I'm using a centralized DB, therefore, I know this is configured correctly as all other sites do not have this problem and connect to the domain using the same credentials that are configured in the DB. 

DomainAdmin
DomainAdminDomain
DomainAdminPassword
JoinDomain

The above values are all configured in the DWDB.  I had my tech test a deployment with a vanilla image deployed from MDT and the PC is joining to the domain w/o any issues.

Thanks,

Rich



old_chicago -> RE: Computer Does Not Join a Domain During Mini-Setup (10/8/2008 8:40:03 AM)

This issue has been resolved.  I had found an error that my colleague had made in the CS.ini for the MACHINEOBJECTOU.  He missed a simple ",".

Rich 



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.328125