This is one of the common issue happen to PVS environment, IF the environment is not properly configured. The trust relationship will failed, if the password expiration days is  set below than computer account password updates. For example, if you set the password to be expired in 5 days, and computer account password updates set for 7 days, the password will then expired 2 days before renewal. Therefore, either disable password expiration, or properly set these 2 options according to Corporate Security policy. Issues : PVS : The Trust Relationship Between This Workstation and The Primary Domain Failed Troubleshooting   Accessed to the VDA, could not authenticate using domain ID.  Convert the VDA to Private mode / Create new version under Maintenance mode, unjoined and rejoined to domain. Put the VDA to Standard Mode / promote to Production, issue persisted. Resolution :  Shut down the target device.  Right click at it, go to Active Directory >

This issue occurred to me a few years back, when we started enrolling Windows Server 2008. When I tried to change my Citrix XenApp server to another farm, CHFARM.exe crashed and I could not do it. Because I was using GUi rather than command line during that time, so I could capture below detail. I did not have any issues in changing farm for XenApp in Server 2003, and my home lab (with Windows Server 2008) also gave a positive result. As I only can see this error on Server 2008 (security permission on my home lab was more relaxed - UAC disabled) and but not on Server 2003 (and my home lab), thus to me it was safe to narrow down the root cause to security permission on Server 2008 (to be exact : User Acess Control) that cause the problem. Issues : CHFARM crashed in the middle of changing Citrix XenApp farm (on Windows Server 2008). Troubleshooting   RDP to the server, launch RUN , type secpol.msc , and press OK . (First hint) At this window, click at I want t

A few days ago I created a script to do some little, tiny checking on my servers. My plan was to create a Task Scheduler so that script can be executed periodically. But ( yeah, there is always a but ), I encountered an error. If we look carefully at the error, it did not mentioned about Securty or policy setting, but I know it must related to UAC. Issues : Receive error when configuring Task Scheduler : An Error has occurred for task <Task Name>. The following error was reported: A specific logon session does not exist. It may already have been terminated. Troubleshooting   Go to Start > Administrative Tools > Click at Task Scheduler  Browse to Task Scheduler (local) > Task Scheduler Library  Right click at the specific Task Scheduler > choose Properties  At General tab, the radio box " Run whether user is logged on or not " is enabled . Which means, the setting is okay.  Further checking, go to Start > Ru