Re: Fresh Install - Saving Individual Users Exchange Data

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



if you are exporting the mail (either manually from the clients or by using
exmerge on the server) and wish to change people's login names I WOULD NOT
recreate the users with their current logon name and then modify it later, I
would create the users in the final manner I wanted.

If we ignore the logon name format change (from Joe to Joe.Blow) there's
actually a quicker way to get the exchange data across, forklift. This
relies on you reinstalling the server with same AD and Server name (it
doesn't really, but is easiest if so) and creating all your users as
identities having the same name as on the origin server. You stop all email
activity to the old server, adjust the location of database and log files to
somewhere easily found and run a backup to flush the logs. On the new
installation you create your empty store, again somewhere easily identified
for database and log files then stop Exchange. You then move the new (empty)
database somewhere else (really they can be immediately deleted, rather than
roll back to this copy should something go wrong Exchange will create a
'dialtone store') and put the database and logs from the old copy in the new
location(s), start Exchange, check that each mailbox is correctly linked to
the expected users, delete any mailboxes which no longer exist. This has the
added advantage of not breaking Exchange 'Single Instance Storage' (which
either export from client or exmerge will do) but it's not really
significant with the small number of users involved, unless of course the 5
have 15GB of shared info in Exchange, which would expand to 75GB if SIS was
not maintained.

The idea occurs that you could migrate all current users with user names
as-is but start a policy of First.Last for any new users. This effectively
implements a broken policy but we ain't talking about thousands of users
here, are we? Current users could get email addresses in the first.last@
format by a simple adjustment to Exchange recipient policy even though their
logon name would be first only.

Re the computer removal: Before removing any PC from the existing AD just
make sure you know (by resetting) the 'local' Administrator account's
password, or create a new user (I use 'setup') as an admin level local
account. You might also want to check each PC for any local accounts the
previously trusted person may have created. I don't see the necessity for
using the 'remove computer' process, that copy of AD will be thrown away
eventually.

I also don't know why someone below suggests the Computer account names must
be maintained. Name them the same or different, AD doesn't care, but in
either case use http://sbs/connectcomputer to join them to the new AD.

Additionally, I'd look at the current partition structure and data layout.
Could changes improve manageability? You have a unique opportunity to make
these changes as part of the process.

as for swinging the server:
1) one of the motivations for the rebuild is to ensure only the required
accounts exist, with standard permissions. A swing would in fact negate
this, moving any improper information in AD as part of the swing process.
2) I consider 5 user/device about 'the break even point' for swing.

"TrickyT" <wigwam326@xxxxxxxxxxxxxx> wrote in message
news:c8c96111-74d6-4d9e-8165-37c17a4aad4e@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On 27 Aug, 19:21, "AllenM" <nore...@xxxxxxxxxxx> wrote:
No the proper way to remove computer accounts in SBS is to use the SBS
wizard/remove Computer. Do not change the account name. The account names
are tied to the email mailboxes you are going to exmerge.After you have
completed the migration then you can do change the login names or rename
the
account.

"TrickyT" <wigwam...@xxxxxxxxxxxxxx> wrote in message

news:a168652a-434b-4421-a316-761b35e1ddba@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On 27 Aug, 18:12, "AllenM" <nore...@xxxxxxxxxxx> wrote:



For such a small project I think Swing Migration is a bit overkill. No
much
data nothing much to reinstall except SBS. Using exmerge will take care
of
mailboxes. Removing the computer accounts from the domain first will
take
care of getting a clean computer account. Obviously use the SBS
connectcomputer wizard to do so.

Three most important things to remember when setting up the new
computers
and accounts.
1. Domain name and server name must be the same.
2. User and Computer account names must also be indentical.
3. Email accounts must be identical.

other than that nothing much more matters. One more important thing
here.
Make sure you have the CD's as well as any License or product keys
needed
to
install. It would be a bummer to erase everything and then not have a
license number to input.

"Charlie Russel - MVP" <char...@xxxxxxxxxxxxxxxxxxxxxxx> wrote in
messagenews:O7ukTVGCJHA.4368@xxxxxxxxxxxxxxxxxxxxxxx

You can use PSTs, but exmerge will do them all at once. I actually
prefer
the "we're going to rebuild the server on Saturday, please save any
emails
you really need to a local archive" approach, and let the users save
their
own data. (and then I take my own copy, cause I like belt _and_
braces.)

Understand that each user will be a NEW user. The names will be the
same,
but they are NOT the same. The new computer is the same name, but
again,
it's NOT the same. It will have a new SID and the domain will be new
as
well. This will cause problems somewhere along the line. Usually
nothing
insurmountable, but expect them anyway.

A different, and I think far superior, approach, is to do a Swing
Migration (www.sbsmigration.com) - this preserves your data, preserves
your domain, and makes the whole process transparent to the end users.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"TrickyT" <wigwam...@xxxxxxxxxxxxxx> wrote in message
news:205c977e-dbea-4f98-a442-d828cf9c7efe@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The server I currently manage has recently been receiving several
Error ID reports, some of which I have asked for help on here to
resolve.

I have now found out that a trusted employee, that has left the
company, may have been doing some tinkering on the server and may
have
got out of his depth which would explain why the server was running
fine, but now has issues.

The client wants me to do a fresh reinstall of the server to remove
any issues that may have occurred and also to satisfy his mind that
no
unauthorised access can occur. Even though I have removed the user
and requested all users to do a password change.

There are only 5 users in the company so there is not too much data.
I can copy the data form each users My Documents (less than 1GB) and
all of the shared company documents (less than 5GB) to an external
USB
hard drive.

Everything will be reinstalled using the existing data.

These are my questions.

There are not many emails for each user. Is there a file in exchange
I can copy and then reimport or should I just export the data from
Outlook into a Personal Folder File (*.pst) and then import when
finished?

As I am using the same data, all of the computers will have the same
name, I assume I will not need to reconnect them to the network.

Is there anything else I need to do before I attempt the fresh
install? I have all of the disks required.

Regards

Trevor

Thanks for all of your replies.

Is this the correct way to remove the computers from the domain?

Right click on 'My Computer' select 'Properties' click on the
'Computer
Name' tab, click on 'Change'. Under 'Member of' select 'Workgroup'
give a
different name from the existing domain in the workgroup name box and
then click OK.

I am going to keep everything the same, IP addresses, server name
etc. The only thin I think I will change is the user names.
Currently everyone logs in with just their first name, which is ok as
there are no duplicates. I am planning to log in with first and
surname.

Regards

Trevor

Thanks for the advice. Will keep all of the names the same and then
change them when I have reimported their email.

I will remove the computers using the SBS wizard. They are all
currently called COMPANY01. COMPANY02 etc. When I remove them, I will
need to add them again. Can I still call them COMPANY01. COMPANY02
etc?

I will then log onto each client with an administrator account. I
connect using the http://server/connectcomputer wizard.

Regards

Trevor


.



Relevant Pages

  • RE: Exchange restore on SBS2003 from SBS2000 backup
    ... I agree with you that using ExMerge is a good ... How to recover or restore a single mailbox in Exchange 2000 Server ... >> the Exchange database from the SBS 2000 backup to the SBS 2003 Server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Entourage account setup applescript not working
    ... I pasted the script at the end just in case. ... When comparing the account settings on 2 computers, ... This script assists a user with the setup of his Exchange account ... Customize the network and server properties below with information ...
    (microsoft.public.mac.office.entourage)
  • Re: Deseperately Need Your HELP!
    ... Since I am going to use the new hardware server, ... around not to upgrade the exchange 2000 frontend server and install exchange ... The error *sounds* like it could be an issue with the Computer Account. ... Error code 0XC0070574: Logon Failure: The target ...
    (microsoft.public.exchange.admin)
  • Re: Deseperately Need Your HELP!
    ... I will not upgrade this exchange 2000 frontend server. ... Account. ... Error code 0XC0070574: Logon Failure: The ...
    (microsoft.public.exchange.admin)
  • Re: Deseperately Need Your HELP!
    ... I just checked the I.M server and verified it ran domainprep ... Can I run the domainprep for exchange again without any issue? ... If your account ... Error code 0XC0070574: Logon Failure: The ...
    (microsoft.public.exchange.admin)