General Chat Thread, Need help with new Server in General; In conversation with a few geeks it has occurred to me that there will be work to do on the ...
20th January 2012, 01:37 PM #61
In conversation with a few geeks it has occurred to me that there will be work to do on the PCs too, won't there?
Some programs run off the server, and some save to the server so surely somehow I would need to alter ALL the paths on the machines to a new server? Or would the fact that the share names and locations are the same be OK? Would this mean renaming my old server and giving the new server its original name? Is this just carp I am speaking? Would explain why one company want to flatten the machines though, presumably they would reimage them after installiing the new server so that all the paths etc will be correct?
IDG Tech News
20th January 2012, 01:44 PM #62
If the whole file tree and ADUC etc is done properly, the end user in theory will not know the difference!
IF you build the server first, DC Promo (Promote the new server), file transfers etc then DCPromo (Demote the old server), the end user in theory will not know the difference unless they are logged in at that moment.
20th January 2012, 02:48 PM #63
Ahh I see. I think. So why are a couple of installers talking about reimaging all the machines?
20th January 2012, 02:55 PM #64
Do they want to update your desktops to Win 7 ? That's one of the only reasons I can see why they want to re-image, and to bump the cost up of course.
Originally Posted by witch
20th January 2012, 03:21 PM #65
For any shares that are explicitly named e.g. \\SERVER1\SOMESHARE and your new server is SERVER2 all that is needed is a CNAME (alias) record in your DNS where the alias name would be SERVER1 and the target would be SERVER2. problem solved!
20th January 2012, 03:23 PM #66
that would make most sense
Originally Posted by pooley
20th January 2012, 06:44 PM #67
S drive is still the S drive even if its on a new server. Some programs run off the server, and some save to the server so surely somehow I would need to alter ALL the paths on the machines to a new server? Or would the fact that the share names and locations are the same be OK?
20th January 2012, 06:53 PM #68
I agree. We had no problem moving shares from one server to another.
Originally Posted by edutech4schools
20th January 2012, 06:55 PM #69
Provided the file tree system remains intact and identical as before, then it will always work
20th January 2012, 07:08 PM #70
Best thing to do with shares is look at using DFS where possible as that way all the shares become \\your.domain\DFS\Share instead of \\servername\share, so whilst you can add in CNAMES into your DNS (works as a nice work around) moving to DFS will make things easier in the future and, in mu opinion, allows you to do things more easily.
The only issue you might have is how the drives map? Are they all mapped locally? in which case, the DNS CNAME will sort it, but you're better off changing it over to being direct, otherwise at somepoint down the line it's going to get confusing ..
Glad you see to be getting things together. It's always a daunting task the new server thing, even if you have done it before and you do have the time available to do it ..
20th January 2012, 08:01 PM #71
Shares are mapped by login script at the moment. All machines are Windows 7 and the worst bit is, the company wanting to flatten them is the company that installed them - I built a machine and they did the rest in the holidays a while ago. And the netbooks.
20th January 2012, 08:06 PM #72
Absolutely no need to flatten them in thay case.
20th January 2012, 08:57 PM #73
What plexar said...hell you could probably get one of us in to do it four much cheaper, and probably quicker than the other company.
I myself would do it as follows.
Build server with identical name and duplicate the aduc.
Install programs with identical file paths as old server.
Copy all files from the old server whilst it stays live and copy to external source. reason being is to have a backup of files at time of migration.
Transfer files from external source to new server.
Make system state back up then set up back up systems. At the end of the working day, copy over updated files.
Dcpromo both servers so they are exactly as before.
Test logins to ensure they are able to log in and get files.
Copy old GPO preferences and paste them into the new GPO setup.
Update GPO as applicable
Test logins again
Sit back, light my pipe and enjoy my handiwork
21st January 2012, 11:45 AM #74
Yeah, if the drives are mapped by login scripts, you can easily move to using GPP Drive Mappings on 2008 R2 whereby you can target the drives at specific user logins and all from the one place, which makes things a little easier in my thoughts.
You certainly don't have to flatten the whole thing though, not unless something is hideously wrong with it, that just sounds like they're wanting more ££ for the job. The company I PM'd across to you are very helpful in this sort of situation if you're still struggling as they would configure the server to your requirements, so as long as you can let them know what that is (i.e. what your current server does (including the mappings and what not) and anything else you would want it to do - they're always very helpful with me, in fact, I probably don't take them up enough on it at times .. lol)
By chris_clemo in forum Network and Classroom Management
Last Post: 18th March 2011, 05:24 PM
By mcnallyfc in forum Hardware
Last Post: 14th September 2010, 10:47 AM
By goodhead in forum Windows
Last Post: 2nd October 2007, 11:42 AM
By projector1 in forum General Chat
Last Post: 26th February 2007, 01:08 PM
Last Post: 13th October 2005, 08:42 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)