I've got a Windows Server 2008 R2 box and I want to make it a RDS server and connect with thin clients. I don't want to do VDI with hyper-v, as this box is already virtualized. RDS is installed and I've installed an RDS CAL. I've browsed the Technet articles, but navigating technet is worthless. Can anyone point me to a concise get-me-started guide to terminal services/remote desktop services? If I can just get aimed in the right direction I can probably figure it out myself. Thanks.
therulebookman's questions
It appears that there is a virus on my network somewhere that is sending phishing emails through my exchange server. I can see the messages in message tracking and I see many SMTP errors for NDR's and rejected connections from external servers, but I do not see any SMTP authentications and I have logging up to MAX. How can I find the IP or hostname of the PC that is infected? Or is there some other explanation than virus?
Anti-virus scan on server is clean. Server is not an open relay.
Thanks
The calendar is the Boss's calendar on Exchange. I have set permissions for it through his Outlook to give the secretary and a few other people "Editor" access to his calendar. All the editors can view the calendar, but only he can add new appointments. Anyone else who tries to add an appointment gets "The item cannot be saved in this folder. The folder was deleted or moved or you do not have permission."
The permissions are correct, editor. The item hasn't been deleted or moved. It's in his mailbox on exchange. The message says something about the mailbox size, but he is well under the size limit anyway. He is using Outlook 2003, and I have tried accessing it from 2003 and 2007, but I don't think that is related
I tried clearing the forms cache and enabling disabled items: no disabled items and clearing cache didn't help. I also tried "Allow all forms" but this apparently doesn't apply in this scenario as we are not using any custom forms.
Is there any way to delete just his calendar and then I can exmerge it back in (after exporting to PST of course)? I really can't exmerge out his mailbox, delete it, and exmerge it back in because he works all sorts of hours, but if this is the only way, then I'll have to do it.
Is there any other possible solution?
I'm replacing three 7 year old servers with one new one. We are a small k-12 independent school, running AD, exchange, a database, and 3 3rd party apps.
From my research it looks like I can build 2 rackmount servers for about the same cost as 1 rackmount server from Dell or HP with a 4 hour 24x7 support contract.
I only really need one server (I'll use VMware esxi), but if I build I will build two identical machines to make up for lack of a support contract.
I can live with 4 hour downtime, but it will not be comfortable. Am I better off buying or building? I see pro's and con's both ways.
What do I need to be considering most, and what am I potentially missing?
I have several clients that will only connect to Exchange every other time they open outlook. It will wait around for the timeout period and then say "Failed to connect to the Exchange Server" (or something like that) and you have the option of Retry, Abort, and Cancel. If you retry it will work at least one of the next two retries. If you cancel and open outlook again it will connect as normal. Exchange is version 2003, clients are either 2003 or 2007, both have the same problem on affected PC's.
I updated the Broadcom driver on the Exchange box to the latest version, and have tried changing the timeout in outlook, neither worked. All other network connections are functioning normally on the affected machines, including always-on DB connections and a live terminal emulator connected to an AS/400.
Ideas? Fixes? Thanks.
edit: Tried rebuilding the outlook profile on one machine already.
edit2: More investigation shows that it is only certain users experiencing the problem, and those users only experience the problem when they are on a different subnet than the exchange server. Is it more likely an Exchange/AD authentication issue, or an issue with the routers for the separate subnets? Or both?