How does my computer know that it is connected to the internet ?

The answer is surprisingly simple for Windows computers. It attempts to connect to

http://www.msftncsi.com/ncsi.txt

NOTE: This address has been updated to www.msftconnecttest.com/connecttest.txt starting with Windows 10, version 1607

If it receives a HTTP 200 (if it receives the text “Microsoft NCSI” in the file) then you are on the internet – if it does not receive this text then you receive the warning symbol on the network item in the system notification area.

So, if you don’t have internet connectivity but need your computer to think you have for some reason (because a piece of sofwtare requires it for a lab or some toher reason) then yuo can simply create your own version of the abve site and file using your internal servers and DNS and fool your computers into thinking that they are indeed internet connected.

No product licenses found on the license server for the selected model

When running the XenApp Configuration Wizard you may get the following error.

There are many reasons this may occur but I have noticed it always occurs with the latest version of the licensing server 11.10 whether you have specified the correct Product Type or not. The work around for me was to choose “Select the model at a later time”

This will let you complete the wizard. You can then use Citrix policies to set the license server location, port and model type at which point everything works.

 

 

 

Securing NetScaler / AGEE interface

By default when you install a NetScaler or AGEE the admin interface can only be connected to by HTTP. To configure the device to allow you to connect by HTTPS complete the following steps:

1) Connect to the devices configuration utility using a browser
2) Expand the Network node
3) Click on RPC
4) Select the NSIP (NetScaler admin IP Address)
5) Click Open
6) Tick the Secure check box
7) Click OK

Installing Windows 8 on XenServer

Having trouble installing the recently released developer preview on XenServer ?

Thomas Koetzing has the fix on his blog

Create a VM with a Windows 7 template and copy the virtual machine UUID from the general tab in XenCenter or use xe vm-list in the CLI. Next you need to run the command xe vm-param-set uuid=<VMUUID> platform:viridian=false

The installation can the proceed as normal.