Fields marked with an asterisk (*) are required.
Microsoft in there best moments came up with pining items (shortcuts etc.) to the new Jump List. This is all crap, not just for the reason that Microsoft uses a binary key for the list and the corresponding link needs to be in place, it's also not configurable through group policies!
Nach der Implementierung von Citrix Universal Print Server (UPS) kommt man schnell auf die Fehlermeldung "0x00000709", wenn man Ausdrucken möchte. Der Grund ist, dass die Druckerhersteller das RawOnly Attribut setzen, selbst wenn andere Formate wie EMF möglich sind. Citrix UPS kann nur EMF und ist die Quelle des Fehlers.
Citrix ist im Geschäft mehr als 20 Jahre; der Erfinder und Dominator des Multiuser Markts. Die Frage ist aber immer die gleiche: "Brauche ich Citrix XenApp oder XenDesktop - Ist Microsoft Remote Desktop nicht genug? Muss ich so viel mehr Geld für Citrix ausgeben? Ich war Microsoft MVP für Remote Desktop Service (RDS) für viele Jahre und ich erinnere mich an meinen letzten Besuch bei Microsoft in Redmond. Ich hatte Änderungen und Ergänzungen empfohlen die mit dem aktuellen Windows Server Version 2012R2 wahr geworden sind. Ich muss keinem Citrix "Verkaufen", wenn Microsoft für die Kundenbedürfnisse ausreichend ist. Es ist kommt immer auf die Anforderungen des Kunden an aber vieles hat sich geändert und es ist Zeit zum Überdenken.
Citrix has been in the business for over 20 years; the founder and dominator of the multi-user market. The questions are always the same: "Do I need XenApp or XenDesktop - Isn't Microsoft Remote Desktop enough? Do I have to spend a lot of extra money on Citrix?" I was a Microsoft MVP for Remote Desktop Service (RDS) for four years and I remember the last time I was in Redmond. I said some things Microsoft should change or add that have become true with the latest release of Windows server. I never have to "sell" anyone Citrix when RDS is just enough. It always depends, but I think things have changed such that it’s now time to re-think.
After implementing Citrix Universal Print Server (UPS), you might run quickly into error message "0x00000709", when printing. The reason for that is that Printer vendor set their printer to RawOnly, even the printer can work with different format like EMF. Citrix UPS uses EMF only and the source of the error message.
Quite often customer tells me that they want to optimize the Windows server performance by running some scripts found on the Internet and they are also setting a bunch of registry keys. In my opinion, this is not just dangerous but can also cause issues later and then everybody is analyzing while spending a lot of time. On the other hand, the same customers do nothing to optimize the user session and waste sometimes a lot of resources and again getting more likely issues.
Let me explain why you should NOT care about the server and focus on the user session.
Ever heard of "context switches"? If yes, then you are probably an Administrator for a Citrix Presentation Server farm. Now this is not a Citrix related problem but the context switches are one of the default performance counters in the Citrix Resource Manager and obviously the most often raised alert. Other systems might also have issues with context switches but if there isn't an alerting monitor you will never know.
Many Citrix or terminal server farms have problems with printer drivers and sometimes even the Administrator is not aware of that. Drivers that are not 100% multiuser aware can have a bad influence in many different ways. Often those buggy drivers can slow down the login process or cause high CPU consumption. In worst cases, printer drivers can even stop the login process for the whole server, kill the spooler service or can cause a blue screen of death (very rare with Windows 2003 and up). For the first two issues, the Citrix health monitor can help tracking the problem.
TThe Windows logon and logoff process is a complex part of a Terminal Server environment, and these processes are complicated even more when Citrix MetaFrame Presentation Server is installed. However, knowing how these processes really work can cut down your troubleshooting time.
This article can’t cover all aspects and every detail of the logon and logoff processes. However, it will take a look at these processes from an administrator’s standpoint (as opposed to taking a developer’s perspective).
The first part of this article covers the session initialization. It covers the steps that take place from the time a client tries to connect until the application shows up on the user’s desktop. (Note that we’re only talking about the actual connection from the client to the server. We are not talking about application enumeration or load balancing since those activities take place before a client connects to a server.)
The second part of this article will cover the disconnection and logoff processes.
Page 2 of 2