![]() ![]() Select the PSMInitSession.exe application and publish it.ĭuring installation, a log file, \Temp\PSMInstall.log, is created to monitor the installation process and to enable you to ensure that Privileged Session Manager was installed successfully. The default location is the Components folder in the PSM installation folder. Select one of the PSM servers that belong to your collection and navigate to the location of the PSMInitSession.exe application on that server. Select the collection you created for your PSM environment then, in the REMOTEAPP PROGRAMS section, select TASKS and Publish RemoteApp Programs. ![]() In the server where you installed the RD connection broker, open the Server Manager. This procedure is done automatically during Privileged Session Manager. ![]() This will enable the RemoteApp feature be installed successfully. In this scenario, manually publish the PSMInitSession.exe remote application in the RDS collection that you configured for the PSM environment, as described below. In an environment where the custom session collection was configured in the RD connection broker role, the RemoteApp feature installation might fail during PSM installation. If you use the default session collection this step is not required. If you are not using the default session collection, see Set up the RemoteApp feature with a custom session collection If this happens, you can repair the installation and add the RemoteApp feature at a later stage, after setting up the prerequisites. If these prerequisites are not set up, the PSM installation will not be able to install the RemoteApp feature. The RemoteApp feature requires a connection broker and a session collection to be associated with it. Make sure that the current server is the only server associated with your session collection. In the User Profile Disks window, clear Enable user profile disks, then click Next. Add a group or a user that you trust to connect to the PSM server via RDP (for example, the administrator user that you are currently logged on with), then click Next. In the User Groups window, remove all user groups. In the RD Session Host window, select the current PSM server, then click Next. In the Collection Name window, specify the collection name, then click Next. Select Tasks, then Create Session Collection, and then click Next. In the Server Manager, select Remote Desktop Services, then Collections. In the Confirm selection window, select Restart the destination server automatically if required, then click Deploy.Īfter the server has restarted, add a session collection: In the Specify RD Session Host servers window, select the current server, then click Next. In the Specify RD Web Access server window, select the current server, then click Next. In the Specify RD Connection Broker server window, select the current server, then click Next. Select the server where the new roles will be installed: In the Deployment Scenario window, select Session-based desktop deployment, then click Next. In the Deployment type window, select Standard deployment, then click Next. In the Installation Type window, select Remote Desktop Services installation, then click Next. In the Add Roles and Features Wizard window, select Installation Type, then click Next. In the Server Manager, display the Dashboard, then select Add Roles and Features. ![]()
0 Comments
Leave a Reply. |