Just Powershell it: Citrix

Import Citrix published applications

Fri, 29 Dec 2006 07:33:23 GMT

After exporting the published application setting in an earlier post, here is the script I used to import the applications in the new farm.

# Powershell script

# Citrix Export published applications

# D. Verweij

###

# First the known steps to connect to the mfcom and initialize the object

$c_farm = new-object -com metaframecom.metaframefarm
$c_farm.initialize(1)

# Then we import the csv file and for each we do..

import-csv c:\citrix\Citrix_apps.csv | foreach{

$c_app=$c_farm.addapplication($_.apptype)
$w_app = $c_app.winappobject
$c_app.Appname = $_.appname
$c_app.description = $_.description
$w_app.defaultencryption = $_.defaultencryption
$w_app.defaultinitprog = $_.defaultinitprog
$w_app.defaultworkdir = $_.defaultworkdir
$w_app.browsername = $_.browsername
$w_app.enableapp = $_.enableapp
$w_app.hidefrompnenum = $_.hidefrompnenum
$w_app.hidefrombrowserenum = $_.hidefrombrowserenum
$w_app.defaultwindowcolor = $_.defaultwindowcolor
$w_app.defaultwindowtype = $_.defaultwindowtype
$w_app.defaultsoundtype = $_.defaultsoundtype
$w_app.desktopintegrate = $_.desktopintegrate
$w_app.mfattributes = $_.mfattributes
$w_app.publishingflags = $_.publishingflags
$w_app.PNAttributes = $_.PNAttributes
$w_app.AllowMultiInstancePerUser = $_.AllowMultiInstancePerUser
$w_app.StartMenuFolder = $_.StartMenuFolder
$w_app.PlaceUnderProgramsFolder = $_.PlaceUnderProgramsFolder
$w_app.WaitOnPrinterCreation = $_.WaitOnPrinterCreation
$w_app.defaultwindowwidth = $_.defaultwindowwidth
$w_app.defaultwindowheight = $_.defaultwindowheight
$w_app.defaultwindowscale = $_.defaultwindowscale
$w_app.parentfolderDN = $_.parentfolderDN
$w_app.pnfolder = $_.pnfolder
$c_app.savedata()
}

Of course there are much more settings to specify and the above are just the one I needed. To see the complete list, just use the "get-member" :

$farm = new-object -com metaframecom.metaframefarm

$farm.initialize(1)

$farm.applications|get-member

note! for some additional settings you need the winappobject properties (some properties in the script above are winappobject properties). The members of winappobject are shown the same way, but you will first have to choose an application:

For instance:

$sampleapp = $farm.applications|where {$_.appname -like "sampleapp"} # appname is the displayname of the published app

$sampleapp.winappobject|get-member

**update**

If you haven't already, you should take a look at the post on http://blogs.msdn.co/powershell where Jeffrey Snover did some tuning on my script. I haven't had the time to test it yet, but I will and you should too. It's great.

The post can be found here:

http://blogs.msdn.com/powershell/archive/2006/12/29/use-copy-property-to-make-it-easier-to-write-read-and-review-scripts.aspx

Have fun!

Grt

Dennis

Export Citrix published applications

Thu, 28 Dec 2006 14:26:05 GMT

During a migration of our Citrix farm to Presentation Server 4.0, I needed to export the published applications from the old Metaframe farm.

I wanted the export to be a csv file with all the properties to recreate the applications in the new farm.

So, for this I made the following script.

# Powershell script

# Citrix Export published applications

# D. Verweij

###

# First the known steps to connect to the mfcom and initialize the object

$c_farm = new-object –com metaframecom.metaframefarm

$c_farm.initialize(1)

# Now we read the properties of the published applications

$c_farm.applications|select-object

@{e={$_.appname};n='appname'},

@{e={$_.groups|foreach {$_.groupname}};n='groupname'},

@{e={$_.users|foreach{$_.username}};n='username'},

@{e={$_.distinguishedname};n='distinguishedname'},

@{e={$_.description};n='description'},

@{e={$_.apptype};n='apptype'},

@{e={$_.browsername};n='browsername'},

@{e={$_.winappobject.enableapp};n='enableapp'},

@{e={$_.winappobject.hidefrompnenum};n='hidefrompnenum'},

@{e={$_.winappobject.hidefrombrowserenum};n='hidefrombrowserenum'},

@{e={$_.winappobject.defaultencryption};n='defaultencryption'},

@{e={$_.winappobject.defaultinitprog};n='defaultinitprog'},

@{e={$_.winappobject.defaultworkdir};n='defaultworkdir'},

@{e={$_.winappobject.defaultwindowwidth};n='defaultwindowwidth'},

@{e={$_.winappobject.defaultwindowheight};n='defaultwindowheight'},

@{e={$_.winappobject.defaultwindowcolor};n='defaultwindowcolor'},

@{e={$_.winappobject.defaultwindowtype};n='defaultwindowtype'},

@{e={$_.winappobject.defaultsoundtype};n='defaultsoundtype'},

@{e={$_.winappobject.defaultwindowscale};n='defaultwindowscale'},

@{e={$_.winappobject.desktopintegrate};n='desktopintegrate'},

@{e={$_.winappobject.mfattributes};n='mfattributes'},

@{e={$_.winappobject.publishingflags};n='publishingflags'},

@{e={$_.winappobject.PNAttributes};n='PNAttributes'},

@{e={$_.winappobject.PNFolder};n='PNFolder'},

@{e={$_.winappobject.parentfolderDN};n='parentfolderDN'},

@{e={$_.winappobject.AllowMultiInstancePerUser};n='AllowMultiInstancePerUser'},

@{e={$_.winappobject.StartMenuFolder};n='StartMenuFolder'},

@{e={$_.winappobject.PlaceUnderProgramsFolder};n='PlaceUnderProgramsFolder'},

@{e={$_.winappobject.WaitOnPrinterCreation};n='WaitOnPrinterCreation'}|

# The last step is to pipe this to the export-csv cmdlet

export-csv c:\citrix\Citrix_apps.csv

Later on I'll go on with importing these apps.

Grt

Dennis

Citrix connection

Wed, 27 Dec 2006 13:44:28 GMT

For the one that doesn't know: Yes, you can do all the crazy stuff in citrix from the wonderfull world of the commandline as you can in the cmc....and more.

A lot of stuff about the com, named MFCOM is written in the pdf "scripting metaframe". (http://support.citrix.com/article/CTX106885) This document is namely for doing stuff with vbscript, but with al little trail and error and a bit of smart thinking you can use this document to begin powershelling the citrix world.

I'll just post some simple scripts to begin with and I hope this wil trigger you to try things yourself and ofcourse.....share it !

Let's do an automated enable and disable of a number of published applications.

First we close them

#--

#first we have to connect to the farm. We do this with new-object and specify that it's a -com object. You don't have to specify the farm name, because it connects to the farm you're in by default.

$citrixfarm = new-object -com metaframecom.metaframefarm

#Then, the farm has to be initialized.
$citrixfarm.initialize(1)

#To close multiple published apps, we need al list of applications. I've put those in a text file. Note that you have to specify the distinguishedname of the application. So, for instance: Applications/Windows/Notepad
gc "c:\scripts\citrixapps\citrixapps.txt" |foreach

{
$disting=$_

   #To see the progress in the commandline I've put in the echo below
   echo "Busy closing --> "+$disting
   $citrixapps = $citrixfarm.applications|where {$_.DistinguishedName -like $disting}
   $citrixapps.enableapp = 0
   $citrixapps.savedata()
}

#--

And....that's all to close them down. Now we'll open them in pretty much the same way. Actually the only difference is putting "enableapp" to "1"

#--

$citrixfarm = new-object -com metaframecom.metaframefarm
$citrixfarm.initialize(1)
gc c:\scripts\citrixapps\citrixapps.txt |foreach

{
   $disting=$_
   "Busy opening --> "+$disting
   $citrixapps = $citrixfarm.applications|where {$_.DistinguishedName -like $disting}
   $citrixapps.enableapp = 1
   $citrixapps.savedata()
}

#--

try and enjoy

Dennis