This may be trivial, but I would like to know how you guys would go about this.
So I was making a website for a department of my university this summer, and now is the time I have to move all the source files and database files from XAMPP directory onto the server. I've got the access to the server through VPN and remote desktop. Now, I am not sure whether to install Apache, phpMyAdmin, MySQL etc. on the server and overwrite single configuration files (e.g. php.ini), or if I could simply move my entire XAMPP folder onto the server. I am using Windows 10 and the server is Windows Server 2012.
You'll need to actually install PHP, MySQL, and Apache to the server directly; simply copying the files from your computer won't install the corresponding system files or services or anything like that. Whether you use XAMPP or install them individually yourself, it's just like most other software that needs to be installed properly in order to function. Then, of course, you can copy over the relevant files that you've changed such as the configuration files and your site.
Related
Can anyone explain to me, in the simplest possible terms, whether it is possible to create/edit and host a SQL database locally on my PC?
I've so far managed to run PHP locally using XAMPP, but have been at a loss as to how I could implement SQL locally too.
For example, can I download phpmyadmin directly to my PC and use it to implement database features on my website without having to be connected to the internet?
It's possible. And you don't need to download any other software.
Fire up XAMPP and start the Apache and MySQL servers then go to your browser and enter http://localhost/phpmyadmin.
Once your MySQL server is up, you can easily access it from applications running locally with the necessary configuration (i.e host, username, password, port etc).
I am trying to deploy the Phpscheduleit(http://sourceforge.net/projects/phpscheduleit/) open source software on a WAMP Server version 2.4.
One of the instructions states "The web server must have write access (0755) to /your-booked/tpl_c and /your-booked/tpl" Does anyone have any idea where I could change the write access to 0755?
Thanks.
I am trying to deploy my first SSAS project. The Sql server is on a remote machine. I'm able to RDP and ping the machine.
I have restarted the SQL Browser service
sql browser has been started with admin account
I've turned off the firewall
I have given full control to the C:\Program Files (x86)\Microsoft SQL Server\90\Shared\ASConfig folder to the user SQLServer2005SQLBrowserUser$etc............
After a few hours of research, I've seen that one solution to this is to give the AS user rights to that folder.
I don't have an AS user at all on that machine.
What am I doing wrong? How do I deploy my first project?
Because I've gotten no responses to this posting, I'm wondering if this might be a bug. Where can I find the documentation for exactly what is needed for deployment?
I had a SharePoint server, now i want to move this from one machine to another machine.
This is what i did for the migration.
I have just installed sharepoint server in my new machine and i have removed the Sharepoint_config and wss_content databased from the new server. and i have restored both the databases from the old server. Then i tried to run the Central Admin and i got Unable to connect to content database error.
Is replacing the DB is wrong. is there any other way to migrate SP server from one machine to another. I have tried my taking Farm backup and restore i had many problem with that. so i feel replacing DB would be better for me. any suggestions please?
Move SharePoint between servers is a huge effort.
Data in databases are very depends on the SharePoint install and its environments. So, I suggest just re-install the SharePoint on the new server, and then restore site collection backups to the new install.
Install SharePoint Server on the new server machine
Backup site collections from the old server, follow this guide: http://technet.microsoft.com/en-us/library/cc263441(v=office.12).aspx
Create Web Applications on the new server
Restore site collections from the prev. backups, follow this guide: http://technet.microsoft.com/en-us/library/cc262087(v=office.12).aspx
Be aware, if you have farm level customize solutions (developed by Visual Studio) or css files deployed in the LAYOUT folder, don't forget to re-deploy them on the new server.
I guess this question is too old and my answer will not help topicstarter... However, I was looking to refresh my own knowledge on this topic and I feel it will be useful to share it here.
This solution is not good for every SharePoint deployments, of course, it's just a general idea.
And I don't think it suits production environments well... but if you are brave and foolish as myself, you can do it there as well, with some additional precautions like backups and so on.
Here are prerequisites:
SharePoint was initially installed in Farm mode (not in Single Server mode)
Both old and new servers are in the same domain
You know Farm Passphrase used for initial installation
Old server is still intact and accessible from the new server
Steps to do
Skip steps 2-6 if you don't want to move databases to new location
Install SharePoint on the new server and join to existing farm. See
https://technet.microsoft.com/en-us/library/cc261752.aspx for details on joining procedure.
Ensure that the SharePoint is read-only. You can just shut down MS SQL DBEngine service if it's ok for your users.
Install MSSQL Server on the new server or other location you want. Remember, that it's not a good idea to keep SharePoint and MSSQL on the same server if it's not a demo/dev environment
Move all SharePoint databases to the new MSSQL Server. You can simply copy all DB files and attach it to the new SQL, or go full backup and restore way.
Important: Create an SQL client alias on the new server with cliconfg tool. See blogs.msdn.com/b/priyo/archive/2013/09/13/sql-alias-for-sharepoint.aspx for details.
Use your old SQL instance name as alias name. E.g. if your old server had SQL installed alongside with SharePoint on SharePoint.mydomain.com, alias name should be "SharePoint.mydomain.com"
Set Server name for alias to the new SQL location. Something like "NewServer.mydomain.com"
Ensure that you specify correct port number for SQL connection or configure network for default dynamic port. It is not necessary only if you have local SQL server on the same machine.
Create identical SQL client alias on the old server (this is needed to correctly remove old server from farm)
Remove old server from the farm. See this technet article for details
Update DNS settings or whatever you use to point users to the new server.
That's it. Hope it will help someone
We have a couple production servers that are configured to only allow access via RDP. There are no acessible shares. The dev team have no say in changing this setup but we want to automate code deployments to these machines. Presently we have to set Remote Desktop to share a local drive with the server, then RDP to the server and manually copy the deployment.
Any one know of a way to tunnel over RDP and drop files to a given directory on the remote host from the command line? The instructions will need to be included in an MSBuild configuration.
If you can get WS-MAN set up, PowerShell remoting and/or pmodem might be your ticket? https://web.archive.org/web/20180429054125/http://www.nivot.org/blog/2009/11/default