Start a Conversation

lkgardner

updated

16 years ago

Solved!

Go to Solution
L

lkgardner

7 Posts

0

5753

October 25th, 2010 17:00

Joining Domain problems

Hi, and thanks for any help that I can get.

I am having problems getting new VDI machines to join the domain.

If I create the VDI and login, I can join the domain with the same username\password that I use in the sysprep files. So not a rights issue.

I have had the template used be both join to the domain and not joined and that seems to make no difference. I have played with Netbios features and that does not help. The VDI does get a valid IP via DHCP.

The DNS name changes but does not join.

Any ideas?

Thanks

lg

  • L

    lkgardner

    7 Posts

    940

    1

    Posted November 3rd, 2010 14:00

    Solution, I think.

    To join domain make sure the following are in place.

    • There are not GPO's that would hinder communication. (My AD was pushing firewall restrictions down)
    • Enter a valid CD-key with Win 7 even if you are using KMS.
    • Use a admin password that Windows likes. (a very strong one)
    • Make sure the AD DNS can be seen. (We use a different DNS for non-domain machines)
    • Of course make sure that the domain user has the correct rights to join machines to the domain.
  • DM

    Dell-Matt-E

    57 Posts

    1030

    0

    Posted October 25th, 2010 17:00

    Can you provide more detail? What OS is the VDI machine? What is your Hypervisor?

  • L

    lkgardner

    7 Posts

    1032

    0

    Posted October 25th, 2010 18:00

    It appears to me that with Windows 7, the only option I have is Quest Sysprep. I could be wrong. Is that true? When I specific Win 7 as the sysprep OS, the VMware option is not available.

  • L

    lkgardner

    7 Posts

    1032

    0

    Posted October 25th, 2010 18:00

    Opps, fairly new at this.

    The template is both Windows 7x86 and X64 on a VMware V4 system.  

  • DM

    Dell-Matt-E

    57 Posts

    1032

    0

    Posted October 25th, 2010 18:00

    Are you using VMware’s Sysprep or Quest Sysprep?

  • DM

    Dell-Matt-E

    57 Posts

    1032

    0

    Posted October 25th, 2010 22:00

    I think there are some limitations with vSphere and its support for Windows 7, I don’t recall off the top of my head. When you specify the domain to join are you entering the full name, e.g. gardner.local rather than just gardner, or that what you meant by playing with the Netbios settings?
    Also, which version of vWorkspace are you using and is PNTools installed in the template? PNTools need to be installed in the template for this to work.
  • L

    lkgardner

    7 Posts

    1032

    0

    Posted October 26th, 2010 01:00

    Thanks Matt for your suggestions.

    I have specific the domain in both formats (domain and domain.suu.edu). Neither works for me.

    I deal with the firewall from hades and so I have played with the IPv4 settings, changing the defaults in the Wins tab from default to 'enable' NetBIOS over TCP/IP, to disable the same, to changing the DNS suffixes and everything in beteen.

    I am using the 7.1 MR1 ( 7.1.369) but have also tried the 7.1.358 version. My connection broker is version 7.1.301.358.

    The machines are created in VM nicely and rename but do not join the domain. I suspect something in my sysprep.

    Thanks again

  • L

    lkgardner

    7 Posts

    1032

    0

    Posted October 26th, 2010 01:00

    Yes, 7.1.369

  • L

    lkgardner

    7 Posts

    1032

    0

    Posted October 26th, 2010 01:00

    Do you recommend or use an unattend.xml file?

  • DM

    Dell-Matt-E

    57 Posts

    159

    0

    Posted October 26th, 2010 01:00

    I always just build my XML through the wizard and it works fine. It would be worth opening a support ticket.

Dell Support Resources

Latest Solutions

View More