plsntn_rules
2004-12-16 15:45:04 UTC
We have an install of SPS 2003 that was not planned out properly. The big
dilemma is that the application is already in production.
It was installed on old hardware and installed on servers that had exiting
applications already installed.
I have been tasked with moving this entire SPS application from these
servers on to new servers that will exclusively handle SPS 2003 and no other
app.
My question is what is the best way to handle this move?
The current install is exactly the way the users want it configured with
content and data hence I do not want to re-invent the wheel. Is there a way I
can move the exisiting config on to new servers?
Please bear in mind that the new servers will not have the same name as the
old servers. Will this be an issue?
Is there a manual or step by step guide I can follow to achive this?
Any help would be greatly appreciated as I am a total novice at SPS 2003.
Thanks You.
dilemma is that the application is already in production.
It was installed on old hardware and installed on servers that had exiting
applications already installed.
I have been tasked with moving this entire SPS application from these
servers on to new servers that will exclusively handle SPS 2003 and no other
app.
My question is what is the best way to handle this move?
The current install is exactly the way the users want it configured with
content and data hence I do not want to re-invent the wheel. Is there a way I
can move the exisiting config on to new servers?
Please bear in mind that the new servers will not have the same name as the
old servers. Will this be an issue?
Is there a manual or step by step guide I can follow to achive this?
Any help would be greatly appreciated as I am a total novice at SPS 2003.
Thanks You.