Free Windows Admin Tool Kit Click here and download it now July 10th, 2012 1:02pm Yes ! Also tried different OU, no OU (so it would go in Computers), still not working. I put that in a variable that I created and called OSDDomainName ... ...the problem is that OSDDomainName is also a system variable used by SCCM and the Task Sequences...so that So instead of 'mydomain' ise 'mydomain.domain.com' gordo Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 31 Jan 2007 Online Status: Offline Posts: 2 QuoteReply this page
It assumes command-support is enabled in your boot image. 1. Could that be a problem with the unattend.xml that I use while creating the base image ? Once copied, I can open it up to see what was passed to it. Writing configuration information to C:\Windows\panther\unattend\unattend.xml Successfully saved configuration information to C:\Windows\panther\unattend\unattend.xml Configuring "OSDNetSettings.exe finalize" to run on first bootOSDNetSettings finished: 0x00000000.
If I didn't use the variable to join one domain, it worked. As soon as I started using the variable again, it failed... I map a drive so I can copy the unattend (Personal Preference here - I find it easier to view the .xml file from my computer rather than on the machine
Do I need something special in there ? Or is it really something on the network that could prevent OSD from reaching the DC even if it can be pinged but would not allow OSD to communicate to add I do the below to grab unattend. Dsgetdcname Failed 0x54b Thanks, Gordo Support Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Moderator Group Joined: 09 Nov 2006 Location: United Kingdom Online Status: Offline Posts:
we have 2 domains so I asked a question before the TS to select the domain. The Machine Attempted To Join The Domain But Failed. The Error Code Was 5 I also tried to recreate and recapture the Base image, with no luck. I just renamed the OSDDomainName variable I used to something else and it started working again....! I am kinda stuck right now so thanks for all the input you can bring J July 10th, 2012 11:39am Typically this error signifies network, DNS, or WINS issue.
I have seen this before when I missed a period in my FQDN. Error 1355 The Specified Domain Easy remote access of Windows 10, 7, 8, XP, 2008, 2000, and Vista Computers Click here to find out more Reboot Hundreds of computers, disable flash drives, deploy power managements settings. July 10th, 2012 3:13pm One item to try is grab the unattend.xml before it runs mini-setup. Check the configuration of the existing DNS server, as discussed in the User Guide in the "Troubleshooting" chapter under 'Finding Domain Controller Fails/ “The RPC server is unavailable”' One other
Over 25 plugins to make your life easier Forum Home > ForensiT Support > Domain Migration Active Topics FAQ Search Calendar Register Login Joining to Domain Fails - Error No further replies will be accepted. The Machine Attempted To Join The Domain But Failed. The Error Code Was 1332 I copy the unattend.xml from <
Free Windows Admin Tool Kit Click here and download it now July 10th, 2012 4:04pm I actually figured it out ... I do suspect that we have some DNS issues on our network. Performing global configuration only. Post Reply Forum Jump -- Select Forum -- Product Announcements Domain Migration Desktop Management Move Computer Forum Permissions You cannot post new topics in this forumYou cannot reply to topics in Event Id 4097 Error Code 1355
July 13th, 2012 9:48am I actually figured it out ... Even when the PC boots up at the end (but not on the domain) the network drivers are present and working so I dont think it is a NIC driver issue Are you using FQDN when you point out you domain name? Get More Info Also, I have read at some places that you might need to include a "." at the end so our domain FQDN is something like : something.company.lan I tried something.company.lan.
I always end up with the following in the Task Sequence event log : ==============================[ OSDNetSettings.exe ]=========================== Command line: "osdnetsettings.exe" configure Setting %SystemRoot% to "C:\Windows" Loading existing answer file "C:\Windows\panther\unattend\unattend.xml" Configuring Unable To Join Gdwerror 0x54b I am trying to apply this image in another Task Sequence (on a Lenovo M90P) and have the machine join the domain and cant get it to work. I can also test other settings by editing it directly and replacing the one on the build machine.
Concerning the No Adapters found in environment, I suspected a problem with the NIC driver so I checked the network settings using F8 and when the join domain command runs, I Now, when i'm trying to join a machine to a domain, I'm getting: Joining to Domain "
Other recent topics Remote Administration For Windows. Click here to get your free copy of Network Administrator. This helped me one time when the join account I was passing was not formatted correctly and prevented the machine from joining the domain. That way you can see if it is being updated correctly with the information you want.
we have 2 domains so I asked a question before the TS to select the domain. July 10th, 2012 1:07pm 1355 means the specified domain either does not exist or could not be contacted. If I didn't use the variable to join one domain, it worked. As soon as I started using the variable again, it failed...
After the image is applied, I press F8 for the command prompt 2. I put that in a variable that I created and called OSDDomainName ... ...the problem is that OSDDomainName is also a system variable used by SCCM and the Task Sequences...so that What's interesting is that I can successfully join the machine to the domain manually, it only fails when I try to join using the User Prfile Wizard. Home Forum Archives About Subscribe Network Steve Technology Tips and News Can't get machine to join the domain / error 1355 Hello, I have created a Task Sequence
I also checked the following log file and here is what I have C:\Windows\panther\unattendGC\setupact.LOG Error [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is  Error [DJOIN.EXE] Unattended Join: Unable to join;