Set default website for StoreFront

With webinterface you can set default website while creating website

But with StoreFront you either have to follow CTX133903 or just set it using IIS

StoreFront error : No certificate associated with this site

I was adding second server in the server group but it was throwing error while replicating configuration

Log Name:      Citrix Delivery Services
Source:        Citrix Configuration Replication Service
Date:          2/17/2014 6:13:06 PM
Event ID:      31
Task Category: (2801)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXX
Description:
An error has occured during the all server configuration update process.
Citrix.DeliveryServices.ConfigurationReplication.Exceptions.ServerUpdateConfigurationException, Citrix.DeliveryServices.ConfigurationReplication, Version=2.4.0.0, Culture=neutral, PublicKeyToken=e8b77d454fa2a856
An error occured running the command: 'Add-DSFeatureInstances'
RemoteEndpoint: net.tcp://XXX/Citrix/ConfigurationReplication

Then we also saw following  message “No certificate associated with this site” though site was https. I tried several thing like renaming url but looks like it something else

Finally found that certificate was saved under “Web hosting   Certificate ” whereas it must be under “Personal – Certificate “

Once it was placed and binding were configured

All the sites were green

After we fixed this error replication went successfully

Autoconfiguration IPv4 on Hyper V VM

I configured on hyperV VM on SCVMM2012R2 and it was not able to communicate over the LAN. When I checked network property it had Autoconfiguration IPv4 enabled with APIPA ( Automatic Private Internet Protocol Addressing ) .

Not sure what was causing it, tried googling but couldn’t find anything relevant. Checked for hidden nic but couldn’t find any. Finally changed IP address and that worked. Looks like above IP was somewhere on the network and this is enabling Autoconfiguration IPv4

Adding second node to the virtual SQL cluster 2012 on Windows 2012R2 using VMM–Part 3

In my previous  blog I explained how to install  the first node in this blog I will explain how to add the second node to the existing cluster.   Run the SQL setup and choose “Add node to a SQL Serverfailover cluster ”

This will run the check for prerequisite and validate it

 

Don’t run the check for updates and then exist the steps. It will run again SQL cluster install rule

Next it will check for product key and then license term. Post which it will identify SQL cluster node and will populate the info

Then it will validate the network for fail over cluster

Next it will pick  account for which you must retype the password

Then it will prompt for error reporting which you can choose as per wish. Click next and proceed further where it will check for node rules

It will give beautiful summary to add the node.

Finally installation of SQL second node will be done

Finally node has been added and here is the summary

Thanks for reading my blog, today I configured DDC on fail over cluster

How to setup virtual SQL 2012 cluster on windows 2012R2 VM using SCVMM2012R2 Part-2

Post windows cluster validation describe in part1, prerequisite like  .Net3.5 feature must be installed on all the SQL server. Other than it will be normal windows fail over cluster and then start SQL setup as follows.

 

It will check for necessary support files and then validated it by running test

Next it will check for the latest update , uncheck it and click next

This will check install file post which it will run the validation for setup support rules

Setup rules will finish with some warning which can be ignored

Now this will ask for product key and if this has already downloaded with key then it will appear

For my Citrix XenDesktop deployment I just need following feature

Feature rules will test for cluster support

Here I am using  network name as CitrixSQL. It does not accept special character

Next it will check validate the space

Don’t worry about qualified as red . I spend lots of time figuring that out but next will explain why it was . So hit next here

Once hit next make sure select both the cluster disk. If you recall in my previous post, I did mention why labeling of disk is mandatory. This was the reason. Update the message with correct reference.

This cluster IP is for SQL cluster node name.

I usually run SQL service using specific account

Next we have server config  where I specify SA password

On the same option Data Directories tab is important. This will insure that database and logs stored separately. After changing click on next.

I don’t want to do error reporting to MS so I hit next where it check for cluster installation rules.

With this we are ready to install and keep our finger crossed

For me SQL installation finish with the following error message

I followed article and manually created  the cluster resource under AD and then gave full control to windows cluster name. Post which all the resource came online.