While doing storefront deployment we came across the error " The Citrix Credential Wallet service is not running"
It also had following error in the event log which point to some kind of timeout while starting the service.
We tried putting service into delay start mode to see if that fix the issue
While doing research we found that config file need to be modified if StoreFront server do not have Internet connectivity
And change the value from true to false and finally service got started
There might be multiple ways to allocate lun to Hyper-V clusters but I follow below way . Once lun is allocated via storage system it will be available via disk management on one of the cluster node. Bring it online and format it without drive letter and partition name.
Once drive is formatted open cluster manager and browse to storage right click to add the storage
Once added it will show up as available storage
Now we need to allocate this to cluster shared volumes
Once this is allocated it will showup under cluster manager and under SCVMM
While running cluster validation it keep throwing warning 
Warning message says that "No Disks were found on which to perform cluster validation tests. To correct this,review that following possible causes:
Here it clearly says that disk should be offline when running this cluster validation test. After bring quorum disk offline and run the validation test and it went through.
While creating virtual networking on one of the Hyper-V 2008R2 host
It was giving an error 12700 VMM cannot complete the host operation on <servername> server because of the error
I tried rebooting/removing and reading back to cluster . But then it always throw an error while creating Virtual Network. Because of this I was not even able to create VM on the cluster . It was giving error "Error 20400 1 parallel subtasks failed during execution.
Found MS KB 2486812 which explain how to fix and what is the root cause. Downloaded nvspbind and run it on problematic Hyper-V cluster.
And finally I was able to create Virtual Network
I wanted to provide CNAME as a DB connection for SCVMM rather than actual server name. The reason for doing so was to make sure incase of mirrored DB goes down, I can make DNS changes and that can take care of SCVMM rather than making registry or application level changes.There are many ways to do so but one registry hack can also make changes.
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\Sql " and update following changes
Restart System Center service and this will update SCVMM as well.
Posts
All Comments
