Skip to main content


Showing posts from April, 2012

Moving Sitecore item from one instance (Active Directory 1) to another (Active Directory 2)

We have Sitecore out of box package designer to package items and to move it to another instance. Let’s say we have two instance of Sitecore. First one is integrated with Active directory 1 (for example: ad1) and second with active directory 2(ad2). But it is really important to unlock all the items before packaging and installing it in another instance.

Scenario: In Instance 1 (ad1), a user (ad1\user1) locks an item. Sitecore item will be locked with ad1\user1 id. User packages the item and moves it to another instance. User installs the package in second instance. Those items will be still locked with ad1\user1 in second instance too. Importantly even if you login with admin user and try to unlock the item, admin will not be able to unlock it.

Resolution: Go to first instance, unlock the item, package it and install it in second instance.

How to deploy a Site in Sitecore in Production (Multi-domain) - 11

In web.config file, we have <sites> node to configure roothpath, startitem, host name etc. For production deployment, we have to use and So we added to <sites> node in web.config file. We came to know that it created two cache folders, one for each website node. To avoid this, we have to create a single node for the site with hostname as “*” (Please don’t use dot in the host name.). <site name=”example” hostname=“*” … />

Kick Logged/Unused session in Sitecore Client in the admin – 10

While the number of sites in Sitecore increases, the number of users using Sitecore client will be huge and there will be slowness in Sitecore. And sometimes, the user session will not be available for another user to login and also there will be few issues with media library too. In such scenario, we need to close the user session explicitly by logging into admin to kick such unused sessions. The url to see all the user session (both using and used session) is

Log into to Sitecore using Admin user and kick such unused session to resolve this issue.