By default when Desktop Viewer is enabled, it does not span on multiple screen. When it is maximizes, it only maximizes on one screen. To have it utilizes multiple screen, do:
Enable Desktop Viewer
Login to your StoreFront Server
Navigate to C:\inetpub\wwwroot\Citrix\<your store or receiver web>\
Edit web.config
Find showDesktopViewer="true" and make sure the value is true, not false
Enable Force Full Screen
Login to your StoreFront Server
Navigate to C:\inetpub\wwwroot\Citrix\<your store>\App_Data\
Edit default.ica
Find [Application]
Add DesktopViewer-ForceFullScreenStartup=true under that tag
Propagate your change across your Server Group
Showing posts with label xenapp. Show all posts
Showing posts with label xenapp. Show all posts
Saturday, September 26, 2015
Thursday, December 18, 2014
XenDesktop 7.5 Publish Application to Multiple Delivery Group
Recently I deployed XenApp/XenDesktop 7.5 environment with StoreFront 2.5. By default, using the GUI console, it only allows you to publish an application to a single Delivery Group.
If you have 4 servers and 2 delivery groups, and in each delivery group, 2 servers are registered, with this configuration in mind, you can only publish a particular application to a single delivery group, which equals to 2 servers only.
There was a requirement to be able to publish an application to all the 4 servers within 2 delivery groups. Apparently this is not possible using the GUI console.
However, using PowerShell you can !
You publish the application to the 1st delivery group using the GUI console, then you publish to the 2nd delivery group using the following
If you have 4 servers and 2 delivery groups, and in each delivery group, 2 servers are registered, with this configuration in mind, you can only publish a particular application to a single delivery group, which equals to 2 servers only.
There was a requirement to be able to publish an application to all the 4 servers within 2 delivery groups. Apparently this is not possible using the GUI console.
However, using PowerShell you can !
You publish the application to the 1st delivery group using the GUI console, then you publish to the 2nd delivery group using the following
Add-BrokerApplication
-Name
"My Published App"
-DesktopGroup
"Delivery Group 2"
Note: There is a bug with this, which I believe is fixed with 7.6. The bug is if you were assigning a user to only a single delivery group, that user won't be able to see any of published application assigned to him/her. The user must be assigned to both delivery group.
Monday, December 15, 2014
Citrix XenApp 6.5 Cloning
Here are the steps I've followed successfully to clone a non Data Collector XenApp role without using PvS:
Find out about VMware Customisation
yes or no
Find out Data Collector
qfarm
Local Admin Password
find out the username/password for local admin of the cloned machine
Shutdown XenApp Server
shutdown
Backup
Take a snapshot of all XenApp Servers
SQL database
Start the XenApp Server
start
XenApp Role Manager
Start XA Role Manager
Edit Configuration
Prepare this server for imaging and provisioning
Do NOT remove this server from the farm
Apply
Change IMA to Manual
(if) there is NO VMware customisation Wizard
Run sysprep here (or not if want to use as a VMware template later)
Shutdown XenApp Server
shutdown
Clone
Clone use vShpere Clone
- customize (if sysprep has not been done)
- no customize (if want to convert this as a template)
After finish cloning, convert the cloned VM to a template
Deploy
Deploy VM from Template and Customize
Make sure it does not have network connected
Remove from Domain
Let it reboot once
Join to Domain
Connect the network
Join the deployed VM to the domain
Reboot
Start IMA
Start IMA
Check Server Join to farm
Change IMA to automatic
Change the original master server IMA to automatic
Wednesday, November 12, 2014
Citrix PS or XenApp Data Store Move - Domain Service Account
To move Citrix SQL data store from one server to another and using domain service account rather than SQL built-in account, follow the process below
Trusted_Connection=Yes
DATABASE=SQL-SERVER-DATABASE-NAME
WSID=CITRIX-SERVER-NAME
SERVER=SQL-SERVER-NAME[\INSTANCE]
- Stop IMA services from all Citrix servers
- Backup the database from the source SQL server
- Restore the database to the destination SQL server
- Add the domain service account to the SQL server and assign dbo rights to the database that just been restored
- Edit the MF20.DSN file on each Citrix Server and make sure the following value exist
Trusted_Connection=Yes
DATABASE=SQL-SERVER-DATABASE-NAME
WSID=CITRIX-SERVER-NAME
SERVER=SQL-SERVER-NAME[\INSTANCE]
- Save the MF20.DSN file
- Run the following command
dsmaint config /user:DOMAIN\USERNAME /pwd:PASSWORD /dsn:"FULL-PATH-TO-MF20.DSN FILE"
Note: /dsn: requires double quote ""
Then run this:
dsmaint recreatelhc
Then Start the IMA Service
Note: /dsn: requires double quote ""
Then run this:
dsmaint recreatelhc
Then Start the IMA Service
Tuesday, May 24, 2011
Citrix XenApp Management Console Bug
Citrix XenApp 5 or 4.5FP2 has got a bug - when you launch CMC and run the discovery, it does not find the XenApp farm, only the Web Interface module.
To fix it, run the following:
cd %CommonProgramFiles%\Citrix\*Present*
%windir%\microsoft.net\framework\v2.0.50727\regasm /codebase pse.core.dll
cd %CommonProgramFiles%\Citrix\*Framew*
CmiLaunch.exe
Run the discovery again and it should find it now
To fix it, run the following:
cd %CommonProgramFiles%\Citrix\*Present*
%windir%\microsoft.net\framework\v2.0.50727\regasm /codebase pse.core.dll
cd %CommonProgramFiles%\Citrix\*Framew*
CmiLaunch.exe
Run the discovery again and it should find it now