+1
From: Damien Solodow [mailto:damien.solo...@harrison.edu]
Sent: Monday, November 5, 2012 12:21 PM
To: NT System Admin Issues
Subject: RE: New job: AD is a mess
Or you could do it in PowerShell...
DAMIEN SOLODOW
Systems Engineer
317.447.6033 (office)
317.447.6014 (fax)
HARRISON COLLEGE
There are still plenty of cases where it is normal/expected to enter the
domain short name rather than the domain FQDN... would need to see a bit
more detail to suggest whether what you're seeing is a problem or not.
There is *probably* nothing mandatory to change on the user accounts in
this rega
Might come in handy.
AD Replication Status Tool
http://blogs.technet.com/b/askds/archive/2012/08/23/ad-replication-status-tool-is-live.aspx
On Mon, Nov 5, 2012 at 9:20 AM, David Lum wrote:
> Learn ADFIND and OLDCOMP.exe for AD cleanup. Also LDIFDE and CSVDE if
> you need to make bulk changes
Or you could do it in PowerShell...
DAMIEN SOLODOW
Systems Engineer
317.447.6033 (office)
317.447.6014 (fax)
HARRISON COLLEGE
From: David Lum [mailto:david@nwea.org]
Sent: Monday, November 05, 2012 12:20 PM
To: NT System Admin Issues
Subject: RE: New job: AD is a mess
Learn ADFIND and
Learn ADFIND and OLDCOMP.exe for AD cleanup. Also LDIFDE and CSVDE if you need
to make bulk changes (like changing UPN from @ABD to ABCDomain.com and the like)
From: Tom Miller [mailto:tmil...@sfgtrust.com]
Sent: Monday, November 05, 2012 8:21 AM
To: NT System Admin Issues
Subject: New job: AD is
Seems like you are putting too much emphasis on the NetBIOS name which is
still supported in 2003 FFL/DFL. Upgrading your FFL won't get rid of the
NetBIOS name, so any apps that still rely on this will still work.
You will not need to do step # 2
Christopher Bodnar
Enterprise Architect I
