C90LE7 Domain Issues

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #6631
    pilot329
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    Hey guys,

    For some reason, when one of our devices running Windows Embedded Standard 7 joins the domain, it shows up in Active Directory with a completely different hostname then what is shown on the machine itself. As a result, this causes an issue when a domain user logs in. The issue can temporarily be resolved by going into ADSIEdit and changing the PrimaryServiceProvider values to the correct hostname for that particular device. This is quite cumbersome though and should not have to be done.

    I don’t know if this is related but after the machine joins the domain, the machine has a problem shutting down. When a user goes to logoff, a memory reference error appears and prevents the user from logging off. On the other hand, when a person tries to shut down the machine, it hangs on the shutdown screen and fails to shut down. If anyone has any ideas that would be greatly appreciated.

    Below are some additional details regarding the device:
    C90LE7
    Image Version: 9.010806.4096
    HAgent Version: 6.0.0.13
    Windows Embedded Standard 7

    Managed with WDM 4.8 (with the latest hotfixes and patches)

    Attempting to deploy 20 thin client devices (all C90LE7’s), joined to a domain for the sole purposes of authenticating users with DigitalPerson Pro Server for AD biometrics and using the Citrix XenApp Client to access our remote applications. We currently are using a few C90LEW’s that work fine, but we would like to have the latest embedded operating system that will last quite some time without additional maintenance/support over the next few years.

    Thanks guys!

    #20502
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    How did you push the images to the clients?
    Have you configured each one individually or used WDM to pull/push the image?
    If latter, have you run Prep4man before pulling the image?

    CG

    #20507
    pilot329
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    I am using the latest version of WDM now (4.8.5) to pull/push the image. I am executing prep4man to reseal the devices before pulling the images. I have customized the answer file for UnattendedJoin to automatically join the domain.

    #20513
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    So that sound fine to me.
    Can you try to upgrade the Bootagent before pulling the image?
    You can also try to mount the hidden BA partition in the Windows Diskmanagement and delete the hostname.arc file in the Wyse folder. Then unmount it again, run Pre4man and pull again.
    Contact your Wyse SE to get the latest Prep4man files. I know there were issues with the first release and they already have an updated version.

    CG

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.