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!