At the start of the year we rebuilt our server infrastructure from Windows Server 2003 R2 (Enterprise) to Windows Server 2008 R2 (Enterprise). Since then we've had a sporradic/rare unusual issue occur with our Print Server.
Our Print Server is setup fairly simply, it's a standard Windows Server 2008 R2 Print Server, it has print drivers (64-bit) for our Xerox ApeosPort IV 5570 machines, and it runs Equitrac Office 4.2 for printer authentication and follow me printing. The servers that the users are printing from are Windows Server 2008 R2 Terminal Servers (2 in a Farm).
The issue we encountered first was that in rare instances users printing and picking up jobs from their Follow-Me print bins on the printer would find that a job would be missing. Another user would come along and do some printing of their own and find the missing job in their own Follow-Me print bin instead.
We originally thought that this was an Equitrac issue and worked closely with our printer support reps in an attempt to find the issue and fix it, but after many logs and months back and forth between Equitrac, our print support reps and ourselves we found that the issue wasn't with Equitrac but seemingly from the Windows Print Server itself.
What we found was that in rare instances (Unfortunately it's rare and I haven't been able to replicate it on demand yet) when a user prints a job, the event log for the print server actually shows that the owner of the job was the LAST user that printed to that print server, not the current user.
Our printer support reps found us an article which seemed to fit our scenario perfectly, but the article is only for Vista SP1 and Windows Server 2008 (Not R2). When we download and try to apply the hotfix (On the off chance that it might fix the issue) it comes up with an error stating that the hotfix is not applicable to this operating system (As expected).
The article referenced above is: http://support.microsoft.com/kb/958741
What we're both wondering now (Myself and our printer support reps) is that if this issue has potentially resurfaced in Windows Server 2008 R2 (Being that the article fits the scenario and symptoms perfectly) but has yet to be fixed, could someone assist us to solve this issue?