One of the best features of the director is the "Filters" page. With this function, we can analyze, drill down and focus on the monitoring and troubleshooting things that are important. It helps you analyze with ease and helps customers solve problems quickly. The filters are explicitly divided into equipment, meetings and connections. Let us deep insight into each one of them and check how it help an administrator to troubleshoot and analyze problems.
machines Filtering
In a XenApp / XenDesktop environment, equipment can fail due to numerous reasons. An administrator must know when, where and why an error occurred. The machine-side in the "Filter" view will help the administrator to find the problem and also the environment in detail understand
The machine panel gives you a picture of .:
- All machines
- error machines - of the main reasons
- saved equipment filter
All machines: Displays the details of all desktop and server machines @ site level. Server and desktop operating systems are shown in various tabs. More filtering can be carried out based on the properties of XD. For e.g.:
Note: Sorting based on the mentioned circumstances allowed. This applies wherever the sorting is allowed. will happen by default listed in the sequencing of the first parameter
Error Machines .: Gives picture of machines in various failure states. You can either all or select one of the other types of errors, as shown below
Saved Machine Filters .: Well, if you want a customized use create filter by criteria provided by available in the filter using any combination, you can do this, that. are an example of a customized filter created and saved.
- Adding a filter
Once saved, you can go to the same, of the main filter tab. This is still available if you log out and log back in return.
Well, we go back and turn up to Filter Machine All machines.
you OS machines will find the desktop detail screen, which gives you a lot of information on the state of the desktop OS machines. You can also select columns from the grid to add or remove, as shown below
The available columns customization .:
times what the parameters are shown in columns all over
- machine name: registered .. the name of the machine on the XenDesktop
- DNS name :. the DNS that resolves the machine
- Catalogue: the catalog of the machine to the one of
- Is Physically. If the machine is a physical and not a VM [1945009?]
- Persist user changes: As the user profiles or user changes are retained. Either v on staff discs or other
- Provisioning type :. As the machine was provided? Was it the MCS or PVS or with
- Allocation type: assigned the machines How? is Are they static or pooled or random pooled
- assigned: Is assigned to the unit
- IP address :. IP address of the computer
- VDA version: Version of the Virtual Desktop Agent
- Remote PC Access: If the machine is a remote PC or not
- Delivery Group: Name of delivery group that the machine belongs
- error type .: the mode of failure. More details in the section below
- Failure. Reason: The reason for the failure. More details below
- downtime. The time when the error occurred
- Prepare: If the machine is prepared? (Is Explicitly for PvD Desktops enables the device to be updated.?)
- Power State: The status of the machine, such as on, off, etc.
- Sessions: number of sessions active on that. machine
- OS :. the operating system running on the computer
- maintenance mode. If the device is in maintenance mode
- Delivery Controller: the Name Delivery Controller that the machine is also associated
- Hypervisor Connection Name: .. the name of the hypervisor, the machines were produced
- hosting server name: DNS name of the hypervisor that is hosted the machine when administered.
- Hosted Machine name: the name displayed for a hosted machine uses as its hypervisor. This is not necessarily the machine DNS name
- no image update :. When the machine is in operation because of a picture pending update or when to update the queue
- Load Evaluator Index: Various Download Index Evaluator associated with this machine
error types, which may occur
the types of errors that can be filtered are: ..
- client Connection Failures - session failed because of problems or compatibility with the customer through the session to start user used to connect
- configuration error -. due to configuration errors caused failures
- machine failures. - Link failures when to start the engine or to react, failed
- not available capacity -. Capacity of VM or resource usage has exceeded the maximum allowable limit unpaid the connection failed
- not available licenses - terminal. Unavailability licenses due to virtual machines to spawn
The reason failure may be classified as:
- Session Preparation - Session prepare request by Broker service VDA failed [1945009[
- Registration timeout - VDA not registered in the time after is turned on for the session start
- ConnectionTimeout -. Client did not connect VDA was prepared according to VDA for the session start
- - License Request failed (usually no license available)
- Ticketing -. Licensing failed generally
- Other - General unresolved error between the client and VDI
- General error - General unresolved errors during the initial brokering operation
- maintenance mode - machine or delivery group in maintenance mode [1945009applicationcannolongerbeusedandhasbeendisabledbytheadmin
- Royalty function Refused - -]
- application disables property is used is not licensed (eg license not using multi-session VDAs) allow reached
- session limit - no more sessions allowed (eg second meeting on VDI VDA starts)
- Prohibited protocol - resource not allowed protocol of session start request
- resources are not available - resource has been removed / disabled, since bullets
- Active session Reconnect disabled - session is already with another endpoint but meeting stealing is disabled [1945008keineSession] to reconnect - specified session not during reconnection [gefundenwerdenkonnte
- spin up failed - VDA could not be turned on for the session start
- refused - VDA actively refused prepare session request [1945009[
- configuration Set Failure - failed necessary configuration data according to VDA before session Start
- to send No machine available -. No machine to start (for example, all shared VDI machines in the group are in use)
- machine not functional - not power managed assigned unregistered machine
You can also cutting and dice
machines were not offers 4 failure options choose
- could not be started: .. All machines start failed
- Stuck on boot :. Machines that have started up, but at boot stuck
- Unregistered. Machines that are not registered to the broker
- Maximum load: when machines are certified for maximum load (for XenApp Server OS machines only)
Sessions
If the administrator more details to find out about the needs hosted on XenApp / XenDesktop sessions, they can use the filter - side sessions. There is a wealth of information about the sessions and its users, which is helpful in figuring out or fix problems
can create for meetings Similar to the machine side saved custom filters, and you can also columns for the grid depending decide what is important to you.
seetime, which means the individual parameters.
- Related users: the user associated with the session
- Associated user UPN: UserPrincipalName - has two parts: the UPN prefix (the account name) and the UPN suffix ( a DNS domain name). The parts are joined together to make the 'at' symbol by the at sign (@) the full UPN
- associated user display name :. Username in the form of DOMAIN username
- Session State: The state of the session. Is it connected or disconnected
- Session Start Time: .. The time starts at the meeting Change
- Session time: time for a session change taken
- Anonymous: Specifies whether a session is anonymous or not
- endpoint name: name of the endpoint device for the session
- endpoint IP :. the terminal IP address
- Receiver version: the version of Citrix Receiver installed on the endpoint
- Connection type :. Whether it is a HDX or a console session
- Machine Name :. the name of the machine
- DNS Name: DNS name
- Catalogue. the name of the catalog that owns the machine
- IP address :. IP address of the computer the session hosting
- VDA version: Version of Virtual Delivery Agent Citrix (VDA) installed on the computer
- Delivery Group: the name delivery group
- Session support: If a session support available
- OS: the name of the operating system.
connections
On the Connections tab, you can give an idea of the condition of connections to XenApp / XenDesktop environment. Picture complains a customer that his meeting is too slow and lacks responsiveness. You can connect to this meeting and to learn detailed information about its connections. Say, he was used instead of a console HDX. The "Connection Type" would clear that detail to give you, and you would, the customer can know the reason why it occurs a delay in the performance.
Any connection: Lists all connection in the XenDesktop
Error connections: a picture of all the failed connections in the XenDesktop give. It can further down are in broken -
- client connection error: .. errors occur because the connection of the client is down to the network
- configuration errors: errors due to configuration problems
- machine failures:
- not available. Capacity: Failure because new machines could not be assigned because of the capacity of 100%
- not available licenses: failure due to insufficient licenses
You can also select the time period during a filter rule to create.
The filter -All connections grid gives a holistic view of the XenDesktop connections and all is important parameters.
a few parameters to filter unique - All connections are pages .:
- Swapping between time (ms): the taken for DDC time to convey the session, or connection
- connection: the host name of the device through which the connection is established
- connection (IP): .. the IP address of the device through which the connection is established
- Secure ICA: ICA is securely encrypted. with the Secure ICA function
- Session Support. Whether it is a single session support or a multi-session support
these things together make all troubleshooting a XenApp / XenDesktop environment simple and effective. Customer response times as Administrator greatly reduced effectively filter before him the wealth of information and back on the one that can solve the problem.
0 Komentar