Category : Windows

Blog, certificate, Citrix, NetScaler, Windows
1

How to create, export and install SSL certificate from the Windows Server to the NetScaler

 

This is an example how to create, export and install Windows Server Root CA signed certificate to the NetScaler appliance.

Create Certificate Request on Windows Server:

 

Choose Request a certificate on your Windows CA:

Choose advanced certificate request:

Choose Submit a certificate…:

Copy-Paste your Certification Request and choose Certificate Template Web Server:

Download and save your certificate:

Complete your Certificate Request:

Open Certificates MMC Snap-in, choose certificate and and export:

Log in to your NetScaler 10.1 and install certificate (for NetScaler 10.5 same method works, GUIs look is just a bit different)

Choose Import PKCS#12:

Choose Output file name whatever you want, browse PKCS#12 certificate file we just exported and type Password we created in certificate export phase:

Choose Manage Certificates / Keys / CSRs:

Download certificate .key file, change filetype association from .key to the .cer and upload it back to the NetScaler:

Choose Install…

Install certificate:

And that’s it! Now you have properly exported and installed certificate on your NetScaler.

 

[facebook_like_button]

 

 

Views: 3531

Read More
Blog, Citrix, Licensing, Microsoft, RDS, VDA, VDI, Windows, XenApp, XenDesktop
2

Citrix VDI and Microsoft RDS licensing explained

People asks continually from me what kind of licenses are needed in current cases and often I come across situations where I need to clarifying for the customers Microsoft and Citrix different licenses. I’ve put together mine checklist in different scenarios.

To access VDI, you need Windows Software Assurance on the client device or Microsoft Virtual Desktop Access licenses. RDS CALs are not used in this case. Windows Software Assurance and Virtual Desktop Access licenses include home use rights.

To connect to VDI, you need the following licenses:

  • Citrix XenDesktop VDI Only Edition or higher.
  • Either Windows Software Assurance or VDA license. You don’t need both. The license is assigned to the client device.

XenDesktop Enterprise and Platinum include the Citrix licenses to connect to Remote Desktop Session Host. But each named user would also need an RDS CAL.

To connect to Remote Desktop Session Host, you need the following licenses:

  • Citrix XenDesktop Enterprise or Platinum
  • Windows Server OS license for the RDS server
  • Microsoft Remote Desktop Services CAL for each named user

 

Streaming App-V to virtual desktops you need MDOP licenses. If you are streaming App-V to Remote Desktop Session Host then App-V is included in the RDS CAL price.

To stream apps using App-V, you need the following licenses:

  • To stream to virtual desktops, purchase MDOP for each client device
  • To stream to RDSH, no additional license is needed.

 

And here is a good links!

Windows Server 2012 R2 Remote Desktop Services Licensing Data Sheet:
http://download.microsoft.com/download/6/B/A/6BA3215A-C8B5-4AD1-AA8E-6C93606A4CFB/Windows_Server_2012_R2_Remote_Desktop_Services_Licensing_Datasheet.pdf

Understanding Remote Desktop Licensing:
http://technet.microsoft.com/en-us/library/cc772298.aspx

Citrix product licensing information:
http://www.citrix.com/buy/licensing/product.html

Citrix licenses explained:
http://support.citrix.com/proddocs/topic/licensing-1111/lic-license-types.html

 

[facebook_like_button]

 

Views: 7724

Read More
Active Directory, Blog, Microsoft, Windows
0

Windows Server 2008 Domain Controller Replication Error “The target principal name is incorrect”

Recently I’ve picked up a client with some issues with Active Directory replication. Domain Controller seemed to be offline and launching Active Directory Domains and Trusts GUI tool error message “The target principal name is incorrect” pop-up.

Fastest way was to demote it, cleanup meta data, seize FSMO roles to the another healthy Domain Controller which has Global Gatalog as well and promote back.

1. Faulty DC: Force demotion of the faulty Domain Controller by running DCPROMO /FORCEREMOVAL.

2. Healthy DC: Perform a metadata cleanup, see: http://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx

3. Healthy DC: Run NETDOM QUERY FSMO to see if the old Domain Controller was an FSMO holder. If yes, seize the FSMO roles that it was holding on another Domain Controller. See: http://support.microsoft.com/kb/255504

4. Faulty DC: After server rebooted change DNS settings to point another Domain Controller if it’s not.

4. Faulty DC: Run DCPROMO to promote Domain Controller back.

 

[facebook_like_button]

 

 

Views: 1810

Read More
1 2