So, I suspect something is amiss in the PFX installer. However, we were using this setup for at least three years. It doesn't to speak to issues surrounding the combination of both applications running on RDS. If the server became flaky again, we'd know for certain PFX had a large degree of culpability. What I should have done is move the QB users off RDS and then put PFX users on. This isn't best practice troubleshooting. We moved the PFX users off RDS and things are fine again. Just last week, I reintroduced the ProSystemFX users back on the RDS server and within six hours the server was locking up in exactly the same way. Update: Quickbooks users never experienced a hiccup in several weeks. If it remains stable, I imagine it's one of the other items, probably Isolation Mode. If it becomes unstable again, we know it's something to do with PFX and I can work with CCH on that. If it remains stable, I plan to put ProSystemFX users back on it. So far, we've not seen a repeat of the problem. I enabled both those items (the latter via Group Policy) and then turned the users back onto Quickbooks only. Then, I started looking into that problem and found out two things about RDS: Printer Driver Isolation Mode and Remote Desktop Easy Print. But I couldn't start the service once it stopped. So, this RDS server publishes many applications but among them are only two used heavily: Quickbooks Enterprise and ProSystemFX (tax prep software).Īfter finding elsewhere that this problem can go away restarting the print server, I tried that. We had them band-aided all this time and had pause for other projects.) (To be clear, we weren't working on this the WHOLE time. I am unsure what, but we were grasping at straws. Well, I am still poking at this and may have done something to resolve the problem. This server was _extremely handy_ when Hurricane Harvey came through. The next week, the first person will go back to locally hosted apps and another person will use the server. Starting tomorrow I'm going to have one of these users start working on the RDS server. I turned off other redirection options but needed to leave drives, sounds, and printers. I think it's a printer since that's the one redirected device most heavily used. Those last two symptoms all lead me to believe that something like a device is getting redirected and it can't be jettisoned when the user leaves the session. The Usermode Port Redirector can't stop either. In my case, I can stop the spooler but can't restart it. I had seen the other thread about the print spooler. The problems didn't start again until about a week after I added that last person. She could have been _causing_ the problems, but I don't know. However, I couldn't correlate it exactly to the last person added because she wasn't experiencing problems. By the time we started seeing the problem again, I went from zero users to four (out of 12). I'm trying to figure out if it's one user or not. If I tried, I'd get the consent prompt, but then nothing would happen. Attached to this symptom was an inability to run Process Explorer elevated. Other symptoms I've seen are a real session with a hung process I couldn't kill. Did they all appear at once? I don't know. When the problem happened every day, we saw multiple of those phantom (4) broken sessions. If someone can save me some Google time on that, I'd appreciate it. Redirecting drives is generally critical to what they do, but I can run a test by turning it off. Looking at the list of users on the system, there is one blank session that cannot be killed. The Remote Desktop Services Usermode Port Redirector Service cannot be stopped.Ģ. I moved everyone back this morning and did some more digging.ġ. This time the users could launch programs but all explorer instances were frozen. It was fine for about two weeks then we saw the problem again this morning. I started slowly moving people back onto the server to see what would happen. After that, we moved everyone to local instances of their software with an eye toward repairing the problem. This happened every morning for three mornings. The server couldn't be restarted gracefully. The original symptom was the connection process would get hung up on securing remote session. About three weeks ago, somewhat inexplicably, our RDS server became flaky.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |