Windows Server

TxtReader · Guest

Hello all,

If someone is an expert with ADMT Scripting, maybe can help me out
with this... :)

My Current scenario:

1 single Destination Domain (company.corp)

12 Domains to be migrated to Destination Domain (company1.com,
company2.com, etc..)

1 single domain to be migrated to Destination Domain (company.org)

The 12 Domains with different DNS and NetBios names were migrated from
the Destination Domain, with a VB application using the ADMT.Script
object.

The problem arises with domain 'company.org', as it has the same
NetBIOS name as 'company.corp'. The workaround to migrate those
resources was to create an 'intermediate' domain (companyorg.com), and
then from this domain the migration to the Destination Domain.

As the VB application needs to be run from the Destination Domain, the
program needs first to migrate users from company.org to the
intermediate domain (companyorg.com).

To accomplish this task, i've tried several procedures:

- CreateObject("ADMT.Script","IntermediateDomainServer") // Won't
work. The process is created remotely but launched locally, in which
the case is i need the process to execute on IntermediateDomainServer.

- Create a remote process on the IntermediateDomainServer using
WINMGMTS and Process.Create from the destination domain. This will
create the process which is a "wscript.exe migration.vbs" file located
in the IntermediateDomainServer that will launch the migration for
some users.
But when i check the migration log, i get that the Migration Process
could not get the needed credentials to migrate SIDHistories, Access
Denied. And finally failing.

As im logged as domain admin in the destination domain, to pass the
correct credentials to run the script I run "runas /env
/user:intermediatedomain\domain admin", so it has right privileges to
do that.

When i connect locally to the console and perform the migration
(giving the same credentials, it works fine).

Anyone can point me out a little or give me a direction? :)

Thanks a lot in advance!

TxtReader

Jeff Qiu [MSFT] · Guest

Hey TxtReader,

After I read your description carefully, I can brief the issue as:
You want to migrate from 12 domains to 1 new domain. Due to the name
conflict, you need to migrate one of the 12 to a temp domain and then to
the new domain.

Thus, what you should do is to create all two way trust among the special
source domain, the temp domain and the new domain.

Let's mark the special source domain as A, the temp domain as B, the new
domain as C.

The correct sequence should be below:

Logon as the A domain's admin on B domain and do the migrate using ADMT.

Then logon as the B domain's admin on the C domain and do the second part
migration.

HTH.

If some special rights is needed in your script, I believe you'd better go
to the microsoft.public.scripting.vbscript group for such discussion.

Regards,

Jeff Qiu
Microsoft Online Partner Support
MCSE 2k/2k3, MCSA 2k/2k3, MCDBA
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1