Re: ADMT
- From: Juha <Juha@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 21 Dec 2007 10:33:00 -0800
Thank you kj for your quick response. Now I get depressed..
Well, I was a little tired when lefting the building;) I don't have access
to site right now. AV is of so I disconnected WAN.
3. I used ADMT (2?) because that was the only thing I found. Can I draw back
to another solution? I have done steps one "migrating seven user accounts"
and two "migrating server group accounts" ( one was account whose name was
domain's netbios name and the other was OWS_1855764xxx_Admin).
The email domain will change in the end of this year. The 40 remote users
had only ISP email. The new server can send/receive currently mails pointed
to new email domain. Still it will be introduced at the first day of 2008.
It is also possible to reinstall new server (Suppose the old one is same as
it was, right?). Will be at Site propably next tiem on Sunday.
Juha
"kj [SBS MVP]" wrote:
Juha wrote:.
I'm migrating from sbs 2003 std to sbs 2003 R2. First migration for
me. Followed MS instructions:
http://www.microsoft.com/downloads/details.aspx?familyid=fa187d1e-8218-4501-9729-222bd8ebb64c&displaylang=en
Wow. OK let me take a stab or two here.
First, the article above is for SBS *2000* to SBS 2003, not SBS2003 *Std* to
*R2*. No 'migration' is required for this, so I'm thinking your intent was
to start with a clean AD on a newly built SBS2003 Server.
I have apx 40 remote non domain workers and only 7 domain computers
(5 w2k Pro SP4 and 2 XP pro SP2) located in the same place as the
server.
It seemed that I failed to migrate computer accounts. Got in the end
of computer mig. wizard a lot of RPC 17xx errors to migration
console. Changed a in different combinations the server or router
DHCP/DNS settings after that and retryed several times to complete
the wizard. Finally noticed (after first time refreshing system
manager) that the client computers were transferred to new server
(except one). All the clients were booted during this unprofessional
procedure.
1. Is it important to succesfully finish computer migration wizard?
After all, I can easyly unjoin and rejoin WSs to new domain, and
everything goes by smoothly, right? W2k clients tries still to log on
to old domain but XP clients log on to new domain.
Yes, if you want the profiles and security translations
2. My instructions tells that if I log on a client during the (whole?)
procedure the Outlook profile will not migrate. All clients has both
exchange and isp account (this a long story) pointing to same mails.
Also the have a lot of contacts, calender, etc info in Outlook. Hope
I wan't loose them.
True. Don't log on durring computer migrations with ADMT.
Lastly. Before migration I saw problems in old domain, related trust
between a client and the domain. Did't really to try to fix them -
there was no money and thought that will fix these in the new domain.
Hmm. No 'trusts' are allowed in SBS.
Semi Lastly. I checked one XP client after computer migratin wizard
and it logged on to new domain. There were still problems
communication with the server (certificate issue). Haven't opened
Outlook on client so far.
Last lastly. I was forced to change the IP of the new server once
before migration. Used related SBS wizard and trien to manually fix
problems I noticed (al least the sbssever.cer were issued to wrong
IP).
3. Enything else I should keep in my mind?
Probably lots. Can you convey more on why you "migrated", instead of
"upgraded", or did a swing type migration?
Hope you guys are here now while Chritmas is coming. To me this was a
great opportunity to migrate while stuff is on holidays. Please help
me?
Juha
Finland
--
/kj
- Follow-Ups:
- Re: ADMT
- From: kj [SBS MVP]
- Re: ADMT
- References:
- Re: ADMT
- From: kj [SBS MVP]
- Re: ADMT
- Prev by Date: Re: Public Calendar problems
- Next by Date: Re: Backup Exec alternative?
- Previous by thread: Re: ADMT
- Next by thread: Re: ADMT
- Index(es):
Relevant Pages
|
