A curious problem that is occurring with one user on our network, and we're not really sure why it's happening.
When opening the Citrix Receiver application, you get the screen with the big circle, pointing to the '+' sign to add an application.
If the user hits that '+', and adds an icon, normally the icon is placed on the 'desktop' within the application.
In the case of this one user however, the icon is grayed out as it's placed on that 'desktop' and then disappears before it solidifies. Leaving the user with the same screen as he started with.
Wat we've done to troubleshoot this
The user can log into the web interface, and start programs that way. So the Receiver is able to properly communicate with Citrix.
We updated the Citrix Receiver to the last version (4.8 / 14.8.0)
Removed the local user profile of the user (the user does not use a roaming profile)
Let someone else log on to the users PC, and test this. The problem does not occur.
Let the user log on to another PC that has no issues. The problem follows the user.
Based on the above, we're no longer looking at the profile of the user. There isn't a roaming profile, and even after removing and recreating the local profile the problem persists.
What we did find was that in the C:\Users\username\appdata\Local\Citrix\SelfService folder, there is a propagation of icons that persists even in a clean/new profile for the user. Of what I managed to track this is apparently coming from StoreFront (we have 2.5 active at the moment), but there is very little to no real information on what is happening here. Apparently StoreFront somehow provides the Citrix Receiver with information that trancends the Windows profile, and thus we're suspecting that this might have some cause in the original problem, tho we're guessing here.
While we did find a means to make an export of the subscription database in StoreFront, and I can find the SID of the user in there with a heap of references, it seems the only means to get rind of his data in the database is apparently to export the database, edit the export to remove the user, wipe the whole database from the server, let it recreate a completely new one, and import the edited export back in. Seeing we're not even sure this is the actual cause of the issue, to do this for one user and potentially hit the whole organisation is going a bit too far in my book.
If anyone has any thoughts on the matter, I would appreciate hearing them.
Question
J.R. van Doornik
A curious problem that is occurring with one user on our network, and we're not really sure why it's happening.
When opening the Citrix Receiver application, you get the screen with the big circle, pointing to the '+' sign to add an application.
If the user hits that '+', and adds an icon, normally the icon is placed on the 'desktop' within the application.
In the case of this one user however, the icon is grayed out as it's placed on that 'desktop' and then disappears before it solidifies. Leaving the user with the same screen as he started with.
Wat we've done to troubleshoot this
Based on the above, we're no longer looking at the profile of the user. There isn't a roaming profile, and even after removing and recreating the local profile the problem persists.
What we did find was that in the C:\Users\username\appdata\Local\Citrix\SelfService folder, there is a propagation of icons that persists even in a clean/new profile for the user. Of what I managed to track this is apparently coming from StoreFront (we have 2.5 active at the moment), but there is very little to no real information on what is happening here. Apparently StoreFront somehow provides the Citrix Receiver with information that trancends the Windows profile, and thus we're suspecting that this might have some cause in the original problem, tho we're guessing here.
While we did find a means to make an export of the subscription database in StoreFront, and I can find the SID of the user in there with a heap of references, it seems the only means to get rind of his data in the database is apparently to export the database, edit the export to remove the user, wipe the whole database from the server, let it recreate a completely new one, and import the edited export back in. Seeing we're not even sure this is the actual cause of the issue, to do this for one user and potentially hit the whole organisation is going a bit too far in my book.
If anyone has any thoughts on the matter, I would appreciate hearing them.
Link to comment
15 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now