server with a temporary name and IP address. Use robocopy to copy over the
files and retain the security. something like robocopy x:\ y:\ /sec /r:2
/w:2. Then use Windows GUI to share the folders. Use Print migrator to
backup the printers on the old server and restore them to the new server.
See:
http://www.microsoft.com/windowsserv…grator3.1.mspx
I would keep the new server as a member server during this part.
Plan on about an hour of down time for the next part, maybe do this on a
Friday evening??/
Once you get all the printers and files to the new server, if the server to
be replaced is a DC, run DCpromo to remove AD. Once a member server rename
and change IP address. Give the new server the proper name and IP address
and promote to DC. If you have AD integrated DNS let it replicate. AD
integrated DNS makes the DNS part easy.
The longest task is to copy over the files but you can either do the
robocopy during the week and just do a refresh before starting or do the
robocopy after you make the new server a DC (if necessary) and cut the
robocopy script loose as the last step and let it run over the weekend.
You might consider stopping the shares on the existing server before running
the robocopy to make sure users are not in the files.
hth
DDS
"JohnB" <> wrote in message
news:…
>I work for a small company of about 75 users. (I started working here a
>month ago) Their server hardware is old, all purchases about 7 years ago.
> The email here is hosted by an outside IT service provider. We use RPC
> over HTTPS.
> There are 3 servers here; 2 DCs that are both File/Print Servers. And 1
> server that is running SQL 2000, with a POS system on there. Also, shared
> user folders/files.
> I realize this is not the ideal setup. That’s what I’m trying to improve
> on.
>
> There is a serious lack of drive redundancy. The SQL server has ONE
> drive.
> The 2 DC’s each have mirrored system drives. But they both have one other
> drive, for which there is no redundancy. That is where the user folders
> and department data is.
>
> I have convinced management that we need to purchase redundant drives
> right away. And have them considering hosting our own Exchange server.
> But they don’t want to do that right now. Which is a good idea, because I
> am swamped with other issues, having just started here. BTW… this is a
> one-man IT department – me.
>
> Here’s the quandry; They want to replace one of the old DCs with a new
> server, instead of putting more money in someting 7 years old (the
> reduntant drives).
> I am leaning towards getting a server with enough horsepower to be the
> Exchange server now. And make that the replacement DC. With the thinking
> that this will save some $$$, in having to just get this one server,
> instead of a mid-range box now, and the Exhange box later.
>
> This is where planning really comes in – and why I’m looking for the ideas
> of others. I’ve migrated shared folders and printers from one server to
> another before. And it isn’t fun. The sever name needs to stay the same,
> to keep their shares from breaking. And, ideally the IP address will stay
> the same, as invaribly there will be someone with a drive letter mapped
> via the server’s IP address.
>
> What would you do?
> I’m dreading the idea of doing the wholesale move of shared files and
> printers to a new server, should I keep the existing DC/File Server?
> Should I get the Exchange cabable server now, and make it the replacement
> DC and file server?
> There’s a lot of options here. I could get the mid-range box now. And
> the Exchange box later.
> One key to all this is; I’m just one person here, I have to do this as
> efficiently as possible. I’ve got to come oup with some kind of plan that
> is do-able, in man hours, for one person.
>
> TIA
>
