|
Yeah then you want to upgrade to a newer version. Among the
other fixes is a fix that stops it from normaling RDNs to lower case.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Noah Eiger Sent: Wednesday, April 05, 2006 9:12 PM To: [email protected] Subject: RE: [ActiveDir] Object case changes with ADMOD File version says:
1.3.0.85 From: joe [mailto:[EMAIL PROTECTED]
Out of random curiosity are
you using a version of ADMOD prior to V01.05.00? joe -- O'Reilly Active Directory
Third Edition - http://www.joeware.net/win/ad3e.htm From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Noah
Eiger Hi – I have been testing a little batch file that uses adfind
and admod to move some computer accounts around in AD. Based on a text file,
computers move to different OU’s. The weird thing is that before being handled
by admod, the accounts are in all capital letters (as seen in the DSA and in
text output of DN’s). After the move, they appear in all lower case.
While this is not the end of the world, it is a little
odd. Why is this happening? Can I keep them in the same
case? The batch is as follows: set
toolPath=C:\Sysadmin\Tools\Apps\Joeware set
compList=C:\Sysadmin\Tools\Scripts\VarFiles\complist.txt set
logFile=c:\sysadmin\logs\compMove_log.txt for /f "tokens=1-3" %%A in (%compList%) do
(
%toolPath%\adfind -b dc=company,dc=com -f
"&(objectcategory=computer)(name=%%A)" -dsq | %toolPath%\admod -move
ou=%%C,ou=%%B,dc=company,dc=com
) >>%logFile% The file format for complist.txt
is: COMPUTER1
OUX OUY COMPUTER2
OUZ OUY Thanks. -- nme -- -- -- |
- RE: [ActiveDir] Object case changes with ADMOD joe
