Windows 2008 Single Label Domain


hopefully can point me on right direction one.  our domain configured single label inherited predecessor.  i’m trying figure out best way resolve least impact end users.  i’ve had @ several other posts recommending using admt i’m not sure if should creating new forest or new domain in our existing forest.   this small domain approx. 500 users have other services in domain which include websites, sql servers, sharepoint , exchange 2010.   

exchange forest wide role & renaming domain ruled out due exchange 2010. considering future prospect of single label domain, better rid of doing lately.i suggest create new forest/domain, migrate using admt/quest or netiq tool. admt free tool ms quest & others paid & costly. admt can't used mailbox migration quest provides solution sql,exchange,sms etc migration.mailboxes can moved exchange server.

single label domain name not best way & better rid doing lately. not 500 user base much, considering other application & critical availability lot of planning & consultation required. migration can go smooth, if planned well. each tool has pros & cons, can talk vendor, evaluate & go ahead.  admt guide way go ahead, 500 user not still want evaluate.

if comfortable admt, 500 not count.

http://awinish.wordpress.com/2010/12/24/intraforest-interforest-migration/

restructuring active directory domains between forests

http://awinish.wordpress.com/2011/02/09/restructuring-active-directory-domains-between-forests/

 

regards


awinish vishwakarma

mvp-directory services

my blog:  awinish.wordpress.com

this posting provided as-is no warranties/guarantees , confers no rights.



Windows Server  >  Directory Services



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS