I have a sharepoint MOSS 2007 Install on a server and need to move it to another new server. Can I just ghost the complete server to the new one or do I need to install and configure the complete server again?
Any suggestions appreciated.
As far as I know you will have to reinstall MOSS on the new server as during the configuration process many settings form the acutal server are stored to the MOSS configuration database. So just moving the MOSS software and database won't work. Even just renaming the server on which MOSS is running will probably lead to a MOSS error.
To make it easy to move MOSS to another server in the future you should think about visualization. By this you can move the server to every server you want just by installing the visualization software and moving the virtual machine to the new host server.
This strategy will also help you in case of emergency when the MOSS server crashes due to a hardware error.
Your best bet would be to do a clean install on the new machine. This gives you the freedom to properly configure your machine(s) - name databases, pick ports for the Central Admin, SSP etc.
Resist the temptation to "upgrade" to a newer operating system (2003 to 2008), a new database (2000 - 2005 - 2008) or add service packs or the infrastructure update. If it isn't installed on the current production system - then don't install it on your new machine. Make a mirror of what you have and it will be much smoother.
Once the new server is configured the way you want it - just do a full backup from the Central Admin page on the old machine - and run a restore from the Central Admin on the new machine. This will pick up all the customizations etc that you have on the old site.
Once it's restored - and you've tested it and it's working the way you expect, run a full backup from the Central Admin page on the new server. That becomes your baseline for moving forward.
Related
Can any one provide me the best practice for turning on/off the windows updates.
Do we need enable windows update by default as best practice in prod environment.
What I have done in my current new prod setup, I have installed all windows update till today in all server and done the necessary restart in the server.
Now I have disabled like below. Please correct me if I am doing any wrong so that I can learn new thing.
You really don't want to block updates all together on a production server as you will leave your system exposed to security issues.
However, as Microsoft is now pushing SharePoint CU's (Cumulative Updates) through this avenue, you don't want them to install automatically either as this could break your production SharePoint instance! You can set up your server to "download only" and then you can manually choose which updates to install.
Here is a really good article I'd recommend so you are more informed about what process you should follow that is the best practice for your organisation.
https://redmondmag.com/articles/2015/02/13/pushing-sharepoint-server-updates.aspx
wondering if you can help me with the following.
I have a new server in my office, with Windows Server 2008 R2, i have 2 developers working here now, i have just installed WAMP on the server and running, i would like that each of the devs to have their own instance in the wamp, i mean if within www i have N quantity of Projects.
Programmer A gets access to some projects only, also the Databases.
At this point i know how to setup the wamp to be accessed in the LAN using Vhosts, but i have no clue how to setup specific privileges.
Could not find anything on the web on that issue.
Can I suggest another method.
As WAMPServer is intended as a developers tool anyway, you install WAMPServer on each developers PC. You make sure the config on all PC's is the same as the Server version.
For an existing project i.e maintenance/upgrade you give them the source and a database backup. They develop this locally and when its ready you take the source and a database backup to your WAMPServer on the Server.
For a new project, they develop it locally and then when its ready you move the project to the Server.
This would be much simpler and would leave the Server version for UAT or LIVE, whatever you are using it for.
Of course there are better solutions involving source management etc, but as a fairly simple and low maintenance solution, this would work.
I am in a situation where the current web server is a production environment and there is no development environment. It is running Joomla on an IIS Web Server and is an Intranet site with all of the security, IP restrictions, Certificates, and whatever else required to run an enterprise level Intranet site.
I am wondering what I can do to set up a development environment to work within (preferably using some type of version control).
I have full reign over the IIS server, and I have had a co-worker set up a VM clone of the current system to work with, however the security is making it difficult to work with and set up.
I would like to not use Visual Studio as I don't believe I have a license for it; however I can get it if need be. I would like to stick with Notepad++ if at all possible.
Thank you.
If you're wanting to literally take the site content out and be able to edit and work without any of the security restrictions of the production environment, there's a couple of ways you could do it. However, it's going to depend on what DB the system is running with.
Joomla, regardless of what web platform it is running on, is coded in PHP, so you don't have to worry about getting visual studio. You can use Notepad++ as normal.
Option 1 - IIS Clone
If you can take a SQL backup of the database, you build a from-scratch box with IIS. You'd need to add the PHP drivers to IIS to do this. Go to Microsoft's site for more info:
PHP for IIS
Option 2 - Apache Port
You can make an Apache box using WAMP to run, if you're using a Windows machine. PHP is PHP, on any platform, so it should work without modification.
The tricky bit will be the database, depending on your situation. If the database is MySQL, you can import your database backup and be good to go, after changing the config files for the Joomla site.
If the site used MSSQL, it's a little trickier. You'll need to install an MSSQL PHP plugin to get this medthod to work. There's plenty of instructions online on how to do this, it's a case of finding the right one for your implementation.
on Sharepoint development purpose. on installing sharepoint2o1o whether standalone option or server farm better suited for developememt
Standalone will install SQL Express on your machine and use it for your Sharepoint instance.
Server Farm will install Sharepoint on existing SQL Server instance if you already have one on either your machine or somewhere else on the network.
So it depends whether you already have SQL Server installed on your machine or not. A standalone installation is actually what it says. It will install as a standalone product without any other product requirement.
I prefer server farm installation because I rather have full SQL Server installed and used by other apps as well. I find SQL Express installation a waste of resources when I already have a full fledged server.
SQL Express is limited to 4GB. If you think your development environment may exceed that, then go for the Server Farm. As for me, we already have a full farm for staging and production, so I get no additional benefit from running a server farm installation in dev. #Robert-Koritnik has a good point that, if you're already running a full SQL instance on your box, you might consider Server Farm just to avoid having another instance of SQL Server on the box. I tend to do my development within a VM, so Standalone works just peachy for me.
Just as a matter of interest. Dont use Standalone for ANY production environment as it limits you in that you cannot add any more WFEs or scale out at all.
If you have a SQL Server license (Not express) , then always choose Farm.
After you have installed SharePoint you need to run the configuration wizard which typically asks what your Database server is what DB Name to use, what port to use for Central Admin, etc. Then it goes through its 1-9 install process...
Our problem is on one of our servers, which has a clean database, clean 12 hive, and no answer file is to be found (nor should it), the Configuration Wizard goes straight through to the 1-10 install process. It doesn't ask any questions at all...
Why would this occur?
This behavior is expected if your server is already attached to a farm. Was the machine previously part of a SharePoint farm and removed via the farm's Central Admin? Was a clean SharePoint uninstall/reinstall performed?