i ran into a serious issue after upgrading the UPS component of my printserver from 7.6 to 7.15
I have Xendesktop VDA on Server 2016, Windows 10 and Windows 7, connecting to printserver with UPD enabled works as expected.
GPOs are in place and some universal drivers are installed on the VDAs. When i connect to a printer with a known driver it maps the vendor driver, otherwise the UPD is used (fallback)
If i now upgrade only the UPS component on the printserver i am no longer able to connect printers in my sessions.
the error message is:
Connect to printer:
a policy is in effect on your computer which prevents you from connecting to this print queue.
The printserveris currently (still) a Windows Server 2008 R2 with UPS 7.6 (the goal is to go to 2016 with UPS 1912, small steps)
The VDA has XenDesktop 1912 CU1 installed
what i tried to rule out:
failed: setup a new printserver with Server 2016 and UPD 1912 CU1
scenario A: clone and inplace UPS upgrade
- cloned the printserver, gave new name (printserver2), rejoined domain and connected printers successfully
- upgraded UPS software from 7.6 to 7.15 on cloned printserver2 - connecting printers failed
Question
Wolfgang Wilhelm
good morning,
i ran into a serious issue after upgrading the UPS component of my printserver from 7.6 to 7.15
I have Xendesktop VDA on Server 2016, Windows 10 and Windows 7, connecting to printserver with UPD enabled works as expected.
GPOs are in place and some universal drivers are installed on the VDAs. When i connect to a printer with a known driver it maps the vendor driver, otherwise the UPD is used (fallback)
If i now upgrade only the UPS component on the printserver i am no longer able to connect printers in my sessions.
the error message is:
Connect to printer:
a policy is in effect on your computer which prevents you from connecting to this print queue.
The printserveris currently (still) a Windows Server 2008 R2 with UPS 7.6 (the goal is to go to 2016 with UPS 1912, small steps)
The VDA has XenDesktop 1912 CU1 installed
what i tried to rule out:
failed: setup a new printserver with Server 2016 and UPD 1912 CU1
scenario A: clone and inplace UPS upgrade
- cloned the printserver, gave new name (printserver2), rejoined domain and connected printers successfully
- upgraded UPS software from 7.6 to 7.15 on cloned printserver2 - connecting printers failed
Scenario B: new server 2016 with UPS version 7.6
connecting printer still fails
Does someone have an idea?
Link to comment
1 answer 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