This message was deleted.
# citrix-vad
s
This message was deleted.
a
Did you check reason for service crash ? (Logs , process dump anayze etc.)
s
yeah, focus on the root cause. Printers are mapped at logon, so if that process fails, there isn't an easy way to kick off the process to map them again, unless you wanted to script something. Either way, your life will be easier in the end to focus on RCA.
d
No, havent looked into those types of logs since its pretty rare occurrence
a
1st step: Check event viewer (Applications / System) for more details. Feel free to share information with us and we’ll help you 😉
d
Sorry, dont want to be difficult but the question here is just in the rare case when this service crashes, for whatever reason, how can you remap the printers without asking them to sign out and sign in?
s
redirected printers or network?
b
We've seen this in some of our large multi-tenant environments. Print services crash; nothing in the event viewer logs indicates an issue. This has become more frequent but very random across our farm over the last 3 months. We have to tell users to log off Citrix and log back in to get the printers to re-map.
d
redirected printers. happens once every two months or so. not a big deal just annoying and figure theres a way to remap
d
@Arthur how does that answer the question I asked? I'm not looking into a reason it crashed, I dont care because it rarely happens. I do however care to reconnect the printers without asking the user to sign out and in.
reason why*
a
Printer mapping is a process that occurs during login. Unfortunately, during the session, remapping of printers may not be possible... Returning to the source of the problem: Most often, it is an issue with the printer driver, and updating it resolves the problem. It's worth checking the event log. It's not complicated, and you can solve the problem once and for all.
d
but that doesnt make much sense. if a user moves between locations, citrix knows how to map the different printers. Why would it not be possible to map after restarting the service?
b
Hi Danny. I am the product manager for HDX printing. The behavior you are seeing is by design. We only map printers during session launch. Restarting the service will essentially have the same effect as the service crashing. Session roaming scenarios are very different because the printer information is saved in the session context. That being said, the print mapping service should ideally never crash. As pointed out in the thread earlier, we can address the underlying issue by capturing the crash dumps and determining the root cause. If you decide to open a support ticket, please feel free to send that information over to me and I can follow up on it.
d
Awesome thank you for that information! Will continue to monitor but everything is fine this week and likely will be until a random occurrence in September lol.
not sure how to tag you but thank you!