Configure a XenApp 6.5 Farm from scratch – Part 2

      Configure Citrix Licensing and Web Interface Server

      1. Rename the computer

        netdom renamecomputer localhost /NewName:XA-WEB1 /Reboot /Force
      2. Set the IP Address and DNS Server

        netsh interface ip set address "Local Area Connection" static 192.168.0.7 255.255.255.0 192.168.0.254 1
        netsh interface ip set dns "Local Area Connection" static 192.168.0.1 validate=no
      3. Join the domain, using PowerShell

        Add-Computer -Domain xenapplab.local
        Restart-Computer

      Install Citrix Licensing and Web Interface

      clip_image033

      clip_image034

      clip_image035

      clip_image036

      clip_image037

      clip_image038

      clip_image039

      clip_image040

      clip_image041

      clip_image042

      clip_image043

      clip_image044

      clip_image045

      clip_image046

      clip_image047

      clip_image048

      clip_image049

      clip_image050

      clip_image051

      clip_image052

      clip_image053

      clip_image054

      clip_image055

      clip_image056

      clip_image057

      clip_image058

      clip_image059

      clip_image060

      clip_image061

      clip_image062

      clip_image063

      Configure XenApp Server

      1. Rename the computer

        netdom renamecomputer localhost /NewName:XA-XA1 /Reboot /Force
      2. Set the IP Address and DNS Server

        netsh interface ip set address "Local Area Connection" static 192.168.0.3 255.255.255.0 192.168.0.254 1
        netsh interface ip set dns "Local Area Connection" static 192.168.0.1 validate=no
      3. Join the domain, using PowerShell

        Add-Computer -Domain xenapplab.local
        Restart-Computer

    Running the commands looks like this:

    clip_image064

      Install XenApp

      clip_image065

      clip_image066

      clip_image067

      clip_image068

      clip_image069

      clip_image070

      clip_image071

      clip_image072

      clip_image073

      clip_image074

      clip_image075

      clip_image076

      clip_image077

      clip_image078

      clip_image079

      Configure XenApp

      clip_image080

      clip_image081

      clip_image082

      clip_image083

      clip_image084

      clip_image085

      clip_image086

      clip_image087

      clip_image088

      clip_image089

      clip_image090

      clip_image091

      clip_image092

      clip_image093

      clip_image094

      clip_image095

      clip_image096

      clip_image097

      clip_image098

      clip_image099

      clip_image100

      clip_image101

      clip_image102

      clip_image103

      clip_image104

      clip_image105

      clip_image106

      clip_image107

Popular posts from this blog

Get local computer UUID/GUID using Windows Powershell

Use the following syntax to get the local computer's UUID/GUID using Windows Powershell: get-wmiobject Win32_ComputerSystemProduct  | Select-Object -ExpandProperty UUID Add -computername after the WMI class to find a remote computer's UUID, example: get-wmiobject Win32_ComputerSystemProduct -computername RANTPC | Select-Object -ExpandProperty UUID
Read more

PSLoggedOn Getting Started on Windows Server 2008 R2

Image
PSLoggedOn is a tool I downloaded to allow me to find out which computers a user is currently logged on to. Getting it up and running wasn’t exactly easy. I’m running a Windows Server 2008 R2 test environment. The first error I encountered was: Error browing network: The list of servers for this workgroup is not currently available. Note: I kept the spelling mistake from the error message to make it easier to find via search engines. To get past this error, you have to enable and start the “Computer Browser” service. Then I started getting the error telling me that the Administrator is not logged on. That’s simply not true because I am logged onto another server (Name: ELARA): I turned the firewall OFF OFF OFF (It is a test network after all). I enabled Network Discovery and to do that I went on a service starting frenzy: DNS Client, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host, Computer Browser After all that, I ran the script against the se
Read more

Citrix Printing Series - Auto-Creating Session Printers

Image
In addition to or as an alternative to creating client printers, XenApp and XenDesktop allow an Administrator to specify which network printers should be created within each session. This process is controlled using the "Session Printers" policy. See the user policy below: You can very cleverly configure what's known as Proximity Printing, which involves the use of the "Session Printers" policy, the "Default Printers" policy and a filter based on a geographic indicator such as an IP Address or client name. Use Session Printers and or Proximity Printing when you have one of the following scenarios: Thin Clients are used that cannot connect to network printers Laptop users roam throughout sites
Read more