Showing posts with label Installation Manager. Show all posts
Showing posts with label Installation Manager. Show all posts

Sunday, 4 December 2011

Hotfix Rollup Pack 1 for XenApp 6 released (finally)

After fixing both killer and smaller bugs on XenApp 6 one at a time for what seems like a year and a half (no, wait, actually its over that…) Citrix has released the first rollup pack of hotfixes for the product. 

This is not a feature pack, so there is nothing “new” as such.  Although if you are running a live XenApp 6 farm with no hotfixes installed the “new” thing will be that it will work.  XenApp 6 had a few new features and importantly was tied to Windows Server 2008 R2 (which was much better for Terminal Services than Server 2008 and a hell of a lot more modern than Server 2003) but frankly was not that stable at release.  There are about 22 public hotfixes out at the moment if you don’t install the Rollup Pack but the hotfix apparently includes all of them.  In fact there are 105 hotfixes listed as being included, many of which were only previously released to those who paid for support and had a specific problem, though since they often replaced each other that overestimates the size of it.  Actually, its only about 28mb but if it has the effect on a XenApp 6 farm that the public hotfixes had it will be essential.

Rollout is per server – every farm server from the Data Collectors down (but not Web Interface, License, etc) needs the install.  Advice from Citrix is to start with the Data Collectors and rollout very quickly from there, and if you have a test server (or better a test farm) you should test there before installing it anywhere else. 

Installation of Hotfixes should be uniform across your farm – the last thing you want is users landing on servers with different patch levels.  Installation Manager is basic but will do just fine as it understands MSP files, which is what you have.

We’re testing now – benchmarking shows no real CPU or Memory difference (positive or negative) between a server with all the public hotfixes vs with the rollup pack – at least on a simple tests of about 50 Office 2010 users.  But experience on XenApp recently would show it is best to take the risk and install patches early – personally I’ll have all servers patches to Rollup Pack 1 in a week.  Just in case.  If you are not convinced, check out the list of fixed issues…

http://support.citrix.com/article/CTX130473

Wednesday, 29 September 2010

Installation Manager for XenApp 6 – installing Acrobat Reader

Now we have Installation Manager installed, we should probably use it.  An MSI and MST file combination is a good standard install, so this is rolling out Acrobat reader to your Citrix servers.

Customising Acrobat Reader

  • Download Acrobat Reader – I got the latest version (9.3.4) from the Adobe website, after a little searching:
    http://ardownload.adobe.com/pub/adobe/reader/win/9.x/9.3.4/enu/AdbeRdr934_en_US.exe
  • Also download the Adobe Customization Wizard 9:
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=3993
  • Install the Adobe Customization Wizard on your PC – accept all the defaults.
  • Extract the EXE using this command: AdbeRdr910_en_US_Std.exe -nos_ne
  • Wait for the window that pops up to do its work…
  • You should then find the extracted files in this folder on Vista and Windows 7:
    %LOCALAPPDATA%\Adobe\Reader 9.3\Setup Files
  • Run the Adobe Customization Wizard
  • Open the AcroRead.msi you just extracted into Setup Files
  • Select Installation Options on the left – set to run Silently and Suppress Reboot

image

  • Select Shortcuts.  Remove the desktop shortcut.
  • Select EULA and Document Status.  Click the checkbox to suppress the EULA dialog
  • Select Online and Acrobat.com Features.  Disable all Acrobat.com features and all updates.
  • Exit from the application and it should ask you if you want to save changes to AcroRead.msi.  Say yes, and it will create the file AcroRead.mst in the same folder as the MSI file.  Move the contents of this folder to your shared fileserver ready for Installation Manager to use them.

Distributing Acrobat Reader using Installation Manager

  • Open Installation Manager
  • Click “Schedule MSI/MSP package…” on the right hand pane
  • Enter a name in the Task name box
  • In the Target List box, you can just enter the names of the servers to install to, separated by commas (no spaces).  Alternatively, click “Servers…”.  This will bring up a worryingly empty list.

image

  • Select Citrix Server Selector (assuming they are in a farm – otherwise use the Windows Server Selector) and click Add
  • Enter the name of a Citrix server (maybe the Data Collector?) in the “Server Address” box and click GO!
  • You should get a nice list of your servers and server folders.  Select servers (use CTRL to select multiple) and click “Add >” to select them.
  • Put the installation files you prepared earlier in a shared folder on a fileserver.
  • Select the MST and MSI files using the Browse buttons (or by just typing of course).
  • Enter a time for the install – or leave it as Now.
  • Select the checkboxes to log off users or reboot the server as needed.  With this install I am just denying logons.

image

  • Click the Advanced button and change the cache location for this task to the one on the shared file location which holds and MST and MSI.  I don’t know if this is necessary but without this change it seems to have trouble finding the task.  You can also change the retry settings here. By default it will retry every 10 minutes for 1 hour.
  • Click OK to schedule your install!
  • Right click the task every few seconds and select Refresh.  It should succeed – you also get the PowerShell code that is fired at the servers.

Distributing an MSP update

  • Once this is succeeded you should have Acrobat Reader 9.3.0 installed.  To update this to 9.3.4 (currently the latest), create a new task, as before.  This time, when you browse for the MSI file, change the drop down at the bottom to MSP files and you should see a list of MSP files:

image

  • Select (now for the annoying bit) the oldest.  In the case of this upgrade you need to update it to 9.3.2, then 9.3.3, then 9.3.4.  If you go straight for 9.3.4 it will fail with the status “Installation Failed: 1642”.  So select 9.3.2 and carry on.
  • You won’t need a transform for this so just select the right servers and change the Shared Folder under Advanced settings to be the one with the MSP in and run it.  It should work and you can check the installed version of Acrobat is upgraded. 
  • Repeat the process creating installation tasks for the 9.3.3 and 9.3.4 updates.  At least it will easy when the inevitable 9.3.5 comes along!

Installation Manager for XenApp 6 as a Published Application

From XenApp 5, Installation Manager is a nice name for what is in fact a package of MMC add-ins, powershell scripts and the Windows Task Manager.  The old Installation Manager from Presentation Server has basically been removed (let’s be honest, it wasn’t that great) and replaced with lots of standard Windows functionality.

Though everything is streamed, right, so you don’t need it anymore. Right?  Well, just in case…

This is how to install IM on XenApp 6 and allow the management interface as a Published Application:

  • Download Installation Manager for Windows Server 2008 R2 from My Citrix and extract
  • On all the servers to receive deployments, install IMUtilities-x64.msi
  • Set up a network share that IM can use as a cache
  • On the server that will host the admin tools, install IMAdmin-x64.msi.  There is a 32-bit version as well, but if this is on a 2008 R2 server, you need the 64-bit one.
  • Search in vain through the Start Menu for a link to it.  There isn’t one.
  • Start, Run, MMC
  • Click File > Add/Remove Snap-In
  • Find Installation Manager and click “Add”
  • You will get prompted for your network location you created earlier

image

  • Click OK and OK to finish adding the snap-in – you should return to the MMC, now with the Installation Manager appearing on the left hand side, with the file server location you specified at the end of it.
  • Click File > Options to finish the configuration. 
  • Click Change Icon if you want to give it a more jazzy icon than the standard MMC one.  Click Browse and find an ico file – or load C:\Windows\System32\shell32.dll which has loads in it.  I went for a nice floppy disk icon from here!

 image

  • Change the console mode from Author – “User mode – Full Access” should do.

image

  • Save it to the local drive of the Citrix server and log off.
  • Open the XenApp Delivery Services Console
  • Right click Application, select Publish Application
  • Enter Installation Manager as the Display Name.
  • Click Next and Next to confirm as an Installed Application, accessed from a server.
  • You actually run mmc.exe with the name of the MSC file you just created as an argument.  So, if you saved it as c:\installationmanager.msc, your command would be
    %SystemRoot%\system32\mmc.exe c:\installationmanager.msc

image

  • Click next, add the icon to your admin users and click next again.
  • Click Change Icon again to find a nice icon again if you want to for your published application.  Or pick a default one.  It depends how much you like icons. Personally I am not a big fan of half the management apps on the farm having the standard MMC icon, but maybe I think about it too much. 
  • Click next and finish to save the icon.
  • I would then edit its properties again and click the Limits tab.  Set it to only allow one instance per user – a second launch will not work as you already have that MSC file open.

image

  • Refresh the application list on your client PC and you should see your new Installation Manager icon.

installationmanager