23

My problem solved! Have a follow this link. Turn off distributed cache: Site loading time with it off: site loading time with it on: !!! From 6.10 seconds down to 79 ms


8

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 ...


6

Sure it is! Here is the link: It's huge because it has Project server, etc...


6

For me, reprovisioning the distributed cache service resolved the performance issue: $serviceInstance. = Get-SPServiceInstance | Where { $_.TypeName -like "Distributed Cache"} $serviceInstance.Unprovision() $serviceInstance.Provision()


5

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


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 to ...


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

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

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 ...


3

It is supported to virtualize the SQL Server, but we cannot make a specific recommendation for you as that would require knowing the performance of the hardware, required overhead, and so on. The best thing you can do is verify the virtualized hardware can support the existing load + some overhead of your SQL instance. As far as the recommended route, you ...


3

Practically, both will work properly with SharePoint, the two products are the same in terms of max configurations. For comparison check Choosing between VMware and Hyper-V I prefer the Hyper-V for the following reasons: Deploying new virtual servers in short times (Minutes). In many cases, there is no downtime for maintenance. The backup process is ...


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

My suggestion to you would not be to "clone" the machine exactly. I would suggestion creating a new VM that has the same software installed as Production (same SP build, etc). Then make use the database attach method for migrating the content databases from your Prod SQL to Test SQL.


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

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

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

If anyone is still struggling with this the answer is here. I also had very slow performance, I increased the memory allocated to the Distributed Cache from the default of 410MB to 7168MB and now my site is behaving as it should do.


2

I think you are pretty much on the right track. Make sure that your VM is at the same level as your production. You can check the SharePoint versions by going into the Operations tab, and under Topology and Services, select Servers in Farm. Install the language pack on your personal VM. Create a new web application in your personal VM. Install all the WSPs ...


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

unfortunatly there is no vm for 2010 available since 2013 came out! you need to build it yourself! you need a few things: 1) a virtual machine like Oracle VM VirtualBox (I use and is reliable) 2) a windows server (for you windows 8x) 3) sharepoint 2010 installation! 4) sql server installation (depending on your structure) you can follow this guide to ...


2

If you want to use Active Directory for your accounts, then yes, you need to configure your machines on a virtual LAN and create an Active Directory domain. This is not a simple process and isn't really on topic for this site. You should be able to find tutorials on this process pretty easily using Google. Does every machine has to have the same ...


2

Yes, but it depends on how you set up the environment. If the Hyper-V VM has full network access (that is, you can ping it from your client), and if you set up your Web Application to use the machine name of the VM, you can just go to http://machineName. Or, if you set up a specific hostname that is not the machine name, or a full FQDN, you can edit the ...


2

There seems to be two images which both are trial versions of SharePoint 2013/2016 There is also two solutiontemplates for SharePoint 2013 Microsoft has a doc describing on how to setup an 2013 dev environment in azure. There is also an article describing how to setup an 2016 environment. If you want to setup one manually. SharePoint 2013 dev/test ...


2

Yes it is possible you need to either create DNS entry (if you have it on your network) or update the host file on VM2 with the details of your SP web app and IP of VM1. host file is located in Windows\system32\drivers\etc


1

Most likely because your machine doesn't have sufficient memory. SharePoint performance mostly depends on Hard disk and memory however SP 2013 is a memory beast, I don't think 12gb is enough if it's a single development server, check this article out, Why SharePoint 2013 requires so much memory? I installed SharePoint 2013 on a single box along with 6gb ...


1

be sure: to add your site into host file on VM (C:\Windows\System32\drivers\etc) Add bindings to IIS (http://technet.microsoft.com/en-us/library/cc731692(v=ws.10).aspx) hope it helps, Andrew


1

I'd probably ensure you're VM's network card is setup in 'Bridged' mode (depending on what flavour of virtualisation you're using) then create a SQL alias on your SharePoint server VM (c:\windows\System32\cliconfg.exe) select enable TCP create an alias of you're choosing (SQLALIAS) point it at the IP address of your local machine and install SharePoint with ...


1

If you install SQL on your local machine and SharePoint on your virtual machine it should work without a problem as long the can access the same network. Make sure that at least the following is true: Both machines are in the same domain and you can login to the machines using the SharePoint administrator account On the SQL machine make sure the port ...


1

First of I'd recommend that you install Windows Server 2008 (R2) on the virtual machine instead of Windows 7. The option to support windows 7 as a dev environment was a bad choice made by the SharePoint team for SP2010 as it's not working 100% (and they've corrected that error in SP2013). Regardless of that my preference regarding user accounts for a dev ...


1

Yes, I'd continue to use one or more domain (service) accounts even for a development machine. If your SharePoint Server was not joined to the domain, it could get its user base from local Windows accounts or other data sources (AD LDS/ADAM, SQL, etc).


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