Windows Server 2000/2003 Thread, W2003 R2 .. I've come to the conclusion ... in Technical; Ok, so it's a week before the Easter "holidays" and I've come to the conclusion it will be one of ...
26th March 2010, 11:09 AM #1
W2003 R2 .. I've come to the conclusion ...
Ok, so it's a week before the Easter "holidays" and I've come to the conclusion it will be one of those holidays I don't get this time (I'm a term time only tech you see) ..
Basically, a number of our workstations are just not playing ball when it comes to talking to our new server and accepting requests and leaving the old behind (the old which I'd like to use for other things really but for now it has to sit there keeping the stubborn workstations happy).
So, it's time for a complete site redeployment me thinks .. fresh server install, fresh images, cable checks, the works ..
My question is (as I've done this on small scale for offices I've worked for in the past (by small scale I mean 1 server, max 10 machines) so not really required imaging there) are there any pitfalls I should be aware of for this, or should it be a case of so long as I've done a good backup of data (use tapes at the moment, but will be cloning the disks out too just in case).
There's only one of me, and I have the 2 main servers, a FOG server (which I'm hoping to get working properly to assist with the new images as I've just not had the time to play as yet) and 75 workstations dotted around the site, so not the biggest of setups, but with 2 weeks to do this in ..
Servers both are 2003 R2, all workstations are XP Pro. Just want to get it all sorted and running smoothly instead of having to jump files about (there's not enough room on the old server to allow for replication and quite often resulted in files going walk about, so had to turn that back off) when the workstations decides to write to the old server instead of the new.
Thanks for any responses. I'm fairly confident in doing all this and know how to do all this, just any pitfalls people have come up against doing this sort of thing in the past that I might not of considered!
24th April 2010, 11:04 PM #2
You didn't get any replies.
Hope it went OK my friend.
Backing up your existing data and knowing exactly what each individual needed access to (apps / data) would have been my biggest prerequisites for this task.
Thanks to superfletch from:
soveryapt (26th April 2010)
26th April 2010, 02:56 PM #3
You can have a thanks for simply replying! lol ..
It went well, other than the fact something in the GPO's went horribly wrong, so we had the first week back without any file access whilst I rewrote them all from the group up in new OUs AGAIN .. lol ..
And indeed, backups (3 of them to be precise! I should trust the tapes, but you just know that something goes wrong and you need the tape to pull from and it's blank! lol)
Anyway, all is back up and running now, apart from the fact I have the odd file that isn't copying with my script, but the staff know I have backups from before they broke up so as long as they saved correctly, I can simply copy their items back in. If it's still not there, they didn't save it! lol ..
By tech_guy in forum Windows Server 2000/2003
Last Post: 9th December 2009, 08:56 AM
By Neville in forum Windows
Last Post: 5th March 2008, 04:12 PM
By Simcfc73 in forum Windows
Last Post: 1st April 2007, 11:54 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)