Tagged: T10
- This topic has 4 replies, 2 voices, and was last updated 8 years ago by jpay00.
-
AuthorPosts
-
April 7, 2016 at 4:09 pm #42682
Hello,
I am looking for some help figuring out why I can launch desktops and published apps from my storefront URL on a PC but when I have the T10 connect to the Citrix environment it fails to launch the apps/desktop. The T10 firmware is 8.1_027. The T10 does get the .ini file, connects ok and can see the published apps. The event log on the terminal shows the following when attempting to start the app.
ICA: pnhost = “afssmpxenappdc1.pccairfoils.com”
ICA: Connecting to “Calculator”
PNA: The desktop is unavailable at this time
ICA: get launch parameter failedI had calculator published to simplify the testing, my other apps do the same behavior. Please excuse some of the commented out pieces, I was turning things on and off to test. Has anyone experienced this or can you see anything obviously wrong with my setup? Any replies would be greatly appreciated.
WNOS.ini below this line————————————————————
#———————————–
# Include Mac File
#———————————–
#V4.3.xxx firmware wnos.ini file for 1200LE and 1125LE.
#
#——————-
# AutoLoad={0, 1, 2}
#——————-
#Selects firmware update mode:
#
# Value Action
# —– ——
# 0 Disable checking for image
# 1 (default) Enable firmware upgrade/downgrade process
# 2 Enable upgrade only
#
AutoLoad=0
#signon=0
#factorydefault=Yes
#—————–
# Vncprompt={1, 0}
#—————–
# A VNC shadow permission prompt. A user can accept or decline VNC shadowing
# on a prompt window before the client desktop is shadowed.
#
# In [user].ini file under /ini/ directory there is an entry
# vncprompt=1
# or
# vncprompt=0
#
# Set to 1 means the user will always be prompted before shadowing starts.
# Default = 1 (by default, the user will always be prompted). The user will
# then choose to decline or accept VNC shadowing.
#
# Set to 0 means the user will not be prompted before shadowing starts, and
# therefore, will not be able to decline or accept shadowing.
Vncprompt=0
Service=vncd disabled=no
#VncPassword=password Encrypt=yes
VncPassword=”NFBBMHBBMDAJNOBP” Encrypt=yes
#—————————————————————
# TimeZone=zone [daylight = {yes, no}] [start=mmwwdd end=mmwwdd]
#—————————————————————
# This statement is valid only if the zone is “Unspecified” on the terminal.
# The allowable zones areGMT - 12:00' to
GMT + 13:00′ at one hour
# increments, and ‘Greenwich Mean Time’.
#
# The option parameter `Daylight’ is to enable/disable the daylight savings
# time. The `mmwwdd’ is a 6 digit number to specify the start and the end
# of daylight saving.
# mm – 01 to 12 for the month of the year from Jan. to Dec.
# ww – 01 to 04 for the week of the month, 05 is the last week.
# dd – 01 to 07 for the day in the week from Monday to Sunday.
#
# TimeZone=”GMT – 05:00″ daylight=yes start=030207 end=110107
Timeserver=10.9.1.1 Timeformat=”12-hour format” Dateformat=mm/dd/yyyy
TimeZone=’GMT – 05:00′ ManualOverride=yes Daylight=yes Start=030207 End=110107 TimeZoneName=”Eastern Standard Time” DayLightName=”Eastern Daylight Time”
#———————
# Resolution={setting}
#———————
# Desktop display resolution. Use supported settings of 640X480, 800X600,
# 1024X768, and 1280X1024. If a resolution setting greater than the Thin
# Client local selection is entered, the Thin Client will operate at the
# lesser of the two.
##Dualhead=yes
Resolution=1024X768
Screen=1 Resolution=1024X768
Screen=2 Resolution=1024X768
#——————–
# AutoPower={yes, no}
#——————–
# Controls how the system starts when the power is first applied to the unit.
# If it is set to yes, the system starts itself up without waiting for users
# to press the power button only if power was lost unexpectedly (if the unit
# was shut down properly before power was removed, when power is restored the
# unit will remain powered off). This setting is useful in a kiosk environment.
# This is a new command with V4.2. The factory default is AutoPower=no.
#
# Once an AutoPower statement is processed, it alters the behavior of the Thin
# Client until a countermanding statement is processed. The affect of an
# AutoPower=yes statement continues even if the statement is removed from the
# ini file in which it was found.
#
# Use of the AutoPower option does not interfere with performing a user
# directed shutdown.
#
AutoPower=yes
#———————-
# EnableLocal={yes, no)
#———————-
# Set to yes to enable locally-configured entries to show up in the Connect
# Manager list (for example, activate local entries). When connections defined
# in local NV-RAM are displayed in the Connection Manager, they are marked
# with an asterisk.
#
EnableLocal=no
#————————————————
# Privilege={None, Low, High}[LockDown={yes, no}]
#————————————————
# Controls operator access to Thin Client resources:
#
Privilege=High Lockdown=no SuppressTaskbar=auto
#————————
DeskColor=”rrr ggg bbb”
#————————
# Specifies the desktop background color in RGB string format (must be
# enclosed in quotes), where rrr, ggg, and bbb are decimal numbers in the
# range of 0 to 255. Default = “16 100 36″ (green).
DeskColor=”64 64 64″
#————————–
# ShutdownCounter=# seconds
#————————–
# Default = 10. Specifies the number of seconds to count down before the
# shutdown sequence starts upon user pressing of the Thin Client power button
# when there are active sessions. Set the value to 0 to commence shutdown
# immediately and prevent display of the countdown popup box.
#
ShutdownCounter=3#—————————————————————–
# ScreenSaver=# minutes [LockTerminal={yes, no}] [SoftSaver={yes, no}]
#—————————————————————–
# Value
# —–
# 0 (Never)
# 10
# 20 (default)
# 30
# 60
# 120
# 180
#
# The optional parameter LockTerminal puts the terminal in LOCK state when the
# screen saver is activated. The user will be prompted with an Unlock Terminal
# dialog box to enter the sign-on password. Note: the user must be signed on
# with a password for this action to take effect.
#
# The optional parameter SoftSaver specifies to use the soft screen saver
# rather than the default of turning off the monitor.
#
ScreenSaver=0 LockTerminal=no SoftSaver=no
#———–
#Rapport server
#———–
RapportDisable=Yes
#———————————–
# Display appearance
# Classic
# vdi – wyse zero interface (dell)
#———————————–
SysMode=classic
#———————————–
# Set link speed to fix 7.1 Bug
#———————————–
#Device=Ethernet Speed=”100M FD”#DisableGuest=yes
#DisablePassword=yesInclude=$mac.ini
END WNOS.INI———————————————————————
BEGIN $MAC.INI——————————————————————-
#V4.3.xxx firmware wnos.ini file for 1200LE and 1125LE.
#——————-
# Connect={ICA, RDP}
#——————-
# Connection protocol. Follow the selections from the following ICA/RDP
# parameter list below. Parameters marked with an asterisk ” * ” are mandatory.
# All connect parameters for each connection must be on the same logical line
# (\ may be used for line continuation – see rules above).
#
#IcaBrowsing=udp
Seamless=yes
Signon=no
DefaultUser=*edited-out*
Password=”*edited-out*”
DomainList=PCCAIRFOILS.COM
PnliteServer=http://afssmpxenappdc1.pccairfoils.com/Citrix/Store/PNAgent/config.xml Storefront=yes DefaultSettings=XenApp
SessionConfig=ICA SessionReliability=yes
#ondesktop=desktops
#ReconnectAtLogon=2 \
connect=ica \
HTTPBrowsing=Yes \
SessionReliability=yes \
#BrowserIP=afssmpxenappdc1.pccairfoils.com \
description=”SMPAQCS” \
icon=default \
application=”SMPAQCS” \
fullscreen=no \
reconnect=5 \
colors=HIGH \
#autoconnect=1 \
resolution=seamlessEND $MAC.INI————————————————————————-
April 7, 2016 at 7:38 pm #42683Correction to the title. I meant T10, not T10LE. oops
April 11, 2016 at 10:13 am #42686I guess the culprit is this line:
PnliteServer=http://afssmpxenappdc1.pccairfoils.com/Citrix/Store/PNAgent/config.xml Storefront=yes
You tell ThinOS to use Storefront but on the other hand you are pointing to a legancy URL.
Try changing it to
PnliteServer=http://afssmpxenappdc1.pccairfoils.com Storefront=yesCG
April 11, 2016 at 10:14 am #42687BTW, with XD 7.6 there is no way any longer to connect directly to a published app. Therefore, you can remove the Connect=ica … section.
CG
April 12, 2016 at 6:59 pm #42695Thank you for the reply CG. I tried the .ini both ways and with removing the connect=ica section. It ended up working after restarting the Citrix Desktop Service on the terminal server using your suggested changes.
Thanks!
-
AuthorPosts
- You must be logged in to reply to this topic.