Today a new version has been released of the VMware Horizon Helpdesk fling by Andrew Morgan. One big change is that the Helpdesk license isn’t required anymore so at least a part of the functionality is available to owners of advanced or standard Horizon licenses.
the entire changelog:
Version 1.4.0.1
No longer requires a helpdesk license! Yay!
Added the ability to interact with vCenter machines
Added the ability to open vCenter VM consoles
Added the ability to perform bulk machine actions
Added the ability to perform refresh / recompose tasks directly from helpdesk.
Fixed performance issues with multiple windows open (see single instance).
Fixed a crash when logon durations could not be accessed.
Added polling to allow logon durations to be received if notavailable when the session page is requested.
Fixed a crash in the ending of processes.
Fixed a metric ton of bugs with delegated administration.
Fixed a memory leak in the tray icon menu, of all places.
Removed the logon page graphic as it was to much of a pain to change it’s colour when changing themes
Fixed some layout issues when changing themes.
Removed empty sites from the viewon the change pod tray menu.
Added preliminary support for Horizon 7.9.
Let’s look into some of the new options (will do the options without the helpdesk license last)
Added the ability to interact with vCenter machines
From the pool view you’ll see an extra button for vCenter actions
And that will give these options
These all speak for themselves in functionality.
Added the ability to open vCenter VM consoles
Open VM console will give an popup that asks for vCenter credentials.
Hit logon and a vrmc client should start if it’s installed
Added the ability to perform bulk machine actions
The vCenter actions above can be done against multiple vm’s but also the various actions from View itself
Added the ability to perform refresh / recompose tasks directly from helpdesk.
No longer requires a helpdesk license! Yay!
when you use the std license the biggest difference is that you can’t view any specifics inside sessions since that’s all limited to the helpdesk license.
I already posted a short blog about this fling over here.
vSphere Mobile Client enables administrators to monitor and manage vSphere infrastructure directly from any mobile device. Whether you want to check on the current or historical resource consumption; you want to get notifications on long running tasks; or you want to check the currently running tasks – the vSphere Mobile Client is there to help.
Features
VM overview: Review the status of your VMs including state (powered on/off), resource usage and configuration information
VM management: Change the power state of a VM or restart it. Locating the virtual machine to operate on can be done through search.
Task monitoring: Subscribe to any running task and receive a notification on your mobile device upon task completion, even when your device is in-active or you have another application running on the foreground.
Performance charts: Monitor the resource usage of a VM in real time or a day, week, month or year back. Counters include CPU, Memory, Storage and Network.
NOTE: vSphere Mobile Client is currently available for Android and iOS devices and vCenter 6.0+ deployments. Check the “Requirements” tab for more details. Access to vSphere infrastructure may require a secure access method such as VPN on a mobile device.
This is a technical preview release and as such it only has a limited subset of the intended functionality. The team would be releasing updates with new features regularly, but our main task is to gather feedback so please do not hesitate to reach out to us.
[sta_anchor id=”wsonescim” /]
Workspace ONE UEM SCIM Adapter
Workspace ONE UEM SCIM Adapter provides SCIM user/group management capabilities to Workspace ONE UEM. The middleware translates the System for Cross-Domain Identity Management, SCIM, to a CRUD REST framework that Workspace ONE UEM can interpret. This capability allows Workspace ONE UEM to synchronize cloud-based identity resources (users/groups/entitlements) without the need for an LDAP endpoint (service to service model). Examples include Azure AD, Okta, and Sailpoint.
[sta_anchor id=”flowgate” /]
Flowgate
The Flowgate fling is all about linking IT & Facility systems with each other.
In enterprise data centers, IT infrastructure and facility are generally managed separately, which leads to information gaps. Collaboration between facility and IT infrastructure systems are limited or manual, and virtualization adds more complexity.
The goal of Flowgate is to make facility awareness in IT management system and make IT operations management and automation better on high availability, cost saving and improved sustainability, with more information on power, cooling, environment (e.g. humidity, temperature) and security.
Built-in adapter for multiple DCIM and CMDB system integration:
Nlyte
PowerIQ
Infoblox
Labsdb
IBIS(TODO)
Pulse IoT Center (TODO)
Open for other facility system integration
Built-in adapter for multiple IT stack systems:
vCenter Server
vRealise Operation Manager
Open for other IT stack integration. More systems will coming soon.
UI based Integration process: One click integration.
Role based access control: API level access control support.
RESTFul API support: Provide unified facility information querying services. APIs for all operations and data query make it easy to integrate with other systems.
Updated flings
[sta_anchor id=”usbesxi” /]
USB Network Native Driver for ESXi
Are you building an awesome homelab but received some funky USB Network adapters? The USB Network Native Driver for ESXi might just have the correct drivers for you.
Changelog
June 17, 2019 – v1.1
Added support for 9 additional USB NIC devices including USB 2.0 RTL8152 & TPLINK (see Requirements page for complete list)
Added support for Jumbo Frames (up to 4K) for RTL8153 & AX88179
ESXi670-VMKUSB-NIC-FLING-24524132-offline_bundle-13958648.zip
ESXi650-VMKUSB-NIC-FLING-24599816-offline_bundle-13964320.zip
[sta_anchor id=”hcibench” unsan=”HCIBench” /]
HCIBench
HCIBench is one of two benchmarking utilities that received an update.
Changelog
Version 2.1
Switched UI to dark theme
Redesigned VMDK preparation methodology, which can complete much faster using RANDOM on deduped storage
Added VMDK preparation process update
Added Graphite port check into prevalidation
Added vCenter/Host password obfuscation
Added “Delete Guest VM” button
Fixed Grafana display issue
Fixed FIO blank results issue
Bug fixes
MD5 checksum of HCIBench_2.1.ova: d37e6f164ed962a6e7ccbe104ba9eaec
[sta_anchor id=”ioblazer” unsan=”IOBlazer” /]
IOBLazer
It looks like the IOBlazer fling was first released in 2014(!!!!) as a tool to benchmark all kinds of storage systems. Since I haven’t posted about it here yet let me give you the overview:
IOBlazer is a multi-platform storage stack micro-benchmark. IOBlazer runs on Linux, Windows and OSX and it is capable of generating a highly customizable workload. Parameters like IO size and pattern, burstiness (number of outstanding IOs), burst interarrival time, read vs. write mix, buffered vs. direct IO, etc., can be configured independently. IOBlazer is also capable of playing back VSCSI traces captured using vscsiStats. The performance metrics reported are throughput (in terms of both IOPS and bytes/s) and IO latency.
IOBlazer evolved from a minimalist MS SQL Server emulator which focused solely on the IO component of said workload. The original tool had limited capabilities as it was able to generate a very specific workload based on the MS SQL Server IO model (Asynchronous, Un-buffered, Gather/Scatter). IOBlazer has now a far more generic IO model, but two limitations still remain:
The alignment of memory accesses on 4 KB boundaries (i.e., a memory page)
The alignment of disk accesses on 512 B boundaries (i.e., a disk sector).
Both limitations are required by the gather/scatter and un-buffered IO models.
A very useful new feature is the capability to playback VSCSI traces captured on VMware ESX through the vscsiStats utility. This allows IOBlazer to generate a synthetic workload absolutely identical to the disk activity of a Virtual Machine, ensuring 100% experiment repeatability.
Changelog
Updates in IOBlazer 1.01:
Added configurable IO alignment
Increased the robustness of the trace file parser in the face of spurious lines
Increased the robustness of the build process by automatically detecting target OS and arch within the Makefile
In the Windows version, changed the raw access mode from volume to physical drive to avoid unnecessary mount/unmount operations at every test run.
[sta_anchor id=”daasmigtool” /]
Horizon DaaS Migration Tool
The Horizon DaaS Migration Tool is for the Horizon DaaS providers to migrate their customers to the latest version of Horizon DaaS.
Changelog
Version 2.1.0
Fix for the bug on “Requested Capacity” at the pool/assignment summary page showing inappropriate values.
Intelligently handling import of new VMs skipping previously imported VMs.
Last Friday it was time for my annual trip tot he Belgian vmug meeting. I consider this my home vmug away from home and have been visiting for years. This was the first time I could give back in Belgium since Hans & mine session was accepted in the call for papers.
Our session
Right after the keynote (from which we sadly had to miss a couple of minutes to get setup) we did our presentation in front of about 22-23 people in the attick of the building. Just like at the Dutch vmug we did it about flings & tools for Vmware Horizon. Luckily we could do some of our demo’s locally because the wifi & 4G weren’t delivering a good speed to connect to our labs.One thing is for sure we did the session in the brightest manner ever.
If you are interested in the slidedeck we partially used you can find it here.
Other sessions
Firts of all the keynote by Joe Baguley was great as always. His vision on how things works or should be done has been evolving over the years but always seems to around the same lines. The 2nd keynote bij Johan van Amersfoor about VDI by day,compute by night wasn’t the first time I have seen this session but it’s so good that I don’t mind watching it several times.
The session about Kubernetes by Eric de Witte contained some usefull information since I haven’t done a whole lot with kubernetes yet. The last two sessions for me where Luc Dekens talking PowerCLI (what else?) and Valentin Bondzio about the computational cost of security. Luc’s session was about his style of coding and steps he takes to write codes plus a bit about working with instant clones.
During the day Hans and I had great fun with the people from EG Innovations and 10Zig in the exhibition area. As usual at the BE vmug the day ended with a great BBQ, those belgians do know their food! While not as big as the Dutch vmug UserCon the Belgian vmug meets are always high quality so I will beep going if my schedule allows me too and yes if needed I will take a PTO day for it.
vRealize Build Tools provides tools to development and release teams implementing solutions based on vRealize Automation (vRA) and vRealize Orchestrator (vRO). The solution targets Virtual Infrastructure Administrators and Solution Developers working in parallel on multiple vRealize-based projects who want to use standard DevOps practices.
This Fling is focused on code quality, code reusability, unit testing, dependency management and parallel releases of vRealize projects. In practice, it is a set of Maven extensions, packaged in a Maven repository format, that support the use of IDE (via Maven) and CLI to develop, test and deliver vRA and vRO-based solutions. It includes a vRO plug-in that exposes autocomplete information for standard and third-party scripting objects and actions and CLI that can deploy packages to vRO and vRA via the standard APIs.
[sta_anchor id=”cassdkpyth” /]
Cloud Automation Services SDK for Python
The Cloud Automation Services SDK for Python is a set of Python classes to simplify automation against several aspects of the Cloud Assembly, Service Broker, and Code Stream API when using Python.
Security incidents are important to track so that all parties know the status of a breach and can respond in concert and with appropriate speed. Current methods to track incidents are generally paper-based manual processes. More recent systems are based on a centralized database with some web interface to interact with the record and response tracking.
We propose that this does not work well enough in the scenarios where:
security incidents may affect more than a single entity
where more than one entity must respond to an incident
some or all entities have no trust in the others
no party can or will be responsible for hosting the full system
For example, a security breach in the supply chain for a food manufacturer could result in several retail businesses with products on shelf that contain a pathogen. Current methods of notifying the proper authorities require a phone tree to call all the correct parties which then react as individuals or local committees. In addition the incident must either be initially submitted to each entity separately or one entity must take responsibility to notify the others.
This Fling:
allows all parties (e.g. retail, governmental, public) to see the incident via a single report transaction
allows all parties to respond in concert as required
allows automated systems to report incidents
allows transparency across all organizations
Updated flings
[sta_anchor id=”horizontoolbox” /]
Horizon Toolbox
The Horizon toolbox is an extension to the Horizon Admin Console giving all kinds of user and session information. It is no replacement for the Horizon Helpdesk (or the fling).
Changelog
May 28, 2019, 7.8.0
Fix some incompatible issues
Only support Horizon View 7.7 & 7.8
[sta_anchor id=”horizonmigtool” /]
Horizon Migration Tool
The Horizon Migration Tool helps you migrating from Citrix to an On-Prem Horizon Environment.
Changelog
Version 3.0.2
Updated the binary package and the document accordingly
Personally I don’t see the added value for this fling since there are already plenty of products that provide the functionality and you can even do it yourself with gpo’s. (and the logo is outdated as well)
A thin client is a stateless, fanless desktop terminal that has no hard drive. Thin clients provide businesses a cost-effective way to access virtual desktop infrastructures (VDI). To simplify the operation steps to access VDI, some features are embedded in thin clients.
For example:
Launch the RDP client default
Hide desktop/task bar
Disable system options to prevent user using other applications
And so on
This Fling will convert physical desktop as a thin client. It will restrict end-users’ behaviors when users log into physical desktops. After user logged in, Horizon view client will be launched automatically and other applications are forbidden to switch. Physical desktop will log off automatically once user exit Horizon view clients.
[sta_anchor id=”idmbackup” /]
Identity Manager Migration/Backup Tool
The Identity Manager Migration/Backup Tool helps you in migrating vIDM settings between environments.
Identity Manager Migration/Backup Tool automates the process of exporting or importing applications and entitlements from one Identity Manager instance to another. If entitlements exists, they will also be backed up to an XML file. This Fling uses Identity Manager API’s for Export, Import, Delete and applying entitlements.
Hiding VMs in Hosts and Clusters view – A very popular desktop client feature is brought into the vSphere HTML5 client where you can go to User’s menu, select My preferences and Inventory tab from where you can show/hide VMs in Hosts and Clusters view by selecting the checkbox.
User’s menu -> My preferences will have additional preference options like Language, Time Zone, Console and Inventory
Developer Center now has API Explorer tab listing all the REST APIs exposed by vSphere SDK.
New layout for the feedback tool and feedback tool can be invoked even when a dialog is open on the screen. This enables taking the screenshot of the client including the dialogs. Also, feedback tool now has the ability to add screenshots, this will help you compare the features between different clients and upload the screenshots.
Improvements
We added the support back to 6.0 vCenters to the fling. You can now point vSphere HTML5 client fling v4.1 to 6.0 or 6.5 or 6.7 version of vCenter servers.
License expiration notification now is increased from 60 to 90 days and includes all the licenses
Evaluation License is now shown in the licenses list
Sorting and Filtering by License Expiration date in the Licenses list
Known Issues
New layout of the feedback tool has issues in the Firefox browser, so you will see old feedback tool in that browser.
There are some areas where feedback tool might not capture the screenshot of the dialog, like VM edit settings.
[sta_anchor id=”horizonhelpdesk” /]
Horizon Helpdesk Utility
For a more complete overview of the Horizon Helpdesk Utility fling so the link I posted in the intro to my previous blogpost.
Changelog
Version 1.3.3.1
Removed machine listings from session view (overkill)
Improved Environment view to include metrics on all connected infrastructure:
vSphere
Hosts
Datastores
Remote Pods
Events
Problem Machines
Added repeated queries for logon breakdown if missed on first instance
Added event query support for logon breakdown
Added events view for Farm and Desktop pools
Added inbuilt find / search to users / machines in pool views
Added support for multiselect in pool / farm views
Added graph / chart views of machines / sessions and problem machines on the environment overview
Added a pod switcher to the environment overview
Added a global search to the environment overview
Added support for Pod Jumping.
the ability to jump to a pod on demand
the ability to jump to a pod a session belongs to
Added support for an architecture view of Desktop Pools
Added support for an architecture view of Farms
Enhanced view of servers load evaluator value
Added bulk user tasks via pool or farm views:
Bulk messaging
Bulk log off
Bulk disconnect
Bulk reset
Bulk restart
Added support for a local pod view (AKA environment view):
Connection servers
Farms
Desktop pools
Added documentation (finally)
Added MSI installation support
Added a start time column to user sessions (this will persist as a preference)
This means that for the fourth consecutive year I have been named a vExpert.
What is a vExpert? (or any other community award like NutanixNTC)
Per the vExpert site the criteria for becoming a vExpert are:
If you are interested in becoming a vExpert the criteria is simple. We are looking for IT Professionals who are sharing their VMware knowledge and contributing that back to the community. The term “giving back” is defined as going above and beyond your day job. There are several ways to share your knowledge and engage with the community. Some of those activities are blogging, book authoring, magazine articles, CloudCred task writing, active in facebook groups, forum (VMTN as well as other non VMware) platforms, public speaking, VMUG leadership, videos and so on.
I totally agree on the above description, for me a real vExpert shares knowledge in one of many ways. But blogging, speaking, tweeting, podcasting, writing isn’t the only way. We answer questions online and offline and if we don’t know the answer than we have an awesome backstop to ask questions called the vCommunity. Is it technical only you might ask? Absolutely not! I have seen hundreds of job changes by now because of the vCommunity. People were helped with personal issues, hell even home deco tips and tricks are shared. I think it’s just in our nature to help one another.
Yes it’s also about advocacy but the sharing of information is all voluntary. Do you want to tweet or blog about stuff? No-one will force you but they do appreciate it if you share news.
One things advocacy program members are also good at is providing feedback. Not only to the software vendor but if you want some feedback about a possible blog post, presentation idea, news item or piece of hardware most of us will give you that feedback. Just be prepared because we can be brutally honest if it sucks!
But there are over 1700 vExperts, is it about quantity or Quality?
This is a point where I personally disagree on how the program is run. I have the idea that they want to grow just to grow and for me the selection criteria could be tightened quite a bit. I value growing but please do it by adding quality. If you look at smaller programs like some of the vExpert subprograms or others like the VMware EUC Champions or Nutanix NTC’s they are most times better managed, get more briefings, nda information and events. Not that the vExpert program is managed badly or doesn’t have an awesome party at VMworld but things just get more complicated at this scale.
But does the program still matter to you?
It certainly does! Through the vExpert program I have managed to grow personally and professionally but also made boatloads of friends online and offline. All the extra’s like licenses, swag and things like that are fun but nothing is as good as knowing you have some great people who are always happy to help you in any way possible!
I want in too, how do I become a vExpert?
Currently the sign ups are closed but until they open again (probably somewhere in June) you can start doing some things already:
Start a blog, most people do it as their own knowledge base. Write about what you experienced at work or a customer so you won’t forget it for next time.
Get a twitter account, follow a bunch of people and interact with them.
Help others out in places like VMTN, Reddit.
Present at a vmug or at your employer about things that could be interesting to others. This could be as basic as explaining how your homelab is setup.
If you need help or feedback on your blog or need help on how to build your presentation I am always happy to provide my 2 cents.
When the sign ups are opened again contact your local vExpert pro with how to tackle the application form. You can also ask me or any other vExpert you might know personally.
Removed machine listings from session view (overkill)
Improved Environment view to include metrics on all connected infrastructure:
vSphere
Hosts
Datastores
Remote Pods
Events
Problem Machines
Added repeated queries for logon breakdown if missed on first instance
Added event query support for logon breakdown
Added events view for Farm and Desktop pools
Added inbuilt find / search to users / machines in pool views
Added support for multiselect in pool / farm views
Added graph / chart views of machines / sessions and problem machines on the environment overview
Added a pod switcher to the environment overview
Added a global search to the environment overview
Added support for Pod Jumping.
the ability to jump to a pod on demand
the ability to jump to a pod a session belongs to
Added support for an architecture view of Desktop Pools
Added support for an architecture view of Farms
Enhanced view of servers load evaluator value
Added bulk user tasks via pool or farm views:
Bulk messaging
Bulk log off
Bulk disconnect
Bulk reset
Bulk restart
Added support for a local pod view (AKA environment view):
Connection servers
Farms
Desktop pools
Added documentation (finally)
Added MSI installation support
Added a start time column to user sessions (this will persist as a preference)
Let’s take a look some of the new goodies, the first change is that you now get a proper connection alert:
The POD switcher
The show environment button will show you the environment as seen from the pod you are currently connected to. A lot of tabs with health information about those components and some counts on sessions, machines and problem machines.
The address behind Connected To will send you to the Horizon Admin Console, this might sound small but I like it!
When you open a pool this is what you see
All of the events for that pool and yes you can sort & filter them!
Some details for a users session
If there are multiple sessions (unlike in my lab) you can select them and mass send messages or do other actions against them.
The view for an RDS farm
So yes the best Horizon helpdesk tool ever just got improved by a 100%!
If you have used the VMware.hv.helper the title of this blog post might sound strange since the set-hvmachine already has a way to set maintenance mode. When Ryan Butler asked me the question this week though I didn’t think of that and dived into the api’s immediately. The machines.Machine_EnterMaintenanceMode method looked good to me and than I though of the vmware.hv.helper and noticed that with
Set-HVMachine -Maintenance ENTER_MAINTENANCE_MODE
it was also possible so set maintenance mode. The usage though made me think immediately that this was not actually using a proper api call but the update function. A quick look at the function itself confirmed this. It sets that status of the virtual machine by directly setting the status.
If you are below version 7.5 of Horizon view it’s probably of no use to continue with the rest of this blog post. The api explorer only mentions the relevant functions since 7.5! They have been tried against 7.0.3 and 6.2 and there they don’t work.
So back to the drawing board it was and I needed to look at the API explorer, there are 4 relevant methods for maintenance mode.
As usual there are methods for multiple machines that use an array of id’s (with machines in the name) and methods for single machines id’s (without the machines in the name).
Since I usually use instant clones these days I created a small pool with three linked clones. With get-hvmachine I can show you their names and state.
Okay so we now know how this works but I don’t want to use to vmware.hv.helper module for this at all because I want to be able to use a list of machines or based on part of the name. That can be done using a query. The query entitytype to use is MachineSummaryView and if you use queryfiltercontains it’s also possible to use only a part of the name for a kind of wildcard selection. Combine several of these in with queryfilteror and it gives the opportunity to select them from a list.
The vSphere PKS Plugin provides a user interface for managing and monitoring Kubernetes cluster deployments for the PKS platform. Using the vSphere PKS Plugin you can view details about your Kubernetes clusters, including master and worker nodes as well as networking configuration.
Features
The vSphere PKS Plugin:
Provides a graphical interface to visualize the Kubernetes clusters deployed and managed by PKS
Provides visibility into underlying infrastructure such as VMs, network objects and storage objects that are created when a Kubernetes cluster is deployed in a vSphere environment
Provides a centralized launch point for viewing components deployed with the Kubernetes cluster, including nodes and network objects such as routers, logical switches, load balancers
Provides a simple user interface to get easy access to the cluster using the kubectl interface and the cluster Dashboard
Remember registered site information (without password)
Easily retry a previously attempted task in case of failures
Search box for keyword filtering of migration task history
Option to clear task history by removing completed tasks
Added documentation and other links under the help menu
Partial fix for an issue related to duplicate network names
Workspace ONE Configuration Tool for Provisioning
[sta_anchor id=”wsoneconfig” /]
The Workspace ONE Configuration Tool for Provisioning assists in building unattend.xml configuration files that can be used by Dell (or others when more provide the service) when delivering systems from the factory to set them up for your environment.
Changelog
Release Update – Version 2.0.0
Improvements
The version number is shown in the window title
The version number is shown as a comment in the generated XML
The product key is now validated to conform with the 11111-11111-11111-11111-11111 pattern
Split the locale settings into ‘Operating System Language’, and ‘Region and Keyboard Settings’.
‘Operating System Language’ maps to the language of the operating system installation media, and ‘Region and Keyboard Settings’ maps to the locale settings available to the user during OOBE
‘Operating System Language’ is now a required field as it is needed for certain customizations, such as adding a user to the administrators group
Removed the ability to set a custom computer name. The computer name now defaults to ‘*’, which causes the Windows OS to generate a random name, taking up to seven characters from the ‘Registered Organization’ field plus eight random characters. This change makes sure every computer has a unique name on the network.
The ‘Auto Admin Logon’ feature is no longer selectable. Instead, it will be activated when it is required by the deployment scenario.
All deployment scenarios now allow for the creation of a local user.
Moved the node from the ‘oobeSystem’ pass to the ‘specialize’ pass
to be consistent with the node
Bug Fixes
Auto Admin Logon would only work with an unattend XML generated for an en-US installation image
Enabled the ASSIGNEDTOLOGGEDINUSER=Y flag to enable the WS1 agent to correctly enroll the user in the ‘Workgroup’ deployment scenario
Fixed an issue where the ‘Show Privacy Settings’ option would have no effect
This post is fairly similar to my posts for .Next Nice in 2017 and VMworld US of this year. For security reasons I decided to go with the XD Design Bobby again. Since it’s a lot harder to open when on my back I feel it’s a bit more secure while travelling on the London Underground. A couple of other changes also have been made, the bubm bag was replaced by a bit smaller pouch from the same maker and my Sony headset has gone to my wife since I settled on the Jabra Move I got from Cohesity at VMworld. The Jabra just sits a bit more comfortable for me and fits perfectly in it’s own bubm case.
For the rest there are the usual suspects: Xiaomi 10k battery pack, HP Probook 440 G5, Microsoft designer mouse, Roundcube Rewirable USB Travel adapter and some various bits & pieces. My suitcase is simply packed with lots of stroopwafels and all the Nutanix NTC gear I have.
Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here:
Cookie Policy
