I have a very odd problem.
I have MetaFrame XP FR3 running in my environment. We recently updated all of our print drivers on our seperate Windows 2000 print server. These are point and print objects and propagated to the end users properly. I then upgraded all of the drivers in server properties of the MetaFrame server. However, when I logged in with a users account, I noticed that they got the generic built in UPD. So, I started doing some digging and I found something that surprised me very much.
In the registry of the MetaFrame server, I found the following key: HKEY_USER\<UID>\Printers\Citrix\<AutoCreated Printer Name>\PrinterDriverData. Inside this key, is all of the information about the old driver. If I delete this key manually and reconnect as the user, all is well. This information from what I can tell is completely static. The first time the user logs onto the system and a printer object is auto-created, this data structure is written and it is never updated. It does not check to see if there is a newer driver on the client, etc... The reasont his happened (and why I have not seen it before) is because the vendor changed the file names of the driver because of a major upgrade and they wanted to avoid possible migration issues. However, this will also happen if you were to change a driver completely to a different product. If a printer object was auto-created with Driver A when the user first logged in and a year later you purchase Product B with a completely different driver (different files, names, driver version, etc...) the issue happens as well.
I have not gotten any support from Citrix on this issue and to further complicate issues there are a total of 3 keys that need to be deleted. So, in an environment with 1000 users, each with 10 printers with 3 keys each, that is 30,000 keys that need to be deleted.
Has anyone out there figure out how to get around this or force this information to refresh, possibly via an utility or API?
Thanks in advance,
Jim
I have MetaFrame XP FR3 running in my environment. We recently updated all of our print drivers on our seperate Windows 2000 print server. These are point and print objects and propagated to the end users properly. I then upgraded all of the drivers in server properties of the MetaFrame server. However, when I logged in with a users account, I noticed that they got the generic built in UPD. So, I started doing some digging and I found something that surprised me very much.
In the registry of the MetaFrame server, I found the following key: HKEY_USER\<UID>\Printers\Citrix\<AutoCreated Printer Name>\PrinterDriverData. Inside this key, is all of the information about the old driver. If I delete this key manually and reconnect as the user, all is well. This information from what I can tell is completely static. The first time the user logs onto the system and a printer object is auto-created, this data structure is written and it is never updated. It does not check to see if there is a newer driver on the client, etc... The reasont his happened (and why I have not seen it before) is because the vendor changed the file names of the driver because of a major upgrade and they wanted to avoid possible migration issues. However, this will also happen if you were to change a driver completely to a different product. If a printer object was auto-created with Driver A when the user first logged in and a year later you purchase Product B with a completely different driver (different files, names, driver version, etc...) the issue happens as well.
I have not gotten any support from Citrix on this issue and to further complicate issues there are a total of 3 keys that need to be deleted. So, in an environment with 1000 users, each with 10 printers with 3 keys each, that is 30,000 keys that need to be deleted.
Has anyone out there figure out how to get around this or force this information to refresh, possibly via an utility or API?
Thanks in advance,
Jim