+ Post New Thread
Results 1 to 5 of 5
O/S Deployment Thread, Very odd - UEFI clients not naming/joining domain - older clients fine in Technical; Hi all, Not much really gets me like this one does but I'm stumped!! I have a right mixed bag ...
  1. #1
    pow
    pow is offline

    Join Date
    Jan 2011
    Location
    Berks/Bucks
    Posts
    8
    Thank Post
    1
    Thanked 2 Times in 2 Posts
    Rep Power
    0

    Very odd - UEFI clients not naming/joining domain - older clients fine

    Hi all,

    Not much really gets me like this one does but I'm stumped!!

    I have a right mixed bag of equipment here that I'm moving all over to Windows 8.1 64 bit from the mixed XP/Vista and 7 32bit environment. I'm using WDS on Server 2012 R2 to help me with this, creating an image for each type of machine with all of the correct drivers preloaded into the image.

    Some of my older kit (Fujitsu Esprimo Desktops, Lenovo ThinkPad 15 Laptops) don't have an EFI BIOS so the install is a standard BIOS 2 partition boot to hard disk install. I name and approve clients, they install no problem and name themselves and join to the domain, so I'm left with a machine that is left that the logon screen ready for my to deploy software via GPO.

    The newer HP ProBooks and Dell Optiplexs here are EFI compatible, so I've switched the BIOS from legacy to EFI mode and they are working beautifully. I had to write a new WDS-Unattend to deal with the new EFI partition structure but that is all working beautifully. I still name and approve these clients in the same way and they install no problem, but prompt me for a computer name and are not joined to the domain - REALLY ANNOYING!

    Can anyone shed any light on this?

    Thanks,

    David.

  2. #2

    AngryTechnician's Avatar
    Join Date
    Oct 2008
    Posts
    3,730
    Thank Post
    698
    Thanked 1,211 Times in 761 Posts
    Rep Power
    394
    Anything telling in the C:\Windows\Panther\setupact.log or C:\Windows\Panther\setuperr.log files? The second should get straight to the point if there's an obvious error occurring.

  3. #3
    pow
    pow is offline

    Join Date
    Jan 2011
    Location
    Berks/Bucks
    Posts
    8
    Thank Post
    1
    Thanked 2 Times in 2 Posts
    Rep Power
    0
    It seems that the EFI clients NEED <ComputerName>%MACHINENAME%</ComputerName> in the XML whereas the BIOS clients just don't care!!! So that's that mystery solved... just to play with the domain join now as I've been pulling the XML file apart!!!!

  4. #4
    pow
    pow is offline

    Join Date
    Jan 2011
    Location
    Berks/Bucks
    Posts
    8
    Thank Post
    1
    Thanked 2 Times in 2 Posts
    Rep Power
    0
    Still having no luck with auto domain join, managed to get it done once but it was still asking for a machine name at that point. Any pointers would be greatly appreciated

  5. #5

    Join Date
    Dec 2011
    Location
    Silverdale, Wa., USA
    Posts
    11
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    POW ... I'm having the same problem. Did you ever get this figured out. (Both the Auto-naming and the Auto-Join Domain) ?

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 15
    Last Post: 19th July 2010, 09:46 AM
  2. Replies: 8
    Last Post: 10th March 2010, 03:46 PM
  3. Replies: 8
    Last Post: 23rd December 2009, 06:05 PM
  4. Replies: 1
    Last Post: 30th November 2009, 06:32 PM
  5. Replies: 3
    Last Post: 15th October 2007, 12:20 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •