Geeks With Blogs

News Clicky Web Analytics

web stats View David Caddick (davidcaddick@gmail.com)'s profile on LinkedIn

Search this Site!

Locations of visitors to this page
View My Stats eXTReMe Tracker
This posting is provided "AS IS" with no warranties, and confers no rights. The opinions expressed within are my own and should not be attributed to any other Individual, Company or the one I work for. I just happen to be a classic techie who is passionate about getting things to work as they should do (and are sometimes advertised and marketed as being able to?) and when I can I drop notes here to help others falling in to the same traps that I have fallen in to. If this has helped then please pass it on - if you feel that I have commented in error or disagree then please feel free to discuss with me either publically or privately? Cheers, Dave
Thin Clients, VDI and Linux integration from the front lines.... Raw and sometimes unedited notes based on my experiences with VMware, Thin Clients, Linux etc.
I was recently asked to help a customer resolve an issue where they felt that once the a couple of the new Citrix Servers were migrated from the old NT Domain to the new AD Domain the IM service appeared to fail - possibly due to restrictions in the GPO's?
 
First of all, not the easiest nut to crack this one, this would appear to have been a number of compounding issues that caused the fault - and coupled with the GPO Security it was easy to believe that this had caused the fault.
 
Check the registry for *stray* Drive Letters
Initially the errors that were remaining from a colleagues failed installations via the IM were clearly indicating an "error 1327 - invalid drive" and referencing R:\.
I carried out a serious search for this through the migrated Servers X, Y and Z and found a number of instances in the Registry, typically the main area of concern is when they are under the HKLM or listed under HKCU "Shell Folders" or "User Shell Folders". I generally take the action of simply deleting the offending info as invalid and let the Server sort itself out. I also discovered 2 instances of R:\Winzip\winzip.exe, now when this isn't even installed under the %SystemDrive% or %Program Files% then you wonder how or why it exists anyway? Needless to say these were deleted as well.
 
Specifically for MSI's this is something of a common failure, in that they do not like running from Mapped Network drives at all, and typically within the standard MSI install template there are a number of checks that the MSIEXEC will carry out before allowing the MSI to proceed - like - checking the registry, etc. and this is when something like the 1327 error will occur.
 
As the Servers are currently being cloned (?) you may want to check the Image/Clone Host for any spurious reference to other drive letters like R:\ ? Perhaps this exists there and is being populated along with the cloning? Co-incidentally I also discovered 2 references to R:\ under the HKCU\.Default...  as I say, might be worth checking the Clone Host?
 
Slow performance from IM?
The next issue I was faced with was the speed with which things were happening on anewly migrated Server V was abysmal. Do not forget that when you are "applying" IM Packages (MSI or ADF's) you are simply manipulating the Data Store and then it is telling the Citrix Server what to do via 2512 and the IMA Service, then once the information arrives it is handed over to the ADF Installer service.
So....   I tried stopping the IMA Service, surprise, it wouldn't stop cleanly - usually a good sign that the LHC needs to be refreshed?
So, I disabled the IMA Service, reboot, use DameWare to remote in, run DSMAINT RECREATELHC, enable the IMA Service, restart the Server
Now things were moving ahead quite well.
 
Failed Citrix Hotfix MSI?
So then I realised that Server V did not appear to be accepting the random Hotfix that I was testing the IM with. Don't forget it's always worth validating that you can actually install the particular MSI via Command Prompt or from the Console - if you are getting errors here then it's clearly not the IM at fault? Anyway, I then started trying to install R05 and it went in clean.
It's always worth checking the credentials and/or enabling verbose logging when faultfinding issues with MSI's?
 
Result
So what I have now tested is that Server W has had Hotfix "R05" installed fine while still in the NT Domain
Server V has had Hotfix "R05" installed while in the AD Domain, this was then uninstalled, GPO Security reapplied, then reinstalled yet again.
It might also just be worth keeping an eye on the Citrix Servers as they are migrated from the NT Domain in to the AD Domain? If the IMA Service can be restarted within 30 - 60 seconds that is fine, if not, then perhaps a pre-emptive RECREATE LHC is in order?
 
Apart from that I have also discovered what appears to be an old PDF from Citrix covering troubleshooting for the IM Service that covers most of this as well
 
I hope this is of some help?
Cheers,
Dave
 
Posted on Thursday, June 15, 2006 5:01 AM Citrix , IT Management , Real Cool Stuff , Microsoft Tips | Back to top


Comments on this post: Troubleshooting the Citrix IM Service

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Dave Caddick | Powered by: GeeksWithBlogs.net