Groups possible for many managed servers?

Hi,
we have to manage 30+ servers in 6 different locations.
In Microsoft Remote Desktop for Mac V 8.0.15 there is only one main group called "My Desktops" and all servers are listed in this group. I don't see a function to add more groups to have a ordered list. Is this possible?

Hi,
Sorry to say but still there is no such way to add other group in ordered list.  
Thanks for your understanding!
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

  • How many managed Servers do you need?

    Hi,
    One thing that has come up time and time again, is when trying to think about a new project and a new WL domain, is trying to know how many WL Managed Servers do you need?
    Does BEA have some sort of metrics which says ok for this amount of input we recommend you having 4 managed servers on 4 single boxes?
    And is there think on have 2 managed servers on 1 box or 2 managed servers on two boxes?
    Any Help Appreciated.
    Kind Regards,
    Alistair.

    Hi :-D
    I don't believe BEA have guide lines on how many Managed servers are required based on Metrics. You could look at some performance evaluations but it's really only relevant if your application acts in the same way.
    Cheers,
    Doug.

  • One custom security realm for many wl servers?

    Is it possible to use one custom security realm for many weblogic servers...ie
    one login for all application on different weblogic server.

    Is it possible to use one custom security realm for many weblogic servers...ie
    one login for all application on different weblogic server.

  • Consolidate ports for multiple managed servers

    Hello, say I've got two managed servers on a single machine - A and B. Each is running a different app in its own jvm on separate ports. Now what I'd like to do is be able to access both apps via the same port..just with different context paths like this:
    http://myserver/a/ would go to the managed server A app
    http://myserver/b/ would go to the manged server B app
    I don't want to put apache or anything else in front of them to do this. I want to know if weblogic itself provides a way to do it either through config or admin server somehow. Thanks for any ideas.

    Ports must be unique when running on the same machine
    A front controller (which do not want to use) is the way to do it.

  • Calculating how many managed servers you need.

    Hi,
    Does anyone know a BEA webpage were it tells you, on the lines of :
    If you have 5000 customer hitting your weblogic cluster you only need 1 managed server. If you have 30,000 you need two managed servers. If you have 500,000 you need three.
    Does anyone know of a performance page like this?
    Regards,
    Alistair.

    There is no such performance numbers from BEA. I think you need to rely on capacity planning process to estimate number of server based on your workload and performance requirements.
    http://dev2dev.bea.com/pub/a/2002/11/Hazarika.html
    http://edocs.bea.com/wls/docs81/capplan/capfact.html#1009720
    There are some benchmark results for WebLogic are available at
    http://edocs.bea.com/wls/docs81/capplan/capbase.html#1054891
    http://www.spec.org/jAppServer2004/results/jAppServer2004.html
    -Jayesh

  • Future support for APPV Management Servers

    I have heard rumors that APPV is moving away from the separate Management servers and future releases will only support SCCM integration.  Is this a true roadmap ?

    I don't have any insider information BUT I have not heard this from anybody. I'd lean on the side of not believing this. It's still an ok solution for small Enterprise. 
    Considering the announcement yesterday, what the future holds for App-V should be very interesting.
    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
    rorymon.com Twitter: @Rorymon

  • Why SCOM 2012 R2 Agent version for Service Manager servers is 6.1.7221.49, why not 7.1.10184.

    Hi ,
    In SCOM 2012 R2 console  if i look at all of my agent managed servers have agent builds of 7.1.10184 but my two service manager  servers have agent builds of 6.1.7221.49
    Can anyone let me know is this known issue or how can we upgrade the agent to correct version.
    Thanks in advance
    Bharath

    Hi,
    SCOM and SCSM are built on the same structure, Management Servers and DAta Warehouse etc. This means that when you install the SCSM Management Server, the Microsoft Monitoring Agent is also installed. When
    you want to monitor Service Manager and the server it´s installed on, you need to configure the SCOM parameters from the control panel at the SCSM management server.
    If you were to try and install the SCOM agent at the SCSM server, it would fail and tell you that you can´t install the agent on a server where Service Manager is installed. The agent will be upgraded when
    you upgrade Service Manager so this is all expected and It´s as it should be :)
    Regards,
    Daniel
    IT Consultant at Viridis IT

  • New Group Required for Service Management

    Hi,
    I could not see Forum Group - Service Management
    This covers Maintenance & Customer Services
    If this group is available, we can put our ideas there and then easily find out.
    In the group SCM, huge data is getting posted and difficult to find out perticular like Service Management.
    Hope to hear soon,
    Regards,
    Jayantkumar Joshi
    INTELLIGROUP ASIA PVT LTD.,
    Sr PM-CS Lead Consultant
    Mobile: 91-9885430724
    [email protected]
    India

    Hi Jayantkumar Joshi,
    Posting a request for a new forum in this, the Suggestion Forum, is the proper place for such a request.  Thanks for taking the time to do so.
    Creating a new forum usually is done under the following conditions:
    1) There is a critical mass of content in a particular area and the collaboration team sees that the creation of a new fourm would best service discussions of that area. (by critical mass, we mean hundreds of references to a topic)
    2) There are requests from a number of community members with some very clear justifications around why such a new forum would be of value to the community.
    (we also would hope that the requestors are active members of the community and actively engaged in using the forums)
    3) The collaboration team sees a new direction or subject evolving and provides a forum for discussing it or a subject becomes so large that it would be better to subdivide it into subcategories. (these requests are trends and we try to avoid creating new forums without being sure there will be active conversation to populate them)
    4) The product management gives us moderation support or there is enough subject matter expertise in the community to create a community led moderation of an area.
    A user can do a search on forums to see examples of such critical mass that warrants its own space.  For example, when subdividing the ABAP forum we searched for key words that were appearing hundreds of times in the general forum and began to create the ability to move discussions to subareas of the ABAP topic for Enhancements, Data Transfer, Dictionary, Form Printing.  Although we did so, people still persist in posting to the ABAP general forum
    We also got community help and support from a number of top contributors in an area as to what topics were constantly recurring.  And lastly and importantly, we turned to subject matter experts internally to get feedback, definition, advice.
    All that being said, we would ask our community to consider:
    1) Is there enough interest in Service Management to create a separate group around this?
    2) Is there enough existing conversation around this topic to move it to such a new area
    3) Is it clear under exactly which catergory this falls: SCM, CRM, PM and how to know exactly what is meant by Service Management (I did a search in help.sap.com and wasn't really sure)
    Each forum needs a contract that states what kind of content we wish to have discussed there.  That is a prerequisite.
    In light of all these comments, please see if your idea meets the criteria: critical mass, clear definition of what is to be discussed, interest of the community.
    best,
    Marilyn

  • While starting managed servers asks for password of localhost

    We have a clustered environment and we are using Virtual IPs for the Managed servers. The managed servers in the forst node is not starting.
    The problem I have narrowed down is that there are startup.properties file for the managed servers.
    It has argument like -Dtangosol.coherence.localhost\=xgsoapd5v1.ea.com (for SOA1)
    While SOA1 it is asking for password for the above host and the managed server is not starting.
    Now SOA2 has the similar argument -Dtangosol.coherence.localhost\=xgsoapd5v2.ea.com (for SOA2), but it is not asking for any password and so the SOA2 managed server is sta! rting.
    Similarly the while starting BAM1 it is asking for a password , but for BAM2 it is not asking for password and it is starting.
    I could not yet figure out why it is behaving differently in the first node.
    This is a copy of production with a chnage in the network. That means only the IP addresses are changed. xgsoapd5v1.ea.com and xgsoapd5v2.ea.com are the hostnames
    It works perfectly in production environment.

    Hi
    Under your domain root folder say in the main machine where you have the AdminServer, you should have a folder structure something like this:
    ../user_projects/domains/yourBPMDomain1/servers. Under the servers folder you can see list of each server. On the main machine you will see one AdminServer folder. Under this there should be a sub-folder named security with one file named boot.properties. This boot.properties file will have encrypted username and password for the weblogic domain.
    If this security/boot.properties exist under the each server folder, then when you start the managed server, it will NOT prompt for the username/password. If it DO NOT exist, it will ask for the credentials.
    Solution is go to each Machine where you the ManagedServers (SOA Server or BAM Server does not matter). Go to each server and under that create a folder named security and create a file named boot.properties and in this file enter plain text username and password something like this and save the file. Now restart all those servers.
    username=domainadminusername
    password=doaminadminpassword
    When you start the servers, server should start taking the above information. AND server will automatically ENCRYPT the above plain text data into hash codes.
    In a nut shell, go to each Server folder across all the remote machines and under that particular managed server create a folder security with one file boot.properties.
    Exmaple locations:
    On Machine1 - user_projects/domains/bpmDomain1/servers/soa_server1/security/boot.properties
    On Machine2 - user_projects/domains/bpmDomain1/servers/bam_server1/security/boot.properties
    You DO NEED the admin username and password in plain text for one time to put in boot.properties. Later on it will get encrypted, so there is no threat for any security loop holes.
    Thanks
    Ravi Jegga

  • Weblogic.Admin command for stopping all Managed Servers in cluster

    Hello All,
    I am using Weblogic 9.2 MP3 on Linux env. I have a domain which has 16 Managed servers which are part of a cluster, I have eight Managed Servers running on one physical machine and other eight running on another physical Machine.
    I know we can do all stop and all start of Managed servers from console if we have node manager setup. We do not want to have node manager setup in our env.
    I am looking for a way to do that using java weblogic.Admin utility
    Please let me know on how we can achieve this using weblogic.Admin utility by passing clustername argument.
    Thanks
    Weblogic Consultant

    hi sir,
    I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
    If u want to use WLST for starting managed servers and clusters
    check the follwing steps.
    1. java weblogic.WLST
    2. startNodeManager()
    3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
    4. TAKE ANOTHER COMMAND PROMPT
    java weblogic.WLST
    5. start('man1','Server') or start('man1','Server','localhost:7003')
    6. start('mycluster','Cluster')
    7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
    8.shutdown('mycluster','Cluster')
    regards
    abhi
    Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

  • Management Servers in untrusted domains

    Hi,
    I am planning a deployment of SCOM 2012 R2 and have several questions regarding the appropriate placement of management and gateway servers.
    The environment has multiple untrusted domains and need to monitor both Windows and Linux computers on both sides of the firewall. The main domain has 1500 Windows computers and 1300 Linux computers. The untrusted domain has 250 Windows servers and
    450 Linux servers.
    It is understandable that gateway servers are utilized to communicate across the firewall.
    The questions are:
    1. Is it possible to locate one or more management servers in the untrusted domain for the Linux servers and another management server to work with the Windows servers and have those management servers in the untrusted domain communicate through the firewall
    via gateway servers to the databases in the main domain?
    2. If it is not possible to have management servers in the untrusted domain communicate via the gateways; how many gateways would be required to relay to the management servers in the main domains management group?
    3. With the number of Linux servers in the untrusted domain is it better to install a separate management group there?
    Thanks, for any advice in dealing with the above scenario.
    --SG

    Hi There,
    Microsoft recommends you to place all the management servers in the same data center so if 1 goes down the other comes to know about it asap.
    If you place it in another location then fail over may happen late.
    Also you have mentioned to place the management servers in another domain, Which is possible but you need to have trust and permission stuff which is a very hectic work.
    So i would suggest you to place gateways as it will help in compression if the network bandwidth is low between the domains and sites.
    And based on the MS's Sizing and management options a Gateway server can manage 100 Unix boxes for a dedicated gateway server and 500 per management server on the same domain.
    So based on your situation as below:
    1300 Linux - Same domain
    450 - Different domain
    3 Management servers for the main domain for dedicated Linux
    1 MS For Windows Agent monitoring.
    Totally 4 in a management group for the same domain one.
    1 Separate management group with 1 MS will be fine for dedicated Linux monitoring for the 450 servers in the other domain.
    If you want to still place gateways then you will need to place 5 Gateway servers which is difficult to manage.
    Operations Manager supports the following number of monitored items.
    Monitored item
    Recommended limit
    Simultaneous Operations consoles
    50
    Agent-monitored computers reporting to a management server
    3,000
    Agent-monitored computers reporting to a gateway server
    2,000
    Agentless Exception Monitored (AEM)-computers per dedicated management server
    25,000
    Agentless Exception Monitored (AEM)-computers per management group
    100,000
    Collective client monitored computers per management server
    2,500
    Management servers per agent for multihoming
    4
    Agentless-managed computers per management server
    10
    Agentless-managed computers per management group
    60
    Agent-managed and UNIX or Linux computers per management group
    6,000 (with 50 open consoles); 15,000 (with 25 open consoles)
    UNIX or Linux computers per dedicated management server
    500
    UNIX or Linux computers monitored per dedicated gateway server
    100
    Network devices managed by a resource pool with three or more management servers
    1,000
    Network devices managed by two resource pools
    2,000
    Agents for Application Performance Monitoring (APM)
    700
    Applications for Application Performance Monitoring (APM)
    400
    URLs monitored per dedicated management server
    3000
    URLs monitored per dedicated management group
    12,000
    URLs monitored per agent
    50
    Refer the below link for the managing details: https://technet.microsoft.com/en-us/library/dn249696.aspx?f=255&MSPPError=-2147217396
    Gautam.75801

  • Administration vs Managed Servers

    We are preparing to upgrade from WLS5.1 to WLS8.1 and I am having a problem with
    the recommendation that the typical production environment have an administration
    server and one (or more) managed servers.
    In our environment, we host applications for multiple customers. Currently, each
    of these customers has a separate instance of WLS5.1 running. In many cases, the
    connection pools have the same name between instances, but with different userids/passwords.
    In the conversion to 8.1, I have been debating having a separate domain for each
    customer application versus a single domain with a separate managed server for
    each customer. The single domain has many desirable features, but it does not
    provide for the multiple userid /passwords for a connection pool. The separate
    domain per customer eliminates the connection pool issue, but essentially doubles
    the number of WLS servers (1 admin and 1 managed) for each customer.
    Even though BEA recommends a separate admin server and managed server, in reality,
    how important is this? Will I cause myself problems in the future if I choose
    to run a combined admin and managed server?
    Thanks for any thoughts on this subject.

    Thanks David. As God as my witness, the tech seriously told me that they all use the same JVM. Then I got seriously confused, like I was an idiot and didn't understand what a JVM was and I started second-guessing myself. The whole conversation was very strange and yes, there was definitely a language barrier and I'm guessing I just wasn't being clear enough...I don't know...all I know is I walked away from the phone call in worse shape then when I first opened the ticket.
    At any rate, do you have recommendations for admin server ram? I know there are performance tuning tools to help us figure out the optimum settings for our managed server, and I plan on implementing them...but going back to the ram for the Admin server, versus managed server...is there a recommended way of specifying different heap size for the managed servers? Is the recommended way to set the the -Xms and -Xmx settings via the 'Arguments' field on Environment > Servers > serverName > Configuration > Server Start tab via the admin console?
    Thanks again for your quick reply!
    Cheers,
    rlb

  • Creating new Managed Servers on remote machines

    Hi,
    We have a multi-machine domain already in place. Nodemanager is configured and we're using the architecture suggested in Oracle SOA Enterprise Deployment Guide, where we have one domain home for the AdminServer and one domain home for the Managed servers. Right now what we need to know is how to add new managed servers in the easiest and fastest way possible on the mserver home on both the adminserver local machine and on the remote machine, this is a development environment and we need to be able to quickly create and delete these servers for developers to work.
    We know that the standard way of doing it is doing a pack (for the managed servers only), and then an unpack on the mserver home both on local and remote machine after changing the root directory of these servers to match those homes. Here is were we have our first doubts. Do the unpack command command has to be run with the already running servers down? Does this pack and unpack process affects what we already have deployed on the running managed servers? And last but not least, is there any way to automate this process? Because we need to give the developers the ability to create clusters on the environment through the admin server console, but without giving them access to the underlying operating system.
    If this seems like a newbie question is because we are, we're just in the process of migrating oas 10g to weblogic 11g and there are tons of basic administration stuff that seem pretty strange for us, we've looked through the Oracle manuals and metalink but even though some show you how to create the domain with remote managed servers for the first time, we couldn't find any mention on how to add the mserver efficiently after that.
    Thanks!

    Cris,
    Thanks again for your help, we're trying to figure out how to present this procedure to our customer, just one thought though, we were thinking about moving away from the architecture presented by de SOA Enterprise Deployment guide, and using a single domain home located on the shared storage, that way we could create the managed servers from the admin console without having to use pack/unpack and deciding where to run the servers just by configuring machines and nodemanager. However, we haven't seen this kind of configuration anywhere on Oracle manuals, is there any other problem you are aware of in this idea? We're using a storage with multipath for the shared disk so we're not very concerned about availability (and if the storage went down the weblogic domain would be the least of our problems).
    Regards, Franco.

  • Running managed servers from different WL versions under a domain

    Hi,
    Would it be possible to run managed servers (in non clustered way) from different versions of WebLogic under a single domain, with admin server of higher WebLogic version controlling the domain and the managed servers?
    Regards,
    Gobi

    Hi Gobi,
    we can make it run such a way but it may lead to many complication with patch sets.
    Few thing work in one environment and other will not so it is not at all recommended way to set such configuration.
    Regards,
    Kal

  • 1 NodeManager, 1 Admin Server and 2 Managed Servers

    Hi All, I'm new in Weblogic and this is my 1st time to post a question on this forum. Would like ask for help from you all above my setup, I'm not sure whether it will work or not. Please find out the scenario below:
    Setup:
    1 Machine (RedHat Enterprise Linux 5.5)
    1 NodeManager
    1 AdminServer (Name: APP)
    2 Managed Servers (Name: APPLIVE, APPUAT)
    Currently I would like to using one NodeManager to control both Managed Servers under 1 machine. When I configure my APP Admin Server and two Managed Servers, i would like to nmEnroll both Managed Servers under one NodeManager but it will overwrite my enroll entries if i enroll 2nd Managed Server.
    Is it possible to configure NodeManager to accept both Managed Servers entries? Thanks. :)
    Edited by: user13602952 on Jan 2, 2011 9:54 PM

    Hi Hong,
    Following are the few things which you help you understand about NodeManager and nmEnroll
    - First of all a Node Manager process is not associated with a specific WebLogic domain but with a machine
    - When you run a nmEnroll then you just give "domainDir" and "nmHome" which would then gets the file called "*nm_password.properties*" which contains the encrypted username and password that is used for server authentication and "*SerializedSystemIni.dat*" file.
    Example:
    nmEnroll([domainDir], [nmHome])
    - With above files it also updates the nodemanager.domains file with the domain information which was mentioned in the above command.
    Thus when you run the nmEnroll command it would get all the details which it needs to start any managed servers in the same Machine, hence you do not need to run the same commend for each managed servers in the same Machine.
    For more information have a look at the below links:
    Topic: Search for "nmEnroll"
    http://download.oracle.com/docs/cd/E13222_01/wls/docs92/config_scripting/reference.html
    Topic: Overview of Node Manager
    http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/nodemgr.html#1091317
    Regards,
    Ravish Mody
    http://middlewaremagic.com/weblogic/
    Come, Join Us and Experience The Magic…

Maybe you are looking for