Track print jobs without using system log I have a bit of an odd question I'm trying to count the number of jobs (in an effort to count separator pages printed) output to our HP network printers, which all have shared print queues setup on 2 print server 2008 R2 nodes I've found lots of powershell scripts to parse event 307 or 805 out of the Windows System event log (after turning print logging on), which would be awesome
2010 2016 Coexistence issue with OWA - social. technet. microsoft. com I recently deployed 2 new Exchange 2016 servers into an existing Exchange 2010 environment I have Exch 2016 setup with a DAG and it is being load balanced with a pair of Kemp loadmaster I have a test user on 2016, the DB is copied to the second server The test user is able to login to OWA without issue However, if I try to login with my user, who is still on 2010 I get the following
Slow networking Performance between VMs on a single host or cluster When we connect to the RDS Hosts and run internet explorer, excel, word, or what ever local app performance is very snappy When we launch AX 2012 and try work in it performance is very poor and that's the issue we are chasing Yes we do know AX 2012 is somewhat of a pig Directly on RDS Hosts performance is good with local apps AX performance is poor across the board