For an existing site, you would want to create the site manually in IIS.
Create a new website in IIS, point the folder to your website folder.
Make sure the binding is setup to something like mywebsite.local.
Make sure the permissions on the website folder are set to allow the AppPool user for your new website to have read & write access.
Restore the ...
SIM only works with ZIP archive of the Sitecore root folder archives, not with the .EXE installer versions.
Also, it relies on the archive name being exactly the same as it is when downloaded directly from Sitecore. So if the 8.2 zip you have has been renamed or altered in any way, SIM will not recognise it.
There are no steps in SIM to clean the default items from the install of Sitecore. You can create a package containing a Post Deploy Step that will delete any items you wish though and add this as a Custom Package in SIM.
Create the following Post Deploy Step:
SIM copies the database files (all the .MDFs and .LDFs) into your \[webroot]\Databases folder, then uses the SQL Server connection string specified in your SIM settings (see image below) to attach the database files to your SQL Server instance and updates your ConnectionStrings.config file to point to that specified instance.
Since SIM does an attach action ...
The hostname should be habitat.dev.local on your Sim installation.
In the site definition you have:
<site name="habitat" patch:after="site[@name='modules_website']"
@Richard Seal's answer is entirely correct, but if you are worried about setting IIS and NTFS security things manually, you can also follow these steps:
Install a fresh Sitecore instance like you normally would using SIM or the installer.
Replace the installed Website folder with the Website folder you received from the client.
Then proceed as with the ...
You're missing Windows Process Activation Service on your computer.
Check Control Panel > Programs > Programs and Features > Windows Process Activation Service.
More details here:
When you download the package the default filenames for SXA are Sitecore Experience Accelerator 1.2 rev. 161216 for 8.1.zip and Sitecore Experience Accelerator 1.2 rev. 161216 for 8.2.zip.
Rename the file removing everything after the revision number and it will then show up in the Modules list, i.e. rename the file to Sitecore Experience Accelerator 1.2 ...
SIM uses a zip archive of the Sitecore root folder, so a simple way to do this would be to take the version of Sitecore you want to setup, install that with the basic options.
Next open up Sitecore and delete all the sample content you do not want. Open SQL Server Management Studio and detach the Core & Master databases.
Finally, locate the ...
It is very simple to run SIMCMD (Command Line version of SIM):
Click Bundled Tools - Command Line
N.B. Step 2 here simply downloads latest version from dl.sitecore.net
Note even though it is available in Release version, this feature is still kind of experimental and does not support all functions of full version. So I highly recommend to ...
When we need to do this type of content refresh, we generally follow the below steps:
Backup the PROD and QA master databases.
Restore a backup of the PROD master database into the QA database server.
Note: you may need to stop the AppPool for your CM environment to perform this restore.
Deploy the latest code and developer-controlled Sitecore items to ...
You need to make sure to delete / remove these entries:
website under c:/inetpub/wwwroot
relevant Application Pool in IIS
relevant entries in hosts file located under C:\Windows\System32\drivers\etc\drivers
relevant databases in SQL Server and also MongoDB collections
open regedit and remove relevant instance name under [HKEY_LOCAL_MACHINE\SOFTWARE\Sitecore ...
SIM is a click-once application
You can launch it from command line, but it's not so obvious how. There are a couple of ways to launch it. One would be to invoke something like iexplore.exe, pointing it to the URL of the SIM installation.
My preferred method is launching it via the local .appref-ms file. You find it like this:
Open up "Start", find ...
Another options would be to use VMware kind of software to take snapshot of complete installation of a dev machine and then create developer machines using that snapshot.
SIM is not the tool for your requirement. You can use it to create quick instance. But, not a tool provide sync environments across developer machines.
We have used a powershell script that does everything:
install SQL databases
install solr and configure
build base VS projects
I would suggest investigating powershell. It will give you a lot of flexibility, for example different steps for different teams.
SIM doesn't perform the post-install steps (running the SQL script, updating the web.config for captcha, etc...). It does "complete", for all intents and purposes, but SIM gets stuck on the placeholder selection dialog at the end of the installation.
But apart from that, everything is installed as it should be.
Since you are installing this on two separate VMs you have two options.
1) If the VMs are in the same domain, you must grant the NetworkService of the computer running SIM access the VMs and run the MSSQLSERVER Service as NetworkService on the computer running SIM. I do not recommend this because you are giving a system account access across servers.
I'd suggest your "blank slate" need not be so blank at all. So I'm guessing here; but after cleaning out the items and templates you mention, wouldn't you normally proceed to set up a set of folders and items - which remain much the same for any solution?
Even if you don't; I would propose you solve what you're trying to achieve here using Unicorn. Basic ...
By default, SQL Server is only configured to allow Windows Authenticated connections. When using a "normal" connection string like the one you mention here, you need Mixed Mode authentication.
Setting Mixed Mode for the first time will force you to define the sa account and a password. For your dev box (and only your dev box) I would normally recommend just ...
You will require to download the followings:
Java SE Runtime Environment 9.0.1
Download all and install the JRE 9.0.1 at default location
Extract all the contents of the SOLR and NSSM in the directory
Now run the save the following as the PowerShell and run it, it will do the rest installation for Solr 6.6.2.
Did you check the IIS? Also check the folder C:\inetpub\wwwroot\[yoursite] if it exists, delete it and check again.
For a clean install you need to do the followings.
Delete all the databases with your installation instance name.
Delete the folder from the inetpub C:\inetpub\wwwroot\[yoursite]
Remove Website from IIS.
Remove host entry from C:\Windows\...
Yes, you should not source control entire /website folder.
I assume that team had made changes to files like cshtml, config, css etc and in that case you will need to compare vanilla version of Sitecore with your website folder and copy new files you find in website folder to source control straight away. There are so many tools available to do this but I ...
With your requirement for remote SQL this might not work. But with SIM you can export an existing instance and then import it again on another dev machine.
I have also used this PowerShell script to create Sitecore 8 instances in CI environments.
Welcome to the site!
If the "shared" part you want is the database, the easiest way is to install Sitecore and then just update the connection strings after the installation. This will point your installation at the existing databases that you have. You can then delete your new 'empty' databases, or keep them for when you want to switch to "isolated" mode.
To add SSL to Solr,We need to generate the ssl key by using java keyttol.exe which is in location ‘C:\Program Files\solr-6.6.2\server\etc’.Set up the certificate by using certificate installation wizard if not OpenSSL.
You can follow the Add SSL to Solr instructions on URL https://horizontalintegration.blog/2018/03/06/sitecore-9-0-installation-with-sif/
Assuming you have installed Solr using the Bitnami Wizard:
To disable authentication, remove the LocationMatch section that you will find at installdir/apache-solr/conf/solr.conf
Restart all services (Solr and maybe Zookeeper) after saving the changes. Now Solr won't ask you for credentials.
The Solr installer of SIM is not very clever, and if it fails ...