![]() ![]() My standard (this varies from case to case) is Orneling – (the management pack name) – Overrides, this way I can keep track of the overrides I´m making and if I delete a management pack i can just delete the Override MP as well to get rid of the overrides for that particular Management Pack.Īfter the Override MP has been created it´s time to import the RDS MP’s needed to be able to monitor our RDS installation. The Run As Account will now be distributed to the selected server and we can move on to importing the Management Packs needed.īefore i import a new Management Pack i always create a new Management Pack for the overrides. Click “Add…” and then typ in the name of the servers, in my case tbvdi01 is the only server and it should look litke this.Open up “Properties” for the new Run As Account (Double click or right click and choose Properties) and then navigate to the “Distribution” tab. ![]() At last, click Create to finish the wizard. By using this option, the account will only be distributed to the RDS servers that we will select in the next step. On the “Distribution Security” page, choose the More secure option.Type the credentials for the account you just created and click Create.Set a display name for the account, in my case it´s “SCOM RDS Monitoring Account”.Right click Accounts and choose “Create Run As Account…” ![]() In the Operations Console, navigate to Administration-> Run As Configuration -> Accounts.In case you´ve never done this before, follow these steps Must be granted the Log On Locally user right (The Local Users group already is granted by default).Īfter the account has been created, get back into SCOM and set up the new account.Must be a member of the local Performance Monitor users group.Must be a member of the local users group.The following must be granted on every server that are running any RDS role I created a new Domain User and gave permissions to the following local groups at the RDS server which also can be found in the Management Pack guide that comes along with the Management Pack. The first thing to do before monitoring RDS is to install the SCOM agent at the RDS server, in my case tbvdi01 that are running all of the services needed for RDS to function.Īfter the agent is installed at the server, open up Active Directory Users and Computers and create a new user to be used for monitoring RDS. The System Center 2012 R2 Preview Management Packs which can be found here.Īfter I had installed RDS and the complete Office 2013 suite were published it looked like this.The Operations Manager Management Server.The Domain Controller of course for running the domain. ![]() This lab is depending on these three products In my home lab, all of the servers from the DC to the SQL server are running Windows Server 2012 R2 RTM and all of the System Center products are running System Center 2012 R2 Preview (at least til next friday when Microsoft launches all of their new products). I have written about how to monitor the Citrix suite (XenApp, XenDesktop, XenServer, Provisioning Services and Web Interface) before but this post will focus on Windows Server 2012 R2 Remote Desktop Services (RDS) instead as a competitor to Citrix XenApp. This is an area where Citrix is really big with their XenApp solution, a solution that many companies are using to deliver applications to their employees. The blog is soon going through a major change which hopefully will get both the visits and the posts to rise.Īs i sat down an evening earlier this week i thought it would be cool to publish some applications in my home lab. So, after about three months off the blog it´s time to get it going again. Monitor Remote Desktop Services 2012 R2 with SCOM ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |