Currently Being ModeratedMar 6, 2012 5:48 AM (in response to mike1210)
These clients are already bound to AD using the Directory Utility app, correct?
Currently Being ModeratedMar 6, 2012 9:48 AM (in response to mike1210)
The only difference I'm seeing between your profile and ours is the fact that you have the "Use Directory Authentication" option checked.
If the Macs are already bound to the domain, this option shouldn't be needed. So uncheck it, and see what happens.
Currently Being ModeratedMar 7, 2012 7:19 AM (in response to Templeton Peck)
Yep that sorted it many thanks for that
Currently Being ModeratedMay 11, 2012 6:05 AM (in response to mike1210)
Hi, i have the same problem. Which Profile do you have? Device, Devicegroup or Userprofile? Is the WLAN active, but not connected at the startup?
I tried any versions....but the connection to WLAN an AD doesn't run. Our Client are connected with AD (this is a workflow in DeployStudio, and works fine wired)
Have anybody a working example?
Currently Being ModeratedMay 12, 2012 3:05 PM (in response to NetMasterCH)
Device group its set to. If you cant get it to work via DS try adding it manually to see if the profile is correct. I've had some post actions not quite behave as they should have via DS, still an awesome package.
Currently Being ModeratedMay 15, 2012 6:26 AM (in response to mike1210)
ok....but the profile is correct and works fine (@DS). Any AD User can connect via LAN, and de Profile is creating at the standart template. When i do this via WiFi, the connection to WLAN and AD failed.
But the Credentials for login are correctly!