One common reason for XenApp to locate the wrong cmstart.exe is because the third party software might have modified the environment path variables to point to its own cmstart.exe. By using the wrong version of cmstart.exe the launch process breaks.
Because XenApp uses an executable named cmstart.exe for the launch of published applications, it might confuse and locate the cmstart.exe of the third party software instead. One of the possible causes for this issue is that the third party software installation utilizes an executable file named cmstart.exe and modifies the environment variables to point to that executable.
Note: In a XenDesktop 7 App Edition scenario on Windows Server 2012, CtxHide.exe will not be present on the system, and does not need to be included in this registry update.įollowing is an example of the AppSetup Value Data: CtxHide.exe UsrLogon.Cmd,cmstart.exe.įollowing are two causes for this error to occur: There are no commas placed between CtxHide.exe and UsrLogon.Cmd. Add the data value CtxHide.exe before the data value UsrLogon.Cmd.Add the data value cmstart.exe after Cmd separated by a comma.HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon Open the Registry Editor and go to the following registry key:.\Microsoft SQL Server\100\Tools\Binn\ C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\ ”Ĭomplete the following steps to add values to the AppSetup String Value and resolve the issue:Ĭaution! Refer to the Disclaimer at the end of this article before using Registry Editor. \Common Files\Citrix\System32\ C:\Program Files (x86)\ThirdParty\Bin\ C:\Program Files (x86) %SystemRoot%\System32\Citrix\IMA C:\Program Files (x86)\Citrix\system32 C:\Program Files (x86) \Citrix\System32\Citrix\IMA C:\Program Files (x86)\Citrix\System32\Citrix\IMA\Subsystems \WindowsPowerShell\v1.0\ C:\Program Files (x86)\Citrix\system32\ C:\Program Files (x86) “%SystemRoot%\system32 %SystemRoot% %SystemRoot%\System32\Wbem %SYSTEMROOT%\System32 After the change, XenApp locates the correct version of cmstart.exe. Move the variable of the location of the third party software after the XenApp variables. #$usageReport | Format-Table -AutoSize | out-file “C:\reports\ usagereport.txt”įollowing are the possible solutions to troubleshoot the error: $usageReport = | select-object pld -unique | foreach ,License,Count,Usage,PctUsed,Alert|ft -AutoSize|Out-File -Append C:\report_do_not_delete\$(get-date -uformat “%Y-%m-%d”).txt To kill a process ID - example: 3856 ( you can only run this commands, once you are in sys internals command prompt) To log in to system internal tool from command prompt, ran To recreate lhc, ran the following command XenAppConfigConsole.exe /ExecutionMode: Leave To remove server from farm through command prompt - log into the citrix member server and open command prompt, ranĬd C:\Program Files (x86)\Citrix\XenApp\ServerConfig Network Access Protection Client Configuration The commands below are available on the Windows Server 2003 Administration Tools Pack ( adminpak.msi) or on the Windows Server 2003 Installation CD.ĪD Management –Domains, Sites, DNS and ADUC You can run the commands below from a command prompt or straight from the menu Start ->Run.
You can download it if you are logged in.List of Microsoft Management Console (MMC) snap-ins and applets. Update: I wrote a powershell script to automate this process. Perform the following sequence:Ĭopy \mf20.dsn %programfiles(x86)%\citrix\independent management architecture /yĬopy the new mf20.dsn and overwrite the old oneĭsmaint config /user: /pwd: /dsn:"C:\Program Files (x86)\CITRIX\Independent Management Architecture\mf20.dsn"Ĭonnects IMA to the datastore. Just get a MF20.dsn file (%programfiles(x86)%\Citrix\Independent Management Architecture folder) of a random XenApp server and edit it with notepad to insert the new connection data. Now that your SQL work is done you can start migrating your servers.
You can limit these permissions to db_reader and db_writer, however every time you update your farm you will need to change these permissions back to db_owner. Select ‘Overwrite the database’ in your restore options, else you’ll get an error.Īfter your restore is completed create a sql login that is db_owner to your datastore. Restore the backup to the newly created database. On the target SQL server create a new database (remember the name).
Here’s to another document about it ?įirst run a full backup of your database on the source SQL server. Part of the process is to move the datastore to a W2K8R2/SQL2008R2 server. We’re currently decommissioning our W2K3 servers.