(2008 R2 defaults to high, stops XP clients connecting for example)īasically in my experience it all comes down to security. Make sure the macs and the server are using the same connection security settings. Make sure you allowed the macs to connect via RDC in the local security of the server by adding them to groups or what ever Make sure your firewall on 2008 R2 is not blocking them. The fix on the blog link above has fixed it for many people however for those of you still having issues I will give you some suggestions on what might be wrong We have the licensing server on a separate server then the RDS server and followed the order of removing de keys as vezard explains. Reactivate the Terminal Services Licensing server by using the Telephone connection method in the Licensing Wizard.Quit Registry Editor, and then restart the server.Right-click each of the following values, click Delete, and then click Yes to confirm the deletion:Ĭertificate X509 Certificate X509 Certificate ID X509 Certificate2.NOTE: If you have to restore this registry subkey in the future, double-click the Exported-parameters.reg file that you saved in this step. Type exported- Certificate in the File name box, and then click Save.On the Registry menu, click Export Registry File.HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM Locate and then click the following registry subkey:.Make sure that the terminal server registry has been successfully backed up.NOTE: Perform the following procedure on each of the terminal servers. Thanks vezard, that solved the problem for us!!!įollowed the link and executed the following steps: We have also used a temperary solution, iTap Mobile RDP which also I have also opened a ticket at Microsoft support, for about 2 weeks now and haven't got it fixed. Nope, we don't have a certificate on our server. do you have a certificate on your server? Support has had us capture network packets on the client and server and forward them, as well as running procmon on both client and server. TryĪ trial of as a short term solution if nothing else. We migrated from a 2003 TS and everything worked fine there. We have tried every different version of RDC and nothing works. We have been using terminalworks as a temporary solution, which also prints. You posted, but I have talked with close to 10 people there so far and still no results. They even tell me things like, "You should contact Apple" I will keep No one there seems to know how to fix this. I have been working with MS Technet support on this for 3 weeks, have the same problems. If possible are you using version 2.1.1 of the Mac RD Client? Are you able to connect from the Mac using CoRD?ĥ. csv file, and then open the file in Notepad. In RD Licensing Manager, have any temporary RDS Per Device CALs been issued? Please create a Per User Usage report, right-click on the report and choose to Save as a. Source TerminalServices* at server startup relating to licensing issues.ģ. Additionally look for errors/warnings from When a Mac user attempts to connect there should be a corresponding error message logged on your server. Please check the server's logs for errors/warnings relating to licensing and post them here. After setting mode via RD Session Host Config, close and then reopen RD Session HostĬonfig and check that it still says Per User.Ģ. The GP setting to Not configured, run gpupdate /force on your server, then attempt to set the mode via RD Session Host Config. In RD Session Host Configuration (tsconfig.msc) is the licensing mode set to Per User? If yes, how are you setting the mode, via Group Policy or manually in RD Session Host Configuration? If you are setting it via GP, please temporarily change Per User RDS CALs are not stored on the client regardless if the client is windows, mac, linux, iOS, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |