With this blog post I want to show you how to install Citrix StoreFront 3.0.1 with all it´s necessary prerequisites from the command line.
If you start the Citrix StoreFront installer via GUI the installer takes care of all the prerequisites on your system. You can see this behaviour in the screenshot:
In enterprise environments it is often not wanted to have installers taking care of prerequisites. I am a fan of total control over the environments I am taking care of. Every component needs to be installed in a controlled way.
[ + ] Continue
I was busy upgrading and rebuilding my home lab in the last weeks. Now I want to share with you in detail how it looks like.
This blog post will cover the following topics:
I was recently asked how to create Citrix policies with PowerShell and I must admit that it took me some time to figure it out. If you search for solutions you get only a few hints on how to do it. The best hint came from Ingmar Verheij (https://www.ingmarverheij.com/set-citrix-policies-via-powershell/) but things changed a little but with the latest XenApp and XenDesktop versions.
Why should we use PowerShell to create Citrix Policies?
Lets start with some words why you should use PowerShell and why you should use Citrix Policies without setting them by Group Policy. PowerShell gives us the possibility to create baseline policies for a whole bunch of customers and you can parameterize your installations or you can recreate your homelab automatically.
And… processing local policies should be much faster (I will recheck that argument shortly by comparing the logon duration between locally set Citrix Policies and GPOs).
Now let me explain how to do it:
[ + ] Continue
With this second blog post regarding Splunk and Helge´s uberAgent I want to share my experiences during installation and configuration.
I will start with an overview of the uberAgent installation, will then switch to some configuration settings and give you a quick overview about how it can be licensed and which operating systems are supported. At the end I will describe how you can clean up your Splunk server to start with a fresh data collection.
At first I want to wish you all a happy new year. I had planned a different blog post as the first one but I had no chance of preventing me writing down these thoughts about the installers of Citrix XenDesktop (respectively XenApp) and VMware Horizon View.
Both companies have large-scale installations out there and both are on the market for a very long time. But although they should have experience with enterprise environments and customization possibilities for their software components they still have room for improvement.
[ + ] Continue
Today I want share the steps that are necessary to install the prerequisites for Helge Klein´s uberAgent. We will start with the installation of Splunk. After this first step is done we will go on and install the server components of uberAgent.
[ + ] Continue
Mit dem folgenden Skript können Sie automatisiert Published Applications / Desktops erstellen. Bitte beachten Sie, dass die Variablen vorher zu definieren sind.
script:
write-host “loading pssnapin for xenapp” -foregroundcolor yellow
add-pssnapin citrix* -erroraction silentlycontinue
$XA_WorkerGroupName = “$env:server_role”
$XA_WorkerGroupName = $XA_WorkerGroupName.Replace(“”, “/”)
$split = $XA_WorkerGroupName.Split(“/”)
$0 = $split[0]
$1 = $split[1]
$farm = get-XAFarm
write-host “loading variables” -foregroundcolor yellow
$XA_Description = “$env:XA_CustomDescription Silo $1 on XenApp Farm $farm”
$XA_FolderPath = “applications$env:s4_role$env:XA_AdvancedFolderPath”
$XA_WorkerGroupName = “$1”
$XA_EncryptionLevel = “Bits128”
$XA_EncryptionRequired = $true
$XA_AudioRequired = $true
$XA_AudioType = “none”
$XA_Random = get-random
$XA_ServersPath = “Servers$env:server_role”
$XA_WaitOnPrinterCreation = $false
$XA_PreLaunch = $false
$XA_EncodedIconData = Get-CtxIcon $env:XA_IconFile -Index 0
$getPA = Get-XAApplication | foreach { “$($_.FolderPath)/$($_.DisplayName)”}
$XA_PAPath = $XA_FolderPath.Replace(“”, “/”)
$PA = “$XA_PAPath/$env:XA_DisplayName”
if ($getPA -contains $PA){
write-host “Published application already exists…”
}
else{
write-host “Published application doesn’t exist. Creating published application…”
$execute = New-XAApplication -ApplicationType $env:XA_ApplicationType -PreLaunch $XA_PreLaunch -FolderPath $XA_FolderPath -DisplayName $env:XA_DisplayName -BrowserName “$env:XA_BrowserName$XA_Random” -Description $XA_Description -CommandLineExecutable $env:XA_CommandLineExecutable -WorkingDirectory $env:XA_WorkingDirectory -WorkerGroupName $XA_WorkerGroupName -accounts $env:XA_accounts -ClientFolder $env:XA_ClientFolder -AddToClientStartMenu $XA_AddToClientStartMenu -StartMenuFolder $env:XA_StartMenuFolder -EncryptionLevel $XA_EncryptionLevel -EncryptionRequired $XA_EncryptionRequired -AudioRequired $XA_AudioRequired -AudioType $XA_AudioType -WaitOnPrinterCreation $XA_WaitOnPrinterCreation -InstanceLimit $env:XA_InstanceLimit -EncodedIconData $XA_EncodedIconData -WindowType $env:XA_WindowType -force -erroraction silentlycontinue
if ($execute -ne $NULL){write-host “Application publishing created successfully” -foregroundcolor green}else{write-host “application publishing failed” -foregroundcolor red}
}
write-host “Clearing variables…” -foregroundcolor yellow
$XA_FolderPath = “”
$env:XA_AdvancedFolderPath = “”
Problembeschreibung:
Fehlerhafte Konfiguration von Anwendungen oder Paketen, kann zu Fehlern beim deployment von Powershell Skripten als Anwendung führen. Die ConfigMgr Log Files sind in den meisten Fällen nicht sehr aussagekräftig, sodass die Fehlersuche sehr schwierig ist.
Fehlercode: 0x80072EE7
Fehlercode: Error ID (1)
Was Sie wissen sollten:
Auf der folgenden Seite finden Sie alle ConfigMgr Logfiles:
ConfigMgr Logfilesr
Folgendes Logfile ist wichtig für die Verteilung von Anwendungen und Paketen: %windir%System32ccmlogsCcmexec.log – Hier werden die aktivitäten des Clients und des SMS Agent Host Dienstes geschrieben.
Alle Logfiles finden Sie auf dem Client unter:
%windir%System32ccmlogs
Die verteilten Pakete können in Troubleshooting fällen im folgenden Verzeichnis auf dem Client gefunden werden und einzeln getestet werden:
%windir%System32ccmcache
Lösung:
Erstellen Sie ein “SCCM Package” unter Einhaltung der folgenden Punkte:
* Definieren Sie den Store, in welchem die Source Files abgelegt werden.
* Aktivieren Sie die Option, dass die Pakete in den Cache des Clients heruntergeladen werden.
* Tragen Sie im “command line” Feld das .ps1 Skript ein “Deployment.ps1” ohne angaben vom Verzeichnis.
* Das Feld “Startup Folder” muss leer bleiben.
Sobald das Paket auf den Client verteilt wird, ist dieses im lokalen Cache unter %windir%System32ccmcache zu finden.
Mit dem folgenden Skript, können Sie ganz einfach eine Datei im Ordner und Unterordner suchen und durch eine neue Datei ersetzen.
$source = “sharescript_v14.ps1”
$target = “shareproject_X”
$FileName = “script_v14.ps1”
Get-ChildItem -recurse -path $target -Include $FileName | ForEach-Object {
$scriptPath = $_.FullName
Write-Host “replace file in $scriptPath”
copy-item $source $scriptPath -force
}
Der Citrix XenApp 6.5 Hotfix XA650R01W2K8R2X64058 scheint in Kombination mit Microsoft App-V Paketen Probleme zu bereiten.
Folgender App-V Fehler erscheint beim Aufruf der Applikation: 04-00000A09
Die Beschreibung des Fehlers finden Sie hier
Im sftlog.txt ist erkennbar, dass der Paketaufruf nicht mehr Case-Sensitiv, sondern insgesamt Lower-Case geschieht.
Aktuell hilft nur eine Deinstallation des Hotfixes oder der Umweg über ein Start-Skript.
Laut Citrix wird an einer Korrektur gearbeitet.
Stay in touch with us and find out what is going on right now.
