Well, as I said in my previous post, I do have some weird things happening. Apparently adding the domain user to the local group “Administrators” makes everything just works fine, yet he can’t do administrator like stuff (like turning off the write protection, changing local user accounts, …).
Also, if you’re looking for a smart way of how to add a certain global group (as in Active Directory group) to a local group, try this:
|
1 |
NET LOCALGROUP Administrators /ADD DOMAINGROUPNAME |
That simple, doesn’t even need the usual credentials to lookup the object, it apparently bypassed that step *shrug*.
And yet another weird thing is: if I run a certain command from a deployment script, it gives me different result as a manual execution of said script would give me .. *shrug*
|
1 2 3 4 5 6 |
; html-script: false ]NETDOM JOIN %COMPUTERNAME% /domain:heimdaheim.de /OU:"OU=Thinclients,OU=Computers,DC=heimdaheim,DC=de" /UserD:%ADMIN% /PasswordD:somepass /User0: Administrator /Password0:Administrator NET LOCALGROUP Administrators /ADD BARFOODomain-Users |
If I put that into a rsp (that is Wyse Device Manager script), it ain’t working. Would I be executing it myself without the WDM, everything works like a charm … *yuck*