RISC.Blog

Immer bestens informiert – abonnieren Sie hier alle Blog-Artikel per RSS-Feed

Step-by-Step – Install Citrix XenApp 7.13 Server VDA

Author: Sinisa Sokolic Kommentare: 0 Datum: 06 Apr 2017

Hello and welcome to the next part of the series dealing with the installation of a Citrix XenApp / XenDesktop 7.13 on Windows Server 2016.

This is the manual part were we are doing a next, next, I agree walk-through for all of you that are new to Citrix XenApp or want to see what changed in the installation from older versions.

Be sure to take a look at the prerequisites befor moving on:

Supported operating systems:

  • Windows Server 2016, Standard and Datacenter Editions
  • Windows Server 2012 R2, Standard and Datacenter Editions
  • Windows Server 2012, Standard and Datacenter Editions
  • Windows Server 2008 R2 SP1, Standard, Enterprise, and Datacenter Editions

The installer automatically deploys the following requirements, which are also available on the Citrix installation media in the Support folders:

  • Microsoft .NET Framework 4.5.2 (4.6 and 4.6.1 are also supported)
  • Microsoft .NET Framework 3.5.1 (Windows Server 2008 R2 only)
  • Microsoft Visual C++ 2008 SP1, 2010 SP1, and 2013 Runtimes (32-bit and 64-bit)

The installer automatically installs and enables Remote Desktop Services role services, if they are not already installed and enabled.

You are ready?

Insert the DVD in the drive or mount the ISO file. If the installer does not launch automatically, double-click the AutoSelect application or the mounted drive.

Click START either in the XenApp or XenDesktop line.

2016-10-30-13_06_45-xendesktop-7-11

On the next screen Choose Virtual Delivery Agent for Windows Server OS.

On the next screen choose “Enable connections to a server machine” because we haven´t installed Provisioning Services yet. Click NEXT.

Leave the option for Citrix Receiver enabled and choose NEXT. You could also uncheck the Citrix Receiver option if you don´t want to create shortcuts through Citrix Receiver or do not want to test double-hop scenarios.

On the next screen choose if you want to to be able to integrate App-V packages on your VDA. if will leave the checkmark enabled. This gives us the chance to install the App-V infrastructure later. Click NEXT.

In the next screen choose to configure the location of the Delivery Controller manually. In a later configuration step we will configure it via Group Policy.

If you want to dive deeper into the configuration options I suggest the “VDA Configuration Options – Part 1” Blog Post by Martin Zugec which brakes down the configuration options to those 5 possibilites:

  1. Auto-Update Method
  2. Policy-based Method (LGPO or GPO)
  3. Registry-based Method (Manual, GPP, specified during installation)
  4. AD-based Method (Legacy OU discovery)
  5. MCS-based Method (Personality.ini)

For now we should be fine with “Do it later”. NEXT.

The installer will ask us one more time if we are sure. Yes we are. Confirm the message with YES.

Leave all the next Features enabled because it should be fine for our lab or test environment.

Optimize performance will set some optimizations for the VDA (only in virtual environments) that you can check here. In enterprise environments I would create a GPO for that optimizations to be in full control of the optimizations. I created a GPO template for that you can download here.

The Remote Assistance Feature is necessary for our support staff. We won´t be able to shadow users if we don´t install that feature. You might remember, we also installed Remote Assistance on the Controller were Citrix Director was installed.

Use Real-Time Audio Transport for audio to enable  use of UDP for audio packets.

Framehawk opens the UDP ports used by Framehawk. Have a look at http://docs.citrix.com/en-us/xenapp-and-xendesktop/7-11/hdx/framehawk.html to get ore information about Framehawk. Citrix recommends that you enable Framehawk only for users experiencing high packet loss. It is also recommended that you do not enable Framehawk as a universal policy for all objects in the Site.

Enable Citrix App-V publishing components enables the VDA to launch App-V packages. Further information can be gathered here: http://docs.citrix.com/en-us/xenapp-and-xendesktop/7-11/install-configure/appv.html

Click NEXT.

We will leave the Firewall settings as suggested. Click NEXT.

The next step shows us a summary of our installation settings and the warning that the installed VDA won´t register with a Citrix Delivery Controller. We´ll configure it later.

Let´s scroll down a bit to see the Features and Firewall settings that are part of the installation. Click INSTALL.

The server will reboot several times. The installation will resume automatically after logging back in.

Reboot.

Resume after reboot.

After completion we can configure the Call Home feature. If you participate your configuration and usage data will periodically be sent to Citrix. You will be able to log in to Citrix Insight Services that I will explain in a seperate blog post. If you´re curious browse to https://cis.citrix.com and have a look for yourself.

Click I want to participate in Call Home and click CONNECT the type in your User name and Password. Click OK.

When you´re done click NEXT.

At the end click FINISH and the server will reboot one last time.

If we look at Programs and Features you will see the installed programs.

And that´s it for today. We installed the Server VDA on Windows Server 2016 with the help of the graphical user interface and with default options.

Cheers,

Sinisa

 

Step-by-Step – Install Citrix XenApp / XenDesktop 7.13 Delivery Controller

Author: Sinisa Sokolic Kommentare: 0 Datum: 05 Apr 2017

Hi and welcome to the next blog post of a series covering the installation of infrastructure components for Citrix XenApp 7.13 on Windows Server 2016.

The overview of the published blog posts can be found on this page: https://www.sinisasokolic.com/citrix/.

This is the manual part were we are doing a next, next, I agree walk-through for all of you that are new to Citrix XenApp or want to see what changed in the installation from older versions.

Be sure to take a look at the prerequisites before moving on:

Supported operating systems:

  • Windows Server 2016, Standard and Datacenter Editions
  • Windows Server 2012 R2, Standard and Datacenter Editions
  • Windows Server 2012, Standard and Datacenter Editions
  • Windows Server 2008 R2 SP1, Standard, Enterprise, and Datacenter Editions

Requirements:

  • Microsoft .NET Framework 3.5.1 (Windows Server 2008 R2 only).
  • Microsoft .NET Framework 4.5.2 (4.6 and 4.6.1 are also supported).
  • Windows PowerShell 2.0 (included with Windows Server 2008 R2) or 3.0 (included with later supported Windows Server versions).
  • Visual C++ 2008 SP1 Redistributable package.

Databases

Supported Microsoft SQL Server versions for the Site Configuration, Configuration Logging, and Monitoring databases:

  • SQL Server 2016, Express, Standard, and Enterprise Editions.
  • SQL Server 2014  through SP2, Express, Standard, and Enterprise Editions. By default, SQL Server 2014 SP1 Express is installed when installing the Controller, if an existing supported SQL Server installation is not detected.
  • SQL Server 2012 through SP3, Express, Standard, and Enterprise Editions. 
  • SQL Server 2008 R2 SP2 and SP3, Express, Standard, Enterprise, and Datacenter Editions.

The following database high availability solutions are supported (except for SQL Server Express, which supports only standalone mode):

  • SQL Server AlwaysOn Failover Cluster Instances
  • SQL Server 2012 AlwaysOn Availability Groups
  • SQL Server Database Mirroring

Windows authentication is required for connections between the Controller and the SQL Server database. Have a look here for further information about databases and requirements.

You are ready?

Insert the DVD in the drive or mount the ISO file. If the installer does not launch automatically, double-click the AutoSelect application or the mounted drive.

Click START either in the XenApp or XenDesktop line.

Choose Delivery Controller on the left side of the next screen.

On the next screen accept the license agreement and choose NEXT.

Now you can choose the core components that will be installed along with the Delivery Controller. I will choose to install Citrix Studio and Director. In bigger enterprise environments I would suggest you install both consoles on one administrative VDA where only administrators can log on. On this system additional tools like GPMC for Group Policy editing purposes could be installed.

Because we will use Microsoft SQL Server as a database on a seperate system we won´t choose SQL Express and it wouldn´t fit in an enterprise environment as well. The database for an enterprise class Citrix XenApp environment should be clustered or replicated over more than one system.

Remote assistance is needed for shadowing users with Citrix Director.

We won´t change the firewall settings in the next screen and will leave it as it is. Click NEXT.

Check the summary page and click INSTALL.

The installer takes care of all the prerequisites.

After completion we can configure the Call Home feature. If you participate your configuration and usage data will periodically be sent to Citrix. You will be able to log in to Citrix Insight Services that I will explain in a seperate blog post. If you´re curious browse to https://cis.citrix.com and have a look for yourself.

Click I want to participate in Call Home and click CONNECT the type in your User name and Password. Click OK.

If you´re connected successfully you will see a green checkmark left to the CONNECT button.

Now we´re done with the installation and the next step is to click on FINISH. If you want to launch Studio leave the checkmark active, otherwise leave it blank.


And with that we are done for today´s manual installation of the Citrix Delivery Controller for XenApp 7.13 on Windows Server 2016. I hope you found it usefull.

Cheers,
Sinisa

Citrix XenApp Login Times – There is always (simple) room for improvement

Author: Sinisa Sokolic Kommentare: 0 Datum: 04 Apr 2017

Last week I had the chance to visit a new customer. I was introduced as Citrix geek with a lot of experience and had to troubleshoot slow logon times and a few other problems the customer had in his Citrix XenApp environment ;-). This is what I like the most 🙂

I started with a few questions regarding the setup of the environment and asked which problems the customer had. It turned out that is was a small environment with 10 VDAs running Windows Server 2012 R2 with Citrix XenApp 7.6.0.5026. [ + ] Weiterlesen

Step by Step – Configure Microsoft RDS Licensing on Windows Server 2016

Author: Sinisa Sokolic Kommentare: 0 Datum: 20 Mrz 2017

Hi and welcome everybody to the next blog post of a series about installing and configuring Citrix XenApp 7.13 on Windows Server 2016. After the sucessfull installation of the Microsoft Remote Desktop (RDS) Licensing component we now need to configure it.

So today we will configure Microsoft RDS Licensing. The RD Licensing Manager can be started over a Start Menu link or through a link in the Servermanager. It is not necessary to add RDS Licenses if you are in a lab environment because the License Server will issue temporary licenses for 180 days and in most cases this should be sufficient for a few tests or demos.

The first thing you will notice is that the License Server is not activated. You can see that on the red mark left to the server name.

2016-10-30-17_54_47-server-manager

If you right click on the server name you can open the configuration of the server. You can see that the Discovery Scope of the License Server is configured to Domain.

2016-10-30-17_54_56-homewap0002-configuration

To change the scope the user we use to reconfigure this option needs to have Enterprise Admin privileges in Active Directory. Click CONTINUE.

2016-10-30-17_55_08-rd-licensing-manager

In the next screen you can choose The forest. Click OK.

2016-10-30-17_55_17-rd-licensing-manager

Choosing Forest makes this Licensing Server available to multiple domains within the forest. Click OK again to finish the configuration for the scope.

2016-10-30-17_55_27-rd-licensing-manager

In the next step we will add this License Server to the Terminal Server License group. Without this configuration the License Server won´t issue CALs to users and no reporting will be possible. Click ADD TO GROUP.

2016-10-30-17_55_36-rd-licensing-manager

In the next screen click CONTINUE.

2016-10-30-17_55_41-desktop

Click OK in the next screen to finish the configuration.

2016-10-30-17_55_46-desktop

The next screen shows green checkmarks for all configuration items. Click OK.

2016-10-30-17_55_50-desktop

Now right click on the server name again and start the Activate Server Wizard. Click NEXT.

2016-10-30-17_56_47-activate-server-wizard

There are a few options you can choose to activate the license server. I have internet access and therefor I will leave it on Automatic connection (recommended).

2016-10-30-17_56_55-desktop

In the next screen type in your First name, last name, company and Country. Click NEXT.

2016-10-30-17_57_25-rd-licensing-manager

Add further company information. Click NEXT.

2016-10-30-17_57_53-rd-licensing-manager

With the next screen we are ready to activate the license server. Leave the checkmark next to Start Install Licenses Wizard now activated.

2016-10-30-17_58_05-rd-licensing-manager

The Activate Server Wizard opens. Click NEXT.

2016-10-30-17_58_14-desktop

Again we have a few options to choose for a license program. As Microsoft partner we have access to a few licenses. I will leave License Pack (retail Purchase).

2016-10-30-18_04_14-activate-server-wizard

On the next screen we need to type in a License code. Click ADD and NEXT.

 

We´re done with adding Licenses. Click FINISH.

2016-10-30-18_05_23-rd-licensing-manager

Now you should be able to see the newly added Licenses in the RD Licensing Manager.

2016-10-30-18_12_09-rd-licensing-manager

That´s your Microsoft RDS Licensing server on Windows Server 2016.

Cheers,
Sinisa

Step-by-Step – Install Citrix License Server 11.14.0 for 7.13

Author: Sinisa Sokolic Kommentare: 0 Datum: 19 Mrz 2017

This is the manual part were we are doing a next, next, I agree walk-through for all of you that are new to Citrix XenApp / XenDesktop or want to see what changed in the installation from previous versions.

You can install Citrix Licensing in two seperate ways and you will see that the installation dialogs and the Control Panel entries will look differently after installation depending on which way you choose.

Prerequisites

Check http://docs.citrix.com/en-us/xenapp-and-xendesktop/7/cds-license-landing-/lic-licensing-prerequisites.html for specific prerequisites.

Installation through the Wizard

Let´s start. Insert the XenApp_and_XenDesktop_7_13.iso in your VM and double click on your DVD drive. Now click on the “Start” button in the XenApp field. There is no huge difference wheter you choose XenApp or XenDesktop, the infrastructure components are the same.

2017-03-04 09_31_15-XenDesktop 7.13

Now choose Citrix License Server on the left lower side in the Extend Deployment area. The installer look changed a little bit from the earlier versions and there is some room on the righht side for more options to come.

2017-03-04 09_34_07-XenApp

Accept the License Agreement and choose NEXT.

2017-03-04 09_34_34-XenDesktop 7.13

If you want you can change the installation directory you can do it here. I will install the License Server in the configured folder.

Always read the small letters in installers and readme´s, it could save your life ;-).

The installer states that you shouldn´t install the License Server and Citrix Director on the same system for scale and performance reasons.

Click NEXT.

2017-03-04 09_34_47-XenDesktop 7.13

In the next step you can change the option to configure the firewall automatically or do it manually later. If you don´t need the settings because you are not using the Windows firewall choose manually, I will choose automatically in my lab.

  • 7279 TCP
  • 27000 TCP
  • 8083 TCP
  • 8082 TCP

2017-03-04 09_34_59-XenDesktop 7.13

Click NEXT.

The next screen shows you a summary of your configured settings.

2017-03-04 09_35_06-XenDesktop 7.13

The installation starts after you click INSTALL.

2017-03-04 09_35_49-XenDesktop 7.13

After some time the installer quits successfully.

You now have a running Citrix License Server. Click FINISH.

Yes, that was hard. You have successfully installed the Citrix Licenser Server. Let´s see how this looks like in Programs and Features.

2017-03-04 09_36_50-Programs and Features

You can see that Citrix XenDesktop 7.13 installed.

What I really don´t like at this place is that we cannot see what excactly is installed. The name of the component simply stated Citrix XenDesktop 7.13 and not Citrix Licensing as I would expect. It would be easier if there was something like “Citrix License Server” or something similar.

Installation with CitrixLicensing.exe

Let´s see how you can get there. Therefore you won´t use the guided installation dialog from the first part instead you will start the Citrix Licensing installer directly from the installation media (x64\Licensing\CitrixLicensing.exe)

2017-03-04 09_43_42-Licensing

You can see a totally different behaviour in the installation dialogs and the Control Panel entry. Let´s move on.

2017-02-23 10_52_15-Citrix Licensing

Agree and click NEXT.

2017-02-23 10_52_22-Citrix Licensing

Choose the install location and click NEXT.

2017-02-23 10_52_29-Citrix Licensing

Configure the ports and if you like let the installer set the Windows Firewall exceptions. NEXT.

2017-02-23 10_53_55-Citrix Licensing

If you like you can configure Citrix Licensing to automatically check for Subscription Renewals. Click INSTALL.

2017-02-23 12_19_50-Citrix Licensing

That´s it. Click on FINISH. If you know check the entry in Control Panel you can see “Citrix Licensing with a product version of 13.0.0.19005.

2017-03-04 09_11_09-Programs and Features

Very confusing isn´t it?

The safest way to check for the really installed version of Citrix Licensing is to check the registry entry for it.

2017-03-04 09_50_00-Registry Editor

Other things to take care of

Because the Citrix Service Provider program requires Customer Experience Improvement Program (CEIP) and Call Home, if you are a Citrix Service Provider, you cannot disable CEIP or Call Home.

That´s it for the manual part of the installation.

Step by Step – Install Microsoft RDS Licensing on Windows Server 2016

Author: Sinisa Sokolic Kommentare: 0 Datum: 18 Mrz 2017

This blog post is part of a series covering the installation and configuration of Citrix XenApp 7.13 on Windows Server 2016.

This is the manual part were we are doing a next, next, I agree walk-through for all of you that are new to Citrix XenApp or want to see what changed in the installation from previous versions.

Today we are going to install one prerequisite that we need for our Citrix environment – Microsoft Remote Desktop Services Licensing.

In smaller environment I typically tend to install the Microsoft Licensing component on the same server as the Citrix Licensing Server. The bigger the environment the more likely you will have separate systems for infrastructure component installation.

If you want to have an overview of High Availability for RDS deyploments you should check this Technet article. You also find the following statement regarding the other options of fault tollerance you might think about…

There are two deployment configurations that are not supported:

Clustering RD Connection Broker servers on RD Virtualization Host servers.
An active-active RD Connection Broker installation.

To install it you need to switch to the Servermanager and start the Add Roles and Features Wizard. Click NEXT.

2016-10-30-17_48_55-add-roles-and-features-wizard

Choose Role-based or feature-based installation. Click NEXT.

2016-10-30-17_49_05-server-manager

As we are on the server were we want to install RDS Licensing click NEXT.

2016-10-30-17_49_10-add-roles-and-features-wizard

In the next screen scroll down to Remote Desktop Services and place a checkmark left to it. Click NEXT.

2016-10-30-17_49_33-server-manager

In the next screen leave everything untouched. Click NEXT.

2016-10-30-17_49_58-server-manager

NEXT.

2016-10-30-17_50_03-server-manager

Now place a checkmark left to Remote Desktop Services Licensing. Click Add features in the opening window.

2016-10-30-17_50_19-server-manager

In the next screen click NEXT.

2016-10-30-17_50_25-server-manager

Everything we need is now selected and ready for installation. Click INSTALL.

2016-10-30-17_50_33-server-manager

You can watch the progress if you like or grap a cup of coffee ;-). But be quick it won´t take long.

2016-10-30-17_50_38-server-manager

After the installation finishes click CLOSE.

2016-10-30-17_53_09-server-manager

And for today we are finished with this installation-quicky.

The following Windows Roles and Features were installed:

  • DisplayName : Remote Desktop Services
  • DisplayName : Remote Desktop Licensing
  • DisplayName : Remote Differential Compression
  • DisplayName : Remote Server Administration Tools
  • DisplayName : Role Administration Tools
  • DisplayName : Remote Desktop Services Tools
  • DisplayName : Remote Desktop Licensing Diagnoser Tools
  • DisplayName : Remote Desktop Licensing Tools

I hope this blog post helped you a bit. In a later one we will configure RDS Licensing.

Cheers,
Sinisa

 

Creating windows base boxes with packer and vagrant

Author: Oliver Gehrmann Kommentare: 0 Datum: 16 Feb 2017

Have you ever heard of DevOps?… No?

Well, neither have I until a few weeks ago. Let’s have a look at what almighty Wikipedia says about it:

“DevOps (a clipped compound of development and operations) is a set of practices that emphasizes the collaboration and communication of both software developers and other information-technology (IT) professionals while automating the process of software delivery and infrastructure changes. It aims at establishing a culture and environment where building, testing, and releasing software can happen rapidly, frequently, and more reliably”

Honestly this could mean a lot, and from my opinion it’s still quite vague. You could ask ten other people and end up with ten different definitions. I think DevOps can be explained simply as operations working together with engineers to get things done faster in an automated and consecutive way.

I’ll try to give you a practical example of a DevOps process. We are looking for a solution to provide reproducible and lightweight Windows environments for our developers. In fact, the reason they need fresh systems literally every couple of hours is because slow deployment and installation standards are not an option. So what did we do? We created a “blueprint” of the environment which can be quick and easily reproducible by our developers. This is the story of how I fell in love with DevOps:

What do we need?

  • VirtualBox to run the virtual machines
  • Packer to create an Windows base image from an ISO file
  • Vagrant to launch and configure a base image tailored to a specific scenario
  • Chocolaty to easily install packages
  • Cmder, a super sexy and useful console emulator which also incorporates Git SCM (to access Git repositorys) – Byebye cmd.exe
  • Windows ISO (optional)

How do we start?

First of all, I would highly recommend to install chocolatey on your client (https://chocolatey.org). Cmder will be next, it can be installed through chocolatey with an admin command promt:

cinst cmder –y

The associated binaries can be found in C:\tools. Navigate to the path and start cmder with admin rights. Now you are ready to install the main components: VirtualBox, Vagrant and Packer. Do yourself a favor and use chocolatey again:

cinst virtualbox vagrant packer-y

So far, so good. Let’s create a new folder, e.g. “Vagrant” and cd into the directory. We’re going to clone the git repository from Joe Fitzgerald here ( https://github.com/joefitzgerald/packer-windows.git)

mkdir \Vagrant
cd \Vagrant
git clone https://github.com/joefitzgerald/packer-windows.git

Now you can move the “packer.exe” from %programdata%\chocolatey\lib\packer\tools to \vagrant\packer-windows

Building boxes!

You are now ready to build the box. Cd into the packer-windows directory and type:

packer build -only virtualbox-iso windows_2012_r2.json

Be patient now. The whole process can take from 3-5 hours! Afterward, you will find a windows_2012_r2_virtualbox.box file which can be used with vagrant.

The box will be automatically configured with:

  • SSH Server
  • WinRM
  • vagrant user account with a vagrant password
  • Latest Windows updates
  • VirtualBox guest additions
  • 60GB disk

Using different ISOs

By default, a MS evaluation ISO is used which is 180 days valid. If you want to use a different ISO, you have to modify the windows_2012_r2.JSON file and change iso_url and iso_checksum:

To figure out the md5 checksum I recommend the “File Checksum and Integrity Verifier utility”. It can be downloaded here:
https://support.microsoft.com/de-de/kb/841290

Use the following syntax:

cd into the fciv.exe directory
fciv.exe –md5 >iso url<

The tool will compute the md5 checksum of the ISO which you have to use in your .json file.
If you don’t have a volume license ISO, you also need to set the Product Key. For that open the answer_files/2012_r2/Autounattend.xml file, search for ProductKey and follow the instructions.
If you are going to configure your VM as a KMS client, you can use the product keys at http://technet.microsoft.com/en-us/library/jj612867.aspx. These are the default values used in the Key element.

Vagrant

Add the created box file to Vagrant. This will also take a short amount of time.

vagrant box add –name windows_2012_r2 windows_2012_r2_virtualbox.box

Vagrant launch

To start the server with vagrant you need a provisioning script with the final provision.

Create a new directory in C:\vagrant (I called mine DSC1)
cd into there
type vagrant init

Edit the created vagrant file and modify it for your needs. You can use this as an example:



Save it
Type: vagrant up

Shortly after, you can connect to the box via vagrant rdp (Username: vagrant, Password vagrant).
Halt the box with “vagrant halt” or destroy it with “vagrant destroy”. A new box can be built again within seconds, just use “vagrant up”.

That’s it! Enjoy your new, reproducible and lightweight windows environment.

Big thanks to Joe for providing this awesome Github repository! Great work.

E2EVC Rome 2016 – Part 2 (Microsoft) – Troubleshoot XenApp With Style

Author: Sinisa Sokolic Kommentare: 0 Datum: 14 Feb 2017

Hi and welcome to this second part about troubleshooting Citrix XenApp.

Last november I had the honor to speak at two well known EUC and Citrix events. First of all at E2EVC in Rome, Italy and the day after at DCUG TecCon in Kassel, Germany. The topic of both sessions was “Troubleshoot XenApp with Style”.

I am writing this blog for all of you that couldn´t attend one of these great conferences. The third part will cover general troubleshooting tools that didn´t fit in the session and part 1 and 2 of the blog series.

The first part is about the Citrix tools you can use. [ + ] Weiterlesen

E2EVC Rome 2016 – Part 1 (Citrix) – Troubleshoot XenApp With Style

Author: Sinisa Sokolic Kommentare: 0 Datum: 25 Jan 2017

Hi and welcome to this first part about troubleshooting Citrix XenApp. Last november I had the honor to speak at two well known EUC and Citrix events.

First of all at E2EVC in Rome, Italy and the day after at DCUG TecCon in Kassel, Germany. The topic of both sessions was “Troubleshoot XenApp with Style”.

I am writing this blog for all of you that couldn´t attend one of these great conferences. This first part is about the Citrix tools because otherwise it would grow too big if I would integrate all parts. The second part is about some of the Microsoft tools. The third part is about general troubleshooting tools that didn´t fit in the session.

Why Should You Read It?

This post is not about the usual problems you might have with Certificates, Firewalls or similar things where you might be able to find an answer googling around or checking the knowledge base.

It is more about the methodology and the tools to use when you are not able to find anything in the whole world wide web. [ + ] Weiterlesen

Neues Jahr, Neue Themen – VCNRW (Januar 2017) Event Nr. 8

Author: Martin Schmittbetz Kommentare: 0 Datum: 24 Jan 2017

Unter diesem Motto luden die Organisatoren Timm und Helge zur ersten VCNRW im Jahre 2017. Wieder einmal war das Event VCNRW super organisiert und erfuhr eine hohe Nachfrage durch die Teilnehmer.

Die Referenten des Abends waren Rainer Kodat mit dem Thema „Mit WEM geht’s schneller?! – Optimierung der User Experience“ und James Rankin mit dem Thema „Windows 10 – Answering the Enterprise Deployment Questions“.

Bei frostiger Außentemperatur begrüßten wir in lockerer Runde neue wie bekannte Gesichter. Von der RISC nahmen Christian, Sinisa, Michael, Oliver und Martin teil. Nach einer leckeren Mahlzeit folgte der erste Beitrag von Rainer Kodat:

Mit WEM geht’s schneller?! – Optimierung der User Experience

Der Vortrag über den Citrix Workspace Environment Manager thematisiert die User Experience von Endanwendern in Virtualisierungsprojekten. Ziel ist es dem Endanwender eine gleichbleibend gute User Experience zu bieten. Rainer zeigte uns in einer Live Demo wie das CPU- und RAM-Balancing funktioniert. Des Weiteren besitzt das Produkt einen Log-on Accelerator, welcher z.B. das Mapping von Netzlaufwerk parallel anstatt seriell ausführt.

WEM basiert hierbei auf einem Service und verzichtet gänzlich auf Filter Treiber.

Windows 10 – Answering the Enterprise Deployment Questions

Nach einer kurzen Pause began James Rankin mit seinem Vortrag. Kern waren die Erfahrungen und daraus folgende Kenntnisse von James im Bezug auf das Windows 10 Deployment im Corporate und Enterprise Umfeld. Der Beitrag beantwortete Schlüsselfragen zum Deployment und gab hilfreiche Tips für nachfolgende Tätigkeiten und Prozesse. Besonders detailliert wurden die Vor-und Nachteile der zahlreichen Windows 10 Branches dargestellt und die daraus resultierenden Update Szenarien.

Im Fokus stand weiterhin der Umgang mit Modern Apps in Windows 10.
„Disable all apps which are not relevant – or you get apps for games and all that stuff!“
Entsprechende Ratschläge und Erfahrung von James aus seinen Projekten zu diesem Thema sind besonders hilfreich für eigene Projekte.

Wir haben die Vorträge mit Spannung verfolgt und freuen uns bereits auf das nächste Event am 27.04.2017.

Wir werden auf jeden Fall wieder teilnehmen!