Tag Info

Hot answers tagged

7

If you don't want to use it on Hyper-V, there's a couple of ways you can go: convert it over the VMware's VMDK format. I've heard of people who have done so successfully, but then I've also seen some comments where issues have arisen in those converted VMs. My take is that if you have a short term need for the VM, converting it is not a bad way to go but I ...


6

Sure it is! Here is the link: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27417 It's huge because it has Project server, etc...


5

Developing for SharePoint for SharePoint with VS2010 requires running it on a machine with SharePoint installed locally. I would not recommend doing the Windows 7 install of SharePoint as you do not get full functionality of the Server edition with a Windows 7 install. Sounds like you have the RAM to run a virtual machine. I would recommend doing a Windows ...


5

what is the lacking's of developing sharepoint environment in VM ? You'll be mostly isolated from your host (eg : no mail notification - which is extremely good for productivity - ) whenever you're on the VM. VM requires resources on your host & depending on your CPU architecture, might be heavy. It also requires a clean and fresh host environment ...


5

For driving SP 2013 with only 12 GB of RAM I recommend that you stop the search from doing continous crawls, and to stop any services that you do not plan to use. Otherwise you will ned a bit more memory. The search continous crawl uses a massive amount of system resources, so in a low performance environment, it should be turned of if it is not extremely ...


5

My problem solved! Have look at: http://blog.blksthl.com/2013/05/15/sharepoint-2013-page-loads-takes-a-very-long-time/ turn off distributed cache: Site loading time with it off: site loading time with it on: !!! From 6.10 seconds down to 79 ms


4

I would suggest TortioiseSVN and VisualSVN Server. Both free if you use the VisualSVN standard edition (http://www.visualsvn.com/server/). This should be more than enough for a single developer. Best bet would be to setup VisualSVN on a separate server/virtual machine.


4

You can either do a dual-boot scenario where boot from more than one hard drive, or you can run some form of virtualization software (VMWare, Virtual Box, or Virtual PC/Server). You would then want to install your dev tools on the server.


4

Tim mentioned the sysprep process which is a good first step. It is also important to understand the definition of a farm. When you run the Configuration Wizard that first time it will create the configuration database. That database includes server names saved in the database tables. You cannot connect to vmdev2's configuration database because it ...


4

CloudShare is the only service I know that offers pre-configured, cloud-hosted SharePoint development VMs. I pay $60 a month for their Pro Plus service, which I feel is fair for what they offer.


3

I would look into the Content Database not being accessible. From Central Admin I would look at the status of the content database as a starting point. You can do that from Application Management under the Database section of options. How are the services looking from the server. Do they look healthy? Might want to check the app pool status under IIS.


3

Okay. finally, I found a article and it helped me right away... http://www.howtogeek.com/howto/vmware/allow-access-to-a-vmware-virtual-machinenat-from-another-computer/ Went to "Virtual Network Editor" from my host computer (found under VMWare menu) Change the IP address for the NAT subnet ip to 192.168.10.0 Followed the article above for more on NAT ...


3

Scripting is your friend, I have done it before where the dev VM images was a master (for tools, and patches) and was refreshed regularly (I aimed for every sprint) with the SharePoint install being automated. Ben Curry and Gary Lapointe did some good work around scripting 2007 builds, which we used. But also I created a custom setup exe that would do a ...


3

First off you need to bump up your RAM. I'd do at least 4GB for a dev machine. Then you need to disable any services you don't need (search is a big one). Also, make sure you're making efficient use of your app pools (no need for a least privileges model in dev unless you explicitly need it). Not sure if your VM is also a DC or not - if it is then you might ...


3

I agree on increasing memory and invest in a secondary SSD drive. If you're going to develop on the machine and use SharePoint Server 4GB is the least amount you should have dedicated to the VM. Another tip is to NOT use a lot of CPU's and cores for your VM - instead of increasing performance you will more likely decrease the VM performance since it has to ...


3

As Steve B said, there's no problem having TFS on another domain. It will prompt you for credentials. We typically develop on SharePoint VMs that are also their own domains - thus they are completely independent. We have no problem with using TFS on our company domain, though it does help if you use Windows's option to remember your credentials. See ...


2

Apart from memory, constantly resetting app pools and spinning SharePoint is very I/O intensive. The biggest performance improvement I have experienced myself was running the main SharePoint VM on an SSD drive. I left the domain controller on a different hard drive. http://planetwilson.blogspot.com/2010/03/ssd-goodness-and-sharepoint-virtual.html


2

If you are single developer you really do not need TFS, that's an overkill. You can look at open source alternatives like Subversion or Mercurial. Here is what you should do: Always install your source control system on a dedicated server Source control server should be part of regular company backup operations. (Your laptop is not the best place to save ...


2

You need to isolate the impact a bit more. Do you have the same issue when loading pages on the server itself? If it is on the server, than as you do as @James recommends and check out the developer dashboard on the offending pages (you'll should do this for the client side too). If it is every page, you need to start collecting information from ...


2

If you are the only person developing at your company, it might make more sense to get them to pay for an account at a dedicated source control hosting company like Codesion. That gets you cheap and accessible source control and nobody at the company has to worry about maintaining the server/VM for it.


2

There are several options for setting SharePoint development machine. A. If you have enough RAM (and you have it) you can run it on virtual machine (VMWare is best option) with Windows Server 2008, VS 2010 and SharePoint installed on it. Pros: You can easily move your virtual machine because virtual machine is not hardware based in this scenario ...


2

Depending on your needs, you may want to consider a trial hosted solution. I've recommended this to users and developers who want to test the SharePoint world with little upfront cost. Andrew Connell has setup one here in a hosted environment. The VM is free and it looks like you can get a 14 days trial subscription to the service that hosts the VM. ...


2

if your SQL box is on a different box, and you only clone the SharePoint box, then yes, the newly cloned box will still reference the existing SQL box. If this is ideal, then you might be all set. You may have some issues with server names and IPs though if you turn the clone on in the same network the actual production box is on. I would lean towards ...


2

Possibility 1: Firewall Rules Double check your firewall settings in all the servers. A very basic connectivity test would be like - If your SQL Server is running on port 1433 , please do a telnet from K2 Server and the WFE Server to the SQL Server on port 1433. Another possibility is if you are using a custom webpart with connectivity to sql based on ...


2

I'm not that kind of pro, but I also used VM for development, I just had a VM on my machine with 8gb of ram, but i noticed that it was still slow so that is why I made a bootable VM to boot from and use all the ram in my computer, and it is going faster. But regarding the advantages and disadvantages there are not that many, only what I've noticed that on ...


2

Ah, I stumbled around and finally got it. Go to "Manage Web Applications" in Sharepoint Central Administration. Click on "Sharepoint - 80" or "myserver" or whatever you named the server and then click on the Managed Paths button. Now check the box for "sites" and click okay. ( You don't have to worry about "Add a New Path".) That must update a setting ...


2

It seems you are looking for something not exactly to be centralized, and not only SharePoint. As MCT (Certified Trainer) I do have access to all VMs I could use during training, however cannot be shared beyond that purpose. I could however share one i've found for SharePoint 2013 - ...


1

Note that SharePoint can also run on a single server, so all components would be on the same server (also SQL Server). In your scenario, the 3 servers most probably referred to the Front End Servers, while the one was probably the Application server.


1

SharePoint consists of following server types: Front End web server - displays data to the user Database server - stores data Application (services) - additional services like user profiles, search, excel, word, visio and so on. There can be several instances of each server type configured as requested. SharePoint is installed to Front End and ...


1

You'll want to look in to sysprep. This shouldn't affect any of your installed files, applications, etc. It will remove all of the machine specific information. You'll want to run sysprep on the new VM. This will allow you to give it a new name, and everything else. It's merely a fresh image, but contains all of your content still in windows. It will also ...



Only top voted, non community-wiki answers of a minimum length are eligible