Hi Fyodorov, all,

For the list members interest, since somebody else might also experience
the same problem, I finally came across the solution.
The problem was caused by a recommendation in the WS2K3 Security Guide (!)
in conjuction with a 'feature' of a component used by 'UserPrep'.
The Security Guide recommends disabling
the 8.3 Name Generation, which we have applied earlier in the NT4->AD
migration process.
Unfotunately, ldifde.exe uses the %TEMP% environment variable in a way
that requires 8.3 names, which aren't available, and in effect cause
'UserPrep' to fail.

The solution was found in:
http://blogs.msdn.com/exchange/archive/2004/02/11/71405.aspx

HOWEVER, is it a bad idea to move user accounts and/or groups to an OU
instead of leaving them on the default Users container?
Our first idea was to do that, but I guess that it would be easier to
configure CAs if we leave the defaults.
Would there be any problem if we move users accounts/groups to adequate
OUs after the migration / mailbox move process is complete?

------------------------------
Manos Anastasiadis
Systems Engineer



> -----Original Message-----
> From: Fyodorov, Andrey FTL [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 30, 2004 7:21 PM
> To: Exchange Discussions
> Subject: RE: Ex5.5->Ex2k3 migration problems - please help
> 
> This caught my eye:
> "[15:22:58] The Domain Servers group does not have READ permissions on the
> Exchange container [15:22:58] ScGetExistingOrgName"
> 
> Have you moved any user accounts or groups out of the default Users
> container in AD?
> 

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: 
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english
To unsubscribe send a blank email to [EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.

Reply via email to