speckytecky Posted April 28, 2009 Posted April 28, 2009 I have a old server that used to be the Windows 2000 DC on our old network. New network on Windows 2003 Standard edition R2 has new name. I have now upgraded the old box to Windows 2003 Standard edition R2 and want to first add it as a member server to the network then give it a role so it can act as the Sophos Enterprise Manager and WDS. It's still showing itself as the DC of the old network. How do I make the change please?
kmount Posted April 28, 2009 Posted April 28, 2009 I'd disconnect it from the network, log onto it and run dcpromo. 1
FN-GM Posted April 28, 2009 Posted April 28, 2009 What he said ^^ Myself i would reinstall 2000 but thats just my preference. 1
speckytecky Posted April 28, 2009 Author Posted April 28, 2009 What he said ^^ Myself i would reinstall 2000 but thats just my preference. Interesting comment FN - why do you say that?
powdarrmonkey Posted April 28, 2009 Posted April 28, 2009 I think Zak means he would re-install 2k3, and I agree with him. Much better to have it completely clean than an upgrade of a has-been, it means at least you can make assumptions about it when you're troubleshooting something later on. 1
Butuz Posted April 28, 2009 Posted April 28, 2009 Hi mate. Hows it going? Agree with the others - definately install Windows 2003 from scratch. Never upgrade a box especially an old 2000 DC - it'll have all sorts of crud on it which will get carried over. Butuz 1
speckytecky Posted April 28, 2009 Author Posted April 28, 2009 Thanks for the very useful answers fellas. Guess what I'll be having a crack at tomorrow then!
FN-GM Posted April 28, 2009 Posted April 28, 2009 I did mean that, my apologies was a quick post. Go with 2003 its much better. I always like clean installs, you know the score and know nothing will come to bite you later. 1
leco Posted April 28, 2009 Posted April 28, 2009 I did mean that, my apologies was a quick post. Go with 2003 its much better. I always like clean installs, you know the score and know nothing will come to bite you later. And if it does, to quote from another post, then it's 90% not your fault:getmecoat: 1
Tom Posted May 5, 2009 Posted May 5, 2009 If you are planning on using this as a WDS server you might want to go with server 2008 rather than 2003R2. You dont get the same multicast support with WDS under 2003 as you do with 2008. 1
powdarrmonkey Posted May 5, 2009 Posted May 5, 2009 If you are planning on using this as a WDS server you might want to go with server 2008 rather than 2003R2. You dont get the same multicast support with WDS under 2003 as you do with 2008. Well, you don't get any multicast support under 2003...
Cue Posted May 5, 2009 Posted May 5, 2009 I find that unless there's anything on there you may need, you're better off reinstalling WS when you're changing the server's role completely, otherwise you may end up with extra unwanted bloat from stuff you installed on there for its past role. That and there's less likely to be problems. 1
speckytecky Posted May 6, 2009 Author Posted May 6, 2009 If you are planning on using this as a WDS server you might want to go with server 2008 rather than 2003R2. You dont get the same multicast support with WDS under 2003 as you do with 2008. I'd love to but the budget has gone walkies this year and the Business Manager tells me that the budget next year is going to be even tighter - thanks Gordon and the rest of the country management team - Pah!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now