vDisk Placement NAS(CIFS, NFS) or Block Based/local?






My choice: Local Storage. Keep it simple. With CIFS you implement another possible bottleneck


Solved Storefront replication or server group join fails

Replication/join server group fails for storefront with an error

An error occured running the command: ‘Get-DSClusterConfigurationUpdateState’
There was no endpoint listening at net.tcp://xxxxxx/Citrix/ConfigurationReplication that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

An error occured running the command: ‘Get-DSClusterConfigurationUpdateState’
Could not connect to net.tcp://xxxxxxxxx/Citrix/ConfigurationReplication. The connection attempt lasted for a time span of 00:00:01.0312440. TCP error code 10061: No connection could be made because the target machine actively refused it xx.xx.xx.xx:808

An error has occured during the all server configuration update process.
Citrix.DeliveryServices.ConfigurationReplication.Exceptions.ServerUpdateConfigurationException, Citrix.DeliveryServices.ConfigurationReplication, Version=, Culture=neutral, PublicKeyToken=e8b77d454fa2a856
An error occured running the command: ‘Add-DSFeatureInstances’
RemoteEndpoint: net.tcp://xxxxx/Citrix/ConfigurationReplication

Storefront Join server to a storefront cluster

– Deinstall current Storefront installation

– Enable Netbios over TCP-IP

– Delete folder <>:\program files\Citrix\Storefront

– Delete folder <>:\inetpub\wwwroot\citrix



If exist delete the following in IIS Manager under application pool:


Citrix Delivery Services Authentication

Citrix Delivery Services Resources

Citrix Receiver for Web


Note: Possible that some application pools can’t be removed. open %windir%\system32\inetsrv\config\applicationhost.config. Remove lines <application path=”/ until </application>. After that you can remove the application pool


– Start the Storefront Installation and  join server group, server will join succesfully!

Add driver package not applied in OSD server 2008R2 and OSD error 31 on Server 2012R2

last days i had the following symptoms/failures with OSD in SCCM 2012 r2:

– Migrated server 2008 r2 task sequence deployment has failed to Run. VMWare VMXNET 3 drivers dont get injected or applied in the OS. Ethernet controller is missing in device management.

– New server 2012 r2 deployement fails with error code 31. Exiting with code 0x80004005 Windows setup failed, code 31.

– After troubleshooting for a day i wasnt able to build and capture task sequences with Operating System Installers in sccm 2012 r2.


I thought build and capture wizard had a bug. after googling i found the following article. wow Microsoft just changed the working!

see this article. This is a nice article also. Helps you with OSD

What’s New in System Center 2012 Configuration Manager SP1

The build and capture task sequence was updated to apply an operating system image instead of running Setup.exe for installation. You can still run Setup.exe for Windows 8 deployments by editing the task sequence in the task sequence editor. :(:(:(
After selecting “Apply operating system from a captured image” instead of “Apply operating system from an installation source” and run the deployment it was successful!