Re: Workstation Migration

Hello Wilson,

Q: Shall I install ADMT on each workstation? If I have 100 users in
office, I do need | to install 100 times on each workstation.

A: you do not need to install ADMT on each workstation. ADMT may want to
be installed DC on the target domain.

Note:

ADMT requires the following permissions to run properly:

o Administrator rights in the source domain.
o Administrator rights on each computer that you migrate.
o Administrator rights on each computer on which you translate security.

You must configure the source domain to trust the target domain.

Q: Compare with "Copy to:" (the function to copy profile to another user)
and ADMT workstation migration, which one work effectively and
efficiently? Because it's not a good choice if I need to install ADMT on
each | workstation.|

A: You do not need to install ADMT on each workstation. In appearance, ADMT
is a more efficient one.

Q: If I use "Copy to", how can the user can keep his/her user access right
| locally? Since they are login to Domain Controller w/ Domain User
already. | Therefore, how can they still keep the administrative right on
his/her own | workstation w/ full control?

A: "Copy to" function is to copy user profile to another one which is just
"Copy->Paste". It would not affect the right on workstations. However,
the user accounts imported by csvde.exe would not have the right before
since they are exact distinct ones with different SID.

If there is anything that is unclear, please feel free to let me know.

Thanks & Regards,

Jason Tan

Microsoft Online Partner Support
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.




--------------------
| From: "Wilson Cheung" <wcwcheung@xxxxxxxxx>
| References: <uytVyNOjFHA.3348@xxxxxxxxxxxxxxxxxxxx>
<#gqI6eRjFHA.940@xxxxxxxxxxxxxxxxxxxxx>
| Subject: Re: Workstation Migration
| Date: Wed, 20 Jul 2005 22:04:18 +0800
| Lines: 107
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Message-ID: <#3gu$OTjFHA.3692@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: n219078006193.netvigator.com 219.78.6.193
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:11326
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Hello Jason,
|
| Thank you for your suggestion and advise on my server migration. As you
| mentioned I can use ADMT to migrate user profile on workstation. Shall I
| install ADMT on each workstation? If I have 100 users in office, I do
need
| to install 100 times on each workstation.
|
| Compare with "Copy to:" (the function to copy profile to another user)
and
| ADMT workstation migration, which one work effectively and efficiently?
| Because it's not a good choice if I need to install ADMT on each
| workstation.
|
| If I use "Copy to", how can the user can keep his/her user access right
| locally? Since they are login to Domain Controller w/ Domain User
already.
| Therefore, how can they still keep the administrative right on his/her
own
| workstation w/ full control?
|
| With many thanks!!
|
| Wilson
|
| "Jason Tan (MSFT)" <v-jasont@xxxxxxxxxxxxxxxxxxxx> wrote in message
| news:%23gqI6eRjFHA.940@xxxxxxxxxxxxxxxxxxxxxxxx
| >
| > Hi Wilson,
| >
| > Thanks for reply!
| >
| > Actually, ADMT is a good tool to migrate user profile on the
workstation
| > in
| > your scenario. You are correct that all user's profiles are stored in
| > workstation locally. Whereas, in nature, "user profile migration" which
I
| > indicated means "translate user profile". That is to say, you can
maintain
| > the previous user profiles when logon workstations.
| >
| > As you mentioned "I used csvde.exe to import the user account", we do
not
| > recommend this method since it actually create the user accounts which
| > have
| > different SIDs though they have the same name. That would cause that you
| > have on permission on the user profiles since user profiles are based on
| > SIDs.
| >
| > If there is anything that is unclear, please feel free to let me know.
| >
| > Thanks & Regards,
| >
| > Jason Tan
| >
| > Microsoft Online Partner Support
| > 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.
| >
| >
| >
| >
| >
| >
| >
| > --------------------
| > | From: "Wilson Cheung" <wcwcheung@xxxxxxxxxxxx>
| > | Subject: Re: Workstation Migration
| > | Date: Wed, 20 Jul 2005 10:26:01 +0800
| > | Lines: 15
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
| > | X-RFC2646: Format=Flowed; Original
| > | Message-ID: <uytVyNOjFHA.3348@xxxxxxxxxxxxxxxxxxxx>
| > | Newsgroups: microsoft.public.windows.server.migration
| > | NNTP-Posting-Host: 202.140.234.94
| > | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| > | Xref: TK2MSFTNGXA01.phx.gbl
| > microsoft.public.windows.server.migration:11313
| > | X-Tomcat-NG: microsoft.public.windows.server.migration
| > |
| > | Hi Jason,
| > |
| > | Eventually, I haven't use ADMT to migrate user account, but only use
| > FSMT
| > to
| > | migrate all files. I used csvde.exe to import the user account. All
| > users'
| > | profile are stored in workstation locally. Therefore there is no need
to
| > | migrate user profile. I am wondering if there is a problem on user
| > | permission. Do you have any clues? Since user_A is a domain user who
| > locate
| > | under OU. However, If I put User_A in Domain Admin group. Then user_A
is
| > | able to have their wallpaper back.
| > |
| > | Thanks,
| > | Wilson
| > |
| > |
| > |
| > |
| >
|
|
|

.

Relevant Pages

  • Re: Workstation Migration
    ... issue is critical to you and ADMT is not a solution in a real situation. ... the user profile on the workstations. ... 811151 How to copy data from a corrupted user profile to a new profile ... | Subject: Re: Workstation Migration ...
    (microsoft.public.windows.server.migration)
  • RE: Migration over Client VPN
    ... ADMT v3 Migration Guide ... When we migrate workstation, we do not need end user to logon the ... When end users logon their PC, logon script will automatically ...
    (microsoft.public.windows.server.migration)
  • Re: Workstation Migration
    ... You may check "user profile" option in the process of "computer migration ... wizard" with ADMT. ... | Subject: Re: Workstation Migration ...
    (microsoft.public.windows.server.migration)
  • Re: Workstation Migration
    ... mentioned I can use ADMT to migrate user profile on workstation. ... ADMT workstation migration, which one work effectively and efficiently? ...
    (microsoft.public.windows.server.migration)
  • RE: migrate computers with ADMT 2.0 or visit each computer
    ... workstation out of domain and join into another domain. ... into domain but the user didn't have permission on the files & folders on ... What ADMT doing is replace the SID of old domain with the corresponding one ...
    (microsoft.public.windows.server.migration)