SCCM 2012 & SCOM 2012 - Cross Forest

My current environment is running Operations Manager and Configuration Manager 2007, I am planning an upgrade them to the 2012 version.
I need to know whether my upgrade to 2012 will support cross forest support ?
Cheers

And, there is no 'upgrade' of Configuration Manager 2007 to Configuration Manager 2012 (if you mean Configuration Manager 2007 instead of "SCCM 2008"). You would need to do a side-by-side migration. There are docs, webcasts, webinars (in fact I just did
one a couple of weeks ago), and TechNet virtual labs on migration to help you gain understanding on how it would work.
However, yes, Configuration Manager (both 2007 and 2012) do support cross forest environments.
Wally Mead

Similar Messages

  • What is Licensing Method for SCCM and SCOM 2012

    What is Licensing Method for SCCM and SCOM 2012
    We have 75000 clients, so we going to implement SCCM and SCOM 2012 environment in azure. Actually we plan to go for One Central Administration site and three primary sites (to manage this clients), going to host in Azure. I need to know how the licensing
    process work for this environment, how many licenses we need to get for this? is charging for Client based, Site based or environment based?  Please update.
    Thank you
    Fazal
    Fazal(MCTS)

    Hi,
    Running the SCCM and SCOM servers themselves in Azure to manage clients outside azure is not really supported if I remember correctly..
    http://blogs.technet.com/b/configmgrteam/archive/2013/10/23/configmgr-and-endpoint-protection-support-for-windows-azure-vms.aspx
    Licensing is explained here.
    http://www.microsoft.com/licensing/about-licensing/SystemCenter2012-R2.aspx
    In short for Client OS you need a cal per client, included in Core CAL and Enterprise CAL.
    For servers it is licensed per CPU and can be licensed for all virtual servers on a host as well, included in the guide above.
    ps. side note a CAS is not really necessary in most case if you don't have more than 100'000 clients, it adds a lot of complexity and I would avoid it if I could.
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • SCCM and SCOM 2012 R2 Databases on one box

    Our current situation is: About 150 Servers(VMware) and 600 windows 7 clients.
    SCCM 2007 and SQL 2008 on one box, and for SCOM 2007 we have a dedicated SQL2005 VM. All of them on W2K3R2 OS.
    Because of end of support for W2K3, we are not going to upgrade the servers.
    New situation is SCCM and SCOM 2012 R2 with SQL 2014 on W2k12R2. I'm considering to install one SQL 2014 server only for SCOM and SCCM. Would performance be an issue??
    I've read   http://www.hasmug.com/wp-content/uploads/2012/10/07-201210-Oct-SQL-Server-Optimization-and-Best-Practices-for-System-Center-Administrators-Kevin-Holman.pdf
    and other articles, but couldn't find info about the pro and cons having both SCOM and SCCM DB's on one SQL 2014 server
    Thanx

    Hi,
    Please refer to the following articles:
    SQL Instances and System Center 2012 (#SYSCTR #SQL #SCOM #SCCM #SCSM)
    http://www.systemcentercentral.com/sql-instances-and-system-center-2012-sysctr-sql-scom-sccm-scsm/
    SCOM 2012 and SQL Server Question
    https://social.technet.microsoft.com/Forums/systemcenter/en-US/fabf4318-4de6-4627-9f6d-71834ac2bcab/scom-2012-and-sql-server-question?forum=operationsmanagerdeployment
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    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 Subscriber Support, contact [email protected]

  • SCOM 2007 cross-forest clients migration

       Hello to all. I'm preparing a cross-forest migration from source domain domain1.a.com to target domain domain2.b.com . 
       Source domain has hundreds of servers (windows 2003 and windows 2008). All source DCs are Windows 2003. Source domain already has SCOM 2007 R2 deployed on its member servers and on others located on another source domains.
       As cross-forest migration will run just for domain1.a.com I need to know:
       1- Is possible to migrate member servers from source-->target and keep source SCOM 2007 R3 monitoring the already migrated member server? 
       2-If positive, what need to be done in advance (before any member server migration) and after each member server migration?
       3-If target forest already have a SCOM 2007 R2 environment, what should need to be done so migrated member servers would be monitored on this target SCOM 2007 R2 (that has nothing to do with the source one) ?
       Thanks in advance, EEOC.

    1. It is possible.
    2. You will have to install certificates in the environment and either manag the agents through a gateway (minimal number of certs) or by installing certs on the agents directly.
    3. Just uninstall the agents and reinstall by the target SCOM 2007 R2 console.
    Juke Chou
    TechNet Community Support

  • SCCM 2007 and 2012 coexistence and Cross Forest support

    Hi All
    I have a question
    My company has recently acquired another company
    That company exist of 2 forests (forest A has one domain namely domain A : and forest B has one domain namely domain B) with a two way forest trusts between them
    Domain A has a SCCM 2007 primary Site
    Domain B has a SCCM 2007 primary site and 2 secondary Sites
    The active directory schema is extended in both domains
    We cannot migrate the SCCM 2007 environment because it is a mess , so we want to build a new SCCM 2012 R2 environment into Domain B and from that environment manage both domains  (OSD, software deployment client management ...)
    We want to install a SCCM 2012 R2 (CU3) primary server into domain B and add two distribution points instead of the two secondary sites and manage both forests (domain A and B) from that primary site server
    Now my questions are
    1 )
    Can an SCCM 2007 environment coexist with a SCCM 2012 environment?
    I believe it can If I make sure that in the new SCCM 2012 environment we only use boundary groups for content locations and not for site assignment and in the SCCM 2007 environment (domain A and domain B) I need to disable the client push account.
    2)
    Discovery , How do we make sure that systems and users are discovered from both domains?
    Do we need to do some additional configuration to make that happen or will this be no problem because of the Two way trust and active directory schema extension.
    3 )
    Can we do all the management from the new SCCM 2012 R2 site , also OSD deployments for both domains ?
    I hope someone can help me with these questions
    Thanks in advance
    Regards
    Johan

    Hi All
    After talk with management and local support the decision is made not to deploy only distribution points but instead deploy secondary sites (of course with management point and distribution point) because the bandwidth to these sites is a
    problem.
    So the situation will be Domain A Primary site (SCCM 2012 R2) and for both remote locations a secondary site , domain B a secondary site (of course all the related ports need to be opened for both domains as explained here https://technet.microsoft.com/en-us/library/hh427328.aspx
    Question 
    Can we do all the management from the new primary SCCM 2012 R2 site (domain A) , also OSD deployments for both domains A and B ?
    I hope someone can review this
    Thx in advance
    Regards Johan

  • SCCM 2012 R2 cross forest with one-way trust feasible?

    We are planning to replace our existing SMS 2003 server with SCCM 2012 R2 (running on Windows server 2012 R2).
    Our requirements are to support client our Windows 7 client PC's in Domain A and also support Xen Desktop clients in a separate domain (Domain B) and forest. We have a one way trust established (Domain B trusts Domain A). The SCCM 2012 R2 server will be
    in Domain A the same as our current SMS 2003 server.
    What we want to do, at a minimum, using SCCM is:
    Client inventory (hardware, software, user) and package distribution.
    Is this do able or a no go? If not directly is there any work-around for this? Appreciate any helpful advice or feedback.
    I have made the below diagram to better illustrate the scenario:
    Note: Domain B does not have WINS implemented (Domain A does). Both domains are running DNS of course.

    Hi,
    The following blog describes the technical requirements that have been put in place for the support of cross forest communication. You could have a look.
    Quote:
    Inner-site Communication (site to site communication) exists in the form of both File Based Replication (SMB Port 445) and Database Replication (TCP/IP port 4022 by default).
    In order to install and configure a child site (primary or secondary), the child site server must be located in the same forest as the parent site or reside in a forest that contains a
    two way trust with the forest of the parent (CAS or primary).
    Site System Roles (MP, DP, etc.) with the exception of the Out of Band Service Point and the Application Catalog Web Service Point can be deployed in an untrusted forest.
    The SLP functionality as known in ConfigMgr 2007 is now performed by a Management Point. In this blog I will refer to this as the Lookup Management Point.
    Most of these items were taken from this TechNet article – please refer to the article for more information -
    Planning for Communications in Configuration Manager .
    For more information:
    http://blogs.technet.com/b/neilp/archive/2012/08/20/cross-forest-support-in-system-center-2012-configuration-manager-part-1.aspx
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.
    Thank you for your reply. The below appears to make it seem as though this can be accomplished without requiring a trust:
    http://blog.coretech.dk/kea/multi-forest-support-in-configmgr-2012-part-i-managing-clients-in-an-untrusted-forest/#comment-284522
    Not sure which is correct...

  • SCCM 2012SP1 - Cross Forest Scenario

    Guys/Girls
    I've configured a cross forest SCCM scenario, with all the SCCM config in one Forest and a single Windows XP SP3 desktop in the other. There is a trust between both Forests/2-way external but I haven't added Forests/Domain to SCCM to enable searching
    etc. I deployed the agent manually in the external Forest using a mapped drive and ccmsetup /mp:........ this all works fine.
    After installation, after the client is approved, when I click on the client in the SCCM console and try to initiate any of the "right-click" features, I just get a stack of access denied errors back "0x80070005". I've tried rebuilding
    WMI, re-installing the client to no avail. Im thinking that its related to the cross forest config but I see no provision for setting up external credentials for the other forest - am I right in thinking that the only account that needs to be configured is
    the "Network Access Account" that the agent uses to make network connections (the rest being run under the guise of the "Local System" account) if so - this is already done too.
    I'm not seeing any access denied entries on the XP desktop and I've been through the DCOM config and local policy to make adjustments/slacken off the permissions...still no dice.
    Am I chasing my tail with this? can I manage a client from the console that actually sits outside of the Forest where the SCCM installation is actually installed?
    The installation is pretty much inline with scenario 1 from the following blog:
    http://blogs.technet.com/b/neilp/archive/2012/08/20/cross-forest-support-in-system-center-2012-configuration-manager-part-1.aspx
    -a

    Reading more closely, I notice now that you said "right-click tools". That explains it as those truly have nothing to do with ConfigMgr. Essentially, what all right-click tools are are individual scripts run on your local system that directly connect
    to the remote system to perform an action. The console initiates these scripts but that's it. Thus, the credentials of the user logged into the console are used to launch those scripts and the problem here is that the user you are running the console
    as does not have permissions to remotely connect to that remote system.
    As mentioned, this has nothing to do with ConfigMgr though because ConfigMgr never ever connects to remote clients -- call client agent communication is initiated by the client.
    Thus, the right-click tools, while sometimes/often useful, should not be confused with native ConfigMgr functionality.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Cross Forest - SCCM 2012SP1

    Hi All - I've re-posted this as I put it in the wrong thread initially under 2007.
    I've configured a cross forest SCCM scenario, with all the SCCM config in one Forest and a single Windows XP SP3 desktop in the other. There is a trust between both Forests/2-way external but I haven't added Forests/Domain to SCCM to enable searching
    etc. I deployed the agent manually in the external Forest using a mapped drive and ccmsetup /mp:........ this all works fine.
    After installation, after the client is approved, when I click on the client in the SCCM console and try to initiate any of the "right-click" features, I just get a stack of access denied errors back "0x80070005". I've tried rebuilding
    WMI, re-installing the client to no avail. Im thinking that its related to the cross forest config but I see no provision for setting up external credentials for the other forest - am I right in thinking that the only account that needs to be configured is
    the "Network Access Account" that the agent uses to make network connections (the rest being run under the guise of the "Local System" account) if so - this is already done too.
    I'm not seeing any access denied entries on the XP desktop and I've been through the DCOM config and local policy to make adjustments/slacken off the permissions...still no dice.
    Am I chasing my tail with this? can I manage a client from the console that actually sits outside of the Forest where the SCCM installation is actually installed?
    The installation is pretty much inline with scenario 1 from the following blog:
    http://blogs.technet.com/b/neilp/archive/2012/08/20/cross-forest-support-in-system-center-2012-configuration-manager-part-1.aspx
    -a

    http://social.technet.microsoft.com/Forums/systemcenter/en-US/a64548eb-11dd-441f-95d7-097c70c96f17/sccm-2012sp1-cross-forest-scenario?forum=configmgrgeneral
    is the original thread. You shouldn't cross post -- you should wait for a mod to move the thread as now we have multiple people answering the same question without the benefit of seeing what others have answered.
    As mentioned there, this really has nothing to do with ConfigMgr and stems from the use of right-click tools.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Recommendations for SCOM 2012 -- 2012 R2 migration

       Hello to all. I have a customer that has SCOM 2012 in its IT environment but uses it barely and does not have any documentation. I proposed to install a new Manament Group (MG) and "reboot" to a paralell SCOM 2012 R2 considering the
    use of new features present on 2012 R2. 
       Questions:
       1- Does SCOM support a side by side migration strategy , like SCCM 2007 R2 --> SCCM 2012 R2 that takes its main source objects and bring them to the new separated Management Group (the SCOM 2012 R2)?
       2- Considering that all regular member servers are monitored by SCOM 2012 (all have agents installed), what is the recommended way to to install SCOM 2012 R2 agents on them (multi homed deploy, deploy a new agent and it will upgrade/remove the
    already existing SCOM 2012, etc)?
      3- Does SCOM allows a approach to install a SCOM 2012 R2 on already existing SCOM 2012 MG and "migrate" its objects to new server and after that decomission SCOM 2012 (the old version)?
      Your inputs and references will be very welecomed.
      Regards, EEOC.

     1- Does SCOM support a side by side migration strategy , like SCCM 2007 R2 --> SCCM 2012 R2 that takes its main source objects and bring them to the new separated Management Group (the SCOM 2012 R2)?
       2- Considering that all regular member servers are monitored by SCOM 2012 (all have agents installed), what is the recommended way to to install SCOM 2012 R2 agents on them (multi homed deploy, deploy a new agent and it will upgrade/remove the
    already existing SCOM 2012, etc)?
    Yes. You can built SCOM 2012 R2 and do side-by-side migration.
    High Level View of System Center 2012 R2 Operations Manager Upgrade Steps – Upgrading 2012 SP1 Agents to 2012 R2 and Running Two Environments:
    1. Retain the original System Center 2012 Service Pack 1 (SP1), Operations Manager environment.
    2. Set up an additional, new System Center 2012 R2 Operations Manager environment with management servers, gateway, Operations Manager Database, Operations Manager Data Warehouse, console, web console, and reporting server.
    3. Upgrade the System Center 2012 Service Pack 1 (SP1), Operations Manager Agents to 2012 R2.
     a. Push-Install option
     b. Manual / Command Line option
      3- Does SCOM allows a approach to install a SCOM 2012 R2 on already existing SCOM 2012 MG and "migrate" its objects to new server and after that decomission SCOM 2012 (the old version)?
    The upgrade path is from SCOM 2012 --> SCOM 2012 SP1 --> SCOM 2012 R2
    High Level View of System Center 2012 R2 Operations Manager Upgrade Steps – Upgrading a Distributed Management Group
    1. Accomplish Pre-Upgrade Tasks
    2. Upgrade the initial management server and then additional management servers (each management server must be upgraded)
    3. Upgrade ACS (because the ACS server must be on same machine as a management server, we recommend you perform this step along with the upgrade of the management server on which ACS resides.)
    4. Upgrade Gateway(s)
    5. Upgrade Console
    6. Push Install to Agent(s) / Upgrading Manually Installed Agents
    7. Upgrade Web Console
    8. Upgrade Reporting Server
    9. Accomplish Post-Upgrade Tasks
    For detail, pls. refer to
    Upgrading System Center 2012 – Operations Manager to System Center 2012 SP1
    https://technet.microsoft.com/en-us/library/jj899854.aspx
    Upgrading System Center 2012 SP1 - Operations Manager to System Center 2012 R2
    https://technet.microsoft.com/en-us/library/dn249707.aspx
    Roger

  • SCOM 2012 R2 Upgrade Plan Discussion

    Dear Experts,
    Currently I have a RMS and one MS Server with SCOM 2007 R2 in my Test Environment (Windows 2008 R2).
    Now, The Upgradation plan is below and please correct me if I am wrong.
    SCOM 2007 R2 CU4 --> SCOM 2012
    SCOM 2012  --> SCOM 2012 SP1
    SCOM 2012 SP1 --> SCOM 2012 R2.
    So we need to purchase of three types of SCOM 2012 versions S/W or else we can simply download those versions from Microsoft ?
    Please provide me the complete process of this Migration cycle.
    Saravana Raja

    Hi Saravana:
    Upgrading to System Center 2012 – Operations Manager is supported from Operations Manager 2007 R2 CU4, or from the latest available CU. See
    http://technet.microsoft.com/en-us/library/hh476934.aspx.
    As for upgrading from SCOM 2012 to SCOM 2012 SP1 to SCOM 2012 R2, MVP Marnix Wolf is clear that you need to perform each upgrade step separately:
    http://thoughtsonopsmgr.blogspot.com/2013/07/upgrade-paths-to-system-center-2012-r2.html. The "complete process" would consists of performing the upgrade for each version one after the other, again, just as you put in your plan.
    You do not need to purchase any additional software, but you will need to download the 3 versions as you described from Microsoft volume license site or other media source.
    John Joyner MVP-SC-CDM

  • Upgrade Paths for SCOM 2012 R2

    I looked through many forums and MS sites but can't find if it's possible to upgrade SCOM 2007R2 to SCOM 2012R2 directly.  Or do you have to upgrade to the integrated SCOM 2012SP1 package first?  or is even that supported?  I'm trying to
    upgrade to 2012R2 from 2007R2 and everything is on the same server.  

    Agree
    The correct upgrade path is
    SCOM 2007 R2 CU4 --> SCOM 2012
    SCOM 2012  --> SCOM 2012 SP1
    SCOM 2012 SP1 --> SCOM 2012 R2
    1) blog for upgrade SCOM 2007 R2 to SCOM 2012
    http://jeroennotebaertsblog.blogspot.hk/2012/01/upgrading-scom-2007-r2-to-scom-2012.html
    http://www.vnext.be/2012/10/23/upgrade-guide-from-scom-2007-to-scom-2012/
    2) blog for upgrade SCOM 2012 to SCOM 2012 SP1
    http://kevingreeneitblog.blogspot.dk/2012/12/scom-2012-installing-service-pack-1-rtm.html
    3) blog for upgrade SCOM 2012 SP1 to SCOM 2012 R2
    http://www.systemcentercentral.com/upgrading-operations-manager-from-2012-sp1-to-2012-r2-step-by-step-upgrading-to-2012-r2-series/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+systemcenterforum+%28System+Center+Central+Rollup%29
    Roger

  • SCOM 2012 SP1 failed to send notifications by IM Channel

    Hello, I have a problem with my SCOM 2012 SP1. When it tries to send notification by IM Channel I get the following alert in SCOM:
    Notification subsystem failed to send notification using
    device/server 'live.august.ru:5060' over 'sip' protocol to
    'sip:[email protected]'.
    Microsoft.Rtc.Signaling.OperationFailureException: The GetInbandDataAsyncResult
    operation has failed with message: "The data session subscription to server
    failed.". See the InnerException and FailureReason properties as well as the
    logs for additional information. . Rule id:
    Subscription077dc311_59c0_4ba5_a432_072b486cd287
    At the same time the following event in the Application Event Log generates on the server with IM service:
    Event Type: Warning
    Event Source: Live Communications Server Authentication
    Event Category: (1003)
    Event ID: 16435
    User:  N/A
    Computer: LCS
    Description:
    At least one invalid authentication signature was detected.
    There were 2 messages with invalid signatures in the last 7112 minutes. The last one had the FROM header: sip:[email protected]
    Cause: This could be due to a client or server which is not handling authentication correctly, or it could be due to an attacker.
    Resolution:
    None needed unless the failure count is high (>100). Check your network for any rogue clients. Restart the server if problem persists.
    Notifications sent by the SMTP channel work fine!
    I Have the following Servers:
    LCS (live.august.ru) - Win 2003 EE SP2 + Live Communication Server 2005 SP1
    SCOM - Win 2012 + SCOM 2012 SP1
    Also I have a third server (Win 2003 + SCOM 2007 R2) and it sends notifications to the same VMLCS server successfully. The configurations of IM Channels are identical on both servers:
    IM server: live.august.ru
    Return address: sip:[email protected]
    Protocol option: TCP
    Authentication method: Kerberos
    IM port: 5060
    I tried to change the Authentication method to NTLM, and the port to 5061, but it doesn't help...

    Hi,
    Please refer to these following articles to configure IM channel correctly:
    How to Create and Configure the Notification Action Account
    http://technet.microsoft.com/en-us/library/hh212835.aspx
    How to Enable an Instant Message Notification Channel
    http://technet.microsoft.com/en-us/library/hh212690.aspx
    Enabling Instant Messaging Notifications in System Center 2012 Operations Manager
    http://opsmgrunleashed.wordpress.com/2012/02/24/enabling-instant-messaging-notifications-in-system-center-2012-operations-manager/
    Alex Zhao
    TechNet Community Support

  • SCCM 2012 - Network requirements for Client communication to primary in a Cross Forest Environment

    Hello, I have been trying to get some definitive answers on what network traffic is required between a client and a primary site versus a secondary in a cross forest scenario.
    Here is the scenario:
    Company A has an existing SCCM 2012 primary Site. Company B (Separate Forest) has now been brought in. One subnet on each side can route to each other and using that one subnet a two way forest
    trust has been setup. But the remote offices have IP address overlaps between companies. At some point in the future all assets on company B will be re-IP and brought over to Company A domain. But in the interim it would be nice to get SCCM cross forest clients
    working. Upgrading to a CAS model with two Primaries would not be preferred here as this is a temporary solution. 
    My questions are as follows.
    If a secondary site is deployed into Company B Forest/Network. I have seen people online elude to that clients will still need to communicate to the Primary located at Company A, even though they
    are assigned to a secondary on Company B’s network. Is this true? Is there any workarounds for this? Is a NAT back to the primary acceptable, or is reverse lookup required?
    Will the Primary need to communicate directly to the clients in Company B? If this is in fact a requirement, then this would be a show stopper. But if its only needed for things like client pushes,
    then we could work around it.
    Thanks

    "But the remote offices have IP address overlaps between companies"
    Technically, this is unsupported because clients, depending upon your boundaries, will not be able to find a local DP since they use IP addresses for this. The only way to work around this is to use AD Site boundaries.
    "though they are assigned to a secondary"
    Clients are *never* assigned to a secondary site -- that's not what secondary sites are for. Yes, clients require communication with an MP in the primary site where they are assigned. There is no way to change this or work-around this except to put
    an MP from the primary site closer to those clients and use the new MP affinity option in R2 CU3.
    Reverse lookups are only used to verify names by applications that wish to have this type of functionality (which are very few in number) and have nothing to do with true network traffic. NATing is an issue for the reason I gave above -- DP location.
    Remote control, client push, and WoL won't work either because there is no way for the traffic to reach the destination behind the NAT.
    All client *agent* communication in ConfigMgr is client initiated in ConfigMgr (remote control, client push, and WoL -- as just mentioned -- are sort of exceptions to this but they don't really involve the client *agent*.)
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • SCOM 2012 Cross forest deployment

    Hi all,
    Is two way trust is mandatory to deploy cross forest scom 2012 if we user certificate also ?
    Thanks,
    Sengottuvel M

    Monitoring across non- trust domain
    1) two way trust between domains OR
    2) using certificate
    Roger

  • Deploying SCOM 2012 Agents to untrusted Forests/Domain

    Can we deploy SCOM 2012 agents to untrusted forest/domain? I don't want to use SCCM 2012 for installing agents via package deployment. Pls suggest.
    Regards,
    Ravi

    Yes, You can deploy SCOM Agent to untrusted domain manually and using Certificate.
    For deployment scom Agent, you can refer below links
    http://www.toolzz.com/?p=279
    http://jimmoldenhauer.blogspot.com/2012/11/scom-2012-deploying-agents-to-untrusted.html
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

Maybe you are looking for