I've been given oversight access to an azure account for our business.
I'm trying to see if there is a way to view the latest code updates and history.
Is there a way to do that in Azure?
An Azure Account might not be enough for that. A Azure Website usually doesn't contain source files (there are exceptions e. g. plain html sites). They contain build artifacts / binaries that are build from the source files.
The code for your Azure Website is probably under version control. That means that your developer are using a plattform to commit the code. An example is Visual Studio Team Services (VSTS), GitHub, etc...
You have to get access to the version control system used by your developers in order to view the latest code updates and history.
Related
I have a sharepoint site that I'd like to migrate to a new tenant. I read that I'll have to use third party tools like Metalogix to do it properly. Are there any alternative ways with which I can achieve this, preferably without a third-party tool? I just have two sites with few contents and couple of apps. I found sharepoint migration tool: http://spmtreleasescus.blob.core.windows.net/install/default.htm But I'm not sure if it's used for tenant-to-tenant migration.
With two sites and perhaps a few document libraries, perhaps a manual migration would work: Manually create the destination sites/libraries, and for a given library, sync it. Since it's a new library, there is no content to sync, but it will create the folders, etc., on your local machine via onedrive. Open that location with windows explorer. Then, go to the source library with Internet explorer, and use the open with windows explorer command. (or, sync it also). Then, simple copy the files from the source to the target library in the windows explorer onedrive view. OneDrive will take care of syncing the files up to the library.
If have a bunch of libraries, or if you need to preserve things like file created dates, then the 3rd party tools are helpful. Another popular one is ShareGate.
The third party tools can often also copy metadata, versions and Content Types.
Some of these tools have free, for limited amounts of data, trial versions.
I am using Team Foundation Server by Microsoft. I will probably migrate from one account(server) to another account, and I would like to preserve following things:
source control of files
users
scrum sprints (epics, backlogs, tasks, bugs)
builds
Azure subscription:
move all web services
move all sql databases
How can I approach this? Is this manual work one by one, or can I use some tool for migration?
There is a TFS migration tool / body of knowledge that will help you thought most of the items you list under TFS. You can find it here. This should be fairly straight forward unless you have customised process templates which then create a few more headaches. Moving Builds may be tricky, there is a recently released article on scripting builds with YAML which may be of use.
For the Azure components, you can:
Move databases between subscriptions
and I believe you can do similar for WebApps/Services. You can also move subscriptions using PowerShell.
Alright, I am obviously missing something here. I have moved several websites over to Azure to take advantage of all that it has to offer. Traditionally our team has always used DreamWeaver to ftp up/down and such. What I don't understand is how I go about getting hooked up to an EXISTING site on Azure. I can easily setup and web deploy to a NEW site, but I am trying to give the rest of the team access to the sites I have setup and I am lost as to how to approach this.
I have tried the File > Open Web Site route, and the issue with that is it never then saves the project/info anywhere in VS, and we are required to hook back up to it each time.
All of our local sites are on a shared network drive, so we all access the same local resources. I thought I could simply pass them all the publish profiles and they could then import, get, and then edit and publish files... but it never gives the option to "get all files" from the server.
Hope this makes sense?! Thanks in advance! :)
For multiple developer scenarios, it would be in your best interest to use a source control system such as Git or TFS. This will allow you not only to share the source across team members, but also give you the benefit of tracking changes and merging files that are modified across team members.
If you aren't comfortable with source control, you do still have access to the files via FTP or Secure FTP.
You could also use WebMatrix which has the concept of download from server built directly into the tooling.
We have a company SharePoint site that we paid a company to configure and setup for us. We are slowly taking over more and more of the administration of this site. We would like to setup a test environment so we can make changes with out affecting daily business.
How can we take what they have already installed, deployed, and configured and make a copy of it?
I know we can backup the database, but what about the stuff the downloaded and deployed into the system?
None of what they installed are paid applications from what i can tell. They look like the base applications from the Microsoft SharePoint site like Case Management, Knowledge Base, and a few others.
Thanks
You should take an inventory of the installed solutions, you can see that in the list of solutions under central administration. Then try to identity 3rd party solutions and get the WSP files (I bet they are stored in a folder on your server :))
Set up a new environment, make sure to install exactly the same version, including any service packs and/or hotfixes. You can get that list when you search for the version number in Google (the version number is usually seen in the Site Administration page).
After that, install your custom solutions and attach the content database, this should be it.
I'm in the process of moving a complete sharepoint install to a different server.
Can anyone tell me if it's possible to just move the existing Shared Services Provider rather than starting from scratch?
All the best
You really need to move the SSP in concert with everything else in the farm. The two things to move are 1. databases and 2. the file system.
A .doc file for moving all of the SharePoint databases has been published here. Microsoft will soon have an updated procedure for this published on TechNet, according to the To The SharePoint blog.
Then to cover off any file system changes, I would set up a clean install of SharePoint (if you didn't need to already by following the document mentioned above) and do a file comparison between your source and destination SharePoint application servers. I usually use WinMerge as its free but Beyond Compare is also good. Also check any custom solutions are deployed on your destination server.
By ensuring your databases are moved correctly and all of your files are in place you should be OK. Make sure you test every custom component on your destination server before erasing the source databases and files (even better, archive the source).
Yes, create a new SSP and move the applications.
How to on migration of applications here
For moving the SSP to a new farm
Or try the Microsoft SharePoint Administration ToolKit v2.0
For another view of this