OEM Deployment of Office 2013 on Offline System, Deployment Strategy

Hello,
Since Office 2010 is no longer offered by Microsoft we have been forced to go to Office 2013, however we are running into major problems with deployment. We configure systems for utilities (Power and Process) which generally are not connected to the internet.
So far we have run into a multitude of problems with deploying Office 2013 basically revolving around having to create an account with Microsoft for our customer and connect the machines to the internet. We have found that the MSDN image of Office Professional
Plus 2013 with an MSDN key will install correctly offline with the typical phone activation. So a few questions:
1) Does the product key determine if it needs to be activated online? For example: Is there a difference between the OEM / Retail / VL keys and or installers?
2) Can I use my MSDN installer with a retail license of Office Professional 2013? Or do I need to get the specific volume license?
3) Will there be MSDN installers for the other versions of Office such as the standalone Excel retail or Office Professional (OEM or Retail)?
3) Is there anyway to install Office 2013 and not activate it until it resides with the End Customer if you have a retail version?
4) Is there any offline method for installing or re-installing Office 2013 if you have a retail version?
5) Is there an OEM or VL version of standalone products available (such as Excel)?
Thanks

Hi,
Microsoft now no longer offers an Office 2010 download from their site, however, if you already have a product key of Office 2010, you can still get Office 2010 installation package from this website:
http://office.microsoft.com/en-us/products/microsoft-office-2010-backup-FX101853122.aspx.
Office OEM is a version of the Microsoft Application Suite sold with new computers. Office 2013 are available from Office 2013 suites and Office 365 subscription which is associated with the Microsoft account, when Office 2013 suites are activated by the
traditional method with a 25-character product key.
For the license issues, we suggest you to contact your local Microsoft customer support to get more information.
More reference about Office 2013 activation:
http://technet.microsoft.com/en-us/library/ee705504(v=office.15).aspx
http://office.microsoft.com/en-us/word-help/activate-office-2013-programs-HA102819770.aspx
Thanks,
Ethan Hua CHN
TechNet Community Support

Similar Messages

  • Office 2013 OEM & WSUS

    Hi All,
    Some
    similar threads out there regarding this however, this scenario is different to most.
    Our corporate network is running OEM versions of Office 2013 (Home Business & Professional versions).
    ALL of these installations are pulling updates (only for Office) direct from Microsoft, not from our WSUS servers.
    How on earth to i resolve this issue? As we begin to upgrade more and more of our staff to this version, the bandwidth required is going to become a problem eventually!
    There must be something right?
    Thanks,
    Nash

    Our corporate network is running OEM versions of Office 2013 (Home Business & Professional versions).
    Okay, first issue... there's no such edition as you've named. (Unless you've dropped a critical comma, and you actually meant "Home, Business, and Professional" editions -- but even then, this description is fatally anomalous!)
    There are three subscription editions and three non-subscription editions available:
    Subscription:
    Office 365 Home
    Office 365 Personal
    Office 365 University
    Non-subscription:
    Office Home & Student
    Office Home & Business
    Office Professional
    And only two of those six are licensed for use in a business setting, so are you saying you have Home & Business Edition, Professional Edition, or a combination of both?
    ALL of these installations are pulling updates (only for Office) direct from Microsoft, not from our WSUS servers.
    So, it's impossible for the non-subscription installations to pull updates from Microsoft if the client is properly configured as a WSUS client. Most PCs that ship with "OEM" installations of Office are shipping with *subscription* instances (and these may
    have come with the first year prepaid, for example).
    If they're CTR versions of O365 (read: Home, Personal, or University) they are
    always going to get updates direct from Microsoft, because that's how subscription editions are updated.
    How on earth to i resolve this issue?
    First step is to confirm that the client is actually a WSUS client.
    If it is, then the second step is to confirm the actual edition of Office that is installed on these systems. If they're subscription instances, and you have available licenses for Office Home & Business or Office Professional, then uninstall the OEM/CTR
    instance of O365, and install the one you want.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Windows 8.1 system with new Office 2013 install not pulling down any Office 2013 updates from my SCCM 2012 SP1 server

    Hi,
    I've just setup a new Windows 8.1 system and added to my SCCM 2012 SP1 server and all is good and it pulled down all the correct Windows updates and pulls down automatically the FEP updates that are distributed from SCCM 2012 daily. 
    I just installed Office 2013 on this system and have activated it as necessary.  The problem is that the system doesn't seem to be pulling down any of the Office 2013 updates that have distributed thru SCCM.  I have other systems with
    Office 2013 installed and they have pulled down Office 2013 updates in the past when I published them.
    If I look at the Office 2013 updates in the SCCM console software section, I can see that for example it shows that Office 2013 SP1 (x86) is needed by one system and installed on 8 other systems and shows as downloaded and deployed.
    I've restarted the new system multiple times and also tried to force a software update check from the Configuration Manager applet but nothing seems to happen.
    What can I check to try and determine what the problem is?
    Thanks in advance,
    Nick

    Yes, the 8.1 system is a member of collection where the update deployment is targeted.
    Are there any specific logs I should check in the client?  If I check the WindowsUpdate.log I can see messages about the machine pulling down the FEP updates but that's all it appears to be doing.
    in CCM\logs, focus on the updatehandler and updatedeployment, to begin with
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Deploying MS Office 2013 with GPO

    OK i would like to deploy office 2013 via GPO, i finally have been able to get the script to work however there is one more detail i need to get figured out.... How can i incorporate into the script so that it will only run once...  my script is below
    and does the following, it uninstalls office 2010 whether it be 32bit or 64bit then silently installs office 2013 as a startup GPO... how would the script look if i'd like to add so that it looks for a specific txt file that if its there it does nothing and
    if it's not it runs install script and perhaps at end of install script maybe it creates that txt file... I need help on the best way to just "RUNONCE"
    here is my script:
    "C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall ProPlus /config "\\****\Office13\Uni_Office_10\SilentUninstall.xml"
    "C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall ProPlus /config "\\****\Office13\Uni_Office_10\SilentUninstall.xml"
    setlocal
    REM ********************************************************************
    REM Environment customization begins here. Modify variables below.
    REM ********************************************************************
    REM Get ProductName from the Office product's core Setup.xml file, and then add "office15." as a prefix.
    set ProductName=Office15.PROPLUS
    REM Set DeployServer to a network-accessible location containing the Office source files.
    set DeployServer=\\****\Office13
    REM Set ConfigFile to the configuration file to be used for deployment (required)
    set ConfigFile=\\****\Office13\ProPlus.WW\config.xml
    REM Set LogLocation to a central directory to collect log files.
    set LogLocation=\\****\Office13\LogFiles
    REM ********************************************************************
    REM Deployment code begins here. Do not modify anything below this line.
    REM ********************************************************************
    IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)
    REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
    :ARP64
    reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall%ProductName%
    if NOT %errorlevel%==1 (goto End)
    REM Check for 32 and 64 bit versions of Office 2010 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS)
    :ARP86
    reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall%ProductName%
    if %errorlevel%==1 (goto DeployOffice) else (goto End)
    REM If 1 returned, the product was not found. Run setup here.
    :DeployOffice
    echo %date% %time% %ComputerName% "Has Run the install Process" >> %LogLocation%\HasRunInstall.txt
    start /wait %DeployServer%\setup.exe /config %ConfigFile%
    echo %date% %time% %computername% Setup ended with error code %errorlevel%. >> %LogLocation%\FinishedInstall.txt
    REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
    :End
    Endlocal

    The problem with Office 2010 and later is that it is not designed to be installed remotely or by a script. You need to create an install spec and set up some prerequisites fist.  If you ten follow the instructions for using a GPO to deploy Office
    you will not need to  use a "RunOnce" key or anything else.
    Note that eh RunOnce key take a command or batch and command and is deleted as soon as it is executed.  The problem you have to solve is how to set the RunOnce key to begin with.
    You really must use the information in the links posted for Office deployment.  You cannot do an end run around this with any success.  If you search for forum posts on this you will see that many have been exactly where you are.  Don't wast
    your time.  Follow the instructions as posted in the Office forum and on the TechNet link.  YOu will find it is actually quite easy and very flexible once you understand the steps.
    \_(ツ)_/

  • WSUS updates not applying to Office 2013 Home and Business OEM version

    Hi
    For some reason I cannot get WSUS updates to automatically install on clients running Office 2013 Home and Business OEM version.
    For example
    If user opens any of the office 2013 apps e.g. Outlook , word etc, it prompts a message at the top under the ribbon toolbar; UPDATE NOW.
    All other updates for OS are downloading and installing just fine from our WSUS server.
    What could this be?
    I dont have this issue with clients running office 2003

    First thing you need to do is be absolutely certain which edition of Office you have installed.
    There are five editions of "Office 365" and these days, almost anything that is "OEM" is almost certainly Office 365:
    Office 365 Home
    Office 365 Personal
    Office 365 Small Business
    Office 365 Small Business Premium
    Office 365 Midsize Business
    Office 365 ships with an activation code for an online management account, and authorizes the installation of the software on up to five devices. Office 365 is updated via the WEB .. ONLY.
    In addition there are three editions of Office 2013:
    Office Home & Student
    Office Home & Business
    Office Professional
    If you have one of these three editions, you should also have a DVD and a Product Activation Code for the SINGLE-PC installation which is licensed for these editions provided by the vendor of your computers. Office 2013 can be updated using WSUS.
    Since you're getting a prompt IN THE APPLICATION to "Update Now", I believe you're looking at instances of Office 365, not Office 2013. Office 2013 (desktop) does not provide in-product prompts for updates/upgrades.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Office 2010 deployment - Bypass/Skip if Office 2013 present

    We have predominantly Office 2007 installed thought out environment and I now have a working Office 2010 app deployment package. Now I am finding that we have a few systems that already have Office 2013 and I'd like to bypass any system that already has
    2013 installed. Currently my 2010 package is installing side by side with 2013 and has resulted in Office being corrupted. I have not been able to find a way to detect Office 2013 and bypass/skip installation. Please help. Thank you in advance.

    Hi,
    You could simply use a Collection query and exclude all devices from the Office 2013 collection that already has Office 2010 installed.. If you deploy it it devices and not users that is..
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • Office 2013 ODT The operating system is not presently configured to run this application

    hi!
    We have RDS 2012 R2 setup up and running with session host, connection broker, rd gateway and rd web. AS office 2013 can be deployed using APP-V 5 SP2, we have created .appv pkg using ODT as mentioned in this
    guide . It was working fine for 2 days and then suddenly we started to get error popup window saying
    "The operating system is not presently configured to run this application" . We are receiving this error on Session host server(win 2k12 r2) which is App-V 5 sp2 client, when we try to open any office 2013 app.
    And If check on App-v server which is also a publishing server. In event viewer i see this log entry.
    Log Name:      Microsoft-AppV-Server-Publishing/Admin
    Source:        Microsoft-AppV-Server-Publishing
    Event ID:      215
    Level:         Error
    Description:
    The request URL doesn't contain the query string for the client OS.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-AppV-Server-Publishing" Guid="{825C7963-9E32-4E3B-B74A-DF2CC3B6822B}" />
        <Execution ProcessID="3092" ThreadID="5176" />
        <Channel>Microsoft-AppV-Server-Publishing/Admin</Channel>
     </Event>
    SaM

    We have the same issue. All other applications seem to work fine.
    App-V 5.0 SP1 with hotfix package 2 installed on the App-V Management/Publishing server. We only use Windows Server 2012 RDS instead of R2. On the RDS servers, App-V 5.0 SP2 is installed. We use User Profile Disks and also used the ODT for Office
    2013.
    I our case it worked for a few hours. We didn't change anything (no updates of other things) other than having a few users try to login with different accounts to test the application. Reinstalling the client doesn't work and we also tried to removed
    all AppVClientPackages and then clear the cache from locations like:
    %LOCALAPPDATA%\Microsoft\AppV\Client\VFS
    %APPDATA%\Microsoft\AppV\Client\VFS
    C:\ProgramData\App-V
    I'll post a solution if I find one.

  • Deploying Office 2013 with Group Policy

    I would like to deploy Office 2013 using group policy. I am new to group policy so am looking for some advice and guidance on the best way to deploy. I would like to deploy with no interaction with the user but yet display a message so that they
    know not to open Office. I would also like to create a custom registry setting so that if I need to re-install, all I have to do is delete the registry setting. I have tried a group policy for installing with OCT  settings (Basic, Suppress
    Model checked, No Cancel checked, Completion Notice checked) and modifying the Config.xml (<Display Level="Basic" CompletionNotice="yes" SuppressModal="yes" AcceptEula="yes" />) but I can not get it to display
    the installer screen so that users know it is installing. It does display the screen when running the setup.exe manually. I have a setting in the OCT that creates the registry setting and that is working correctly. My group policy is set to run the
    below bat file at startup in the Computer Configuration.
    setlocal
    REM *********************************************************************
    REM Environment customization begins here. Modify variables below.
    REM *********************************************************************
    REM Get ProductName from the Office product's core Setup.xml file, and then add "office15." as a prefix.
    set ProductName=Office15.Standard
    REM Set DeployServer to a network-accessible location containing the Office source files.
    set DeployServer="\\xxxxxx\setup.exe"
    REM Set LogLocation to a central directory to collect log files.
    set LogLocation=\\xxxxx\Logfiles
    REM *********************************************************************
    REM Deployment code begins here. Do not modify anything below this line.
    REM *********************************************************************
    IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)
    REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
    :ARP64
    reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
    if NOT %errorlevel%==1 (goto End)
    REM Check for 32 and 64 bit versions of Office 2013 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS)
    :ARP86
    reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
    if %errorlevel%==1 (goto Office) else (goto End)
    REM If 1 returned, the product was not found. Run setup here.
    :Office
    %DeployServer%
    echo %date% %time% Setup ended with error code %errorlevel%. &gt;&gt; %LogLocation%\%computername%.txt
    REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
    :End
    Endlocal
    Any advice or guidance would be greatly appreciate on how to get a pop up message while software is installing or if there is a better way to deploy.

    > but I can not get it to display the installer screen so that users know
    > it is installing. It does display the screen when running the setup.exe
    > manually. I have a setting in the OCT that creates the registry setting
    > and that is working correctly. My group policy is set to run the
    > below bat file at startup in the Computer Configuration.
    Check http://gpsearch.azurewebsites.net/#2308 - if this is enabled, you
    will not be able to show "anything" in startup scripts...
    Martin
    Mal ein
    GUTES Buch über GPOs lesen?
    NO THEY ARE NOT EVIL, if you know what you are doing:
    Good or bad GPOs?
    And if IT bothers me - coke bottle design refreshment :))

  • "Combine supported files in Acrobat" right-click funtion is slow or locks up system since upgrade to Office 2013

    I have several admins who have for years combined quantities of large Word documents into a single PDF by highlighting them, right-clicking, and selecting "Combine supported files in Acrobat."  Until recently, they were all using Office 2010 Pro Plus and a variety of versions of Acrobat - Standard 9, Professional 9, Standard 10.  They said it was quick and painless.  We've recently deployed Office 2013 Pro Plus, and they are complaining that doing the same thing they've always done is either completing but yeilding only the first document in the resulting PDF or rendering their systems unresponsive.  I have reproduced their issues and have found some evidence online of Possible incompatibilities between Office programs and the Adobe Acrobat PDFMaker Office COM Addin add-in, however Adobe's list of Compatible web browsers and PDFMaker applications indicates that Office 2013 supports PDFMaker versions as old as Acrobat 6, and we are not that outdated.  Any suggestions?  This is crippling their productivity.
    Thanks!
    Carrie

    Only the updated Acrobat XI supports Office 2013. The updates are necessary to address the changes to OFFICE introduced after Acrobat XI was released (OFFICE 2013 is more recent than the original AA XI release). No other versions of Acrobat can be used with OFFICE 2013 other than printing to the Adobe PDF printer.

  • How to install Office 365 Pro Plus Ms office 2013 Offline through MDT Task Sequence

    Hi 
    How can i deploy the Office 365 pro Plus Ms Office 2013 (that come with Office 365 E3 License) offline to Client Machines through MDT Task Sequence?
    Shailendra Dev

    There is a wealth of information on Office 365 deployments at:
    http://technet.microsoft.com/en-us/library/gg715562(v=office.15).aspx
    Overview:
    Download the office deployment tool
    configure your config.xml file
    download the bits locally to your server.
    create a package for MDT.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Deploy Office 2013 with language pack

    Hi,
    We want to deploy Office 2013, for this I followed the tutorial:
    http://gallery.technet.microsoft.com/office/How-to-Deploying-Office-0f954e7f
    In the first step I need to make an MSP file, but this file doesn't get used in the deployment? I think this is a fault in the tutorial.
    Also the uninstall string is setuP.exe /uninstall. Is this correct?
    Second we want to deploy the dutch language pack with SCCM 2012, but I can't find out how. The package need to be installed but Office 2013 still need to be default language English.
    Can someone help me out with this?
    Thanks in advance.

    Some troubleshooting tips:
    Run the installation command locally using SYSTEM account (Get psexec.exe, open cmd, run "psexec.exe -s cmd", this will open a new command line window with SYSTEM privilege, try running your installation command there)
    Check the Office 2013 installation logfiles to see if your configurations are correct, more info on that here:
    http://blogs.technet.com/b/odsupport/archive/2010/12/30/troubleshooting-office-installation-failures.aspx
    After those two steps are ready and you're sure your installation command works, you try it with ConfigMgr
    With ConfigMgr, check %windir%\ccm\logs\ -folder for AppEval.log, AppEnforce.log and AppDiscovery.log, more info on these logfiles you can find here:
    http://blogs.technet.com/b/configmgrdogs/archive/2012/05/26/new-logs-in-configmgr-2012-client-logs.aspx

  • Office 2013 - Word cannot establish a connection with this document after the system resumed from suspend mode

    Hiya!
    This issue has been answered numerous times for Office 2010 and Office 2007, but I have yet to any solutions or Hotfixes that work for Office 2013 (x64) on Win7.
    How to replicate the issue:
    Open a file from a network share.
    Edit file.
    Leave computer on with file open. Computer goes to sleep or into stand-by mode.
    Wait a bit
    Wake up computer
    CPU opens file in Read-Only mode and gives you the following error "Word cannot establish a network connection with this document after the system resumed from suspend mode. Save the document into a different file to keep any changes."
    What I've tried:
    http://support.microsoft.com/kb/2434898 - Office 2007 registry fixes. Does not apply.
    http://support.microsoft.com/kb/2413659 - Office 2010 problem. This exact issue. Says 'No microsoft products that match this hotfix are installed'
    Work Around:
    I can saving new versions of these files overrides this issue, but this is sometimes not possible for end-users who only have specific access to ONE SPECIFIC FILE in a particular network share.
    Please let me know how I can alleviate this issue!
    Thanks
    -Chris

    Hi,
    Are those problematic documents created via previous versions of Office?
    Please also try to run a repair of your Office 2013 installtion and check if it helps. See:
    http://office.microsoft.com/en-in/excel-help/repair-office-programs-HA010357402.aspx
    Regards,
    Steve Fan
    TechNet Community Support

  • Office 2013 OEM and Office Home & Business 2013 registration

    Hi to all,
    in our company we brought some Office 2013 OEM licenses and 1 Home and Business 2013. The problem is that i have registered the OEMs with my personal Microsoft account and now i need to register the Home and Business and i want to avoid to register it with
    this. Then, my questions are:
    1. What is the procedure to register a Microsoft company account.
    2. Is there the possibility to move OEM license from my personal account to a the company account ?
    Thank you.

    Hi,
    I noticed that the questions were about licensing rather than Office client issues, please understand we discuss questions and feedbacks about Office client in this forum, we are not familiar with the procedure/migration you mentioned.
    To help you get the best resource upon this topic, I suggest you contact your local customer service to get more appropriate assistance:
    http://support.microsoft.com/gp/customer-service-phone-numbers/en-us
    Regards,
    Melon Chen
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Office 2013 Home and Business OEM First Run screen

    Hi There
    We are starting to roll out office 2013 oem Home and Business our users are reporting that the first run screen get coming up every time there open an office application.
    In Group Policy I've disable the First Run Movie and Office First run on application boot however the users are still getting to first run screen this is every annoying.
    Any help with would be great?
    Cheers,
    Brett

    The policy setting should work: it correctly adds bootedrtm=1 value to HKCU\Software\Policies\Microsoft\office\15.0\firstrun. But for some reason Office apps ignore it. I tried disabling the entire policy, then go through the welcome screen. After finishing
    with it, office created the same value, but in another place (HKCU\Software\Microsoft\Office\15.0\FirstRun), and the screen never appeared anymore.
    So to make the setting work, you have to manually create registry setting (via GPO preference) with the following data:.
    [HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\FirstRun]
    "BootedRTM"=dword:00000001
    P.S. this was pretty easy, but did anyone look at disabling the EULA prompt? The acceptance is marked by creating a registry key for each user, but the path contains computer name :)) Therefore if all users of the PC have accepted the agreement, and you
    renamed the computer, the popup comes back again. And of course group policy is impossible with such path.

  • SCCM 2012: Office 2013 click to run deploy?

    Hi,
    We would like to run Office 2013 next to Office 2010. Therefore the click-to-run option (app-v is only possible for Office 2013 ProPlus) looks the way to go.
    I found a nice guide a Office 2013 Plus “Click to run” Deploy in SCCM:
    http://www.peters.com/Blogs/Lists/Posts/Post.aspx?ID=90 However (posted it also on the site), can I use the /admin to generate the configuration.xml instead and use it within SCCM 2012 deploy?
    J
    Jan Hoedt

    No. Click-to-run does not use the traditional Office setup methodology and thus does not have the same configuration options. More info at
    http://technet.microsoft.com/en-us/library/jj219420(v=office.15).aspx
    Jason | http://blog.configmgrftw.com | @jasonsandys

Maybe you are looking for